[kinfocenter] [Bug 372081] misinterpretation of system information
https://bugs.kde.org/show_bug.cgi?id=372081 Looserof7changed: What|Removed |Added CC||looser...@gmail.com --- Comment #5 from Looserof7 --- Created attachment 102042 --> https://bugs.kde.org/attachment.cgi?id=102042=edit Bigger Image I'm extremely sorry for the delay, I didn't have internet connection for a while, so please excuse me, being noob I didn't understand anything of comment4 , but I would try my best to help. Here is the screenshot, -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357171] Create new symlink dialog shows directories but not files
https://bugs.kde.org/show_bug.cgi?id=357171 --- Comment #6 from taro yamada--- Sorry, #5 was wrong... -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 184760] Cannot activate wireless connection
https://bugs.kde.org/show_bug.cgi?id=184760 syed abdul khayyumchanged: What|Removed |Added CC||abdulkhayyu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
https://bugs.kde.org/show_bug.cgi?id=372094 --- Comment #3 from Kevin Kofler--- Also, your change is labeled "Use cdrecord for burning blueray instead of wodim.", but K3b did not attempt to use wodim to burn BluRay even before your change. If you look more closely at the code you removed, you will notice that it took care to prefer growisofs over wodim for all DVD and BluRay burning tasks. (The only reason we need wodim at all is that growisofs does not support CDs.) In fact, ironically, your change actually made K3b attempt to use wodim for BluRay! (Then you added a followup to just unconditionally prefer growisofs: http://quickgit.kde.org/?p=k3b.git=commitdiff=f3f4602e30c67bf622b5a52ea39c78817b1dd020 , which I'm not sure is a good idea either. It is much better than wodim, but is it better than current versions of cdrecord? Probably not. You will need to revert that first so that you can revert fcb0ff1f.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370430] Dolphin samba read-write issue on top folder share
https://bugs.kde.org/show_bug.cgi?id=370430 demlakchanged: What|Removed |Added CC||kde-bugtrac...@demlak.de --- Comment #4 from demlak --- Hi, i can confirm.. and add more related info: it seems to be not read-only on the top folder.. it is just no write permission.. because i'm able to delete and rename files and folders in that top folder. this also happens on mtp:// (and maybe other kio_slaves) kde 5.8.3 kde frameworks 5.27.0 dolphin 16.08.2 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
https://bugs.kde.org/show_bug.cgi?id=137436 Kevin Koflerchanged: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #15 from Kevin Kofler --- Yes, in the long run, to work with something maintained, we will need K3b to work well with http://libburnia-project.org/ . Cdrecord has licensing issues preventing it from shipping in some distributions (https://fedoraproject.org/wiki/Forbidden_items#cdrtools), cdrkit/wodim and dvd+rw-tools/growisofs are both dead projects. At the very least, its cdrskin tool should be supported similarly to wodim: check for it (I would check for "cdrskin", "cdrecord" and "wodim" in that order, or you end up picking up a "cdrecord" that is really wodim), then add hasFeature("cdrskin") checks where useful, i.e., cdrskin is probably preferable to growisofs for all burning tasks (both DVD and BluRay), and you need to check its support for various features. The proposed patch from comment #1 is far from sufficient. It only checks for the cdrskin binary (after wodim!), but it treats it as if it were cdrecord, so you end up with all the workarounds for cdrecord limitations. But I think the best way would be to just use the libburn library and stop spawning external tools entirely. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
https://bugs.kde.org/show_bug.cgi?id=372094 --- Comment #2 from Kevin Kofler--- And in the long run, to work with something maintained, see wishlist bug #137436. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355410] the scroll speed of QML scroll area is too slow with Libinput
https://bugs.kde.org/show_bug.cgi?id=355410 Ben Bullardchanged: What|Removed |Added CC||benbullar...@cox.net --- Comment #20 from Ben Bullard --- (In reply to Rex Dieter from comment #5) > marking confirmed. I strongly suspect this to be a Qt5 issue though (not a > kde.org one) I'm wondering if this has been reported to QT folks? https://www.qt.io/developers/ I'm not a developer and don't have an account there. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
https://bugs.kde.org/show_bug.cgi?id=372094 --- Comment #1 from Kevin Kofler--- I will also note that your changes have several logic errors: -: K3b::AbstractCdrtoolsProgram( QLatin1String( "cdrecord" ), QLatin1String( "wodim" ) ) +: K3b::AbstractCdrtoolsProgram( QLatin1String( "cdrecord" ), QLatin1String("cdrecord") ) (2 times the same command, probably not what you want) -// but prefer growisofs to wodim for DVDs +// but prefer growisofs for DVDs if ( d->usedWritingApp == K3b::WritingAppAuto ) { -if (k3bcore->externalBinManager()->binObject("cdrecord")->hasFeature( "wodim" )) -d->usedWritingApp = K3b::WritingAppGrowisofs; -else -d->usedWritingApp = K3b::WritingAppCdrecord; +d->usedWritingApp = K3b::WritingAppCdrecord; (The comment says "prefer growisofs", the code says "prefer cdrecord".) but instead of fixing those errors, please revert this commit wholesale, or K3b will have to be removed from Fedora. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372046] plasma5 show tiny icons in HiDPI screens
https://bugs.kde.org/show_bug.cgi?id=372046 --- Comment #3 from Giuseppe Ghibò--- Created attachment 102041 --> https://bugs.kde.org/attachment.cgi?id=102041=edit patch equivalent to original behaviour of QT_AUTO_SCREEN_SCALE_FACTOR=0 This patch maintains the same original behaviour of QT_AUTO_SCREEN_SCALE_FACTOR=0 but moves the configuration in an external config file. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] New: Please restore wodim support
https://bugs.kde.org/show_bug.cgi?id=372094 Bug ID: 372094 Summary: Please restore wodim support Product: k3b Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: kevin.kof...@chello.at CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- In: https://quickgit.kde.org/?p=k3b.git=commitdiff=fcb0ff1f36c319fd1e2b4bd92c2c08fdc690212c you removed support for wodim. Please revert this commit. Fedora ships only cdrkit, not cdrtools, due to licensing issues: https://fedoraproject.org/wiki/Forbidden_items#cdrtools . If you need a distribution shipping wodim for testing, try Fedora. DVD support in wodim is crap and BluRay support is nonexistent, but that's why the code you removed, which prefers growisofs, is there! What will happen now that you removed the detection for wodim is that K3b will think that wodim is cdrecord (because it symlinks itself to cdrecord) and no longer disable use of wodim for things it does not support. Please do not remove code you don't understand. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370465] window state is hard to tell by looking at the task manager button
https://bugs.kde.org/show_bug.cgi?id=370465 JanKusanagichanged: What|Removed |Added CC||jan-b...@gmx.co.uk -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)
https://bugs.kde.org/show_bug.cgi?id=367639 --- Comment #53 from Kevin Kofler--- In these commits, I see things like ,ms[0] == 0 or ms[1] != 0, where ms is a QStringList, so you are comparing a QString against 0. This doesn't look right. Either use isEmpty() or compare with the string "0", depending on what you actually meant. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 330162] The Akonadi Server doesn't start, because of a D-Bus error
https://bugs.kde.org/show_bug.cgi?id=330162 --- Comment #3 from Peter XP--- Actually, the solution to Bug 362138 from Ekeluo Chukwuogor seems to have worked for me, too. Thank you Ekeluo. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372093] New: corrupts image file when crashing
https://bugs.kde.org/show_bug.cgi?id=372093 Bug ID: 372093 Summary: corrupts image file when crashing Product: digikam Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Metadata Assignee: digikam-de...@kde.org Reporter: ka...@posteo.eu Target Milestone: --- After having seen a few mid-work crashes, some image files are corrupted in the sense that they load, but only contain the upper part of the image. It seems the write to the image file stopped mid-file, presumably caused by a program crash. In most of the crash situations digikam was in the process of changing metadata to a bunch of images. My guess is that it was not only changing this metadata in its database, but also inside the image files itself. When the process crashes while rewriting an image file, this file doesn't seem to be protected against corruption. (I. e. it seems the file gets overwritten directly instead of writing a copy and replacing the former file only when he new copy was written correctly.) [NB: It would take me weeks to find my way through the source code. If someone might point me to the src file taking care of overwriting image file in the relevant cases, I _might_ be able to submit a code proposal.] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372083] Task Switcher visualization stuck on "Breeze"
https://bugs.kde.org/show_bug.cgi?id=372083 Christoph Feckchanged: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Component|general |general Product|systemsettings |kwin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350356] wish:icons of minimized apps need to be darker
https://bugs.kde.org/show_bug.cgi?id=350356 David Edmundsonchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from David Edmundson --- *** This bug has been marked as a duplicate of bug 370465 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370465] window state is hard to tell by looking at the task manager button
https://bugs.kde.org/show_bug.cgi?id=370465 David Edmundsonchanged: What|Removed |Added CC||bad...@gmail.com --- Comment #4 from David Edmundson --- *** Bug 350356 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 372081] misinterpretation of system information
https://bugs.kde.org/show_bug.cgi?id=372081 Christoph Feckchanged: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com --- Comment #4 from Christoph Feck --- Adding Hugo for the KCapacityBar issue. The default rendering of KCapacityBar is visible on https://api.kde.org/frameworks/kwidgetsaddons/html/classKCapacityBar.html "inline text" mode draws the text inside the bar "outline text" mode draws the text below the bar KInfoCenter uses the "outline text" mode. KCapacityBar::minimumSizeHint() assumes this layout. With Fusion style (which does not customize the rendering), the text is correctly drawn below the bar, and elided with trailing dots, if it does not fit completely. With Breeze style, the text is rendered to the right of the bar, and the bar and leading text characters vanish when it does not fit completely. Can KCapacityBar respect the different layout, in other words, is there some QStyle::sizeFromContents() for this custom ControlElements implemented in Breeze? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi
https://bugs.kde.org/show_bug.cgi?id=362941 --- Comment #14 from Stormi--- Just adding a comment to make sure it has been taken into account that the issue not limited to java applications. It has been reported both in this bug report and in the duplicate bug 358328 various applications that have the same issue: - easystroke - gajim - solaar - stardict - radiotray (gtk+3, not gtk+2, which is definitely a lead) About your "There is no need to ask for updates" comment, as a bug triager for the Mageia distro I totally expect users to ask whether someone is working on the bug they reported every few months. It's part of user / developer interaction. Here it had not been said until your comment that someone was going to have a look. This very bug has been reported first in january (see duplicates older than this one) and is one of the reasons we still haven't been able to release Mageia 6 to the public, since although we are a desktop-agnostic distro, KDE / Plasma is the most used desktop and we can't release with so many applications that can't be interacted with via the system tray. So maybe asking if someone is intending to work on it was not that misplaced after all, or was it? Anyway, thanks for your intention to diagnose the origin of the bug, be it in XembedSNIProxy or something else. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 371954] Gdrive doesn't show all files/folders
https://bugs.kde.org/show_bug.cgi?id=371954 --- Comment #4 from Michał Dybczak--- Created attachment 102039 --> https://bugs.kde.org/attachment.cgi?id=102039=edit Output of "journalctl -b | grep kf5.kio.gdrive" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349677] Crash when opening KMenu, Add Widgets, or networkmanagement
https://bugs.kde.org/show_bug.cgi?id=349677 --- Comment #25 from Kevin--- I no longer have this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348487] Plasma crashes after resuming from screen energy saving mode
https://bugs.kde.org/show_bug.cgi?id=348487 David Edmundsonchanged: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #3 from David Edmundson --- This is against an old version of Qt/Plasma and there has been no update or newer duplicates. Hopefully that implies this has been fixed in the many developments that have happened in Plasma and our supporting libraries. If it still occurs please open a new bug report with a more recent backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351596] Plasma Crash on Login
https://bugs.kde.org/show_bug.cgi?id=351596 David Edmundsonchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from David Edmundson --- This is against an old version of Qt/Plasma and there has been no update or newer duplicates. Hopefully that implies this has been fixed in the many developments that have happened in Plasma and our supporting libraries. If it still occurs please open a new bug report with a more recent backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349677] Crash when opening KMenu, Add Widgets, or networkmanagement
https://bugs.kde.org/show_bug.cgi?id=349677 David Edmundsonchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #24 from David Edmundson --- This is against an old version of Qt/Plasma and there has been no update or newer duplicates. Hopefully that implies this has been fixed in the many developments that have happened in Plasma and our supporting libraries. If it still occurs please open a new bug report with a more recent backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350877] Plasmashell crash while moving files in dolphin
https://bugs.kde.org/show_bug.cgi?id=350877 David Edmundsonchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from David Edmundson --- This is against an old version of Qt/Plasma and there has been no update or newer duplicates. Hopefully that implies this has been fixed in the many developments that have happened in Plasma and our supporting libraries. If it still occurs please open a new bug report with a more recent backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351462] After changing framebuffer-size plasmashell does not show anymore
https://bugs.kde.org/show_bug.cgi?id=351462 David Edmundsonchanged: What|Removed |Added Resolution|--- |WONTFIX CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- Sorry for ignoring this report. xrandr --scale has never been something that worked properly and it's not something we can support. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347013] Crashed when dragging menu items in the application menu
https://bugs.kde.org/show_bug.cgi?id=347013 David Edmundsonchanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- This is against an old version of Qt/Plasma and there has been no update or newer duplicates. If it still happens, please open a new bug report with a more recent backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341666] crashing with webview type [@ WebCore::TextureMapperLayer::addChild]
https://bugs.kde.org/show_bug.cgi?id=341666 David Edmundsonchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from David Edmundson --- This is against an old version of Qt/Plasma and there has been no update or newer duplicates. If it still happens, please open a new bug report with a more recent backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 352573] Plasma crashes when trying close KDE Connect widget
https://bugs.kde.org/show_bug.cgi?id=352573 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from David Edmundson --- This is against an old version of Qt/Plasma and there has been no update or newer duplicates. If it still happens, please open a new bug report with a more recent backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 --- Comment #47 from k...@hottier.com --- Hello, I have approximatively the same hardware than the one described in this bug. When I try to activate the OpenGL compositor, kwin becomes so slow that it is not usable anymore, the time between a mouse button click and the click handling is more than one minute. Xrender works fine. As far as I understood m00nraker and Sergei succeed to enable OpenGl compositor by disabling the selftest as described here : https://bugs.kde.org/show_bug.cgi?id=360033#c28 Unfortunately, it does not change anything for me as the test was successful. here is some output : (I tried with Kwin 5.8.2 too) qdbus org.kde.KWin /KWin supportInformation == Version === KWin version: 5.8.0 Qt Version: 5.6.1 Qt compile version: 5.6.1 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: 11804000 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, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: DejaVu Sans,10,-1,5,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 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: 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: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 99 glPlatformInterface: 1 windowsBlockCompositing: true 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: no Number of Screens: 1 Screen 0: - Name: DVI-I-1 Geometry: 0,0,1280x1024 Refresh Rate: 60.0197 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 6500/PCIe/SSE2 OpenGL version string: 2.1.2 NVIDIA 304.131 OpenGL platform interface: GLX OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 304.131 GPU class: NV40/G70 OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.18.4 Linux kernel version: 4.6 Direct rendering: Requires strict binding: no GLSL shaders: limited Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- blur Currently Active Effects: - blur Effect Settings: blur: blurRadius: 12 cacheTexture: true kwin_x11 --replace OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 6500/PCIe/SSE2 OpenGL version string: 2.1.2 NVIDIA 304.131 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 304.131 GPU class: NV40/G70 OpenGL version:
[kinfocenter] [Bug 372081] misinterpretation of system information
https://bugs.kde.org/show_bug.cgi?id=372081 --- Comment #3 from Christoph Feck--- Git commit 1fd35936668a168c19beb7c8def4f42380e43a4d by Christoph Feck. Committed on 04/11/2016 at 22:37. Pushed by cfeck into branch 'master'. Fix battery charge state display M +1-1Modules/devinfo/soldevicetypes.cpp http://commits.kde.org/kinfocenter/1fd35936668a168c19beb7c8def4f42380e43a4d -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371916] execution tree xtree concept
https://bugs.kde.org/show_bug.cgi?id=371916 --- Comment #10 from Philippe Waroquiers--- (In reply to Ivo Raisr from comment #8) > Sometimes the function name follows pattern: "XTthing_operation", > sometimes "operationXT" and sometimes something completely different. Fair enough. I will do a pass of pub_too_xtree.h and somewhat reduce my name creation creativity :) -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 372081] misinterpretation of system information
https://bugs.kde.org/show_bug.cgi?id=372081 Christoph Feckchanged: What|Removed |Added CC||cf...@kde.org --- Comment #2 from Christoph Feck --- ... decrease the size of the left section, or increase the size of the right section ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process
https://bugs.kde.org/show_bug.cgi?id=371889 David Edmundsonchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #5 from David Edmundson --- If there's high CPU usage we need some sort of log of what it's doing when using high CPU otherwise we can't do anything. Options are either: perf record -g -p `pidof plasmashell` or callgrind You can use callgrind remote to profile only part of a process: http://zariko.taba.free.fr/c++/callgrind_profile_only_a_part.html Both will need relevant permissions and debug symbols. Please reopen when you have something. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 372092] Re-identify automatically when coming back from away
https://bugs.kde.org/show_bug.cgi?id=372092 --- Comment #1 from Dan Dart--- I think it can only be reproduced by severing the connection whilst away, so new connections under the name/status of the away nick are by default not identified. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372079] Animation performance decrease as time goes on
https://bugs.kde.org/show_bug.cgi?id=372079 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from David Edmundson --- Thanks, but this is too vague to be a bug report. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 372054] KDE screen saver not working when VirtualBox guest is running.
https://bugs.kde.org/show_bug.cgi?id=372054 Christoph Feckchanged: What|Removed |Added CC||cf...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Christoph Feck --- The KDE 4 workspace is no longer maintained by KDE developers. If the issue is visible with Plasma 5.8, please add a comment or reopen the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 haoxian.z...@gmail.com changed: What|Removed |Added CC||haoxian.z...@gmail.com --- Comment #10 from haoxian.z...@gmail.com --- It seems I have this problem as well. But I am using Google calendar ICSs. However, the situation is a little different. At first, I could not tick on PIM Events Plugin because of the crash problem. Later, it worked. But I cannot remember from which version of Plasma but not too old because I started using openSUSE Tumbleweed several months ago. Now, after snapshot 20161102 update, when I click the clock in the bottom right of the taskbar to try to view the calendar, the Desktop stop responding and the indicator of disk IO keep shining meaning that something is reading disk, and `plasmashell` process eats all the memory. During this, the mouse hardly responses. So I have to hard power off my laptop. (I am newbie knowing very few tricks to continue in such circumstances.) So it seems that the problem is not relevant to ownCloud. Hopefully this info helps. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 372092] New: Re-identify automatically when coming back from away
https://bugs.kde.org/show_bug.cgi?id=372092 Bug ID: 372092 Summary: Re-identify automatically when coming back from away Product: konversation Version: 1.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: k...@dandart.co.uk Target Milestone: --- When I come back from global away, servers go and change my nick! I'd already set up identifying, so sounds like auto-identify does not happen when asked by NickServ, only on first connect. So I believe behaviour should be auto identify when asked at any occasion, especially after changing nick to saved value, not just on connect. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 339548] Can not enter an investment Dividend transaction
https://bugs.kde.org/show_bug.cgi?id=339548 geo...@wildturkeyranch.net changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371666] Plasma crashes irreversibly when enabling Holidays or scroling in Holidays' list
https://bugs.kde.org/show_bug.cgi?id=371666 --- Comment #16 from opensuse.lietuviu.ka...@gmail.com --- But I can not reprode crash during scroll of regions in Plasma 5.8.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372091] New: Plasma Crashes when Folder View widget is set to "Show a place"
https://bugs.kde.org/show_bug.cgi?id=372091 Bug ID: 372091 Summary: Plasma Crashes when Folder View widget is set to "Show a place" Product: plasmashell Version: 5.8.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sudokuusol...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I switched between the various options under Location in the Folder View settings window. When I choose "Show a place" and hit Apply, Plasma crashes. The only action which causes a crash is changing to "Show a place" from another option. - Once Plasma recovers, the option is kept and seems to work as intended. - Changing from "Show a place" to any other option does not cause Plasma to crash. - Changing the place of choice in the "Show a place" dropdown menu does not cause a crash. - Plasma only crashes again if the Location option is changed to something other than "Show a place", applied, then changed back again. - Custom settings of the application: All settings are default aside from changing the Location. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff68a04b800 (LWP 535))] Thread 9 (Thread 0x7ff59a3f7700 (LWP 1841)): #0 0x7ff67ea55db0 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7ff67ea0fed1 in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #2 0x7ff67ea106f8 in () at /usr/lib/libglib-2.0.so.0 #3 0x7ff67ea1089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7ff68406a72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff68401423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7ff683e370f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7ff68719a2d5 in () at /usr/lib/libQt5Qml.so.5 #8 0x7ff683e3bd78 in () at /usr/lib/libQt5Core.so.5 #9 0x7ff682f4b454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7ff6837517df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7ff5c2b6c700 (LWP 971)): #0 0x7ff68374848d in poll () at /usr/lib/libc.so.6 #1 0x7ff67ea10786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff67ea1089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff68406a72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff68401423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff683e370f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ff5c50980a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7ff683e3bd78 in () at /usr/lib/libQt5Core.so.5 #8 0x7ff682f4b454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7ff6837517df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7ff5d5bad700 (LWP 755)): #0 0x7ff68374848d in poll () at /usr/lib/libc.so.6 #1 0x7ff67ea10786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff67ea1089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff68406a72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff68401423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff683e370f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ff687d39856 in () at /usr/lib/libQt5Quick.so.5 #7 0x7ff683e3bd78 in () at /usr/lib/libQt5Core.so.5 #8 0x7ff682f4b454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7ff6837517df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7ff65700 (LWP 718)): #0 0x7ff682f5110f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff6897c9ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7ff6897c9b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7ff682f4b454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7ff6837517df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7ff66a39a700 (LWP 716)): #0 0x7ff67ea102e2 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #1 0x7ff67ea107f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff67ea1089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff68406a72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff68401423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5
[plasmashell] [Bug 371666] Plasma crashes irreversibly when enabling Holidays or scroling in Holidays' list
https://bugs.kde.org/show_bug.cgi?id=371666 --- Comment #15 from pitlochry--- @opensuse.lietuviu.ka...@gmail.com: Yes, you are right it is only _sometimes_ (perhaps in one of two cases) when enabling Holidays. But it is always, when scroling in Holidays' list. Thanks for your confirmation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372090] New: Plasma show events only after second enable of holidays
https://bugs.kde.org/show_bug.cgi?id=372090 Bug ID: 372090 Summary: Plasma show events only after second enable of holidays Product: plasmashell Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: opensuse.lietuviu.ka...@gmail.com Target Milestone: 1.0 Created attachment 102038 --> https://bugs.kde.org/attachment.cgi?id=102038=edit video.webm Strange, that when I select to show holidays event in calendar, it don't display events in calendar at first try. After dissable and re-enable - it shows. (However, few times plasma crashed after first enable (not always). ) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 371721] slaveinterface.cpp do not compile under Centos 6.8
https://bugs.kde.org/show_bug.cgi?id=371721 --- Comment #12 from caulier.gil...@gmail.com --- [gilles@localhost kio]$ pwd /home/gilles/devel/kio [gilles@localhost kio]$ ls autotests CMakeCache.txt cmake_install.cmake COPYING.LIB docs KF5KIOConfig.cmake KF5KIOConfigVersion.cmake metainfo.yaml src cmake CMakeFiles CMakeLists.txt CTestTestfile.cmake ecm_uninstall.cmake KF5KIOConfig.cmake.in Makefile README.md tests [gilles@localhost kio]$ grep -r open64 src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:extern FILE *fopen (__const char *__restrict __filename, __const char *__restrict __modes) __asm__ ("" "fopen64") src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:extern FILE *freopen (__const char *__restrict __filename, __const char *__restrict __modes, FILE *__restrict __stream) __asm__ ("" "freopen64") src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:extern FILE *fopen64 (__const char *__restrict __filename, src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:extern FILE *freopen64 (__const char *__restrict __filename, src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:extern int open (__const char *__file, int __oflag, ...) __asm__ ("" "open64") src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:extern int open64 (__const char *__file, int __oflag, ...) __attribute__ ((__nonnull__ (1))); src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o: "KIO::filesize_t\0open64\0written\0metaData\0" src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:case 10: _t->open64(); break; src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:if (*reinterpret_cast<_t *>(func) == static_cast<_t>(::open64)) { src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o:void KIO::SlaveInterface::open64() src/core/moc_slaveinterface.cpp:QT_MOC_LITERAL(15, 166, 6), // "open64" src/core/moc_slaveinterface.cpp: "KIO::filesize_t\0open64\0written\0metaData\0" src/core/moc_slaveinterface.cpp:case 10: _t->open64(); break; src/core/moc_slaveinterface.cpp:if (*reinterpret_cast<_t *>(func) == static_cast<_t>(::open64)) { src/core/moc_slaveinterface.cpp:void KIO::SlaveInterface::open64() [gilles@localhost kio]$ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371666] Plasma crashes irreversibly when enabling Holidays or scroling in Holidays' list
https://bugs.kde.org/show_bug.cgi?id=371666 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added CC||opensuse.lietuviu.kalba@gma ||il.com --- Comment #14 from opensuse.lietuviu.ka...@gmail.com --- I can _sometimes_ (not always) reproduce plasma 5.8.2 (in openSUSE 42.2 RC2) crash after enabling "Holidays" at "Available calendar plugins" or after selecting regions for holidays and pressing Applay. However KDE bug application waits for very long time and don't produce backtrace. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 371721] slaveinterface.cpp do not compile under Centos 6.8
https://bugs.kde.org/show_bug.cgi?id=371721 --- Comment #11 from caulier.gil...@gmail.com --- As explained before, this only happen under 32 Centos 6.8, not 64 bits version. Centos is used to create 32 bits and 64 bits AppImage bundles for my office. Typically, Kate and QtCreator (and more KF5 applications later) are used to develop real time acquisition codes on an experimental Tokamak. We use Centos 6, for legacy reasons, to be compatible with hardwares. And we want to use a modern code editor as Kate, especially in 32 bits, instead official GEdit under Centos 6, which is just a dinosaur. So, as i need to compile whole Qt5/KF5 with a C++11 compatible compiler, i need a more recent version of GCC under Centos 6. With a 64 bits system, we have plenty of repos with different versions of GCC, supported by Centos 6. With a 32 bits system, nothing. I need to use CERN Centos repo where a GCC is available. This can explain the difference between 32 and 64 bits, even if GCC version is the same for both. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372089] New: Chromium
https://bugs.kde.org/show_bug.cgi?id=372089 Bug ID: 372089 Summary: Chromium Product: kwin Version: 5.8.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: paul.zrexx...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.4-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Chromium loaded then, dialog box for "Chromium ... 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 0x7f27644f1940 (LWP 2635))] Thread 5 (Thread 0x7f273ecb5700 (LWP 3057)): #0 0x7f2763e7d751 in ppoll () at /lib64/libc.so.6 #1 0x7f2761553b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f2761555428 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f27615021ea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f27613308b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f275bccba75 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f2761335558 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f275d19a454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2763e8639f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f272e8c4700 (LWP 2742)): #0 0x7f275d1a010f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f27604bd834 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f27604bd879 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f275d19a454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2763e8639f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f273dd71700 (LWP 2727)): #0 0x7f2763e7d751 in ppoll () at /lib64/libc.so.6 #1 0x7f2761553b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f2761555428 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f27615021ea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f27613308b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f275bccba75 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f2761335558 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f275d19a454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2763e8639f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f274cff0700 (LWP 2651)): #0 0x7f2763e7d68d in poll () at /lib64/libc.so.6 #1 0x7f2758976876 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f275897698c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f276155879b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f27615021ea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f27613308b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f275aea43e5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f2761335558 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f275d19a454 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2763e8639f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f27644f1940 (LWP 2635)): [KCrash Handler] #6 0x7f275bcb7130 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #7 0x7f275bcb8095 in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #8 0x7f275bcc1d35 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f275bc4b5fe in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5 #10 0x7f275bc4b6c7 in QQmlComponentPrivate::completeCreate() () at /usr/lib64/libQt5Qml.so.5 #11 0x7f275bc4b530 in QQmlComponent::create(QQmlContext*) () at /usr/lib64/libQt5Qml.so.5 #12 0x7f273dd914b7 in () at /usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so #13 0x7f2763aa6d39 in () at /usr/lib64/libkwin.so.5 #14 0x7f2763988229 in KWin::Client::createDecoration(QRect const&) () at /usr/lib64/libkwin.so.5 #15 0x7f2763988bed in KWin::Client::updateDecoration(bool, bool) () at /usr/lib64/libkwin.so.5 #16 0x7f27639e75b5 in KWin::Client::manage(unsigned int, bool) () at /usr/lib64/libkwin.so.5 #17 0x7f276396b7e4 in KWin::Workspace::createClient(unsigned int, bool) () at /usr/lib64/libkwin.so.5 #18 0x7f27639d47c7 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /usr/lib64/libkwin.so.5 #19 0x7f276150132f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /usr/lib64/libQt5Core.so.5 #20
[Network Management] [Bug 262475] wireless connection not accessable
https://bugs.kde.org/show_bug.cgi?id=262475 syed abdul khayyumchanged: What|Removed |Added CC||abdulkhayyu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372068] Kate 3.13.3 randomly switches keyboard layout
https://bugs.kde.org/show_bug.cgi?id=372068 --- Comment #2 from Dominik Haumann--- *** Bug 372069 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372069] Kate 3.13.3 randomly switches keyboard layout
https://bugs.kde.org/show_bug.cgi?id=372069 Dominik Haumannchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Dominik Haumann --- *** This bug has been marked as a duplicate of bug 372068 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372068] Kate 3.13.3 randomly switches keyboard layout
https://bugs.kde.org/show_bug.cgi?id=372068 --- Comment #1 from Dominik Haumann--- Do you maybe accidentally hit the global keyboard shortcut for keyboard layout switches (e.g. Ctrl+Alt+k or similar, don't know exactly) ? In any case, please upgrade to a newer version of KDE Plasma and Kate. You can also use a current version of Kate through the AppImage (make it executable and start it), see https://kate-editor.org/get-it/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372088] New: ungrouped clip cannot be moved if both were selected during ungroup operation
https://bugs.kde.org/show_bug.cgi?id=372088 Bug ID: 372088 Summary: ungrouped clip cannot be moved if both were selected during ungroup operation Product: kdenlive Version: git-master Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: s_chriscoll...@hotmail.com Target Milestone: --- When both clips of a group are selected prior to the ungroup operation, one of the clips will be unmovable afterward. Steps to reproduce: 1. Drag a video clip that has sound onto a track (in my case, "Video 3"). 2. Right-click the video clip on the timeline and select "Split Audio". 3. THIS STEP IS IMPORTANT: Ctrl-click the audio clip so that both the video and audio clip are selected. 4. Right-click on the video clip and select "Ungroup Clips". 5. Now, try to drag the audio clip on the timeline. Result: The audio clip is unmovable. If you right-click the audio clip in step 4 instead of the video clip, then the video clip will be the one that is unmovable. Tested using Kdenlive 16.11.70 w/ MLT 6.3.0 OS: KDE Neon 5.8.3 64-bit (Plasma Desktop 5.8.3, KDE Frameworks 5.27.0, Qt 5.7.0) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before
https://bugs.kde.org/show_bug.cgi?id=371990 --- Comment #8 from clush...@gmx.net --- Created attachment 102037 --> https://bugs.kde.org/attachment.cgi?id=102037=edit Patch to fix crash: Remove PinPortBase objects when owner is removed - rebased -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before
https://bugs.kde.org/show_bug.cgi?id=371990 --- Comment #7 from clush...@gmx.net --- Thank's for commit the first part already. I've rebased and retested the fix for the crash, and found another issue when selecting both component and attached pin. That's fixed as well with the new patch. I tried the suggested child/parent cleanup, but encounter several problems with this. Briefly, the PinPortBase is a subclass of UMLWidget, but this class is meant to represent root graphic items. The PinPortBase would be a child widget, and needs to behave differently, e.g. when moving the parent component. I'll continue to work on this. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 372067] Can't reach folder of selected file after clicking a file on the found files window
https://bugs.kde.org/show_bug.cgi?id=372067 Alex Bikadorovchanged: What|Removed |Added CC||alex.bikado...@kdemail.net --- Comment #2 from Alex Bikadorov --- Thanks for reporting -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 372067] Can't reach folder of selected file after clicking a file on the found files window
https://bugs.kde.org/show_bug.cgi?id=372067 Alex Bikadorovchanged: What|Removed |Added Latest Commit||http://commits.kde.org/krus ||ader/4e2ba6e91413d12fdfd31d ||6c23d862f6ffcf5c63 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Alex Bikadorov --- Git commit 4e2ba6e91413d12fdfd31d6c23d862f6ffcf5c63 by Alexander Bikadorov. Committed on 04/11/2016 at 18:59. Pushed by abikadorov into branch 'master'. FIXED: [ 372067 ] Wrong path when showing non local files and folders from search dialog in panel Bug came with 1da1b23f M +6-1krusader/Search/krsearchdialog.cpp http://commits.kde.org/krusader/4e2ba6e91413d12fdfd31d6c23d862f6ffcf5c63 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 372087] New: climbs description
https://bugs.kde.org/show_bug.cgi?id=372087 Bug ID: 372087 Summary: climbs description Product: Discover Version: 5.6.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: pek...@mail.ru Target Milestone: --- Created attachment 102036 --> https://bugs.kde.org/attachment.cgi?id=102036=edit screenshot of the screen descriptions in the preview are outside the boundaries of the drawing -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 339548] Can not enter an investment Dividend transaction
https://bugs.kde.org/show_bug.cgi?id=339548 --- Comment #21 from geo...@wildturkeyranch.net --- On 10/05/14 15:34, allan wrote: > https://bugs.kde.org/show_bug.cgi?id=339548 > > --- Comment #6 from allan--- > May this now be closed? > This is so far in the past that I have lost track of what it is. Yes, please close. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371497] Wishlist: Add option to launch application on discrete GPU
https://bugs.kde.org/show_bug.cgi?id=371497 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 372082] Screenlocker is to large for smaller resolutions (1024x600)
https://bugs.kde.org/show_bug.cgi?id=372082 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||k...@davidedmudnson.co.uk Ever confirmed|0 |1 --- Comment #1 from Martin Gräßlin --- Adding David as the expert for the theme -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps
https://bugs.kde.org/show_bug.cgi?id=371877 --- Comment #11 from Martin Gräßlin--- To explain a little bit: on X11 it's possible for a window to grab the keyboard. If a window does that all key events are sent to that window and not to others. So if e.g. Virtual Box has grabbed the key events, the global shortcut (like Alt+Tab) cannot be activated as kglobalacceld5 does not get the events. If the global shortcut activates, it means the window has not grabbed the shortcut. And that's something you can verify with the grab tool. Overall it sounds more like you have problems with those applications than with our software. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356141] virtual desktop ?
https://bugs.kde.org/show_bug.cgi?id=356141 Lukáš Karaschanged: What|Removed |Added CC||lukas.ka...@centrum.cz --- Comment #2 from Lukáš Karas --- I got similar stacktrace when I restarted kded5 process and it turn off my external monitor (keep just notebook display). I have Kubuntu 16.10 kwin 5.7.5 Qt 5.6.1 Intel graphics card Backtrace k pádu, na který jsem narazil/a: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa275910940 (LWP 4388))] Thread 8 (Thread 0x7fa1d8bff700 (LWP 14354)): #0 0x7fa28c3d2ea3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa28a254caf in qt_safe_select (nfds=21, fdread=fdread@entry=0x7fa1c8000a58, fdwrite=fdwrite@entry=0x7fa1c8000ce8, fdexcept=fdexcept@entry=0x7fa1c8000f78, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fa28a256754 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fa1c8000f78, writefds=0x7fa1c8000ce8, readfds=0x7fa1c8000a58, nfds=, this=0x7fa1c80b00b0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa1c80008c0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7fa28a256c6a in QEventDispatcherUNIX::processEvents (this=0x7fa1c80b00b0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7fa28a2010fa in QEventLoop::exec (this=this@entry=0x7fa1d8bfec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fa28a026d43 in QThread::exec (this=this@entry=0x559902cdb170) at thread/qthread.cpp:500 #7 0x7fa284ad7c65 in QQmlThreadPrivate::run (this=0x559902cdb170) at qml/ftw/qqmlthread.cpp:141 #8 0x7fa28a02bc68 in QThreadPrivate::start (arg=0x559902cdb170) at thread/qthread_unix.cpp:341 #9 0x7fa28597970a in start_thread (arg=0x7fa1d8bff700) at pthread_create.c:333 #10 0x7fa28c3dd0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7fa25bfff700 (LWP 9779)): #0 0x7fa28c3d2ea3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa28a254caf in qt_safe_select (nfds=17, fdread=fdread@entry=0x7fa1d4000a78, fdwrite=fdwrite@entry=0x7fa1d4000d08, fdexcept=fdexcept@entry=0x7fa1d4000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fa28a256754 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fa1d4000f98, writefds=0x7fa1d4000d08, readfds=0x7fa1d4000a78, nfds=, this=0x7fa1d40008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa1d40008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7fa28a256c6a in QEventDispatcherUNIX::processEvents (this=0x7fa1d40008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7fa28a2010fa in QEventLoop::exec (this=this@entry=0x7fa25bffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fa28a026d43 in QThread::exec (this=this@entry=0x55990577fb10) at thread/qthread.cpp:500 #7 0x7fa284ad7c65 in QQmlThreadPrivate::run (this=0x55990577fb10) at qml/ftw/qqmlthread.cpp:141 #8 0x7fa28a02bc68 in QThreadPrivate::start (arg=0x55990577fb10) at thread/qthread_unix.cpp:341 #9 0x7fa28597970a in start_thread (arg=0x7fa25bfff700) at pthread_create.c:333 #10 0x7fa28c3dd0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7fa264e28700 (LWP 9778)): #0 0x7fa28c3d2ea3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa28a254caf in qt_safe_select (nfds=16, fdread=fdread@entry=0x7fa1cc01eff8, fdwrite=fdwrite@entry=0x7fa1cc01f288, fdexcept=fdexcept@entry=0x7fa1cc01f518, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fa28a256754 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fa1cc01f518, writefds=0x7fa1cc01f288, readfds=0x7fa1cc01eff8, nfds=, this=0x7fa1cc0008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa1cc01ee60, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7fa28a256c6a in QEventDispatcherUNIX::processEvents (this=0x7fa1cc0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7fa28a2010fa in QEventLoop::exec (this=this@entry=0x7fa264e27c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fa28a026d43 in QThread::exec (this=this@entry=0x559903864120) at thread/qthread.cpp:500 #7 0x7fa284ad7c65 in QQmlThreadPrivate::run (this=0x559903864120) at qml/ftw/qqmlthread.cpp:141 #8 0x7fa28a02bc68 in QThreadPrivate::start (arg=0x559903864120) at
[krita] [Bug 363968] Preview thumbnail in .kra/.ora files are sometimes cropped instead of full canvas
https://bugs.kde.org/show_bug.cgi?id=363968 --- Comment #5 from Raghavendra kamath--- Created attachment 102035 --> https://bugs.kde.org/attachment.cgi?id=102035=edit preview.png which is corrupted -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 372086] New: Make configuration option for LZO compression of OpenVPN connection tri-state
https://bugs.kde.org/show_bug.cgi?id=372086 Bug ID: 372086 Summary: Make configuration option for LZO compression of OpenVPN connection tri-state Product: plasma-nm Version: 5.8.3 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: editor Assignee: lu...@kde.org Reporter: matthias.h.na...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- The graphical editor has a checkbox to either enable or disable the LZO compression of OpenVPN connections. This option is translats to "comp-lzo=no" or "comp-lzo=yes" respectively in the corresponding configuration file under /etc/NetworkManager/. At the level of OpenVPN this corresponds to the equally named option. Howerver, this option is tri-state and can be left unconfigured which has a different meaning than "yes" or "no". See man page of OpenVPN. If at the client side either "comp-lzo=no" or "comp-lzo=yes" and at the server side the configuration is left unspecified under certain conditions the connection can be successfully established but become useless due to LZO errors Nov 03 21:09:56 nm-openvpn[17410]: OpenVPN 2.3.12 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Oct 30 2016 Nov 03 21:09:56 nm-openvpn[17410]: library versions: OpenSSL 1.0.2j 26 Sep 2016, LZO 2.08 Nov 03 21:09:57 nm-openvpn[17410]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 03 21:09:57 nm-openvpn[17410]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay Nov 03 21:09:57 nm-openvpn[17410]: Attempting to establish TCP connection with [AF_INET]193.197.62.25:1194 [nonblock] Nov 03 21:09:58 nm-openvpn[17410]: TCP connection established with [AF_INET]193.197.62.25:1194 Nov 03 21:09:58 nm-openvpn[17410]: TCPv4_CLIENT link local: [undef] Nov 03 21:09:58 nm-openvpn[17410]: TCPv4_CLIENT link remote: [AF_INET]193.197.62.25:1194 Nov 03 21:09:59 nm-openvpn[17410]: WARNING: 'comp-lzo' is present in local config but missing in remote config, local='comp-lzo' Nov 03 21:09:59 nm-openvpn[17410]: [openvpn.scc.kit.edu] Peer Connection Initiated with [AF_INET]193.197.62.25:1194 Nov 03 21:10:01 nm-openvpn[17410]: TUN/TAP device tap0 opened Nov 03 21:10:01 nm-openvpn[17410]: /usr/libexec/nm-openvpn-service-openvpn-helper --debug 0 17403 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_1 --tap -- tap0 1500 1592 141.3.200.95 255.255.255.0 init Nov 03 21:10:01 nm-openvpn[17410]: GID set to nm-openvpn Nov 03 21:10:01 nm-openvpn[17410]: UID set to nm-openvpn Nov 03 21:10:01 nm-openvpn[17410]: Initialization Sequence Completed Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 255 Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 255 Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 255 Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 51 This behaviour is expected and reproducible. If one edits the configuration file under /etc/NetworkManager/ manually be means of a text editor and removes the "comp-lzo=" directive from the configuration file, everything works as expected. However, as soon as one opens the connection in the graphical connection editor again, the "comp-lzo" directive is re-inserted into the configuration file and set to whatever the checkbox state is in. After that the OpenVPN connection does not work and one must edit the configuration file again. Proposed solution: Make the checkbox tri-state. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363968] Preview thumbnail in .kra/.ora files are sometimes cropped instead of full canvas
https://bugs.kde.org/show_bug.cgi?id=363968 Raghavendra kamathchanged: What|Removed |Added CC||raghavendr.ra...@gmail.com --- Comment #4 from Raghavendra kamath --- I found that after the commits for this bug. the preview.png that gets generated is mostly horrizontal lines and noise the so the previews are corrupted or not correct. an example preview.png extracted from the kra saved from krita after these commits can be viewed here -> https://dl.dropboxusercontent.com/u/3793/preview.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 --- Comment #8 from sk-os--- There's still something strange going on in 5.8.2. After changing my screen setup - unplugged external monitor or switched over to another hdmi port - I get a default background at the next boot on my secondary monitor. So the wallpaper and the widgets are reset. primary monitor stays normal. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 371890] kded5 always crashes when running screenfetch
https://bugs.kde.org/show_bug.cgi?id=371890 Fabian Maurerchanged: What|Removed |Added CC||dark.shad...@web.de --- Comment #2 from Fabian Maurer --- Thanks, had exactly the same issue on Arch with qt-base 5.7.0. The problem was indeed solved by installing the latest git version. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 372085] New: KMail 5.3.2: forwarding or replying to html mails do not preserve links
https://bugs.kde.org/show_bug.cgi?id=372085 Bug ID: 372085 Summary: KMail 5.3.2: forwarding or replying to html mails do not preserve links Product: kmail2 Version: 5.3.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Created attachment 102034 --> https://bugs.kde.org/attachment.cgi?id=102034=edit example email with embedded links When forwarding replying an HTML mail -tags are not preserved. Steps to reproduce: import the attached email and forward it. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 353026] KRunner closes when focus is lost
https://bugs.kde.org/show_bug.cgi?id=353026 frederik.sch...@gmail.com changed: What|Removed |Added CC||frederik.sch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369051] Too low similarity threshold in fuzzy/duplicate search bloats the results with potentially unwished high-similarity results [patch]
https://bugs.kde.org/show_bug.cgi?id=369051 --- Comment #2 from caulier.gil...@gmail.com --- Mario, The patch is very interesting and well implemented. I plan to introduce your code after 5.3.0. Q : currently, the icon view of fuzzy searches result is not filter by average order. All items found are mixed. It can be a good idea to sort item in this view, this will increase the usability. Your viewpoint ? Best Gilles Caulier -- 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 #2 from RJ--- (In reply to Martin Gräßlin from comment #1) > Could you please provide some information on what you did to get this crash? Sorry, I don't know. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371478] Job Queue does not declare completed a rendering despite having concluded.
https://bugs.kde.org/show_bug.cgi?id=371478 Wegwerfchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Wegwerf --- So I now finally saw this for one of my projects too, so I'm confirming. However, this is not reproducible at 100% and it does not happen to all projects, but only to some. How to reproduce (hopefully): this is a freshly created project where I render the timeline into several parts (using guides). I then add several rendering jobs from the same project to the job queue, and at the same time explicitly start all rendering jobs so they run in parallel. Typically, from 6 or 7 rendering jobs running in parallel, at least 1 or 2 get stuck at the final one or two seconds, despite the rendering having finished properly as I can see from the final video file. In addition, the .txt MLT render XML input files never get correctly cleaned up; this happens to both finished and hung jobs. The hanging jobs were running for several minutes, so this happens not only to quick jobs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]
https://bugs.kde.org/show_bug.cgi?id=123097 --- Comment #29 from caulier.gil...@gmail.com --- ok, Also, i see in Setup dialog databse page that some TODO are not yet implemented, especially for the GUI. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]
https://bugs.kde.org/show_bug.cgi?id=123097 --- Comment #28 from Jan Wolter--- Hello Gilles, thanks for your help. I will show your code the next days and complete the fix for this issue. @Note 1: Ok, I will replace tabs by blanks. @Note 2: You are right, "@eaDir" is still hard-coded, but with adjusted patch I should be able to use the new settings from DbEngineParameters. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372020] Ungrouped clips don't stay ungrouped.
https://bugs.kde.org/show_bug.cgi?id=372020 Wegwerfchanged: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Edward, can you supply a minimized project that triggers this behavior? Did you create the project also with Kdenlive 16.08.2? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371871] Missing ZOOM SLIDER for PROJECT MONITOR.
https://bugs.kde.org/show_bug.cgi?id=371871 Wegwerfchanged: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #5 from Wegwerf --- I would rather like to see scrollbars getting implemented, as they are also used in other places, such as the title editor, and the timeline. This would give a consistent UI experience to novice users, while advanced users may use the shortcut using Shift+Ctrl+Wheel. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372084] git master: rendering dialog: opening file/directory selector ignores currently set path/file name
https://bugs.kde.org/show_bug.cgi?id=372084 Wegwerfchanged: What|Removed |Added Summary|Rendering dialog: opening |git master: rendering |file/directory selector |dialog: opening |ignores currently set |file/directory selector |path/file name |ignores currently set ||path/file name -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372084] Rendering dialog: opening file/directory selector ignores currently set path/file name
https://bugs.kde.org/show_bug.cgi?id=372084 Wegwerfchanged: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372084] New: Rendering dialog: opening file/directory selector ignores currently set path/file name
https://bugs.kde.org/show_bug.cgi?id=372084 Bug ID: 372084 Summary: Rendering dialog: opening file/directory selector ignores currently set path/file name Product: kdenlive Version: git-master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de Target Milestone: --- In the rendering dialog when clicking on the "folder" button next to the "output file" input field, the "open file" dialog which then opens ignores the path set in the "output file" input field. Instead, it always starts with the $HOME folder. This seems to be a regression, as formerly I think to remember that the "open file" dialog that opens from the rendering dialog correctly used the path as specified for the "output file", unless this is invalid. So the expected behavior is to restore the existing behavior, where "open file" uses the path given as "output file", unless it is invalid; only then it should revert to using $HOME as a sane fallback. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps
https://bugs.kde.org/show_bug.cgi?id=371877 --- Comment #10 from atmarx--- Thanks for being understanding. My apologies for sounding like an entitled jerk. It is a fresh install of KDE Neon -- I meant upgrade in the sense that I went from 5.7.5 in Kubuntu to 5.8.2 (now .3). I ended up reinstalling again since the other Neon install was only a few days old, and I must have messed something up with the shortcuts in the original install. Remmina and Virtualbox work mostly as you say, passing the combos through. Virtualbox though sometimes misses alt+f4 and prompts to close the VM instead of letting the VM handle alt+f4. TeamViewer is a mess, not capturing any alt or meta key combos. I've raised a bug with their devs, who are calling it a 'feature request' (when it provides a checkbox to capture and send key combos to the remote host and doesn't do that, I call it a bug, but whatever...) With respect to the key grabs, kglobalaccel5 has almost all of them -- I'm guessing each one is a specific combo and correlates to the global shortcuts? kwin_x11 has another handful. I'm not sure if the focus has to be in Teamviewer or VB, but with both of them up and running (a VM loaded in VB and a remote connection in TV), the logs aren't reporting any grabs for them. If the grabs only register when the focus is on the apps, should I set a cron job to run it and then leave the app focused? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372083] New: Task Switcher visualization stuck on "Breeze"
https://bugs.kde.org/show_bug.cgi?id=372083 Bug ID: 372083 Summary: Task Switcher visualization stuck on "Breeze" Product: systemsettings Version: 5.8.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: caip...@fastmail.fm Target Milestone: --- After the latest Neon updates, I can't change my Task Switcher visualization. Selecting any option other than Breeze and clicking on "Apply" has no effect, and closing and opening the settings window again revert the changes made. KDE Neon 5.8.3 (user edition). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 372082] New: Screenlocker is to large for smaller resolutions (1024x600)
https://bugs.kde.org/show_bug.cgi?id=372082 Bug ID: 372082 Summary: Screenlocker is to large for smaller resolutions (1024x600) Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: breeze-theme Assignee: plasma-b...@kde.org Reporter: plusf...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Created attachment 102033 --> https://bugs.kde.org/attachment.cgi?id=102033=edit picture to show the "bug" on smaller resolutions, like 1024x600, the time is shown half outside the screen, while below the input field there is enough space left. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 372081] New: misinterpretation of system information
https://bugs.kde.org/show_bug.cgi?id=372081 Bug ID: 372081 Summary: misinterpretation of system information Product: kinfocenter Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: looser...@gmail.com Target Milestone: --- Here, I just came across these weird things in k-infocenter. I'm uploading attachments. In-case of memory, I have used 74% out of 400GB, remaining amount which should amount to around 80-90GB free memory, but it shows I have only 0.8GB free. I have included 2 screenshots of similar problem. Another one is information is regarding my battery, where it displays my battery is fully charged, but it isn't, and my battery notification shows it is 78% and discharging. Here's the link for screenshots: https://drive.google.com/open?id=0Bw1lzCYKRpNqMzBlNjZvaERlWUk -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371897] Invalid Modified date for files in FTP mode
https://bugs.kde.org/show_bug.cgi?id=371897 Alex Bikadorovchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #12 from Alex Bikadorov --- > Still, it turns out that when Krusader 2.5.0 is installing on KDE4 it pulls > not all dependencies for Qt5. This is a problem with the package you installed. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371737] Lost config and bookmarks after update to 2.5
https://bugs.kde.org/show_bug.cgi?id=371737 --- Comment #9 from Alex Bikadorov--- Bookmarks are in another directory: Old path: /home/{user_directory}/.kde4/share/apps/krusader/ New path: /home/{user_directory}/.local/share/krusader/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372053] [new color selector] lag and weird rendering of color wheel for Filter > Color > Color to Alpha
https://bugs.kde.org/show_bug.cgi?id=372053 --- Comment #2 from David REVOY--- @wolthera : thank you! :) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 372080] New: Resuming from suspend while using docking station hangs the desktop
https://bugs.kde.org/show_bug.cgi?id=372080 Bug ID: 372080 Summary: Resuming from suspend while using docking station hangs the desktop Product: Powerdevil Version: 5.8.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: kamesh...@yahoo.co.in Target Milestone: --- Created attachment 102032 --> https://bugs.kde.org/attachment.cgi?id=102032=edit lspci.txt I have a HP ultraslim docking station and HP probook 650 G2. Normally suspend to RAM works. But when I use the docking station and then try to suspend, then resuming from suspend hangs the desktop. Screen is blank and keyboard does not work (backlight comes up and goes off). Forcing me to do hard reset. This happens even if I suspend the laptop after removing from the docking station. I am using KDE Neon user edition. KDE plasma version: 5.8.3 KDE Frameworks version: 5.27.0 Qt version: 5.7.0 Kernel version: 4.4.0-45 generic OS type: 64 bit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369622] KDE apps always use 32px icons in system tray
https://bugs.kde.org/show_bug.cgi?id=369622 --- Comment #8 from Guo Yunhe (郭云鹤)--- https://git.reviewboard.kde.org/r/129329/ This patch should fix the 22-22- ID prefix proglem. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 Till Schäferchanged: What|Removed |Added Version|Git (master)|5.3.2 Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||till2.schaefer@uni-dortmund ||.de --- Comment #14 from Till Schäfer --- i can confirm this bug for kmail 5.3.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 372076] Aggiunta di spesa bancaria su inserimento registri
https://bugs.kde.org/show_bug.cgi?id=372076 --- Comment #2 from Paolo Marchiori--- Grazie per la sollecita risposta , non ci avevo pensato. 2016-11-04 16:28 GMT+01:00 Jack : > https://bugs.kde.org/show_bug.cgi?id=372076 > > --- Comment #1 from Jack --- > If I understand correctly, you want to include Bank Expenses as part of an > existing transaction instead of needing to use a separate transaction. > You can > do this by using the "Split Transaction" which is the button to the right > of > the Category entry. It allows splitting a transaction into multiple > categories. > > Does this help? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 372076] Aggiunta di spesa bancaria su inserimento registri
https://bugs.kde.org/show_bug.cgi?id=372076 --- Comment #1 from Jack--- If I understand correctly, you want to include Bank Expenses as part of an existing transaction instead of needing to use a separate transaction. You can do this by using the "Split Transaction" which is the button to the right of the Category entry. It allows splitting a transaction into multiple categories. Does this help? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372079] New: Animation performance decrease as time goes on
https://bugs.kde.org/show_bug.cgi?id=372079 Bug ID: 372079 Summary: Animation performance decrease as time goes on Product: plasmashell Version: 5.8.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cristian...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Using magic lamp, as time goes on, animations that were once fluid become choppy and laggy until I reboot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371917] libinput device configuration does not persist across VT switches
https://bugs.kde.org/show_bug.cgi?id=371917 Martin Gräßlinchanged: What|Removed |Added Flags||ReviewRequest+ URL||https://phabricator.kde.org ||/D3264 --- Comment #3 from Martin Gräßlin --- Implementation for the idea outlined in comment #2 at https://phabricator.kde.org/D3264 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372032] Crash when opening file
https://bugs.kde.org/show_bug.cgi?id=372032 Kevin Funkchanged: What|Removed |Added Version|5.0.2 |git master -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372032] Crash when opening file
https://bugs.kde.org/show_bug.cgi?id=372032 Kevin Funkchanged: What|Removed |Added Version Fixed In||5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 354246] kde-open5 should open the original URL, not the one it was redirected to
https://bugs.kde.org/show_bug.cgi?id=354246 Jaumechanged: What|Removed |Added CC||minter...@gmail.com --- Comment #3 from Jaume --- Having the same issue here. Intranet links clicked within Slack opens in the browser as the login page. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371897] Invalid Modified date for files in FTP mode
https://bugs.kde.org/show_bug.cgi?id=371897 --- Comment #11 from aco...@gmail.com --- I more thoroughly installed Qt5, then set up Locales. Now everything is OK. The date format is what I need now. Thank you Still, it turns out that when Krusader 2.5.0 is installing on KDE4 it pulls not all dependencies for Qt5. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372032] Crash when opening file
https://bugs.kde.org/show_bug.cgi?id=372032 Kevin Funkchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdev ||platform/e53e0722e2a3abe35a ||5ef7633e95e2f140ef75b2 Status|UNCONFIRMED |RESOLVED --- Comment #3 from Kevin Funk --- Git commit e53e0722e2a3abe35a5ef7633e95e2f140ef75b2 by Kevin Funk. Committed on 04/11/2016 at 14:44. Pushed by kfunk into branch 'master'. Bump item repository version This is needed since we've changed the size of the Problem DUChain item in 08f7e619b0becbf021a7be2ad53ab53bce64f73f M +1-1CMakeLists.txt http://commits.kde.org/kdevplatform/e53e0722e2a3abe35a5ef7633e95e2f140ef75b2 -- You are receiving this mail because: You are watching all bug changes.