[krita] [Bug 358146] Window size and position are not saved
https://bugs.kde.org/show_bug.cgi?id=358146 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361566] Panel auto-hide is completely broken
https://bugs.kde.org/show_bug.cgi?id=361566 ro...@i.ua changed: What|Removed |Added CC||ro...@i.ua --- Comment #1 from ro...@i.ua --- Confirm, the same for me. Linux 4.5.0-2-MANJARO #1 SMP PREEMPT Wed Mar 16 04:25:52 CET 2016 x86_64 GNU/Linux plasma-workspace 5.6.1-1 -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 361602] strange behaviour on switching desktops with non-KDE5 applications
https://bugs.kde.org/show_bug.cgi?id=361602 Thomas Lübking changed: What|Removed |Added CC||cf...@kde.org --- Comment #1 from Thomas Lübking --- *Might* be https://git.reviewboard.kde.org/r/127153/ but if there's no (active) window on the current desktop (because the splash doesn't activate or is just gone on the spot) when the "runner" calls (back) focus, that request will still be honored. I can't test or inspect the behavior, though. @Christoph I'm only providing phase-out support, but am no longer using KDE (or Qt, for that matter) so please don't rely on me. I'll oc. fix bugs in my styles etc., but that's it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #17 from Enrico Tagliavini --- Maybe that's a fluke but it seems like this happens only in some specific, albeit common, configuration. In my case I move my laptop between two desks. One has a 1080p monitor (exactly the same resolution as the laptop screen), the other has a 1680x1050 monitor. I get the black screen after login only with the former one. The latter works as expected. Anybody with this problem and two monitors of different resolutions by any chance? However, oddly enough, for my colleague desktop (note: not a laptop), where he has two monitors of the same resolution, everything works fine. However, being a desktop, he never connect or disconnect monitors which might be related (see bug #353052). This all is on Fedora 22 and 23, fully up to date. Currently using plasma 5.5.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355886] Brush preset choice from quick menu not affecting the choice in docker and the other way around (issue of one preset always active in chosen tag)
https://bugs.kde.org/show_bug.cgi?id=355886 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #7 from Boudewijn Rempt --- Let's confirm then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355865] Blur filter does not support wrap around
https://bugs.kde.org/show_bug.cgi?id=355865 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt --- Thanks for testing! Let's close the bug then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355773] Duplicating Artistic Text will remove multiple spaces
https://bugs.kde.org/show_bug.cgi?id=355773 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Boudewijn Rempt --- Thanks for testing. This probably is because we save the text as xml which strips double spaces. The text tools need rewriting any case. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352422] The outline selection tool (lasso tool) is very pixelated, anti-aliasing doesn't work.
https://bugs.kde.org/show_bug.cgi?id=352422 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Boudewijn Rempt --- Thanks for testing! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro
https://bugs.kde.org/show_bug.cgi?id=342105 --- Comment #25 from Boudewijn Rempt --- The problem is in the huion drivers. To quote from a mail we sent to the Huion people" "The biggest problem we have with Huion tablets at the moment is that it doesn't implement CSR_SYSBTNMAP (part of WTInfo function) [0]. That is really a problem. This function of Wintab is supposed to tell the application how the user configured the stylus buttons, which one is "right button", which one is "middle button". Huion driver has this configuration in the driver, but it doesn't expose this info in the Wintab interface. It uses button mapping only for the synthesized mouse events, but not in the Wintab packets. " -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361617] kmail is causing system instability
https://bugs.kde.org/show_bug.cgi?id=361617 Thomas Lübking changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Component|general |effects-window-management --- Comment #2 from Thomas Lübking --- tempList.count() will be 0, so the "index % tempList.count()" segfaults. The problem will be that there're > 1 windows (kmail?) when invoking the tabbox, then kmail crashes and the list turns empty when painting happens. The entire paint routine of the effect (and likely coverswitch?) isn't hard against that => exit early when tempList.isEmpty() -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361587] git master 2016-04-10 - Screen Grab crashes
https://bugs.kde.org/show_bug.cgi?id=361587 Evert Vorster changed: What|Removed |Added Resolution|REMIND |FIXED --- Comment #7 from Evert Vorster --- Why did you apply the fix to Applications/16.04 instead of master? It's a pain to build a different branch than master. :P Thanks for the fix, though. Kind regards, Evert -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361617] kmail is causing system instability
https://bugs.kde.org/show_bug.cgi?id=361617 --- Comment #1 from Martin Gräßlin --- you used alt+Tab when it crashed, right? -- 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 #2 from Martin Gräßlin --- The window only shows if you have alt pressed for more than 90 msec. So if you do a quick alt+Tab the window is not supposed to show. Is that maybe the case for you? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #18 from Martin Gräßlin --- (In reply to wolfyrion from comment #17) > So do we know if this is an NVIDIA driver problem or Plasma 5? I can disable/enable compositing on my Intel system without any problems. It doesn't mean that it's not a problem in our stack, but it makes it look more like an NVIDIA problem - especially if one considers the amount of changes in that driver lately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361572] desktop cube setting ignored
https://bugs.kde.org/show_bug.cgi?id=361572 --- Comment #3 from Martin Gräßlin --- (In reply to illumilore from comment #2) > Compositing > === > Compositing is active > Compositing Type: XRender You are using the XRender compositor which doesn't support the Cube effect. If you did not manually change to XRender it might be that you don't have an OpenGL driver installed. Best check with glxinfo (feel free to attach here) which driver is installed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 361462] KLauncher crash in xcb_disconnect()
https://bugs.kde.org/show_bug.cgi?id=361462 --- Comment #1 from Martin Gräßlin --- Could you please provide some information on what you did to get this crash? -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 356999] HTML formatting on incoming messages not being processed
https://bugs.kde.org/show_bug.cgi?id=356999 Aranjedeath changed: What|Removed |Added Flags||kpeople+ --- Comment #3 from Aranjedeath --- I hate double-posting but none of the bug information is right (as far as platforms). I'm running the latest version in Kubuntu 16.04 (it's in beta or whatever right now), which means "Chat Application" 15.12.1, Kde Frameworks 5.18, Qt 5.5.1. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 356999] HTML formatting on incoming messages not being processed
https://bugs.kde.org/show_bug.cgi?id=356999 Aranjedeath changed: What|Removed |Added CC||orangewi...@gmail.com --- Comment #2 from Aranjedeath --- I can confirm this as well. A friend uses pidgin, and everything he sends comes through as escaped HTML. ampersands are & and the like. If he pastes something that has formatting, it keeps the formatting (in HTML), a la
[krita] [Bug 360541] Low resolution canvas on Surface Pro 4 with OpenGL turned off
https://bugs.kde.org/show_bug.cgi?id=360541 --- Comment #10 from ramskulls...@gmail.com --- Image fields are also squashed for me. Can confirm changing icon size just spaces them apart, for sizes larger than 16x16. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361617] New: kmail is causing system instability
https://bugs.kde.org/show_bug.cgi?id=361617 Bug ID: 361617 Summary: kmail is causing system instability Product: kwin Version: 5.6.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: a...@dymitruk.com Application: kwin_x11 (5.6.2) Qt Version: 5.5.1 Frameworks Version: 5.21.0 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: KDE neon on 15.10 -- Information about the crash: - What I was doing when the application crashed: trying to configure kmail for a few gmail accounts - Unusual behavior I noticed: dialog of some error popped up for a brief instant and dissappeared. Couldn't use krunner as it was exited by dialog before I could choose anything The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Floating point exception Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2500570840 (LWP 1362))] Thread 4 (Thread 0x7f24e8f43700 (LWP 1378)): #0 0x7f250005288d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f24fe131bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f24fe13374f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f24e97e3a49 in QXcbEventReader::run (this=0x1d05ec0) at qxcbconnection.cpp:1230 #4 0x7f24fe3eea6e in QThreadPrivate::start (arg=0x1d05ec0) at thread/qthread_unix.cpp:331 #5 0x7f24ff6476aa in start_thread (arg=0x7f24e8f43700) at pthread_create.c:333 #6 0x7f250005de9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f24e18e5700 (LWP 1409)): #0 0x7f24fe6237b6 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f24d40008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:184 #1 0x7f24fe623b9e in QEventDispatcherUNIX::processEvents (this=0x7f24d40008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #2 0x7f24fe5cd50a in QEventLoop::exec (this=this@entry=0x7f24e18e4d60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #3 0x7f24fe3e9ac4 in QThread::exec (this=) at thread/qthread.cpp:503 #4 0x7f24f8cee105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7f24fe3eea6e in QThreadPrivate::start (arg=0x1f17630) at thread/qthread_unix.cpp:331 #6 0x7f24ff6476aa in start_thread (arg=0x7f24e18e5700) at pthread_create.c:333 #7 0x7f250005de9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f24d9910700 (LWP 1415)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f24fd573194 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f24fd5731d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f24ff6476aa in start_thread (arg=0x7f24d9910700) at pthread_create.c:333 #4 0x7f250005de9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f2500570840 (LWP 1362)): [KCrash Handler] #6 0x7f24fd6d449d in KWin::FlipSwitchEffect::paintScreen (this=this@entry=0x26ff720, region=..., data=..., mask=) at ../../effects/flipswitch/flipswitch.cpp:148 #7 0x7f24fd6d59fb in KWin::FlipSwitchEffect::paintScreen (this=this@entry=0x26ff720, mask=mask@entry=32, region=..., data=...) at ../../effects/flipswitch/flipswitch.cpp:121 #8 0x7f24ffc1a50a in KWin::EffectsHandlerImpl::paintScreen (this=0x26a62e0, mask=32, region=..., data=...) at ../effects.cpp:420 #9 0x7f24ffbf1479 in KWin::Scene::paintScreen (this=this@entry=0x20b8b60, mask=mask@entry=0x7ffe8ff046b0, damage=..., repaint=..., updateRegion=updateRegion@entry=0x7ffe8ff04680, validRegion=validRegion@entry=0x7ffe8ff04690, projection=...) at ../scene.cpp:150 #10 0x7f24ffc088a9 in KWin::SceneOpenGL::paint (this=0x20b8b60, damage=..., toplevels=...) at ../scene_opengl.cpp:751 #11 0x7f24ffbe4789 in KWin::Compositor::performCompositing (this=0x1dda6b0) at ../composite.cpp:726 #12 0x7f24fe5ff753 in QObject::event (this=0x1dda6b0, e=) at kernel/qobject.cpp:1261 #13 0x7f24feec49dc in QApplicationPrivate::notify_helper (this=this@entry=0x1cfc400, receiver=receiver@entry=0x1dda6b0, e=e@entry=0x7ffe8ff04b10) at kernel/qapplication.cpp:3716 #14 0x7f24feec9ea6 in QApplication::notify (this=0x7ffe8ff04d70, receiver=0x1dda6b0, e=0x7ffe8ff04b10) at kernel/qapplication.cpp:3499 #15 0x7f24fe5cfd7b in QCoreApplication::notifyInternal (this=0x7ffe8ff04d70, receiver=0x1dda6b0, event=event@entry=0x7ffe8ff04b10) at kernel/qcoreapplication.cpp:965 #16 0x7f24fe6252fd in QCoreApplication::sendEvent (event=0x7ffe8ff04b10, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #17 QTime
[kscreenlocker] [Bug 360396] kscreenlocker-greet ignores KB and Mouse after screen energy saving activates
https://bugs.kde.org/show_bug.cgi?id=360396 --- Comment #23 from PhillB --- The old kscreenlocker_greet binary is still working well here. No lockups so far with the latest xorg-x11-drv-intel-2.99.917-19.20151206.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are receiving this mail because: You are watching all bug changes.
[sweeper] [Bug 361482] Though the sweeper shows cleaned up, the cleaning wasn't successful
https://bugs.kde.org/show_bug.cgi?id=361482 --- Comment #5 from Srinivas --- Though "sweeper" shows cleanup has finished, the following things have not be cleaned. I also installed "bleachbit" and tried to clean. I have similar issue. The system hasn't been cleaned. Thanks for all your help. Saved Clipboard Contents... Recent Documents... Run Command History... Recent Applications... Thumbnail Cache... Cookies... Favorite Icons... Web History... Web Cache... Form Completion Entries... Cookie Policies... From: Burkhard Lueck via KDE Bugzilla Sent: Friday, April 8, 2016 9:54 AM To: srinivas.chan...@live.com Subject: [sweeper] [Bug 361482] Though the sweeper shows cleaned up, the cleaning wasn't successful https://bugs.kde.org/show_bug.cgi?id=361482 --- Comment #4 from Burkhard Lueck --- $ sweeper --version Qt: 4.8.6 KDE: 4.14.8 Sweeper: 1.9 The only error message I see here is Clearing of Run Command History failed and apparently a lot of data has gone Which of these items is not cleared for you? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361572] desktop cube setting ignored
https://bugs.kde.org/show_bug.cgi?id=361572 --- Comment #2 from illumilore --- $ qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.5.5 Qt Version: 5.5.1 Qt compile version: 5.5.1 XCB compile version: 1.11.1 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: 11702000 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.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 3, 4, 5 borderSize: 3 gridUnit: 12 font: Droid Sans,10,-1,5,50,0,0,0,0,0 smallSpacing: 3 largeSpacing: 12 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 1 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 showGeometryTip: false condensedTitle: false electricBorderMaximize: false electricBorderTiling: false electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 2 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 1 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 97 glPlatformInterface: 1 Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 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: HDMI-0 Geometry: 0,0,1920x1080 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: XRender Loaded Effects: --- zoom dimscreen slidingpopups kwin4_effect_login screenshot minimizeanimation kwin4_effect_windowaperture kwin4_effect_translucency kwin4_effect_scalein desktopgrid kwin4_effect_maximize kwin4_effect_fade presentwindows highlightwindow kwin4_effect_dialogparent logout screenedge kscreen Currently Active Effects: - Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 dimscreen: slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: screenshot: minimizeanimation: kwin4_effect_windowaperture: kwin4_effect_translucency: kwin4_effect_scalein: desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true kwin4_effect_maximize: kwin4_effect_fade: presentwindows: layoutMode: 0 showCaptions: true showIcons: true doNotCloseWindows: false ignoreMinimized: false accuracy: 20 fillGaps: true fadeDuration: 150 showPanel: false leftButtonWindow: 1 rightButtonWindow: 2 middleButtonWindow: 0 leftButtonDesktop: 2 middleButtonDesktop: 0 rightButtonDesktop: 0 highlightwindow: kwin4_effect_dialogparent: logout: useBlur: true screenedge: kscreen: -- You are receiving this mail because: You are watching all bug chan
[kcalc] [Bug 361594] kcalc 16.03.90 window does not come up, process hangs
https://bugs.kde.org/show_bug.cgi?id=361594 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 360105 *** -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 Christoph Feck changed: What|Removed |Added CC||andreas.eckst...@gmx.net --- Comment #12 from Christoph Feck --- *** Bug 361594 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361616] New: cannot preview edited video files
https://bugs.kde.org/show_bug.cgi?id=361616 Bug ID: 361616 Summary: cannot preview edited video files Product: kdenlive Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@kyletravers.com I am unable to preview the edits. The video cursor bar does not move and I can not play previews of my edits. Not sure why. Please help. Reproducible: Always Steps to Reproduce: 1. Place several clips in the timeline 2. Attempt to play timeline 3. Cannot play edits Actual Results: nothing Expected Results: Should play a preview from where you click on the timeline -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 361602] strange behaviour on switching desktops with non-KDE5 applications
https://bugs.kde.org/show_bug.cgi?id=361602 Christoph Feck changed: What|Removed |Added CC||thomas.luebk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 Billy W changed: What|Removed |Added CC||spacedevi...@gmail.com --- Comment #6 from Billy W --- Im having some issues with saving brushes as well. I make a new file save it go to alter it and overwrite it.. this creates a new file and not always overwrites the intended file.. this results in several saves in the brush catalog.. so it gets messy. I can confirm that the toolbar customize window is broken since there is now movable options in the window. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 339890] Right-click on file crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=339890 wavemotion...@yahoo.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #7 from wavemotion...@yahoo.com --- My apologies for letting this languish so long. Your suggestion fixed my issue, and again I'm sorry for not coming back to update the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360815] System Load Viewer displays 0 every 3 seconds
https://bugs.kde.org/show_bug.cgi?id=360815 Martin Klapetek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361357] git master - issues with new Clip Properties Widget
https://bugs.kde.org/show_bug.cgi?id=361357 --- Comment #6 from Jesse --- Sweet, Farid! Also, JB, it looks like #4 in the OP was addressed and implemented. Thanks for that! However, there is still an issue: when the Clip Properties widget and the Project Bin widget are grouped together, double-clicking a clip in the Project Bin still makes the Clip Properties widget close/disappear and open/re-appear. When the Clip Properties widget is on its own in the layout or is grouped to a different set of widgets, this issue isn't present. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Lasse Liehu changed: What|Removed |Added CC||lasse.li...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361612] gtk3 Breeze theme contains lots of deprecation errors
https://bugs.kde.org/show_bug.cgi?id=361612 Lasse Liehu changed: What|Removed |Added CC||lasse.li...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 --- Comment #5 from wolthera --- It's really weird, because it was all working fine about two weeks ago or so? Definitely working fine at the start of march. Input settings aren't affected, btw. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 wolthera changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||griffinval...@gmail.com --- Comment #4 from wolthera --- yeah, couldn't get anything work here either. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 Lukasz changed: What|Removed |Added CC||dolo...@outlook.com --- Comment #7 from Lukasz --- Possibly related to Bug 358765 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #1 from earl_c...@yahoo.com --- Created attachment 98326 --> https://bugs.kde.org/attachment.cgi?id=98326&action=edit Candidate patch to propagate termination signal Here is an attempt to propagate the signal that terminates a thread into the entire program. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] New: Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615
Bug ID: 361615
Summary: Inconsistent termination when an instrumented
multithreaded process is terminated by signal
Product: valgrind
Version: 3.11 SVN
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: earl_c...@yahoo.com
The valgrind code attempts to terminate the program in a way that is consistent
with the disposition of a signal that is not handled by the instrumented
program. Unfortunately, the results depend upon whether the unhandled signal is
received by the main thread, or another thread.
Reproducible: Always
Steps to Reproduce:
Running the following test script (which compiles and runs the test program)
illustrates the problem:
---
#!/bin/sh
test()
{
rm -f foo.pid
"$@" > foo.pid 2>/dev/null &
PID=$!
while [ "$(wc -l < foo.pid)" -lt 2 ] ; do
sleep 1
done
head -1 foo.pid
kill $(tail -1 foo.pid)
wait $PID
echo $?
}
gcc -o foo foo.c -lpthread
echo Plain
test ./foo
test ./foo x
echo ''
valgrind --version
test valgrind ./foo
test valgrind ./foo x
echo ''
valgrind/bin/valgrind --version
test valgrind/bin/valgrind ./foo
test valgrind/bin/valgrind ./foo x
echo ''
---
#include
#include
#include
#include
void *
slavethread(void *arg)
{
while (1)
sleep(1);
}
int main(int argc, char **argv)
{
pthread_t slave;
if (argc > 1)
printf("unblocked\n");
else
{
if (pthread_create(&slave, 0, &slavethread, 0))
return 255;
sigset_t sigmask;
if (sigfillset(&sigmask))
return 255;
if (sigprocmask(SIG_BLOCK, &sigmask, 0))
return 255;
printf("blocked\n");
}
printf("%d\n", getpid());
fflush(stdout);
while (1)
sleep(1);
return 0;
}
Actual Results:
$ sh foo.sh
Plain
blocked
143
unblocked
143
valgrind-3.10.0.SVN
blocked
137
unblocked
143
valgrind-3.11.0
blocked
137
unblocked
143
Expected Results:
Ideally, all the test cases should show:
blocked
143
unblocked
143
In the absence of that, the exit codes between the blocked and unblocked cases
should be the same (and not show 137 in the blocked case, and 143 in the
unblocked case).
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 --- Comment #3 from Wayne Parker --- I can confirm this is definitely a problem. I can't save shortcuts, or brush preset changes. Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359127] Desktop theme KCM 'details' and editing tab no longer present/functional
https://bugs.kde.org/show_bug.cgi?id=359127 Wulf changed: What|Removed |Added CC||wulf.richa...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 344456] Plasma 5 desktop does not suspend with only upower, no systemd
https://bugs.kde.org/show_bug.cgi?id=344456 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 361526] krunner crashes when shortcut is pressed
https://bugs.kde.org/show_bug.cgi?id=361526 --- Comment #1 from mp3.1...@o2.pl --- Everything is fine after removing bumblebee and optirun. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 Nikola Schnelle changed: What|Removed |Added CC||n.schne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361537] libgit2 v0.23: Kate crashes on startup
https://bugs.kde.org/show_bug.cgi?id=361537 --- Comment #4 from Lukasz --- Created attachment 98325 --> https://bugs.kde.org/attachment.cgi?id=98325&action=edit test log Also during the compilation I ran tests and they failed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 Wayne Parker changed: What|Removed |Added CC||artmess...@live.com --- Comment #2 from Wayne Parker --- I can confirm this is definitely a problem. I can't save shortcuts, or brush preset changes. Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361537] libgit2 v0.23: Kate crashes on startup
https://bugs.kde.org/show_bug.cgi?id=361537 Lukasz changed: What|Removed |Added Attachment #98300|0 |1 is obsolete|| --- Comment #3 from Lukasz --- Created attachment 98324 --> https://bugs.kde.org/attachment.cgi?id=98324&action=edit stacktrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361614] New: Hidden visibility in system tray settings isn't remembered unless the entry is closed during the same session
https://bugs.kde.org/show_bug.cgi?id=361614 Bug ID: 361614 Summary: Hidden visibility in system tray settings isn't remembered unless the entry is closed during the same session Product: plasmashell Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: irli...@gmail.com The hidden visibility setting in the system tray settings window aren't saved unless the application represented by the entry is closed once during the session in which the changes have been made. Reproducible: Always Steps to Reproduce: 1. Toggle visibility to "Hidden" of entries in system tray settings 2. Logout 3. Login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361613] New: Dropbox icons disappears completely when entry is hidden
https://bugs.kde.org/show_bug.cgi?id=361613 Bug ID: 361613 Summary: Dropbox icons disappears completely when entry is hidden Product: plasmashell Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: irli...@gmail.com The Dropbox icon displays properly in the task manager widget (taskbar), however when it is explicitly hidden in the system tray settings and Dropbox subsequently restarted, the icon won't appear either in the task manager widget or in the "Status & Notifications" window which contains the explicitly hidden icons. I suspect this has to do with the fact that the Dropbox entry in the system tray settings doesn't have a proper name, it's just an icon without a title. Reproducible: Always Steps to Reproduce: 1. Install dropbox 3.16.1-1 https://aur.archlinux.org/packages/dropbox/ 2. Toggle Visibility of Dropbox entry in System Tray Settings -> Entries to Hidden 3. Close Dropbox 4. Start Dropbox Actual Results: Dropbox icon doesn't appear in the "Show hidden icons" window. Expected Results: The Dropbox icon should appear. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 358926] QFileIconProvider doesn't provide under Plasma 5
https://bugs.kde.org/show_bug.cgi?id=358926 --- Comment #6 from Diabolo --- I have found a momentary workaround, you can try first QMimeDatabase mimeDatabase; QFileInfo fileInfo ( fileName ); QMimeType mimeType = mimeDatabase.mimeTypeForFile( fileInfo ); and then it->setIcon ( 0, QIcon::fromTheme( mimeType.iconName() ) ); show the good icon. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361612] New: gtk3 Breeze theme contains lots of deprecation errors
https://bugs.kde.org/show_bug.cgi?id=361612 Bug ID: 361612 Summary: gtk3 Breeze theme contains lots of deprecation errors Product: Breeze Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: marius_...@yahoo.com I have the latest gtk3 theme from Breeze and when selected as the gtk3 theme ( I have gtk3 3.20.2 ) I get lots of errors about deprecated stuff : http://pastebin.com/Hbi04HYA This is for eclipse using gtk3. When it actually starts Eclipse looks very bad too and so does Meld. Selecting another theme fixes the problem. If the issues are indeed those mentioned and the fixes are relatively easy I'm willing to help with the fix but I'm no expert. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361611] New: Plugin 'Advanced Slide Show' - "Print Caption" does not work
https://bugs.kde.org/show_bug.cgi?id=361611 Bug ID: 361611 Summary: Plugin 'Advanced Slide Show' - "Print Caption" does not work Product: digikam Version: 4.14.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Presentation Assignee: digikam-de...@kde.org Reporter: richard@xs4all.nl The Plugin 'Advanced Slide Show' - "Print Caption" does not work. I use the plugin from Gwenview. Reproducible: Always Steps to Reproduce: 1. Start gwenview to start the kipi plugin AdvancedSlideShow ( Gwenview -> Plugins -> > > Tools -> AdvancedSlideShow ) 2. There is an option to enable 'print caption' 3. This should display EXIF information from the photo, when the slide show is running Actual Results: Nothing is displayed ( at least not the caption ). The file name and progress marker are displayed. Expected Results: The caption ( EXIF ) should be displayed. Some information from GIlles: Op zondag 10 april 2016 11:11:42 schreef u: > Hi, > > The print caption show image comment passed from kipi host to the plugin > by libkipi. > > the kipi interface is reimplemented in kipi host. Each kipi host pass the > right information to populate caption in plugin. > > In digiKam, if Exif comment exist, it populate the database and pass this > information through kipi interface if a plugin need it. > > In other word, the problem is in the kipi host re-implementation. > > Best > > Gilles Caulier 2016-04-10 11:49 GMT+02:00: Hi Gilles, thanks for your response. The EXIF information exists in Digikam, but it is not displayed. Now how do I report this bug? I'm ( very ) familair with the KDE bug tracking system, but in this particular case, which component do I select to report the error for? ps: can you confirm that you see the same problem perhaps it is something local in my installation... -- Richard Op zondag 10 april 2016 21:59:48 schreef u: > yes, problem is reproducible. > > Please report it to digiKam component of KDE bugzilla, into Presentation > section. > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 361610] New: “Server failed the authenticity check” not cancelable
https://bugs.kde.org/show_bug.cgi?id=361610 Bug ID: 361610 Summary: “Server failed the authenticity check” not cancelable Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: cdauth+bugs.kde@cdauth.eu CC: kdepim-b...@kde.org, vkra...@kde.org When connecting to an IMAP server whose certificate can not be authenticated, a popup comes up that contains the following message: “The server failed the authenticity check (testdomain.example.org). The certificate is not signed by any trusted certificate authority”. The message has the buttons “Details”, “Continue”, “Cancel”. When clicking Cancel, the message comes up immediately again. When ignoring the message, another message of the same type will come up every 30 seconds or so, stealing the focus, thus making the computer basically unusable without accepting the invalid certificate. When pressing Cancel, Akonadi should not attempt to reconnect to the server until restarted or until a connection is manually initiated (by clicking the “Check Mail” button in KMail for example). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348873] kwin crahed after waking up from suspend-to-RAM
https://bugs.kde.org/show_bug.cgi?id=348873 Thomas Lübking changed: What|Removed |Added CC||kysstf...@gmail.com --- Comment #8 from Thomas Lübking --- *** Bug 361609 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361609] kwin announced closure after entering a PlayOnLinux game - Diablo II LOD that would have been fullscreen, but left me in 800 x 600 desktop
https://bugs.kde.org/show_bug.cgi?id=361609 Thomas Lübking changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Lübking --- The resolution change is the problem. This largely looks like a bug in the nvidia driver when transferring memory between GPU & RAM (on randr events), but given the massive bug in QScreen, the driver could be only the messenger (and the problem fixed with Qt 5.6 - but I'd not bet on that) *** This bug has been marked as a duplicate of bug 348873 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361609] New: kwin announced closure after entering a PlayOnLinux game - Diablo II LOD that would have been fullscreen, but left me in 800 x 600 desktop
https://bugs.kde.org/show_bug.cgi?id=361609 Bug ID: 361609 Summary: kwin announced closure after entering a PlayOnLinux game - Diablo II LOD that would have been fullscreen, but left me in 800 x 600 desktop Product: kwin Version: 5.6.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kysstf...@gmail.com Application: kwin_x11 (5.6.1) Qt Version: 5.5.1 Frameworks Version: 5.20.0 Operating System: Linux 4.5.0-sabayon x86_64 Distribution: "Sabayon Linux amd64 16.04" -- Information about the crash: - What I was doing when the application crashed: Had launched POL Diablo II LOD and when I saw the low-res desktop I attempted to correct by switching to an open app of nvidia-settings to change back to hi-res for resolving. While I was investigating the failure to launch fullscreen (which has worked correctly for me recently but I have been having Plasma crashes with KDE in general also recently - the main reason that I now have some debug info & an account in case I ever can properly report that Plasmashell segfault), I noticed the icon in the systray for CRA & that's when I knew about the kwin crash). - Unusual behavior I noticed: Screen switched to 800 x 600 but I was left with not just a desktop but a desktop exhibiting the behavoir of KDE in midst of an Alt-Tab operation (which I had not done at that point although I did later to reach an existing open instance of nvidia-settings). -Distro: Sabayon The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fee51a1c880 (LWP 2406))] Thread 4 (Thread 0x7fee328e2700 (LWP 2411)): #0 0x7fee515165cd in poll () from /lib64/libc.so.6 #1 0x7fee4f71fc6a in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7fee4f7220cf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fee333cb559 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fee4f9dc893 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7fee50b1051c in start_thread () from /lib64/libpthread.so.0 #6 0x7fee515201ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fee2adee700 (LWP 2421)): #0 0x7fee515185a3 in select () from /lib64/libc.so.6 #1 0x7fee4fbbfbf1 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x7fee4fbc123b in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #3 0x7fee4fbc174d in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fee4fb781fa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fee4f9d810c in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fee4a2df4a5 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7fee4f9dc893 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fee50b1051c in start_thread () from /lib64/libpthread.so.0 #9 0x7fee515201ad in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fee28843700 (LWP 2423)): #0 0x7fee50b15e7f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7fee4ebab0c4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQt5Script.so.5 #2 0x7fee4ebab109 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQt5Script.so.5 #3 0x7fee50b1051c in start_thread () from /lib64/libpthread.so.0 #4 0x7fee515201ad in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fee51a1c880 (LWP 2406)): [KCrash Handler] #6 0x7fee514c2979 in __memcpy_sse2_unaligned () from /lib64/libc.so.6 #7 0x7fee4af46a22 in KWin::GLVertexBuffer::setData(int, int, float const*, float const*) () from /usr/lib64/libkwinglutils.so.8 #8 0x7fee510d10ce in KWin::SceneOpenGL2::doPaintBackground(QVector const&) () from /usr/lib64/libkwin.so.5 #9 0x7fee510d6905 in KWin::SceneOpenGL::paintBackground(QRegion) () from /usr/lib64/libkwin.so.5 #10 0x7fee510bd493 in KWin::Scene::paintSimpleScreen(int, QRegion) () from /usr/lib64/libkwin.so.5 #11 0x7fee510d1063 in KWin::SceneOpenGL2::paintSimpleScreen(int, QRegion) () from /usr/lib64/libkwin.so.5 #12 0x7fee510bf0f5 in KWin::Scene::finalPaintScreen(int, QRegion, KWin::ScreenPaintData&) () from /usr/lib64/libkwin.so.5 #13 0x7fee510e8a6f in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () from /usr/lib64/libkwin.so.5 #14 0x7fee4f1c769f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () from /usr/lib64/libkwineffects.so.8 #15 0x7fee510e8a2d in KWin::EffectsHand
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #8 from caulier.gil...@gmail.com --- while next week, this will be fine Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 361608] New: Akonadi Segault when trying to sync IMAP (intensive sync of many hundreds of emails)
https://bugs.kde.org/show_bug.cgi?id=361608 Bug ID: 361608 Summary: Akonadi Segault when trying to sync IMAP (intensive sync of many hundreds of emails) Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mathieu.belivea...@gmail.com CC: kdepim-b...@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.89.0) Qt Version: 5.5.1 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I was syncing kmail with my work place's exchange server through IMAP via Davmail. Note: This happend during an initial sync covering two years worth of emails. May be related to bug: 353957 (the stack trace is awfully similar). Although the crash reporting assistant wouldn't let me link my bug report to this one. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f53fb8ce840 (LWP 10405))] Thread 4 (Thread 0x7f53f91cf700 (LWP 10413)): #0 0x7f5408c5088d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f54043f5bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f54043f774f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f53fb5277e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f540955da6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f54046146aa in start_thread (arg=0x7f53f91cf700) at pthread_create.c:333 #6 0x7f5408c5be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f53f1e50700 (LWP 10558)): #0 0x7f5408c5088d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f54038971ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f54038972fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f540979550b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f540973c50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5409558ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f540955da6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f54046146aa in start_thread (arg=0x7f53f1e50700) at pthread_create.c:333 #8 0x7f5408c5be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f53f0a45700 (LWP 10585)): #0 0x7f54038db860 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5403896789 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f540389711b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f54038972fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f540979550b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f540973c50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5409558ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f540955da6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f54046146aa in start_thread (arg=0x7f53f0a45700) at pthread_create.c:333 #9 0x7f5408c5be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f53fb8ce840 (LWP 10405)): [KCrash Handler] #6 0x7f540c3a9693 in Akonadi::Entity::id (this=this@entry=0x7f54098123d8 ) at ../../../../akonadi/src/core/entity.cpp:72 #7 0x0045833e in ImapResourceBase::retrieveItems (this=this@entry=0xfeabb0, col=...) at ../../../resources/imap/imapresourcebase.cpp:435 #8 0x7f540c74e32d in Akonadi::ResourceBasePrivate::slotItemRetrievalCollectionFetchDone (this=, job=0x103d3c0) at ../../../../akonadi/src/agentbase/resourcebase.cpp:954 #9 0x7f540c750200 in Akonadi::ResourceBase::qt_static_metacall (_o=, _c=, _id=, _a=) at ./moc_resourcebase.cpp:294 #10 0x7f540976d8ea in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f540aac1752 in KJob::result (this=this@entry=0x103d3c0, _t1=_t1@entry=0x103d3c0) at ./moc_kjob.cpp:555 #12 0x7f540aac2311 in KJob::finishJob (this=0x103d3c0, emitResult=) at ../../../src/lib/jobs/kjob.cpp:109 #13 0x7f540aac232a in KJob::emitResult (this=) at ../../../src/lib/jobs/kjob.cpp:295 #14 0x7f540c43a3b3 in Akonadi::JobPrivate::delayedEmitResult (this=) at
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 361607] New: Screen went down when changing settings on widget CWP.
https://bugs.kde.org/show_bug.cgi?id=361607 Bug ID: 361607 Summary: Screen went down when changing settings on widget CWP. Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: cbel...@cfl.rr.com Application: plasma-desktop (4.11.14) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.13.0-85-generic x86_64 Distribution: Ubuntu 14.04.4 LTS -- Information about the crash: I was attempting to change the settings on a widget, CWP, when suddenly the screen went blank. -- Backtrace: Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a5f9e17c0 (LWP 4937))] Thread 19 (Thread 0x7f0a3531a700 (LWP 4939)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0a58655ffb in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f0a58953f00 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f0a58656039 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f0a53168182 in start_thread (arg=0x7f0a3531a700) at pthread_create.c:312 #4 0x7f0a5f2da47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 18 (Thread 0x7f09aefc7700 (LWP 4940)): #0 0x7f0a52a9261a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0a52a929a9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a52a50a59 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a52a50f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0a52a510ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0a5be7a7be in QEventDispatcherGlib::processEvents (this=0x7f09a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7f0a5be4c0af in QEventLoop::processEvents (this=this@entry=0x7f09aefc6de0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f0a5be4c3a5 in QEventLoop::exec (this=this@entry=0x7f09aefc6de0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f0a5bd48c5f in QThread::exec (this=this@entry=0x1c064a0) at thread/qthread.cpp:537 #9 0x7f0a5be2d823 in QInotifyFileSystemWatcherEngine::run (this=0x1c064a0) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7f0a5bd4b32f in QThreadPrivate::start (arg=0x1c064a0) at thread/qthread_unix.cpp:349 #11 0x7f0a53168182 in start_thread (arg=0x7f09aefc7700) at pthread_create.c:312 #12 0x7f0a5f2da47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 17 (Thread 0x7f09a19cf700 (LWP 4945)): #0 0x7f0a5f2cd12d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0a52a50fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a52a510ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a5be7a7be in QEventDispatcherGlib::processEvents (this=0x7f099c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f0a5be4c0af in QEventLoop::processEvents (this=this@entry=0x7f09a19cede0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f0a5be4c3a5 in QEventLoop::exec (this=this@entry=0x7f09a19cede0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0a5bd48c5f in QThread::exec (this=) at thread/qthread.cpp:537 #7 0x7f09a4c86fe7 in KCupsConnection::run() () from /usr/lib/libkcupslib.so #8 0x7f0a5bd4b32f in QThreadPrivate::start (arg=0x248c550) at thread/qthread_unix.cpp:349 #9 0x7f0a53168182 in start_thread (arg=0x7f09a19cf700) at pthread_create.c:312 #10 0x7f0a5f2da47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 16 (Thread 0x7f0998e3f700 (LWP 9372)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0a5bd4b816 in wait (time=18446744073709551615, this=0x1c85830) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1dc2268, mutex=0x1c511b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f0a578c1e6c in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1dc2240, th=0x661f8f0) at ../../../threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7f0a578c4903 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1c7b590, th=0x661f8f0, previous=0x0) at ../../../threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7f0a578c491c in ThreadWeaver::WorkingHardState::applyForWork (this=0x1c7b590, th=0x661f8f0, previous=0x0) at ../../../threadweaver/Weaver/WorkingHardState.cpp:71 #6 0x7f0a578
[Artikulate] [Bug 361571] Artikulate crashes on Start up
https://bugs.kde.org/show_bug.cgi?id=361571 Xavier Aragon changed: What|Removed |Added CC||xarax-...@elliptic.info.tm --- Comment #2 from Xavier Aragon --- I experienced this same crash on Kubuntu 16.04 Beta (which is of course not assumed to be fully stable yet). When I ran Artikulate from command line, I got the following warning: QQmlApplicationEngine failed to load component file:///usr/share/artikulate/qml/Main.qml:24 module "QtQml.Models" is not installed It seems in Ubuntu the missing module comes from package qml-module-qtqml-models2, and after installing that one, Artikulate starts without crashing. I'm not familiar with Qt/Qml packaging and don't know if this should be fixed on KDE or distribution side. In Ubuntu 16.04 the Qt version would seem to be 5.5.1, i.e. the same as in openSuse of the original bug reporter. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361606] New: GTK theme is buggy ,icons are overlapped and some time there is no text to display
https://bugs.kde.org/show_bug.cgi?id=361606 Bug ID: 361606 Summary: GTK theme is buggy ,icons are overlapped and some time there is no text to display Product: Breeze Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: medo.ta...@gmail.com GTK theme looks ugly on firefox and every GTK app like uGet , icons are also overlapped and there is no text in uGet Menus or popup windows , i noticed that bug after updating to version 2.6.2 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361587] git master 2016-04-10 - Screen Grab crashes
https://bugs.kde.org/show_bug.cgi?id=361587 --- Comment #6 from Jean-Baptiste Mardelle --- Git commit 4aa03eb05f8866f45382aa1c5bfc5bc9c53a934d by Jean-Baptiste Mardelle. Committed on 10/04/2016 at 19:02. Pushed by mardelle into branch 'Applications/16.04'. Screen grab: display full log if capture crashes M +5-2src/monitor/monitor.cpp M +1-1src/monitor/monitor.h M +12 -3src/monitor/recmanager.cpp M +3-1src/monitor/recmanager.h http://commits.kde.org/kdenlive/4aa03eb05f8866f45382aa1c5bfc5bc9c53a934d -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 David Jarvie changed: What|Removed |Added CC||ha...@laging.de --- Comment #17 from David Jarvie --- *** Bug 361115 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361115] daylight savings time is handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=361115 David Jarvie changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from David Jarvie --- *** This bug has been marked as a duplicate of bug 336738 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361605] New: kmail crash on double click email
https://bugs.kde.org/show_bug.cgi?id=361605 Bug ID: 361605 Summary: kmail crash on double click email Product: kontact Version: unspecified Platform: Chakra OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: luc...@bluewin.ch Application: kontact (5.1.90 rc) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.5.0-1-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: kmail 16.03.90 How to reproduce: double click and email from the email list. (I tested with a nestled email, one from a list of replies) Results: kmail/contact crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9063055840 (LWP 9372))] Thread 23 (Thread 0x7f90603e3700 (LWP 9373)): #0 0x7f9076f3718d in poll () from /usr/lib/libc.so.6 #1 0x7f907149fae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f90714a1757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f9062d6a329 in QXcbEventReader::run (this=0xea5c70) at qxcbconnection.cpp:1313 #4 0x7f9077840238 in QThreadPrivate::start (arg=0xea5c70) at thread/qthread_unix.cpp:340 #5 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7f9057fff700 (LWP 9374)): #0 0x7f906f353336 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f906f308b7f in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f906f309183 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f906f309322 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f9077a691fb in QEventDispatcherGlib::processEvents (this=0x7f9058c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f9077a11c2a in QEventLoop::exec (this=this@entry=0x7f9057ffed50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f907783b434 in QThread::exec (this=this@entry=0x7f9079d5dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #7 0x7f9079cea495 in QDBusConnectionManager::run (this=0x7f9079d5dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:181 #8 0x7f9077840238 in QThreadPrivate::start (arg=0x7f9079d5dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #9 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7f9056dee700 (LWP 9376)): #0 0x7f9070e7b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9074f023fb in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7f9074f02439 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7f900f8ae700 (LWP 9377)): #0 0x7f9076f4c707 in __libc_disable_asynccancel () from /usr/lib/libc.so.6 #1 0x7f9076f33179 in read () from /usr/lib/libc.so.6 #2 0x7f906f351b41 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f906f308ca4 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #4 0x7f906f309183 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x7f906f309322 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #6 0x7f9077a691fb in QEventDispatcherGlib::processEvents (this=0x7f90080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #7 0x7f9077a11c2a in QEventLoop::exec (this=this@entry=0x7f900f8add80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7f907783b434 in QThread::exec (this=) at thread/qthread.cpp:503 #9 0x7f9077840238 in QThreadPrivate::start (arg=0xfe6150) at thread/qthread_unix.cpp:340 #10 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7f9007fff700 (LWP 9378)): #0 0x7f9070e7b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9074c0f1c4 in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7f9074f32291 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7f90077fe700 (LWP 9379)): #0 0x7f9070e7b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9074c101f3 in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7f9074f32291 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7f9070e75464 in start_thread () from /usr/l
[kdenlive] [Bug 361587] git master 2016-04-10 - Screen Grab crashes
https://bugs.kde.org/show_bug.cgi?id=361587 --- Comment #5 from Jean-Baptiste Mardelle --- Git commit 5f1836afa284940136632e3ea801ced339964368 by Jean-Baptiste Mardelle. Committed on 10/04/2016 at 18:42. Pushed by mardelle into branch 'Applications/16.04'. Fix screen grab offset parameters not working, warn if destination folder is not writable M +17 -8src/monitor/recmanager.cpp http://commits.kde.org/kdenlive/5f1836afa284940136632e3ea801ced339964368 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #17 from wolfyrion --- This bug becomes more annoying when you are using cairo-dock and try to use opengl applications like Unreal Engine or UInity 3D. Cairo dock is using opengl and everything gets disable and the only thing you can see from the dock is a Black Square Dock >< So do we know if this is an NVIDIA driver problem or Plasma 5? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 andreas changed: What|Removed |Added Target Milestone|--- |1.0 Product|Breeze |plasmashell Component|Icons |Theme - Breeze CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361587] git master 2016-04-10 - Screen Grab crashes
https://bugs.kde.org/show_bug.cgi?id=361587 Evert Vorster changed: What|Removed |Added Resolution|--- |REMIND Status|UNCONFIRMED |RESOLVED --- Comment #4 from Evert Vorster --- I finally managed to get screen captures to work again. Turns out that the directory that I wanted to save the captures in did not exist. However, the time it took to find this issue does make the point that the error message is not informative enough. I would have loved to be able to see the actual error message from ffmpeg, rather than the generic "This and that crashed, check your settings" -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 360825] LibreOffice menu item radio buttons completely covered with blue color
https://bugs.kde.org/show_bug.cgi?id=360825 André Marcelo Alvarenga changed: What|Removed |Added CC||alvare...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 360304] Missing animations cions
https://bugs.kde.org/show_bug.cgi?id=360304 andreas changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Mister Ypsilon changed: What|Removed |Added CC||mrypsil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #7 from Omar Amin --- Hi Mr Gilles, I'll look into it during this week, and will finish it by next Friday, Please let me know if you need it finished earlier. Regards, Omar -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361587] git master 2016-04-10 - Screen Grab crashes
https://bugs.kde.org/show_bug.cgi?id=361587 --- Comment #3 from Evert Vorster --- Created attachment 98323 --> https://bugs.kde.org/attachment.cgi?id=98323&action=edit My screen capture profile I had a higher frame rate, and also has -threads=1, but setting the profile to exactly your example still did not make any difference. Screen capturing still crashes. Is there any way to get a more detailed error message out of this system? -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 361602] New: strange behaviour on switching desktops with non-KDE5 applications
https://bugs.kde.org/show_bug.cgi?id=361602 Bug ID: 361602 Summary: strange behaviour on switching desktops with non-KDE5 applications Product: kstart Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: bugzi...@kerridis.de I encountered a strange kstart behaviour when I try to start applications on a different desktop than the current one: With KDE5 applications it works as expected, "kstart --desktop 2 " switches to the new desktop and the application window appears on that desktop. It doesn't matter if I invoke that command from a launcher or krunner or konsole. But with KDE4- and non-KDE applications it behaves different (e.g. Amarok or Gimp): If I invoke the full command from konsole or krunner kstart switches the desktop it behaves as expected, no difference to starting a Plasma 5 app. But invoking any launcher (via kickoff, krunner, quicklaunch, single launcher in panel or on desktop) , the desktop switches to the target desktop, the application gets launched (I see the gimp splash therefore I now it is started on the target desktop) - and then the desktop switches back to where I have executed the launcher and opens the application window on that desktop. As the command does work as expected when typed in konsole or krunner but not when executed via a launcher and the latter only with applications that don't belong to KDE5 I guess it's not really a kstart problem. But I didn't know where else to report. The funny thing is - it did work as expected in KDE4 so it's obviously not a problem of the non-KDE apps. Reproducible: Always Expected Results: The desktop shouldn't switch back to the primary one after the desktop number was set by kstart, even if an application launcher maybe reports it was launched from another desktop. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 361601] global search in log viewer (ktp-log-viewer) not work
https://bugs.kde.org/show_bug.cgi?id=361601 painless roaster changed: What|Removed |Added Summary|global search in log viewer |global search in log viewer |not work|(ktp-log-viewer) not work -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 361601] New: global search in log viewer not work
https://bugs.kde.org/show_bug.cgi?id=361601 Bug ID: 361601 Summary: global search in log viewer not work Product: telepathy Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: log-viewer Assignee: kde-telepathy-b...@kde.org Reporter: painless.roas...@gmail.com global search in log viewer not work Reproducible: Always Steps to Reproduce: 1. open log viewer 2. enter search term 3. push enter Actual Results: search not work in empathy global search in log viewer is ok -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 361364] Problems in scanning, using Canoscan 8800F
https://bugs.kde.org/show_bug.cgi?id=361364 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |kare.s...@iki.fi CC||caulier.gil...@gmail.com Component|general |general Product|kipiplugins |libksane Version|4.6.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 359922] QCA: make: error: ‘QIODevice’ has not been declared void update(QIODevice *file);
https://bugs.kde.org/show_bug.cgi?id=359922 Jeff Singleton changed: What|Removed |Added CC||gvib...@gmail.com --- Comment #1 from Jeff Singleton --- Mark this as confirmed and reproducible. Version 2.1.0.3 Debian 8.4 AMD64 -- 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 Thomas Lübking changed: What|Removed |Added Component|general |tabbox --- Comment #1 from Thomas Lübking --- Might be rather a problem in kglobalaccel - if you assign the alt+tab shortcut to something different (eg. showin krunner) and apply your "Press Alt+Tab and release it very quickly™" pattern, does that trigger krunner reliably? > Alexander Potashev Do you use a multilayout keyboard and/or some input mapper (xim, fctix, etc..) for cyrillic input? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361600] Cannot delete custom tag and the last brush added.
https://bugs.kde.org/show_bug.cgi?id=361600 --- Comment #1 from Bruno de Souza Lino --- Created attachment 98322 --> https://bugs.kde.org/attachment.cgi?id=98322&action=edit Bug in display -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361595] ligature font doesn't work
https://bugs.kde.org/show_bug.cgi?id=361595 --- Comment #2 from malcolm.mie...@protonmail.com --- I've found that it might be FiraCode's fault because version 0.6 works. Although every other version of FiraCode works with Kate but not kdevelop. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361600] Cannot delete custom tag and the last brush added.
https://bugs.kde.org/show_bug.cgi?id=361600 Bruno de Souza Lino changed: What|Removed |Added OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361600] New: Cannot delete custom tag and the last brush added.
https://bugs.kde.org/show_bug.cgi?id=361600 Bug ID: 361600 Summary: Cannot delete custom tag and the last brush added. Product: krita Version: 3.0 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Documentation Assignee: krita-bugs-n...@kde.org Reporter: bruno.souza.l...@gmail.com I cannot delete user created tags nor change what brushes it has, except ones that added before the last one was added. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361595] ligature font doesn't work
https://bugs.kde.org/show_bug.cgi?id=361595 --- Comment #1 from Kevin Funk --- Note: Also see discussion in forums: https://forum.kde.org/viewtopic.php?f=218&t=132175&p=355058 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 361599] [OS X] Crash in the "File Already Exists" dialog when copy/pasting a file in KDevelop's file manager
https://bugs.kde.org/show_bug.cgi?id=361599 RJVB changed: What|Removed |Added CC||kf...@kde.org, ||m...@milianw.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 361599] New: [OS X] Crash in the "File Already Exists" dialog when copy/pasting a file in KDevelop's file manager
https://bugs.kde.org/show_bug.cgi?id=361599
Bug ID: 361599
Summary: [OS X] Crash in the "File Already Exists" dialog when
copy/pasting a file in KDevelop's file manager
Product: frameworks-kio
Version: 5.20.0
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: rjvber...@gmail.com
CC: kdelibs-b...@kde.org
When copy/pasting a file into its own directory using KDevelop's project/file
manager, the File Already Exists dialog is presented to paste the file under a
different name. A crash occurs every time doing that.
Reproducible: Always
Steps to Reproduce:
1. Copy a file (in KDevelop's project manager view)
2. Paste the file into its own directory
3. observe the crash
Actual Results:
KDevelop crashes
Expected Results:
The opened dialog is functional and allows to paste the file under a different
name.
Backtrace:
Process 38794 stopped
* thread #1: tid = 0xc63e05, 0x000102682628 QtWidgets`QScrollArea::widget()
const [inlined] QWeakPointer::data() const at
qsharedpointer_impl.h:597, queue = 'com.apple.main-thread', stop reason =
EXC_BAD_ACCESS (code=1, address=0x26f)
frame #0: 0x000102682628 QtWidgets`QScrollArea::widget() const
[inlined] QWeakPointer::data() const at qsharedpointer_impl.h:597
594 inline bool isNull() const { return d == Q_NULLPTR ||
d->strongref.load() == 0 || value == Q_NULLPTR; }
595 inline operator RestrictedBool() const { return isNull() ?
Q_NULLPTR : &QWeakPointer::value; }
596 inline bool operator !() const { return isNull(); }
-> 597 inline T *data() const { return d == Q_NULLPTR ||
d->strongref.load() == 0 ? Q_NULLPTR : value; }
598
599 inline QWeakPointer() : d(Q_NULLPTR), value(Q_NULLPTR) { }
600 inline ~QWeakPointer() { if (d && !d->weakref.deref()) delete d; }
(lldb) bt
* thread #1: tid = 0xc63e05, 0x000102682628 QtWidgets`QScrollArea::widget()
const [inlined] QWeakPointer::data() const at
qsharedpointer_impl.h:597, queue = 'com.apple.main-thread', stop reason =
EXC_BAD_ACCESS (code=1, address=0x26f)
* frame #0: 0x000102682628 QtWidgets`QScrollArea::widget() const
[inlined] QWeakPointer::data() const at qsharedpointer_impl.h:597
frame #1: 0x000102682628 QtWidgets`QScrollArea::widget() const
[inlined] QPointer::data() const at qpointer.h:80
frame #2: 0x000102682628 QtWidgets`QScrollArea::widget() const
[inlined] QPointer::operator QWidget*() const at qpointer.h:86
frame #3: 0x000102682628
QtWidgets`QScrollArea::widget(this=0x0001198461b0) const + 8 at
qscrollarea.cpp:224
frame #4: 0x00010184f34a
libKF5KIOWidgets.5.dylib`KIO::RenameDialog::resizePanels(this=0x7fff5fbf5800)
+ 106 at renamedialog.cpp:593
frame #5: 0x000103640383 QtCore`QObject::event(this=,
e=) + 659 at qobject.cpp:1256
frame #6: 0x00010250304f
QtWidgets`QWidget::event(this=0x7fff5fbf5800, event=0x0001198dab80) +
3359 at qwidget.cpp:9173
frame #7: 0x0001024c2f66
QtWidgets`QApplicationPrivate::notify_helper(this=,
receiver=0x7fff5fbf5800, e=0x0001198dab80) + 294 at
qapplication.cpp:3714
frame #8: 0x0001024c6225
QtWidgets`QApplication::notify(this=, receiver=,
e=) + 7877 at qapplication.cpp:3677
frame #9: 0x000103613b07
QtCore`QCoreApplication::notifyInternal2(receiver=0x7fff5fbf5800,
event=0x0001198dab80) + 167 at qcoreapplication.cpp:1020
frame #10: 0x000103614706
QtCore`QCoreApplicationPrivate::sendPostedEvents(receiver=0x,
event_type=0, data=0x00010b7131e0) + 566 at qcoreapplication.h:227
frame #11: 0x00010c46b0ce
libqcocoa.dylib`QCocoaEventDispatcherPrivate::processPostedEvents(this=0x00010c20a3c0)
+ 190 at qcocoaeventdispatcher.mm:883
frame #12: 0x00010c46b9b1
libqcocoa.dylib`QCocoaEventDispatcherPrivate::postedEventsSourceCallback(info=0x00010c20a3c0)
+ 33 at qcocoaeventdispatcher.mm:920
frame #13: 0x7fff8347e5b1
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
frame #14: 0x7fff8346fc62 CoreFoundation`__CFRunLoopDoSources0 + 242
frame #15: 0x7fff8346f3ef CoreFoundation`__CFRunLoopRun + 831
frame #16: 0x7fff8346ee75 CoreFoundation`CFRunLoopRunSpecific + 309
frame #17: 0x7fff891d1a0d HIToolbox`RunCurrentEventLoopInMode + 226
frame #18: 0x7fff891d1685 HIToolbox`ReceiveNextEventCommon + 173
frame #19: 0x7fff891d15bc
HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 65
frame #20: 0x7fff8969e24e AppKit`_DPSNextEvent + 1434
frame #21: 0x7fff8969d89b AppKit`-[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
frame #22: 0x7fff899fce2e AppKit`-[NSApplication
_realDoModalLoop:peek:] + 642
frame #23: 0
[kwin] [Bug 360336] Default task switcher still briefly appear when changed
https://bugs.kde.org/show_bug.cgi?id=360336 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361598] New: Alt+Tab does not always work when pressing it quickly
https://bugs.kde.org/show_bug.cgi?id=361598 Bug ID: 361598 Summary: Alt+Tab does not always work when pressing it quickly Product: kwin Version: 5.6.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: aspotas...@gmail.com See Steps to Reproduce. Reproducible: Always Steps to Reproduce: 1. Open at least two applications. 2. Press Alt+Tab and release it very quickly, so that the task switcher does not appear. Actual Results: Sometimes the window is not switched. Expected Results: Window should always switch. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361597] New: Firewire capture not working in version 15.12.1
https://bugs.kde.org/show_bug.cgi?id=361597 Bug ID: 361597 Summary: Firewire capture not working in version 15.12.1 Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: fomin.and...@gmail.com Firewire selection not latching in configuration. There is no record monitor window in the main GUI or selection in the drop down menu. Also, there is no response to capture device selection in the configuration wizard. Reproducible: Always Steps to Reproduce: 1. Try selecting firewire in the capture configuration. In my case, I select the HDV option. 2. 3. Actual Results: No connection with camcorder. No record monitor window in gui to select the connection. Expected Results: The gui should have a record monitor window as in previous versions. Please do not drop this feature. There are many people that still use tape based camcorders or have large DV libraries. There are few practical options in Linux to capture HDV. I have tried LIVES and found it crashes right away. Kino is hasn't been supported for years and has no HDV capture option. I have used this option in Kdenlive .9.8 and .9.10 often. If possible, can you make these versions available for download until the issue gets resolved in the latest version? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdbusaddons] [Bug 355545] KDBusService constructor is crashing on calling exit()
https://bugs.kde.org/show_bug.cgi?id=355545 Martin Sandsmark changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||martin.sandsm...@kde.org --- Comment #2 from Martin Sandsmark --- Copying in my comment on https://git.reviewboard.kde.org/r/127625/ : It seems like it is this that it happening: https://bugreports.qt.io/browse/QTBUG-48709 >From my understanding it can't really be fixed, short of somehow getting KDBusService to delete the QApplication before calling exit(), which might get nasty with QApplications allocated on the stack? In any case it seems to be a general bug with KDBusService and how it is supposed to be used, not something that we can easily fix in konsole. See also my workaround here: https://git.reviewboard.kde.org/r/127626/ It should be fixed in KDBusService, using a similar workaround in all apps that use it is not feasible. I'm not sure how it can be worked around, though, it can't just delete the QApplication itself, since pretty much everyone allocate it on the stack. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361591] Tab order in new custom document dialogue switches from width to resolution instead of hight
https://bugs.kde.org/show_bug.cgi?id=361591 --- Comment #4 from Amir Adar --- Very well. Thanks again! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358611] Assistant tool force lines to position not that one mouse is pointing
https://bugs.kde.org/show_bug.cgi?id=358611 --- Comment #7 from wolthera --- It's better to just make a seperate assistant for this. It just needs design and the like. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361591] Tab order in new custom document dialogue switches from width to resolution instead of hight
https://bugs.kde.org/show_bug.cgi?id=361591 --- Comment #3 from wolthera --- Oh, no don't worry about. If I am right we used an old version of the source deliberately because of organisational reasons(like, the code used in the release is the same as in the tarballs for the alpha, which makes it the same code, and thus clearer). Just continue resting with the build you have. The new alpha packages are mostly there to fix an issue with fedora. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361584] Toolbox Icons disappeared
https://bugs.kde.org/show_bug.cgi?id=361584 --- Comment #3 from Avelino De Sabbata --- Oh thanks! I have installed oxygen icons set and the problem was solved. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361596] New: Crash when opening color space browser
https://bugs.kde.org/show_bug.cgi?id=361596 Bug ID: 361596 Summary: Crash when opening color space browser Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: tokyogeometry+k...@gmail.com Krita crashes immediately when the color space browser is opened. Reproducible: Always Steps to Reproduce: 1. Open a dialog box which has 'Color Space Browser' button. (New Document dialog box, Image properties dialog box, etc) 2. Click on the button. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361591] Tab order in new custom document dialogue switches from width to resolution instead of hight
https://bugs.kde.org/show_bug.cgi?id=361591 --- Comment #2 from Amir Adar --- Thank you for the reply. :) I didn't realize this was an old build. I downloaded it yesterday from the pre-alpha 3 announcement post (https://krita.org/item/3-0-pre-alpha-3-is-out/), so I figured it must have been the latest. Now I see there's another build in the download page. Should I use the one from there if I want to keep testing? -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 338097] KSystemLog crashes when opening the program
https://bugs.kde.org/show_bug.cgi?id=338097 andrew brewster changed: What|Removed |Added CC||ab@ntlworld.com --- Comment #9 from andrew brewster --- Still getting this type of crash: Application: ksystemlog (0.4) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.1.15-desktop-2.mga5 x86_64 Distribution: "Mageia 5" -- Information about the crash: Program starts up OK and shows system log, click Kernel Log button on toolbar, and the program crashes. The crash can be reproduced every time. -- Backtrace: Application: KSystemlog (ksystemlog), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x7f142687c908 in QStandardItem::child(int, int) const (column=0, row=13227328, this=0x31) at ../../src/gui/itemviews/qstandarditemmodel_p.h:85 #7 0x7f142687c908 in QStandardItem::child(int, int) const (this=, row=13227328, column=0) at itemviews/qstandarditemmodel.cpp:1700 #8 0x7f142687cb12 in QStandardItemModel::data(QModelIndex const&, int) const (index=..., this=) at ../../src/gui/itemviews/qstandarditemmodel_p.h:162 #9 0x7f142687cb12 in QStandardItemModel::data(QModelIndex const&, int) const (this=, index=..., role=0) at itemviews/qstandarditemmodel.cpp:2653 #10 0x7f14266c1551 in QComboBoxPrivate::itemText(QModelIndex const&) const (this=this@entry=0xa5bc10, index=...) at widgets/qcombobox.cpp:1287 #11 0x7f14266c4b2f in QComboBoxPrivate::_q_emitCurrentIndexChanged(QModelIndex const&) (this=0xa5bc10, index=...) at widgets/qcombobox.cpp:1279 #12 0x7f1426f7888a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0xa39a10, m=m@entry=0x7f14272c8860 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7ffdb5b86ce0) at kernel/qobject.cpp:3567 #13 0x7f1426fc2114 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int) (this=this@entry=0xa39a10, _t1=..., _t2=0, _t3=0) at .moc/release-shared/moc_qabstractitemmodel.cpp:196 #14 0x7f1426f5e492 in QAbstractItemModel::endInsertRows() (this=0xa39a10) at kernel/qabstractitemmodel.cpp:2433 #15 0x7f142687e225 in QStandardItemModelPrivate::rowsInserted(QStandardItem*, int, int) (this=, parent=parent@entry=0xa39a30, row=row@entry=0, count=count@entry=1) at itemviews/qstandarditemmodel.cpp:558 #16 0x7f142687ef6f in QStandardItemPrivate::insertRows(int, int, QList const&) (this=0xa39a50, row=row@entry=0, count=count@entry=1, items=...) at itemviews/qstandarditemmodel.cpp:433 #17 0x7f14268807fc in QStandardItem::insertRow(int, QList const&) (this=, row=row@entry=0, items=...) at itemviews/qstandarditemmodel.cpp:1457 #18 0x7f1426880873 in QStandardItemModel::insertRow(int, QList const&) (this=this@entry=0xa39a10, row=row@entry=0, items=...) at itemviews/qstandarditemmodel.cpp:2498 #19 0x7f14266c5f45 in QComboBox::insertItem(int, QIcon const&, QString const&, QVariant const&) (aitem=0xc27e10, arow=, this=0xa39a10) at ../../src/gui/itemviews/qstandarditemmodel.h:438 #20 0x7f14266c5f45 in QComboBox::insertItem(int, QIcon const&, QString const&, QVariant const&) (this=this@entry=0xa39b50, index=index@entry=0, icon=..., text=..., userData=...) at widgets/qcombobox.cpp:2145 #21 0x0041a303 in KSystemLog::StatusBar::changeMessage(QString const&) (auserData=..., atext=..., aindex=0, this=0xa39b50) at /usr/include/QtGui/qcombobox.h:331 #22 0x0041a303 in KSystemLog::StatusBar::changeMessage(QString const&) (this=0xa51550, message=...) at /usr/src/debug/ksystemlog-4.14.3/src/statusBar.cpp:123 #23 0x004262cc in KSystemLog::MainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (text=..., this=) at /usr/src/debug/ksystemlog-4.14.3/src/mainWindow.cpp:459 #24 0x004262cc in KSystemLog::MainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x31, _id=13227328, _a=0x0, _c=) at /usr/src/debug/ksystemlog-4.14.3/build/src/mainWindow.moc:80 #25 0x7f1426f7888a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0xadce70, m=m@entry=0x697d80 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdb5b871b0) at kernel/qobject.cpp:3567 #26 0x0043b897 in LogManager::reload() (_t1=..., this=0xadce70) at /usr/src/debug/ksystemlog-4.14.3/build/src/lib/logManager.moc:135 #27 0x0043b897 in LogManager::reload() (this=this@entry=0xadce70) at /usr/src/debug/ksystemlog-4.14.3/src/lib/logManager.cpp:105 #28 0x00420aaa in TabLogViewsWidget::load(LogMode*, LogManager*) (this=, logMode=logMode@entry=0x8de870, manager=0xadce70) at /usr/src/debug/ksystemlog-4.14.3/src/tabLogViewsWidget.cpp:280 #29 0x0042103b in KSystemLog::MainWindow::selectLogModeAct
[kdevelop] [Bug 361595] New: ligature font doesn't work
https://bugs.kde.org/show_bug.cgi?id=361595 Bug ID: 361595 Summary: ligature font doesn't work Product: kdevelop Version: 4.7.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: malcolm.mie...@protonmail.com I used to have font ligature on kdevelop (for example using firaCode the '==' would become one character only) and it doesn't work anymore. Weirdly, it works perfectly fine on Kate. Reproducible: Always Steps to Reproduce: 1. change the font to firaCode or other font with ligature 2. enter something like == or <= 3. nothing happens Actual Results: Nothing while it should display only one symbol, I still have two symbols Expected Results: I should see only one symbol -- You are receiving this mail because: You are watching all bug changes.
