[kmymoney] [Bug 401180] Crash when creating account.
https://bugs.kde.org/show_bug.cgi?id=401180 Kai Uwe Broulik changed: What|Removed |Added Component|general |general Product|kde |kmymoney CC||k...@privat.broulik.de Assignee|unassigned-b...@kde.org |kmymoney-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 401182] Configure Desktop Crashed Plasma
https://bugs.kde.org/show_bug.cgi?id=401182 Kai Uwe Broulik changed: What|Removed |Added Product|kde |frameworks-kirigami Component|general |general CC||k...@privat.broulik.de Target Milestone|--- |Not decided Assignee|unassigned-b...@kde.org |notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351687] Desktop grid expands onto other screens during zoom-in animation
https://bugs.kde.org/show_bug.cgi?id=351687 bastimeyer...@gmail.com changed: What|Removed |Added Summary|Desktop grid on two |Desktop grid expands onto |monitors looks a little |other screens during |funny on exit |zoom-in animation -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 --- Comment #1 from Michail Vourlakos --- Comment on attachment 116393 --> https://bugs.kde.org/attachment.cgi?id=116393 Multiple gloabl keyboard shortcut entries. Are you using Multiple Layouts from Settings Window? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351687] Desktop grid on two monitors looks a little funny on exit
https://bugs.kde.org/show_bug.cgi?id=351687 bastimeyer...@gmail.com changed: What|Removed |Added CC||bastimeyer...@gmail.com --- Comment #2 from bastimeyer...@gmail.com --- This bug makes the desktop grid very annoying to use and has already prevented me many times to fully switch to the Plasma desktop environment. I'd really appreciate it if it could be fixed soon, as it has been reported more than 3 years ago. To add a bit more detail, imagine having 2 screens, a secondary one on the left hand side and the primary one on the right hand side, and you are using 9 workspaces in a 3x3 grid with the 5th workspace being the current active one (the one in the center). Zooming out and showing the desktop grid is working absolutely fine, but if you want to zoom back in, the grid of the secondary screen is being expanded onto the primary screen for the duration of the whole animation. This means that for a split second, the content of the 6th workspace of the secondary screen is being shown on the primary screen. What needs to be done here is that the expanding grid of the zoom-in animation has to be cropped on a per-screen basis, so that it doesn't expand onto the other screens. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401136] Color scheme names are not translatable
https://bugs.kde.org/show_bug.cgi?id=401136 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- It just uses the filename of the scheme. Perhaps we could introduce a Name= key to a [General] section of the .colors file, but that also needs wiring up scripty to extract those. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401151] docx files opened as archives in remote folders
https://bugs.kde.org/show_bug.cgi?id=401151 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Does this only happen with gdrive kio or also other remote locations like sftp, ftp, smb, etc? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401102] Screen can not be locked while viewing workspaces
https://bugs.kde.org/show_bug.cgi?id=401102 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Component|general |general Status|REPORTED|RESOLVED Product|kscreenlocker |kwin Resolution|--- |WORKSFORME Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org --- Comment #1 from Kai Uwe Broulik --- This cannot be fixed on X as this effect grabs the keyboard, but should work fine on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 277134] Shortcut grabbing doesn't work correctly when «Make Caps Lock an additional Ctrl» and «Meta on Left Ctrl» is set
https://bugs.kde.org/show_bug.cgi?id=277134 --- Comment #4 from Tore Anderson --- Yes, this is still not working correctly, but it behaves a bit different than in 2011. With the two options enabled (which are now named «Caps Lock is also a Ctrl» and «Left Ctrl as Meta»), this is the following results when attempting to grab/learn a new shortcut: - Physically pressing Caps Lock + Space: --- expected result: «Ctrl+Space» --- actual: «CapsLock, Ctrl+Space,Ctrl + ...» (the «...» indicates that it is still expecting more keypresses to complete the shortcut sequence) - Physically pressing Left Ctrl + Space: --- expected result: «Meta+Space» --- actual result: «Meta+Alt+Space,Alt+ ...» (again «...» - it is still listening for more keystrokes» Physicall pressing Left Windows + Space: --- expected result: «Meta+Space» --- actual result: «Meta+Space, Meta+ ..» (again «...»). I'm using Fedora 28 (kdelibs-4.14.38-6.fc28.x86_64). Tore -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401159] Screwed XFCE dark color themes after installing and using plasma-desktop with breeze-dark and oxygen design
https://bugs.kde.org/show_bug.cgi?id=401159 --- Comment #3 from Naquatis --- I found the solution to remove the style problems between KDE and XFCE on my old Arch Linux system I simply used: rm -rf ~/.gtkrc-2.0 and that helped to make the theming between both desktop environments consistent again. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 400720] Impossible to dismiss the app dashboard clicking on the empty area below search results
https://bugs.kde.org/show_bug.cgi?id=400720 --- Comment #2 from Eike Hein --- The problem is actually in ItemMultiGridView, and also affects the "All Applications" page (inbetween categories). -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 380746] Improvements to object name completion in R Console window
https://bugs.kde.org/show_bug.cgi?id=380746 Thomas Friedrichsmeier changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |wishlist CC||thomas.friedrichsmeier@ruhr ||-uni-bochum.de Summary|Completion list doesn't |Improvements to object name |work in the console |completion in R Console ||window --- Comment #10 from Thomas Friedrichsmeier --- Some of this is still valid. Converting into wishlist item. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401055] Transfer is reported as successful when Dolphin crashes
https://bugs.kde.org/show_bug.cgi?id=401055 --- Comment #5 from wg9rffujwz8y2...@airmail.cc --- I managed to find a way to crash. It's basically what I've said before (just saturate I/O) but using a slow 5400rpm HDD makes it reproducible. Crash 1 was rsync in the background + Dolphin making a transfer. When you try to access the slow disk (HDD) it crashes. And that failed transfer was reported as a sucess after the crash. Crash 2 is just rsync from my ssd to a slow HDD. Once you try to browse that disk on Dolphin it crashes. I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401055] Transfer is reported as successful when Dolphin crashes
https://bugs.kde.org/show_bug.cgi?id=401055 --- Comment #4 from wg9rffujwz8y2...@airmail.cc --- Created attachment 116399 --> https://bugs.kde.org/attachment.cgi?id=116399=edit Crash 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401055] Transfer is reported as successful when Dolphin crashes
https://bugs.kde.org/show_bug.cgi?id=401055 --- Comment #3 from wg9rffujwz8y2...@airmail.cc --- Created attachment 116398 --> https://bugs.kde.org/attachment.cgi?id=116398=edit Crash 1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 401150] Alt+Tab just shows a window in another workspace
https://bugs.kde.org/show_bug.cgi?id=401150 Aaron Honeycutt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389963] Tooltips take the whole horizontal screen when showing long download url
https://bugs.kde.org/show_bug.cgi?id=389963 Sourabh Sharma changed: What|Removed |Added CC||en17cs301...@medicaps.ac.in -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 --- Comment #3 from Steve Ramage --- Also FYI, this is affecting 5.14.3, but that option is not available in the version list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 --- Comment #2 from Steve Ramage --- Also a work around I have done is to simply map a keyboard short cut to the following shell script and run it: xrandr --output DP-3-2 --primary xrandr --output DP-3-1 --primary Besides the momentary flicker, it fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 --- Comment #1 from Steve Ramage --- This might be related to 372586, I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] New: Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 Bug ID: 401187 Summary: Maximized windows covered by plasma after monitor wake up Product: plasmashell Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ubu...@sjrx.net Target Milestone: 1.0 Created attachment 116397 --> https://bugs.kde.org/attachment.cgi?id=116397=edit Screenshot of issue. SUMMARY STEPS TO REPRODUCE 1. Setup triple monitor installation (maybe an issue with dual or single displays), two external and main laptop display 2. Maximize a window on the primary screen (the bottom of the window should stay above the plasma bar). 3. Turn off external display 1 and 2 3-a) Laptop display turns off automagically (not sure if this matters). 4. Wait 5 seconds. 5. Turn external displays back on 5-a) Laptop display turns on automagically. 6. Look at maximized window on primary display. OBSERVED RESULT Bottom of maximized window is below the plasma bar. EXPECTED RESULT Bottom of maximized window should be above the plasma bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Output of xrandr -q in this state: xrandr -q Screen 0: minimum 320 x 200, current 5120 x 2520, maximum 8192 x 8192 eDP-1 connected 1920x1080+1540+1440 (normal left inverted right x axis y axis) 309mm x 173mm 1920x1080 60.03 + 60.01* 59.9759.9659.9348.03 1680x1050 59.9559.88 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1280x800 59.9959.9759.8159.91 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 700x525 59.98 800x450 59.9559.82 640x512 60.02 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 640x400 59.8859.98 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-3-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 708mm x 398mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0024.0029.9723.98 1680x1050 59.88 1600x900 60.00 1280x1024 75.0260.02 1440x900 59.90 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-3-2 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 708mm x 398mm 2560x1440 59.95*+ 1920x1080 60.0059.94 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1440x900 59.89 1280x800 59.81 1152x864 75.00 1280x720 60.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-3-3 disconnected (normal left inverted right x axis y axis). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 346601] Allow automatic sorting for favorites in Application Launcher
https://bugs.kde.org/show_bug.cgi?id=346601 --- Comment #5 from Nate Graham --- What would make sense to me is a three-way sort option chooser: Sort by: () Program name () Program description () Manual ordering -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 397996] Missing icons for korganizer (appointment-recurring and appointment-reminder)
https://bugs.kde.org/show_bug.cgi?id=397996 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397989] Icons missing in agenda view
https://bugs.kde.org/show_bug.cgi?id=397989 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=397996 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 397996] Missing icons for korganizer (appointment-recurring and appointment-reminder)
https://bugs.kde.org/show_bug.cgi?id=397996 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=397989 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 342056] Ridiculously slow file copy (multiple small files)
https://bugs.kde.org/show_bug.cgi?id=342056 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=339830 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 339830] Slow file transfer (fish, sshfs)
https://bugs.kde.org/show_bug.cgi?id=339830 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=342056 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400713] Icon scale hdmi Kubuntu Neon
https://bugs.kde.org/show_bug.cgi?id=400713 --- Comment #9 from Nate Graham --- (In reply to Michal Janousek from comment #8) > Thank you for your willingness. I must set scale to 1.5 and font scale 140. That's your problem. Set one or the other, but not both. Try setting the scale to 1.5x and then adjusting the font *size* (not DPI) if you want text to be bigger. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499 --- Comment #11 from Matt Fagnani --- Memory leaks were detected with 8-9 definitely lost blocks, 48 indirectly lost blocks, and 19 possibly lost blocks per run. I'm unsure if the segmentation faults are related to those memory leaks. One line I wrote should have been Invalid reads/writes were common at other points in the stack. The invalid reads/writes of freed memory seem to have started earlier in the shutdown process than those which directly caused in the segmentation faults. Memory corruption might have been involved as a result of the use-after-frees. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401159] Screwed XFCE dark color themes after installing and using plasma-desktop with breeze-dark and oxygen design
https://bugs.kde.org/show_bug.cgi?id=401159 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Nate Graham --- Thanks, let us know if you ever find a reproducible test case! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499 --- Comment #10 from Matt Fagnani --- Created attachment 116396 --> https://bugs.kde.org/attachment.cgi?id=116396=edit valgrind --read-var-info=yes --log-file=valgrind-ksysguard-3.txt ksysguard output -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499 --- Comment #9 from Matt Fagnani --- Created attachment 116395 --> https://bugs.kde.org/attachment.cgi?id=116395=edit valgrind --log-file=valgrind-ksysguard-2.txt ksysguard output -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499 --- Comment #8 from Matt Fagnani --- Created attachment 116394 --> https://bugs.kde.org/attachment.cgi?id=116394=edit valgrind --log-file=valgrind-ksysguard-1.txt ksysguard output -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499 --- Comment #7 from Matt Fagnani --- I ran valgrind on ksysguard three times. valgrind showed invalid reads and writes each time after I closed ksysguard. 97 invalid reads and 23 invalid writes were listed on both of the first and third runs. 89 invalid reads and 19 invalid writes were listed on the second run. All the invalid reads and writes I looked at involved lines like "Address 0x1133204c is 36 bytes inside a block of size 132 free'd". I think that line meant that memory was being used after it had been freed or use-after-frees had been detected. Invalid reads/writes with similar traces to the segmentation faults which I reported before were shown. Invalid reads with a similar trace to the segmentation faults at operator==(QString const&, QString const&) (s1=..., s2=...) at tools/qstring.cpp:3153 were shown twice per run as in the following example ==3167== Invalid read of size 4 ==3167==at 0x67F9BAA: operator==(QString const&, QString const&) (qstring.cpp:3153) ==3167==by 0x5C6AF8E: QLabel::setText(QString const&) (qlabel.cpp:287) ==3167==by 0x48DD49B: TopLevel::answerReceived(int, QList const&) (ksysguard.cpp:450) ==3167==by 0x5231924: KSGRD::SensorAgent::processAnswer(char const*, int) (SensorAgent.cpp:186) ==3167==by 0x5238E8D: KSGRD::SensorShellAgent::msgRcvd() (SensorShellAgent.cpp:93) ==3167==by 0x6959B43: call (qobjectdefs_impl.h:376) ==3167==by 0x6959B43: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3754) ==3167==by 0x695A050: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3633) ==3167==by 0x68C70F4: QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) (moc_qprocess.cpp:362) ==3167==by 0x68CC8AA: QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) (qprocess.cpp:1070) ==3167==by 0x68CCE86: _q_canReadStandardOutput (qprocess.cpp:1081) ==3167==by 0x68CCE86: QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_qprocess.cpp:207) ==3167==by 0x6959A15: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3771) ==3167==by 0x695A050: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3633) ==3167== Address 0xe976c28 is 328 bytes inside a block of size 404 free'd ==3167==at 0x4836D85: operator delete(void*, unsigned int) (vg_replace_malloc.c:581) ==3167==by 0x5C6962A: QLabelPrivate::~QLabelPrivate() (qlabel.cpp:110) ==3167==by 0x6960D9B: cleanup (qscopedpointer.h:60) ==3167==by 0x6960D9B: ~QScopedPointer (qscopedpointer.h:107) ==3167==by 0x6960D9B: QObject::~QObject() (qobject.cpp:884) ==3167==by 0x5B5C095: QWidget::~QWidget() (qwidget.cpp:1564) ==3167==by 0x5C171A0: QFrame::~QFrame() (qframe.cpp:262) ==3167==by 0x5C6A5AA: QLabel::~QLabel() (qlabel.cpp:239) ==3167==by 0x5C6A5ED: QLabel::~QLabel() (qlabel.cpp:243) ==3167==by 0x695FEF2: QObjectPrivate::deleteChildren() (qobject.cpp:1997) ==3167==by 0x5B5BFFF: QWidget::~QWidget() (qwidget.cpp:1705) ==3167==by 0x5CECD5B: QStatusBar::~QStatusBar() (qstatusbar.cpp:251) ==3167==by 0x5CECD9D: QStatusBar::~QStatusBar() (qstatusbar.cpp:256) ==3167==by 0x695FEF2: QObjectPrivate::deleteChildren() (qobject.cpp:1997) ==3167== Block was alloc'd at ==3167==at 0x4835C89: operator new(unsigned int) (vg_replace_malloc.c:328) ==3167==by 0x5C69A6F: QLabel::QLabel(QWidget*, QFlags) (qlabel.cpp:213) ==3167==by 0x48DB080: TopLevel::TopLevel() (ksysguard.cpp:105) ==3167==by 0x48DEF92: kdemain (ksysguard.cpp:588) ==3167==by 0x1090CA: main (in /usr/bin/ksysguard) Invalid reads with a similar trace to the segmentation faults at QLabelPrivate::clearContents() at widgets/qlabel.cpp specifically at line 1309 were shown once per run as in the following example, although 14-20 other traces per run with QLabelPrivate::clearContents() at different lines of qlabel.cpp at the top of the stack were found. ==3167== Invalid read of size 4 ==3167==at 0x5C6A39D: QLabelPrivate::clearContents() (qlabel.cpp:1309) ==3167==by 0x5C6AFD4: QLabel::setText(QString const&) (qlabel.cpp:293) ==3167==by 0x48DD49B: TopLevel::answerReceived(int, QList const&) (ksysguard.cpp:450) ==3167==by 0x5231924: KSGRD::SensorAgent::processAnswer(char const*, int) (SensorAgent.cpp:186) ==3167==by 0x5238E8D: KSGRD::SensorShellAgent::msgRcvd() (SensorShellAgent.cpp:93) ==3167==by 0x6959B43: call (qobjectdefs_impl.h:376) ==3167==by 0x6959B43: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3754) ==3167==by 0x695A050: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3633) ==3167==by 0x68C70F4: QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) (moc_qprocess.cpp:362) ==3167==by 0x68CC8AA: QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) (qprocess.cpp:1070) ==3167==by 0x68CCE86: _q_canReadStandardOutput
[kdenlive] [Bug 401186] New: MLT thread settings messes up timeline scrubbing
https://bugs.kde.org/show_bug.cgi?id=401186 Bug ID: 401186 Summary: MLT thread settings messes up timeline scrubbing Product: kdenlive Version: 18.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: cdfro...@gmail.com Target Milestone: --- Setting MLT processing threads higher than 1 messes up the timeline stopping you from scrubbing through the timeline/ EXPECTED RESULT being able to set my MLT processing threads to the amount of threads I have and be able to actually scrub through my timeline,this bug makes it almost impossible to edit a video. SOFTWARE/OS VERSIONS Kdenlive 18.08.2 Xubuntu 18.04 LTS (available in About System) KDE Plasma Version: N/A using XFCE KDE Frameworks Version: 5.44.0 Qt Version: Qt 5.9.5 ADDITIONAL INFORMATION Every time this happens I have to reset it to 1 just to be able to edit and when I want to render I need to change it so I have better render speeds/performance.. Kdenlive with MLT set to 1 thread (working) http://i.imgur.com/8H3Y09N.png Kdenlive after set to 6 as I have a 6 core 6 thread cpu 8600k cpu https://i.imgur.com/yMZLx69.png -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 342938] Background is a mess of white and gray patterns
https://bugs.kde.org/show_bug.cgi?id=342938 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.15.0 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/sys ||temsettings/ed4367d86a63240 ||23ba17624b6731f861f68f173 --- Comment #7 from Nate Graham --- Git commit ed4367d86a6324023ba17624b6731f861f68f173 by Nate Graham, on behalf of Jan Przybylak. Committed on 19/11/2018 at 02:32. Pushed by ngraham into branch 'master'. Remove the background gradient from icon view Summary: The icon view showed a very faint gradient in the background. It looked weird, broken and not really like a gradient for some reason. I think it looks better now. There are some screenshots attached to the bug report. FIXED-IN: 5.15.0 Reviewers: #vdg, ngraham Reviewed By: #vdg, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D16998 M +0-44 icons/CategoryDrawer.cpp https://commits.kde.org/systemsettings/ed4367d86a6324023ba17624b6731f861f68f173 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 398684] KDE Connect doesn't request storage permission on start.
https://bugs.kde.org/show_bug.cgi?id=398684 Roger E changed: What|Removed |Added CC||guruso...@gmail.com --- Comment #2 from Roger E --- Is this related to https://bugs.kde.org/show_bug.cgi?id=364571 and https://bugs.kde.org/show_bug.cgi?id=380022 ? I don't see any permissions prompts on my phone as shown in Nicolas Fella's screenshot, but am unable to browse phone files from computer. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 364571] Can't mount android filesystem on Dolphin
https://bugs.kde.org/show_bug.cgi?id=364571 Roger E changed: What|Removed |Added CC||guruso...@gmail.com --- Comment #6 from Roger E --- Similar issue here. Phone appears mounted in Dolphin sidebar and 2 folders show when selecting phone (google) - "All Files" and "Camera pictures". Clicking on either shows message "The file or folder /run/user/1000/16ec513c1576d9d5/storage/emulated/0 does not exist." similar to the previously attached screenshot from mathwiz2008. journalctl -b |grep kdeconnect returns nothing. Send files from phone, remote input, run command all work fine. Computer:- Kernel: 4.19.1-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.13.5 Distro: siduction 17.1.0 Patience - kde - (201703051755) (Debian Sid) kdeconnect:amd64/unstable 1.3.1-1 Phone:- Google Pixel running Android Pie -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 401185] New: RTL CTL
https://bugs.kde.org/show_bug.cgi?id=401185 Bug ID: 401185 Summary: RTL CTL Product: konsole Version: 18.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: ghavami...@hotmail.com Target Milestone: --- SUMMARY RTL scripts should start from the right side of the terminal, and adjust back to left with LTR Eg English. Most terminals do not make special provisions and align all of the text on the left, including Konsole, mlterm may be a reference exception STEPS TO REPRODUCE Type or paste RTL language eg Arabic, Farsi, Hebrew etc OBSERVED RESULT Left justification EXPECTED RESULT Right screen alignment SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 283333] Make it possible to drag windows around the screens in Present Windows like in Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=28 Gastón M. Tonietti changed: What|Removed |Added CC||gaston.tonie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 399275] Khelpcenter menu does not work (some parts of TreeView)
https://bugs.kde.org/show_bug.cgi?id=399275 Luigi Toscano changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/khe ||lpcenter/d2940a285b1b3657c5 ||1a45d85947dd0196249216 Resolution|--- |FIXED --- Comment #1 from Luigi Toscano --- Git commit d2940a285b1b3657c51a45d85947dd0196249216 by Luigi Toscano, on behalf of Aleksei Nikiforov. Committed on 19/11/2018 at 00:47. Pushed by ltoscano into branch 'Applications/18.12'. Contents items expanding issue Summary: There is contents tree on left side of application window of Khelpcenter. If you select "Single click to open files and directories" in application "System Settings" in menu "Input devices" -> "Mouse", upon single click on any expandable item in contents (let's for example take "Application Manuals" or "System Settings Modules") it expands, upon double click it swiftly expands and collapses back. If it's already expanded, it collapses, and on double click it collapses and expands back. However, if you select "Double click to open files and directories (select icons on first click)" in "System Settings", you no longer can expand/collapse any expandable items in Khelpcenter's contents tree using mouse clicks. You need to double click to expand it, and in best case you can see it swiftly expanding and collapsing back if it's collapsed, or vice versa if it's expanded. It looks like with "Double click" setting selected contents item receives two events on double click: "selected" and "double click". On first event "expanded/collapsed" state is toggled via explicit calls to corresponding functions (see function Navigator::slotItemSelected), on second event this state is toggled again, thus reverting it to original state. This patch sets a specific setting to get rid of second event and make behaviour similar no matter which mouse settings is used, "single click" or "double click". Reviewers: yurchor, mlaurent, ltoscano Reviewed By: ltoscano Subscribers: pavelmos, ltoscano, kde-doc-english Tags: #documentation Differential Revision: https://phabricator.kde.org/D16352 M +1-0navigator.cpp https://commits.kde.org/khelpcenter/d2940a285b1b3657c51a45d85947dd0196249216 -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 399274] Duplicated menu items in khelpcenter
https://bugs.kde.org/show_bug.cgi?id=399274
Luigi Toscano changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/khe
||lpcenter/3e5549ebe181560d92
||e803cccfde58ebc3573625
Status|REPORTED|RESOLVED
--- Comment #1 from Luigi Toscano ---
Git commit 3e5549ebe181560d92e803cccfde58ebc3573625 by Luigi Toscano, on behalf
of Pavel Mars.
Committed on 19/11/2018 at 00:20.
Pushed by ltoscano into branch 'Applications/18.12'.
Remove duplicate submenus.
Summary:
Signed-off-by: Pavel Mars
Remove duplicate submenus.
On the left side of the khelpcenter window is the content ("Contents").
If you open the item "Application Manuals" -> "System" -> "Info Center", the
item "Info Center" will generate a tree of additional menu items.
If you open the menu item "KInfoCenter Modules" in the same content and then
open the menu items that appear (for example, "Device Viewer", "Memory",
"OpenGL" or any other item), the same additional menu item tree will be
generated.
This change removes duplication of generated trees.
This is achieved by registering the URLs of the elements of the content tree in
a separate container and checking the URL to be opened: if the base address
from the URL is registered, then we request the generation of the menu tree
from the registered element of the tree, but not from the current one.
Reviewers: yurchor, ltoscano
Reviewed By: yurchor, ltoscano
Subscribers: ltoscano, kde-doc-english
Tags: #documentation
Differential Revision: https://phabricator.kde.org/D16308
M +35 -1navigatorappitem.cpp
M +3-0navigatorappitem.h
https://commits.kde.org/khelpcenter/3e5549ebe181560d92e803cccfde58ebc3573625
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 329690] Built Tool View: Link to source file is not correct if make ran with the -C option
https://bugs.kde.org/show_bug.cgi?id=329690 ichramm changed: What|Removed |Added Version|4.6.0 |5.3.0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Platform|Archlinux Packages |Neon Packages --- Comment #3 from ichramm --- Bug persists in 5.3.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389551] kwin_wayland crash when monitor is switched off (or input is changed)
https://bugs.kde.org/show_bug.cgi?id=389551 Andrius Štikonas changed: What|Removed |Added CC||andr...@stikonas.eu -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] New: Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 Bug ID: 401184 Summary: Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created Product: latte-dock Version: 0.8.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: scum.filter+...@gmail.com Target Milestone: --- Created attachment 116393 --> https://bugs.kde.org/attachment.cgi?id=116393=edit Multiple gloabl keyboard shortcut entries. Global Shortcuts stop working after reboot and multiple entries are introduced. STEPS TO REPRODUCE/OBSERVED RESULT 1. Set keyboard shortcut for widget (for example, Event Calendar, Weather, Notifications, etc.) by right-clicking on the widget, selecting Configure and setting the shortcut in Keyboard Shortcuts. 2. Reboot 3. Keyboard shortcuts remain in Global Shortcuts > Latte Dock, however a new entry is also added with an empty shortcut value and previously set shortcuts no longer work. EXPECTED RESULT Keyboard shortcuts should work after reboot and only a single entry should exist per widget. SOFTWARE/OS VERSIONS KDE neon User Edition 5.14 Release 18.04/Bionic plasmashell 5.14.3 lattedock 0.8.2 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 306470] KTuberling: German voiceover for "Pepper" is incorrectly translated
https://bugs.kde.org/show_bug.cgi?id=306470 Frederik Schwarzer changed: What|Removed |Added CC||schwar...@kde.org --- Comment #1 from Frederik Schwarzer --- Still the case in version 1.0.0. We need more voice people. :) -- You are receiving this mail because: You are watching all bug changes.
[ktuberling] [Bug 245460] when you click on the green pepper is says "pepperoni"
https://bugs.kde.org/show_bug.cgi?id=245460 Frederik Schwarzer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Frederik Schwarzer --- In version 1.0.0 from Kubuntu 16.04 all peppers trigger the "pepper" sound sample correctly. I cannot find the commit that would have fixed this but I guess it's OK to close since the game is working correctly and the theme file is alright as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #14 from wg9rffujwz8y2...@airmail.cc --- (In reply to Martin Flöser from comment #12) > To anybody encountering the problem: please go to Compositor settings and > change "Keep window thumbnails" to "Always". That's the setting I have and > which could explain why I don't see the problem. I did and had to reboot, some UI elements went black. > If you can confirm that this fixes the problem we can remove the setting and > enforce it on Wayland. The setting doesn't really make sense on Wayland, > that's why I have set it to Always. It's been a few hours and I haven't encountered the bug so far. It most definitely helped (probably fixed it but I need to use the system for a few days). P.S.: VirtualBox's fullscreen mode is broken for me (accel on or off) and it looks exactly like this bug where mouse clicks stop working in the host or guest system. I'm not sure it's related or just something not implemented yet. I thought I should mention it. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 395383] Settings are not saved in printer global settings
https://bugs.kde.org/show_bug.cgi?id=395383 Ross changed: What|Removed |Added CC||r.esmaeilbe...@gmail.com --- Comment #4 from Ross --- I want to second it. I have almost the same issue: SUMMARY On Kubuntu 18.04.1 with Plasma 5.12.7 I can not save printer options properly. I have used the same printer with the same driver with Ubuntu 18.04 without any issues. STEPS TO REPRODUCE 1. Open 'Printers--System Settings Module' 2. In 'Configure your printer' section, select 'Add printer' 3. Choose 'Manual URI' 4. In 'connections' type 'socket://IP' where IP is the ip address for the printer and then click on 'Next'. 5. Select 'Manually provide a PPD file' and then 'Next'. 6. Give the printer a name ... Note: the driver is KONIKA MINOLTA C652SeriesPS(P) After the printer is appeared in the list of Printers: 7. Set it as 'default' and click on 'Configure' 8. In 'Printer Options'change some settings 9. Apply -> OK 10. Open the Printer settings again and you see that the settings have not been saved. OBSERVED RESULT When opening a PDF file with evince to print, I think most of the options are available. The printer will print normally except that I do not see the staple option in evince (in the advanced tab) and so the printer does not apply staple. In Okular I do not see any staple option and presumably it should use the default settings (which are not saved in this case). An observation in the first try: Only in the first try to add staple option, I observed that evince has the option 'staple' available but together with a yellow color (kind of warning, don't remember exactly). EXPECTED RESULT Printer settings are not saved. In particular, staple options do not apply. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04.1 (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389928] Saving GIH brush doesn't save the "create mask from color" property
https://bugs.kde.org/show_bug.cgi?id=389928 --- Comment #5 from Kenneth Evans --- There seems to be more to it than just in saving the GIH. "Use color as mask" is unchecked for the brushes saved in Krita _and_ the default GIH brushes, but the latter work as masks anyway. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389928] Saving GIH brush doesn't save the "create mask from color" property
https://bugs.kde.org/show_bug.cgi?id=389928 Kenneth Evans changed: What|Removed |Added CC||k...@kenevans.net --- Comment #4 from Kenneth Evans --- I was going to submit this as a bug, but this seems to be the same issue. The bottom line is that GIH files saved in Krita default to not being masks, even if the "Use color as mask" is checked. This happens with some GDquest brushes as well as my own. I am on Krita 4.1.5 on Windows. Here is what I was going to submit. SUMMARY Brushes saved as GIH in Krita with "Use color as mask" checked, default to having this unchecked and don't behave as masks when this brush is selected for the tip. It can be fixed by checking "Use color as mask" for the tip. However, this has to be rechecked every time you go back to this brush. This may be a problem with the GIH save in Krita as other brushes which are GIH files do open as masks but have "Use color as mask unchecked", as well). E.g. bristles_circle_random. I did not test all the GIH brushes. I note ones by GDQuest also have this problem. STEPS TO REPRODUCE 1. Create a GIH file in Krita from, say, the Texture 256x256 Predefined option. 2. Save it as 1 layer Regular or multiple layer Random (either gives the problem), checking the "Use color as mask" option. 3. Import it in the Brush Editor and use it as a tip. OBSERVED RESULT Shows white background. (Can see in the preview.) EXPECTED RESULT Acts as a mask. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 401183] New: Crash KMail after closing
https://bugs.kde.org/show_bug.cgi?id=401183 Bug ID: 401183 Summary: Crash KMail after closing Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: freekdekru...@kde.nl Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.19.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I closed KMail after reading and deleting messages in several accounts. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43b6edfa40 (LWP 4916))] Thread 29 (Thread 0x7f4364ff9700 (LWP 31240)): #0 0x7f43c93f98c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f43c26cfd37 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7f43c26d1a0a in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7f43c26d1af2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7f43c26d68b1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7f43c26d7baf in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:42 #6 0x7f43c26e21c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7f43c93f3554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f43ca77cccf in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f43327fc700 (LWP 31239)): #0 0x7f43c93f98c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f43c26cfd37 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7f43c26d1a0a in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7f43c26d1af2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7f43c26d68b1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7f43c26d7d91 in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #6 0x7f43c26e21c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7f43c93f3554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f43ca77cccf in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f428e44c700 (LWP 7416)): #0 0x7f43c93f98c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f43c26cfd37 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7f43c26d1a0a in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7f43c26d1af2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7f43c26d68b1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7f43c26d7d91 in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #6 0x7f43c26e21c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7f43c93f3554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f43ca77cccf in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f429bfff700 (LWP 4962)): #0 0x7f43ca78a0cc in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f43ca78bdf4 in __fprintf_chk () from /lib64/libc.so.6 #2 0x7f43be95f02f in event_logv_ () from /usr/lib64/libevent-2.1.so.6 #3 0x7f43be95f1f4 in event_warn () from /usr/lib64/libevent-2.1.so.6 #4 0x7f43be960b60 in ?? () from /usr/lib64/libevent-2.1.so.6 #5 0x7f43be956998 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #6 0x7f43c26a47ad in base::MessagePumpLibevent::Run () at ./../../3rdparty/chromium/base/message_loop/message_pump_libevent.cc:247 #7
[kmymoney] [Bug 401133] KMyMoney crashed after finishing loan wizard
https://bugs.kde.org/show_bug.cgi?id=401133 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Thomas Baumgart --- This looks like a division by zero during forecast calculation to me. No idea how that happens. A workaround maybe to turn off the forecasting plugin for now. Is this a fresh new file or has it been used with prior versions? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401173] Wish for file saving: set changed datetime to exif datetime
https://bugs.kde.org/show_bug.cgi?id=401173 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- You have the option in the digiKam metadata setting to deactivate the update of the timestamp. Then the modification date of the file is preserved. Just tested, works. Maik -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 353252] Certification fails with "Allgemeiner Fehler" (Common Failure)
https://bugs.kde.org/show_bug.cgi?id=353252 c.woll...@web.de changed: What|Removed |Added Version Fixed In||gpg4win 3 Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 207850] Reversed Ranges from OpenOffice not handled
https://bugs.kde.org/show_bug.cgi?id=207850 --- Comment #3 from Colin --- I now use LibreOffice rather than OpenOffice. LibreOffice Calc saves the range in the correct order. You can close this bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 401182] New: Configure Desktop Crashed Plasma
https://bugs.kde.org/show_bug.cgi?id=401182 Bug ID: 401182 Summary: Configure Desktop Crashed Plasma Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: n...@horsefucker.org Target Milestone: --- Application: plasmashell (5.14.3) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.14.81-1-lts x86_64 Distribution: "Antergos Linux" -- Information about the crash: Attempting to change the wallpaper crashed Plasma, however this only happened once and is not reproducible for me. - What I was doing when the application crashed: Right Click Desktop, Pick "Configure Desktop". OS is Antergos Linux (4.14.81-1-lts) w. Plasmashell v 5.14.3. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc8910920c0 (LWP 766))] Thread 17 (Thread 0x7fc85edef700 (LWP 8999)): #0 0x7fc894983693 in () at /usr/lib/libglib-2.0.so.0 #1 0x7fc894983872 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7fc894984e86 in () at /usr/lib/libglib-2.0.so.0 #3 0x7fc894984fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fc896b8ffe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc896b3b8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fc896984eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fc8982bb859 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fc89698ef65 in () at /usr/lib/libQt5Core.so.5 #9 0x7fc8958a7a9d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fc896673b23 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fc831ffb700 (LWP 7494)): #0 0x7fc8958adafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc89698f71c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc8471cd469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fc8471d1339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fc8471cc52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fc8471d1392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fc8471cc52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fc8471cf389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fc89698ef65 in () at /usr/lib/libQt5Core.so.5 #9 0x7fc8958a7a9d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fc896673b23 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fc8327fc700 (LWP 7493)): #0 0x7fc8958adafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc89698f71c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc8471cd469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fc8471d1339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fc8471cc52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fc8471d1392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fc8471cc52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fc8471d1392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fc8471cc52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fc8471d1392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fc8471cc52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fc8471cf389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fc89698ef65 in () at /usr/lib/libQt5Core.so.5 #13 0x7fc8958a7a9d in start_thread () at /usr/lib/libpthread.so.0 #14 0x7fc896673b23 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fc832ffd700 (LWP 7492)): #0 0x7fc8958adafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc89698f71c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc8471cd469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fc8471d1339 in () at
[calligrasheets] [Bug 207851] Fill adds precision to numbers
https://bugs.kde.org/show_bug.cgi?id=207851 Colin changed: What|Removed |Added Version|2.1 |3.0.1 --- Comment #3 from Colin --- Still occurs in 3.0.1 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 401181] New: Kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=401181 Bug ID: 401181 Summary: Kopete crashed on exit Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: kdeuser@saur0n.science Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.19.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: closed the application (menu File -> Exit) Additonal info: two accounts were registered (one ICQ and one GaduGadu) -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54f2932940 (LWP 19704))] Thread 6 (Thread 0x7f54d7fff700 (LWP 19752)): #0 0x7f54f8491739 in syscall () at /lib64/libc.so.6 #1 0x7f54f89aca24 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7f54f7b4ad14 in () at /usr/lib64/libQt5Network.so.5 #3 0x7f54f89b79b7 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f54f6834554 in start_thread () at /lib64/libpthread.so.0 #5 0x7f54f8496ccf in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f54dee20700 (LWP 19744)): #0 0x7f54f683a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f54df2e7f5b in () at /usr/lib64/dri/i965_dri.so #2 0x7f54df2e7c87 in () at /usr/lib64/dri/i965_dri.so #3 0x7f54f6834554 in start_thread () at /lib64/libpthread.so.0 #4 0x7f54f8496ccf in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f54ee21d700 (LWP 19743)): #0 0x7f54f596ad89 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f54f59234a6 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f54f5923e7b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f54f592406c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f54f8bb1adb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f54f8b5eadb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f54f89adde6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f54f89b79b7 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f54f6834554 in start_thread () at /lib64/libpthread.so.0 #9 0x7f54f8496ccf in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f54eecd7700 (LWP 19742)): #0 0x7f54f5920ec7 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f54f59233d3 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f54f5923e7b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f54f592406c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f54f8bb1adb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f54f8b5eadb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f54f89adde6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f54f9ba6545 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7f54f89b79b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f54f6834554 in start_thread () at /lib64/libpthread.so.0 #10 0x7f54f8496ccf in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f54efea4700 (LWP 19738)): #0 0x7f54f848c2c9 in poll () at /lib64/libc.so.6 #1 0x7f54f6c99cc7 in () at /usr/lib64/libxcb.so.1 #2 0x7f54f6c9b8ea in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f54f0c4d519 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f54f89b79b7 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f54f6834554 in start_thread () at /lib64/libpthread.so.0 #6 0x7f54f8496ccf in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f54f2932940 (LWP 19704)): [KCrash Handler] #6 0x7f54ddd74f96 in () at /usr/lib64/libKF5KHtml.so.5 #7 0x7f54de36d0a7 in ChatMessagePart::writeTemplate() () at /usr/lib64/libkopetechatwindow_shared.so.1 #8 0x7f54de3748ec in ChatMessagePart::changeStyle() () at /usr/lib64/libkopetechatwindow_shared.so.1 #9 0x7f54de3871b5 in () at /usr/lib64/libkopetechatwindow_shared.so.1 #10 0x7f54f8b89902 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #11 0x7f54f95024a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f54f9509af0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7f54f8b5fe09 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #14 0x7f54f8b62dfb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f54f8bb2493 in () at /usr/lib64/libQt5Core.so.5 #16 0x7f54f5923c15 in
[kppp] [Bug 52360] takes many attempts to connect to ISP
https://bugs.kde.org/show_bug.cgi?id=52360 --- Comment #4 from houns...@magma.ca --- You can close this ticket. I no longer have the equipment to test the issue any more -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 401180] New: Crash when creating account.
https://bugs.kde.org/show_bug.cgi?id=401180 Bug ID: 401180 Summary: Crash when creating account. Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bba...@bradtech.ca Target Milestone: --- Application: kmymoney (5.0.0) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: Trying to create an account of type savings. Tried a couple more times same result. The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0013d60940 (LWP 16709))] Thread 25 (Thread 0x7eff3cd95700 (LWP 16733)): #0 0x7ffed7fc3b62 in clock_gettime () #1 0x7f000b5d3ea6 in __GI___clock_gettime (clock_id=1, tp=0x7eff3cd949d0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f000c4a7951 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f000c4a6189 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f000c4a6765 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f000c4a7dae in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0001023a98 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f000102446b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f000102464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f000c4a804b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f000c44c30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f000c277bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f000c282adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f00035f76db in start_thread (arg=0x7eff3cd95700) at pthread_create.c:463 #14 0x7f000b5c488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7eff3e3ff700 (LWP 16732)): #0 0x7ffed7fc3b62 in clock_gettime () #1 0x7f000b5d3ea6 in __GI___clock_gettime (clock_id=1, tp=0x7eff3e3fe9d0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f000c4a7951 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f000c4a6189 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f000c4a6765 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f000c4a7dae in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0001023a98 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f000102446b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f000102464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f000c4a804b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f000c44c30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f000c277bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f000c282adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f00035f76db in start_thread (arg=0x7eff3e3ff700) at pthread_create.c:463 #14 0x7f000b5c488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7effb9ffb700 (LWP 16731)): #0 0x7f00035fd9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x2116cb0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f00035fd9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x2116c60, cond=0x2116c88) at pthread_cond_wait.c:502 #2 0x7f00035fd9f3 in __pthread_cond_wait (cond=0x2116c88, mutex=0x2116c60) at pthread_cond_wait.c:655 #3 0x7effe0a635cb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7effe0a632d7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f00035f76db in start_thread (arg=0x7effb9ffb700) at pthread_create.c:463 #6 0x7f000b5c488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7effba7fc700 (LWP 16730)): #0 0x7f00035fd9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x2116cb0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f00035fd9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x2116c60, cond=0x2116c88) at pthread_cond_wait.c:502 #2 0x7f00035fd9f3 in __pthread_cond_wait (cond=0x2116c88,
[systemsettings] [Bug 280294] Font installer ignores optical sizes
https://bugs.kde.org/show_bug.cgi?id=280294 Sebastian Schubert changed: What|Removed |Added Platform|Gentoo Packages |openSUSE RPMs Version|unspecified |5.14.2 --- Comment #3 from Sebastian Schubert --- The bug is still present in current openSUSE Tumbleweed with KDE system settings version 5.14.2, KDE font installer 1.0. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401179] New: (5.14.3) Allow lesser than 1 scale factor
https://bugs.kde.org/show_bug.cgi?id=401179 Bug ID: 401179 Summary: (5.14.3) Allow lesser than 1 scale factor Product: KScreen Version: git Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: pas...@gmail.com Target Milestone: --- I'm using KDE Plasma and KDE SC on a macos hardware which comes with so called "retina" screen. Using a resolution of 2880x1800 is obviously useless, because too difficult to read, the list of screen resolution is also not changeable (fixed). Up to now i workaround the issue by using xrandr to downscale the screen to 1440x900 using a scale factor of 0.5 into an early system script. Works fine, still i had to workaround that in kcm kscreen again to position the second external screen correctly. ie, i have to put the position of the second screen half the width of the first screen (remember, kscreen only allow scaling from 1 to more) so that both my first screen downscale and second screen position does not get wrong. All works so fine, but at a manual maintains cost. I would like kscreen kcm allow less than 1 scale factor so that i can just correctly setup my screens without requiring work around / own script. STEPS TO REPRODUCE 1. Use a mac book laptop with a retina screen and an external non retina screen 2. Try to setup your screens so that it fit your needs OBSERVED RESULT First retina screen is too small to be usable EXPECTED RESULT Be able to downscale my retina screen resolution SOFTWARE/OS VERSIONS Linux/KDE Plasma: KaOS Linux KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401107] Unable To Match Transaction
https://bugs.kde.org/show_bug.cgi?id=401107 --- Comment #6 from Robert Blackwell --- (In reply to Jack from comment #5) > So I think it's OK to close this as not a bug, and I'll try to file a > separate bug against KMessageBox for not making the window large enough to > actually show the message. I concur with your thoughts. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 364417] Skanlit crashes out when trying to do a scan or preview scan
https://bugs.kde.org/show_bug.cgi?id=364417 Matthew changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Matthew --- Skanlite still has problems on Fedora 29, as it did under 24, 25, 26, 27, 27. However on Fedora 29 it does not seem to crash so often, I can however get it to loose the scanner if I close Skanlite and immediately try to re-open it. I then get a message that no scanner can be foumd. This can however be solved by closing Skanlite again, then re-opening Skanlite after a pause of a few seconds. Though the application no longer seems to crash as before, there is still a problem with doing multiple scans in one session with Skanlite. Once a Preview and then a full scan has been carried out, a subsequent attempt to do a preview (or a full scan), results in a distorted lighting effect on the resulting image, it looks like half the scan light isn't working. The only 2 ways I have found to do multiple scans are:- 1/ close the Skanlite application after each scan and restart Skanlite for the next scan. 2/ After a successful Preview and Full scan has been completed, click the Lampswitch selection box found under Specific Scanner options tab. Click on the tick box to remove the tick, then click again to re-tick the box. Do this Lampswitch selection process twice or three times. Then Preview and Full scan should again result in a clean image. On versions of Fedora before 29, the Lampswitch trick was intermittent, it sometimes didn't work, so Skanlite had to be closed down and restarted, which if done too quickly, caused Skanlite to crash on re-opening as mentioned in original report. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401178] New: Item duplication in application list due to the both Flatpak/repo sources enabled
https://bugs.kde.org/show_bug.cgi?id=401178 Bug ID: 401178 Summary: Item duplication in application list due to the both Flatpak/repo sources enabled Product: Discover Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: adam.golan...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- Created attachment 116392 --> https://bugs.kde.org/attachment.cgi?id=116392=edit Which GIMP is better? SUMMARY STEPS TO REPRODUCE 1. Open Discover 2. Click Settings, enable Flatpak integrations 3. Go back to the application list, sort by name OBSERVED RESULT There is a lot of doubled content from the very beginning of list, with items of the same name yet with different descriptions (for example: AbiWord: Compose, edit, and view documents and AbiWord: A word processor). There is no indication about source of given application. EXPECTED RESULT Items from the flatpak sources could be in some way colored or labeled, to avoid confusion. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499 --- Comment #6 from Matt Fagnani --- Crashes involving segmentation faults in operator== (s1=..., s2=...) at tools/qstring.cpp:3153 were reported for: kpat at https://bugs.kde.org/show_bug.cgi?id=363726#c5 kdeconnectd at https://bugs.kde.org/show_bug.cgi?id=400010#c1 Suggested fixes are noted on those pages. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401177] New: Discover doesn't show Wallpapers, only "still looking" throbber
https://bugs.kde.org/show_bug.cgi?id=401177 Bug ID: 401177 Summary: Discover doesn't show Wallpapers, only "still looking" throbber Product: Discover Version: 5.14.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: adam.golan...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open Discover 2. Select Plasma Addons 3. Select Wallpapers OBSERVED RESULT Empty page, with "Still looking" animated throbber on bottom. I checked that for 10 minutes. EXPECTED RESULT Wallpaper list or message about wallpaper unavailability SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 388966] Enabling "Search" plugin freezes KTorrent application
https://bugs.kde.org/show_bug.cgi?id=388966 Uwe Dippel changed: What|Removed |Added CC||udip...@gmail.com --- Comment #6 from Uwe Dippel --- Same here, Kubuntu 18.04, daily updates. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 339830] Slow file transfer (fish, sshfs)
https://bugs.kde.org/show_bug.cgi?id=339830 --- Comment #5 from Alexander Potashev --- May be related to bug #342056 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 339830] Slow file transfer (fish, sshfs)
https://bugs.kde.org/show_bug.cgi?id=339830 --- Comment #4 from Alexander Potashev --- (In reply to Alexander Potashev from comment #3) > It is even slower when copying from one ssh remote to another. I've got > these results testing copying KIO fish: > 1. server A -> local: 1100 KB/s > 2. local -> server B: 180 KB/s > 3. server A -> server B: 24 KB/s (I was copying one large file in all of these tests.) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 339830] Slow file transfer (fish, sshfs)
https://bugs.kde.org/show_bug.cgi?id=339830 --- Comment #3 from Alexander Potashev --- It is even slower when copying from one ssh remote to another. I've got these results testing copying KIO fish: 1. server A -> local: 1100 KB/s 2. local -> server B: 180 KB/s 3. server A -> server B: 24 KB/s -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 401015] Check that the name of the types exported to QML with qmlRegisterType starts uppercase
https://bugs.kde.org/show_bug.cgi?id=401015 Sergio Martins changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/cla ||zy/90ef5de73c8cb09eda1480a4 ||930450e243abe6de Status|ASSIGNED|RESOLVED --- Comment #3 from Sergio Martins --- Git commit 90ef5de73c8cb09eda1480a4930450e243abe6de by Sergio Martins. Committed on 18/11/2018 at 19:58. Pushed by smartins into branch 'master'. New check: lowercase-qml-type-name Warns when QML types registered with qmlRegisterType() or qmlRegisterUncreatableType() don't start with uppercase. It's required by the engine. M +1-0Changelog M +1-0CheckSources.cmake M +1-0README.md M +6-1checks.json A +4-0docs/checks/README-lowercase-qml-type-name.md M +1-0readmes.cmake M +2-0src/Checks.h A +69 -0src/checks/level0/lowercase-qml-type-name.cpp [License: LGPL (v2+)] A +38 -0src/checks/level0/lowercase-qml-type-name.h [License: LGPL (v2+)] A +7-0tests/lowercase-qml-type-name/config.json A +11 -0tests/lowercase-qml-type-name/main.cpp [License: UNKNOWN] * A +1-0tests/lowercase-qml-type-name/main.cpp.expected The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://commits.kde.org/clazy/90ef5de73c8cb09eda1480a4930450e243abe6de -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 339830] Slow file transfer (fish, sshfs)
https://bugs.kde.org/show_bug.cgi?id=339830 Alexander Potashev changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 339830] Slow file transfer (fish, sshfs)
https://bugs.kde.org/show_bug.cgi?id=339830 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 342056] Ridiculously slow file copy (multiple small files)
https://bugs.kde.org/show_bug.cgi?id=342056 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 394003] Loosing LaTeX output after backend restarting
https://bugs.kde.org/show_bug.cgi?id=394003 Nikita Sirgienko changed: What|Removed |Added Latest Commit|https://commits.kde.org/can |https://commits.kde.org/can |tor/3321535207ce936c5585b6d |tor/9ce803cebc402667e4d8c1f |10b32db168c5cc51f |ef5692006b1d33910 --- Comment #3 from Nikita Sirgienko --- Git commit 9ce803cebc402667e4d8c1fef5692006b1d33910 by Nikita Sirgienko. Committed on 18/11/2018 at 19:49. Pushed by sirgienko into branch 'Applications/18.12'. Fix bug with losing LaTeX typesetting after backend restart FIXED-IN: 18.12 (cherry picked from commit 3321535207ce936c5585b6d10b32db168c5cc51f) M +1-0ChangeLog M +1-1src/cantor_part.cpp M +2-1src/worksheet.h https://commits.kde.org/cantor/9ce803cebc402667e4d8c1fef5692006b1d33910 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #5 from Matt Fagnani ---
Those ksysguard crashes with segmentation faults at operator==(QString const&,
QString const&) (s1=..., s2=...) at tools/qstring.cpp:3153 seem to involve the
line if (s1.d->size != s2.d->size) in the function
/*!
\relates QString
Returns \c true if string \a s1 is equal to string \a s2; otherwise
returns \c false.
The comparison is based exclusively on the numeric Unicode values of
the characters and is very fast, but is not what a human would
expect. Consider sorting user-interface strings with
localeAwareCompare().
*/
bool operator==(const QString , const QString ) Q_DECL_NOTHROW
{
if (s1.d->size != s2.d->size)
return false;
return qt_compare_strings(s1, s2, Qt::CaseSensitive) == 0;
}
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/tools/qstring.cpp
The QStrings s1 or s2 might be null due to their memory being freed or some
other reason. s1.d->size or s2.d->size might be null pointer dereferences which
lead to the segmentation faults. Checking if s1 or s2 are null before the line
if (s1.d->size != s2.d->size) might avoid the crashes.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #13 from Patrick Silva --- I just found a way to reproduce: open Firefox and unmaximize its window move Firefox window near to plasma panel right click your wallpaper on the space between Firefox and plasma panel while context menu is open, click Firefox entry in plasma panel (context menu closes) click Firefox entry in plasma panel again (Firefox is minimized) click Firefox entry again to restore it Now mouse clicks on Firefox window have no effect I can't reproduce after set "Keep window thumbnails" to "Always" in compositor settings. Wayland session crashed here when I configured "Keep window thumbnails" to "Always". Is this a know problem? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 312132] KDevelop fails to autocomplete std::shared_ptr members
https://bugs.kde.org/show_bug.cgi?id=312132 Valentyn Pavliuchenko changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Valentyn Pavliuchenko --- Moving back to reported as requested. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 312132] KDevelop fails to autocomplete std::shared_ptr members
https://bugs.kde.org/show_bug.cgi?id=312132 --- Comment #5 from Valentyn Pavliuchenko --- I followed my original steps to repro and I see this working good with KDevelop 5.2.4. So this bug seems to be fixed now. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384785] Properties windows shrink when you move it, instead of having scroll bars
https://bugs.kde.org/show_bug.cgi?id=384785 emohr changed: What|Removed |Added Flags||timeline_corruption+ CC||fritzib...@gmx.net --- Comment #1 from emohr --- Please try with the actual Kdenlive AppImage version 18.08.3 Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 401150] Alt+Tab just shows a window in another workspace
https://bugs.kde.org/show_bug.cgi?id=401150 Aaron Honeycutt changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #12 from Martin Flöser --- To anybody encountering the problem: please go to Compositor settings and change "Keep window thumbnails" to "Always". That's the setting I have and which could explain why I don't see the problem. If you can confirm that this fixes the problem we can remove the setting and enforce it on Wayland. The setting doesn't really make sense on Wayland, that's why I have set it to Always. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397745] Meta Key doesn't work after gaming.
https://bugs.kde.org/show_bug.cgi?id=397745 --- Comment #5 from Martin Flöser --- Well, it's pretty obvious isn't it? UrbanTerror does soemthing strange which breaks this feature. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384305] I can not add clips to the project
https://bugs.kde.org/show_bug.cgi?id=384305 emohr changed: What|Removed |Added Flags||corner_case+ Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||junior-jobs CC||fritzib...@gmx.net --- Comment #1 from emohr --- Confirmed. If the library is empty the “added clip“ button is available. It should be grayed out as long as no clip is in the library. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401176] New: No embedded videos in software description, just blank space and nonclickable links
https://bugs.kde.org/show_bug.cgi?id=401176 Bug ID: 401176 Summary: No embedded videos in software description, just blank space and nonclickable links Product: Discover Version: 5.14.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: adam.golan...@gmail.com Target Milestone: --- Created attachment 116391 --> https://bugs.kde.org/attachment.cgi?id=116391=edit Discover app with blank popup SUMMARY STEPS TO REPRODUCE 1. Open Discovery 2. Find "Cool Effect" (https://store.kde.org/p/1110512) OBSERVED RESULT Under Watch this video is blank space and non-clickable, non-selectable link. User can click this blank space to open empty preview pop-up box. EXPECTED RESULT embedded player and/or clickable/selectable link. Actually in given example this video is non-existent on YouTube, but still, even without player, link should be at least selectable, to enable copying it to clipboard. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400499] ksysguard crashed when closing
https://bugs.kde.org/show_bug.cgi?id=400499 --- Comment #4 from Matt Fagnani --- Created attachment 116390 --> https://bugs.kde.org/attachment.cgi?id=116390=edit New crash information added by DrKonqi ksysguard (5.14.3) using Qt 5.11.1 - What I was doing when the application crashed: I was looking at the network activity in ksysguard 5.14.3, and then I closed ksysguard. drkonqi appeared. I've reported crashes with similar traces which have occurred < 10% of the times I've closed ksysguard in the last 2 months. -- Backtrace (Reduced): #7 0xb5c95bb2 in operator==(QString const&, QString const&) (s1=..., s2=...) at tools/qstring.cpp:3153 #8 0xb6886f8f in QLabel::setText(QString const&) (this=0x1ed6de0, text=...) at widgets/qlabel.cpp:287 #9 0xb7ec749c in TopLevel::answerReceived(int, QList const&) (this=0x1e42a80, id=1, answerList=...) at /usr/src/debug/ksysguard-5.14.3-1.fc29.i386/gui/ksysguard.cpp:450 #10 0xb753d925 in KSGRD::SensorAgent::processAnswer(char const*, int) (this=0x1ef9870, buf=0x2082740 "100.00\nksysguardd> 335696\nksysguardd> 37632\nksysguardd> 0\nksysguardd> 0\nksysguardd> 0\nksysguardd> 0\nksysguardd> /dev/mapper/fedora-root\t30832636\t25986096\t3257292\t90\t/\n/dev/mapper/fedora-home\t84853"..., buflen=608) at /usr/src/debug/libksysguard-5.14.3-1.fc29.i386/ksgrd/SensorAgent.cpp:91 #11 0xb7544e8e in KSGRD::SensorShellAgent::msgRcvd() (this=0x1ef9870) at /usr/include/qt5/QtCore/qarraydata.h:206 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 383577] Stereo Amplifier doesn't work.
https://bugs.kde.org/show_bug.cgi?id=383577 emohr changed: What|Removed |Added Flags||timeline_corruption+ CC||fritzib...@gmx.net --- Comment #1 from emohr --- What do you mean with "Stereo Amplifier". I havn't such effect. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 383122] Kdenlive crashes on playback
https://bugs.kde.org/show_bug.cgi?id=383122 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #1 from emohr --- Please try with the actual Kdenlive AppImage version 18.08.3 Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382678] 3 point balance does not work on a track
https://bugs.kde.org/show_bug.cgi?id=382678 emohr changed: What|Removed |Added Keywords||Brainstorm CC||fritzib...@gmx.net Version|17.04.1 |18.08.2 Flags||Brainstorm+ Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from emohr --- Confirmed. It still doesn't work in version 18.08.2. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 394003] Loosing LaTeX output after backend restarting
https://bugs.kde.org/show_bug.cgi?id=394003 Nikita Sirgienko changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/can ||tor/3321535207ce936c5585b6d ||10b32db168c5cc51f Version Fixed In||18.12 --- Comment #2 from Nikita Sirgienko --- Git commit 3321535207ce936c5585b6d10b32db168c5cc51f by Nikita Sirgienko. Committed on 18/11/2018 at 19:11. Pushed by sirgienko into branch 'master'. Fix bug with losing LaTeX typesetting after backend restart FIXED-IN: 18.12 M +1-0ChangeLog M +1-1src/cantor_part.cpp M +2-1src/worksheet.h https://commits.kde.org/cantor/3321535207ce936c5585b6d10b32db168c5cc51f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401049] Cursor turns red when moving over certain speed
https://bugs.kde.org/show_bug.cgi?id=401049 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com --- Comment #2 from mthw0 --- I am using Wayland so It should be Night Color. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 394003] Loosing LaTeX output after backend restarting
https://bugs.kde.org/show_bug.cgi?id=394003 Nikita Sirgienko changed: What|Removed |Added Summary|Loose LaTeX output after|Loosing LaTeX output after |backend restarting |backend restarting -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377609] [Windows] Icons missing
https://bugs.kde.org/show_bug.cgi?id=377609 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from emohr --- goto settings -> enable "force breeze icon them" -> the icons should appear I closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 279075] Message fails to send in Groupwise Messenger when remote user closes chat window
https://bugs.kde.org/show_bug.cgi?id=279075 Alan Moore changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Alan Moore --- I no longer use kopete or have access to groupwise messenger services. You may as well close this bug, nobody's touched it in 7 years, I doubt that's going to change now. I don't know what status would be appropriate, feel free to change. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381234] Crash when play title text
https://bugs.kde.org/show_bug.cgi?id=381234 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||Translation_missing+ --- Comment #1 from emohr --- Please try with the actual Kdenlive AppImage version 18.08.3 Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380475] Dctdnoiz effect crashes Kdenlive
https://bugs.kde.org/show_bug.cgi?id=380475 emohr changed: What|Removed |Added Flags||timeline_corruption+ CC||fritzib...@gmx.net --- Comment #1 from emohr --- Please try with the actual Kdenlive AppImage version 18.08.3 Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401175] New: Move Screen brightness/Dim screen to Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=401175 Bug ID: 401175 Summary: Move Screen brightness/Dim screen to Screen Energy Saving Product: systemsettings Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexander.reim...@pm.me Target Milestone: --- Created attachment 116389 --> https://bugs.kde.org/attachment.cgi?id=116389=edit Image for better description Screen brightness and Dim Screen options under Power Management -> Energy Saving are all screen related options and shout be moved to Screen Energy Saving. Just like Button events handling has other sub-options that are related to button events. This would also enable the user to turn all screen related options on/off with one click. SOFTWARE/OS VERSIONS Linux: 4.19.2 64-bit (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
