[krita] [Bug 476076] Masked brushes use pen pressure, even if pen pressure is disabled in the brush
https://bugs.kde.org/show_bug.cgi?id=476076 --- Comment #6 from Flo Tasser --- All good. Thank you. :) And thanks for asking better questions than I did, never easy to communicate these things well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476076] Masked brushes use pen pressure, even if pen pressure is disabled in the brush
https://bugs.kde.org/show_bug.cgi?id=476076 --- Comment #3 from Flo Tasser --- Created attachment 162559 --> https://bugs.kde.org/attachment.cgi?id=162559=edit gif of the behaviour -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476076] Masked brushes use pen pressure, even if pen pressure is disabled in the brush
https://bugs.kde.org/show_bug.cgi?id=476076 --- Comment #2 from Flo Tasser --- (In reply to David REVOY from comment #1) > Hi, it might be a good idea to write here in the report the name of the > brush-tip, if you can. > > I ask that, because some *.gih brush tips (Gimp animated brush tip) can map > mulitple brush mask to pressure, rotation, or drawing angle. And Krita will > honor that before any built-in curve based sensor. So, it might be the case > with your brush tip. > > For more info about gih brushes: > https://docs.krita.org/en/general_concepts/file_formats/file_gih.html#file- > gih > https://docs.gimp.org/2.8/en/gimp-using-animated-brushes.html Thank you for the idea David. Didn't think of that. But it was a custom brush tip in this example, generally it happens with other brushtips, too. They were all single images, not a .gih Tested with some random animated bruth tips, same result. It seems as if opacity and flow of the mask brush have nothing to do with the toggles. Will try to record a short video. I'll append another screengrab, this time as a gif. Hope it makes sense. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476076] New: Masked brushes use pen pressure, even if pen pressure is disabled in the brush
https://bugs.kde.org/show_bug.cgi?id=476076 Bug ID: 476076 Summary: Masked brushes use pen pressure, even if pen pressure is disabled in the brush Classification: Applications Product: krita Version: 5.2.0 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: minor Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: floriantas...@googlemail.com Target Milestone: --- Created attachment 162557 --> https://bugs.kde.org/attachment.cgi?id=162557=edit screenshot SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1) I have a simple brush, without any sensors on. No pressure for opacity or for flow. 2) The brush has a masked brush tip activated. But also, no pressure for opacity and flow. 3) If I have the pressure in Krita globally disabled (I have the "Use Pen Pressure" Toggle in my custom toolbar) it paints with 100% opacity and flow (as I want to). 4) If I activate the global pressure sensitivity, even tho the brush is not supposed to use pressure, it still uses opacity and/or flow of my pen. Running Krita 5.2.0 on Windows. Tried on yesterdays nightly build, same results. OBSERVED RESULT The brush works with pressure, even though pressure sensitivity is disabled in all my brush settings that I can find. Additionally, if I activate the (under Masked Brush) "Opacity" option, but then in the Masked Brush Opacity options disable "Enable Pen Settings" it works. EXPECTED RESULT The brush should just paint the same way as if I would paint with the mouse: completely disabled pressure all the time SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION see my attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466619] New: Discover crashes after closing during initial loading
https://bugs.kde.org/show_bug.cgi?id=466619 Bug ID: 466619 Summary: Discover crashes after closing during initial loading Classification: Applications Product: Discover Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: g...@flo-edelmann.de CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.1) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-32-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: After the upgrade to Plasma 5.27.1, clicking on the VLC icon in the new startup wizard opened Discover. While it was still loading, I closed the window. After that, the crash occurred. Opening Discover later via the Kickoff menu works without a problem, even if I try to close it while loading. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f1277702a8b in AbstractResource::isInstalled() () at /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #5 0x564b28f4db8c in () #6 0x564b28f41ea2 in () #7 0x7f12754f40d4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff986d1ea0, r=0x7f1268009680, this=0x564b322e7190) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate(QObject*, int, void**) (sender=0x564b2c1bde10, signal_index=0, argv=0x7fff986d1ea0) at kernel/qobject.cpp:3923 #9 0x7f12754ed177 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x564b2c1bde10, m=m@entry=0x7f1275754140 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff986d1ea0) at kernel/qobject.cpp:3983 #10 0x7f12754ed233 in QObject::destroyed(QObject*) (this=this@entry=0x564b2c1bde10, _t1=, _t1@entry=0x564b2c1bde10) at .moc/moc_qobject.cpp:219 #11 0x7f12754f23e7 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:1010 #12 0x7f12754f843d in QTimer::~QTimer() (this=0x564b2c1bde10, __in_chrg=) at kernel/qtimer.cpp:165 #13 0x7f12754e711e in QObjectPrivate::deleteChildren() (this=0x564b2b3447d0) at kernel/qobject.cpp:2137 #14 0x7f12754f21a6 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:1115 #15 0x564b28f41a72 in () #16 0x7f12754e9883 in QObject::event(QEvent*) (this=0x564b2b0f8930, e=0x564b2b8e8690) at kernel/qobject.cpp:1334 #17 0x7f1276f6c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x564b2b0f8930, e=0x564b2b8e8690) at kernel/qapplication.cpp:3640 #18 0x7f12754bc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x564b2b0f8930, event=0x564b2b8e8690) at kernel/qcoreapplication.cpp:1064 #19 0x7f12754bf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=52, data=0x564b2af96c00) at kernel/qcoreapplication.cpp:1821 #20 0x7f12754c2f4c in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:86 #21 0x564b28f3fc63 in () #22 0x7f1274a29d90 in __libc_start_call_main (main=main@entry=0x564b28f3f340, argc=argc@entry=2, argv=argv@entry=0x7fff986d2528) at ../sysdeps/nptl/libc_start_call_main.h:58 #23 0x7f1274a29e40 in __libc_start_main_impl (main=0x564b28f3f340, argc=2, argv=0x7fff986d2528, init=, fini=, rtld_fini=, stack_end=0x7fff986d2518) at ../csu/libc-start.c:392 #24 0x564b28f406a5 in () [Inferior 1 (process 4757) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459401] New: Can't export recording timelapse
https://bugs.kde.org/show_bug.cgi?id=459401 Bug ID: 459401 Summary: Can't export recording timelapse Classification: Unclassified Product: krita Version: 5.1.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Dockers/Recorder Assignee: krita-bugs-n...@kde.org Reporter: opalfl...@gmail.com Target Milestone: --- Created attachment 152226 --> https://bugs.kde.org/attachment.cgi?id=152226=edit can't export recording timelapse SESSION: 17 Sep 2022 22:04:46 +0700. Executing /snap/krita/75/usr/bin/krita -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417577] New: Remote Input not working with specific monitor arrangement
https://bugs.kde.org/show_bug.cgi?id=417577 Bug ID: 417577 Summary: Remote Input not working with specific monitor arrangement Product: kdeconnect Version: 1.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: flokol...@gmail.com Target Milestone: --- Created attachment 125960 --> https://bugs.kde.org/attachment.cgi?id=125960=edit monitor arrangement SUMMARY The Remote Input within the app is not working with my specific monitor arrangement, as seen in the attachment. STEPS TO REPRODUCE 1. Have a dual monitor setup where the secondary monitor is above the main monitor 2. move mouse to main monitor 3. use Remote Input in the App OBSERVED RESULT The cursor is going up no matter in which direction you swipe. EXPECTED RESULT You are able to swipe left, right and down. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.53-arch (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION See my desktop arrangement in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409534] New: remote keyboard shuffles input
https://bugs.kde.org/show_bug.cgi?id=409534 Bug ID: 409534 Summary: remote keyboard shuffles input Product: kdeconnect Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: kde-b...@cyborgsociety.org Target Milestone: --- SUMMARY fast typing leads to shuffled characters STEPS TO REPRODUCE 1. open sms app 2. connect to remote keyboard 3. type fast OBSERVED RESULT characters appear in shuffled order EXPECTED RESULT characters appear in correct order SOFTWARE/OS VERSIONS kdeconnect: 1.3.4-0xneon+18.04+bionic+build13 Operating System: KDE neon KDE Plasma Version: 5.16.2-0xneon+18.04+bionic+build38 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-25-generic OS Type: 64-bit kdeconnect app: 1.12.9 (fdroid as of 2019-06-22) OS: lineageos 7.1.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409528] New: unable to select default email client / outlook for sending by email
https://bugs.kde.org/show_bug.cgi?id=409528 Bug ID: 409528 Summary: unable to select default email client / outlook for sending by email Product: digikam Version: 6.1.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-SendByMail Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@cyborgsociety.org Target Milestone: --- SUMMARY unable to send picture using MS outlook DISCLAIMER I don't use windows but installed digikam on a friends computer because he had the same problem using default photo app. So I'll try to update this bug but it may take some time and my description is from my memory and thus may not be very accurate. STEPS TO REPRODUCE Fresh install of digikam 6.1 on windows 10. - select picture - select "send by email" from menu - Dialog to select email client opens and offers some options. OBSERVED RESULT - "MS outlook" or "default email client" not selectable EXPECTED RESULT Best result: Default email client is used and no dialog opens at all Second best: Dialog has "MS outlook" option SOFTWARE/OS VERSIONS Windows: Windows 10 (1803 / 17134.829 / 64bit) KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 353245] Support of OMEMO in Kopete
https://bugs.kde.org/show_bug.cgi?id=353245 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #3 from flo --- Meanwhile working in desktop clients: https://dino.im https://gajim.im updated xeps: OMEMO (v0.3.0): https://xmpp.org/extensions/xep-0384.html OMEMO jingle (v0.2.0): https://xmpp.org/extensions/xep-0396.html -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409025] Multiple notification
https://bugs.kde.org/show_bug.cgi?id=409025 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #4 from flo --- Happens to me too. kdeconnect: 1.3.4-0xneon+18.04+bionic+build13 Operating System: KDE neon KDE Plasma Version: 5.16.2-0xneon+18.04+bionic+build38 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-25-generic OS Type: 64-bit kdeconnect app: 1.12.9 (fdroid as of 2019-06-22) OS: lineageos 7.1.2 Do you need more information? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #13 from flo --- Why does this bugfix doesn't get "backported" to 18.08? To me it seems like a trivial patch for an annoying crash. What I did to get my assumption: $ git clone git://anongit.kde.org/konsole $ cd konsole $ git branch -r --contains 5006d0e194d642d8059e15edf9704fd38b579979 origin/HEAD -> origin/master origin/martin/inactivebg origin/master -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395476] The minimum window size of System Settings is too big for a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=395476 --- Comment #4 from flo --- Suggestions for solutions for scroll bar problem (which is not grave for me): 1. At lease using my default(?) font size [Noto Sans 10] there is probably enough space to cut from left navigation if you remove "(GTK)" from "Gnome Application Style (GTK)" 2. Improve views with scrollbar I checked every view (in my setup) and found not so many horizontal scroll bars: - VIEW [-> SUBVIEW]: POSSIBLE FIX - Icons -> Emoticons: buttons for theme options and single emoticon options in same line - Application Style -> Gnome Application Style (GTK): "GTK Themes" and "Behaviour" could be placed below each other - Shortcuts -> Global Shortcuts: (no ad-hoc idea) - Notifications: line break for long descriptions - Connections: make list appear as submenu since Connections itself has no submenu - Input Devices -> Touchpad -> Taps: why is it? - I can center and scrollbar gets needless - Multimedia -> Audio CDs: Only "Names" tab needs reorganization - Power Management -> Energy Savings: "[] Even when an external monitor is connected" could be reworded or placed to the right (does not look good anyways) - Printers: like "Connections" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395476] The minimum window size of System Settings is too big for a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=395476 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #3 from flo --- I agree that minimum size (of 1154px on my system) is too big. I have a 1920px width screen and use a lot of window width of 960px (side by side). And this is quite possible with System Settings window by dragging the window to one edge of the screen and it works well with this window size (width 960px). Now you can also increase width and go back to 960px. But if you switch "Workspace Theme -> Look and Feel" from Breeze to Breeze Dark (or vice versa) the window enlarges to its "minimum" size. If the window was attached to the right edge of the screen then the right window border (and the apply button...) jumps off the screen. - kde-neon - konsole 18.08.2 - KDE Frameworks 5.51.0 - Qt 5.11.2 (built against 5.11.1) - plasmashell 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343477] System color theme change not propagated to scrollbar and tabbar
https://bugs.kde.org/show_bug.cgi?id=343477 flo changed: What|Removed |Added CC||david.bies...@sas.com --- Comment #4 from flo --- *** Bug 373439 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373439] tabbar uses white text on light background
https://bugs.kde.org/show_bug.cgi?id=373439 flo changed: What|Removed |Added Resolution|WORKSFORME |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #6 from flo --- At least for my part it is the same bug as #343477 *** This bug has been marked as a duplicate of bug 343477 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343477] System color theme change not propagated to scrollbar and tabbar
https://bugs.kde.org/show_bug.cgi?id=343477 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #3 from flo --- I can also confirm this - kde-neon - konsole 18.08.2 - KDE Frameworks 5.51.0 - Qt 5.11.2 (built against 5.11.1) - plasmashell 5.14.2 Addition: In Konsole -> Settings -> Configure Konsole... -> TabBar: Switching on and off "Show 'New Tab' and 'Close Tab' buttons" fixes colors for tabbar (but not for buttons in tabbar) @Sebastian: Thanks for pointing me here. maybe #373439 is duplicate of this one and should be closed -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373439] tabbar uses white text on light background
https://bugs.kde.org/show_bug.cgi?id=373439 --- Comment #3 from flo --- Created attachment 115892 --> https://bugs.kde.org/attachment.cgi?id=115892=edit konsole screen shot 2 - using dark theme: dark font color on non-selected (dark) tabs Oops - the only thing I did was: switching "Show 'New Tab' and 'Close Tab' buttons" on and off again :) -> inactive tab font color and active tab color changed (sort of fixed unreadable text problem) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373439] tabbar uses white text on light background
https://bugs.kde.org/show_bug.cgi?id=373439 --- Comment #2 from flo --- screen shot attachment 115889 taken with - kde-neon - konsole 18.08.2 - KDE Frameworks 5.51.0 - Qt 5.11.2 (built against 5.11.1) - plasmashell 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373439] tabbar uses white text on light background
https://bugs.kde.org/show_bug.cgi?id=373439 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #1 from flo --- Created attachment 115889 --> https://bugs.kde.org/attachment.cgi?id=115889=edit konsole screen shot - using dark theme: dark font color on non-selected (dark) tabs -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373714] Please make active / passive tab color configurable
https://bugs.kde.org/show_bug.cgi?id=373714 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #2 from flo --- I agree this bug report can be closed. It is very old an does not apply (at least not to me). If I select breeze-dark in "Workspace Theme"->"Look and Feel" the selected tab in konsole is very light compared to non-selected tabs. (Font color of non-selected tabs is also very dark and almost unreadable -> time for new bug..) Also attached image shows mac light theme. - kde-neon - konsole 18.08.2 - KDE Frameworks 5.51.0 - Qt 5.11.2 (built against 5.11.1) - plasmashell 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #9 from flo --- Created attachment 115368 --> https://bugs.kde.org/attachment.cgi?id=115368=edit New crash information added by DrKonqi konsole (18.08.1) using Qt 5.11.1 - What I was doing when the application crashed: selecting text in vim in local file system pressing shift key (still the same after update of kde-neon's ubuntu base to 18.04 bionic) -- Backtrace (Reduced): #6 0x7fd94592d2f9 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x51) at /usr/include/c++/7/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x51) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x51) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:101 #10 QVector::isDetached (this=0x559f00b90128) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:106 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #8 from flo --- correction of last comment: no ssh but editing of git commit message -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #7 from flo --- Created attachment 115267 --> https://bugs.kde.org/attachment.cgi?id=115267=edit New crash information added by DrKonqi konsole (18.08.1) using Qt 5.11.1 - What I was doing when the application crashed: this time used ssh + vim and /double clicked/ while pressing shift --- Plasma Version: 5.13.5 -- Backtrace (Reduced): #6 0x7f81e6bd8ffc in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x100010001002f) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x100010001002f) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x100010001002f) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:101 #10 QVector::isDetached (this=0x1108b40) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:106 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #6 from flo --- Created attachment 115123 --> https://bugs.kde.org/attachment.cgi?id=115123=edit New crash information added by DrKonqi konsole (18.08.1) using Qt 5.11.1 - What I was doing when the application crashed: did: git commit in vim edited message and then tryed to select text in command mode pressing shift key -- Backtrace (Reduced): #6 0x7f85ae835ffc in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x5f0053454c4946) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x5f0053454c4946) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x5f0053454c4946) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:101 #10 QVector::isDetached (this=0x1dc14f0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:106 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #5 from flo --- Latest crash (in above comment #4) using KDE Plasma Version: 5.13.5 Frameworks Version: 5.50.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #4 from flo --- konsole crashed again while selecting text in vim pressing shift key - no ssh involved -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #3 from flo --- Created attachment 114897 --> https://bugs.kde.org/attachment.cgi?id=114897=edit New crash information added by DrKonqi konsole (18.08.1) using Qt 5.11.1 - What I was doing when the application crashed: again I worked via ssh in vim and selected text pressing shift-key (forgot to mention vim via ssh last time) -- Backtrace (Reduced): #6 0x7efe46be6ffc in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x280) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x280) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x280) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:101 #10 QVector::isDetached (this=0x2f5db30) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:106 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 --- Comment #1 from flo --- additional notes: - this happens since ~1 Month ago. I always keep my system uptodate. (kde-neon user edition) - I always work with multiple konsole windows and tabs - this bug is really annoying and makes work with konsole a pain -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398320] New: konsole crashes sometimes when selecting or pasting text while pressing shift key
https://bugs.kde.org/show_bug.cgi?id=398320 Bug ID: 398320 Summary: konsole crashes sometimes when selecting or pasting text while pressing shift key Product: konsole Version: 18.08.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: kde-b...@cyborgsociety.org Target Milestone: --- Application: konsole (18.08.0) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.15.0-33-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: select or paste text in vim (usually I work with vim and select or paste text while pressing shift key due to changed vim behavior automatically switching to visual mode when not pessing shift key) The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3f6b7cd8c0 (LWP 8085))] Thread 2 (Thread 0x7f3f4ef33700 (LWP 8110)): #0 0x7f3f6b176811 in __GI_ppoll (fds=fds@entry=0x7f3f48013ee8, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f3f6766db21 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f3f48013ee8) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7f3f48013ee8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7f3f6766f1b2 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f3f676195ba in QEventLoop::exec (this=this@entry=0x7f3f4ef32cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f3f6744e5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f3f6555df35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f3f67459727 in QThreadPrivate::start (arg=0x7f3f657d6d60) at thread/qthread_unix.cpp:367 #9 0x7f3f62a0e6ba in start_thread (arg=0x7f3f4ef33700) at pthread_create.c:333 #10 0x7f3f6b18241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f3f6b7cd8c0 (LWP 8085)): [KCrash Handler] #6 0x7f3f6adceffc in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x7) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x7) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x7) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:101 #10 QVector::isDetached (this=0x1ef9400) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:106 #11 QVector::detach (this=0x1ef9400) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:383 #12 QVector::data (this=0x1ef9400) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:127 #13 Konsole::Screen::copyLineToStream (this=this@entry=0x13cd350, line=line@entry=659, start=163, count=count@entry=1, decoder=decoder@entry=0x7ffcc2c628d0, appendNewLine=, options=...) at /workspace/build/src/Screen.cpp:1346 #14 0x7f3f6adcf58b in Konsole::Screen::writeToStream (this=this@entry=0x13cd350, decoder=decoder@entry=0x7ffcc2c628d0, startIndex=startIndex@entry=178752, endIndex=endIndex@entry=178752, options=options@entry=...) at /workspace/build/src/Screen.cpp:1275 #15 0x7f3f6add0152 in Konsole::Screen::text (this=0x13cd350, startIndex=178752, endIndex=178752, options=...) at /workspace/build/src/Screen.cpp:1226 #16 0x7f3f6add01f6 in Konsole::Screen::selectedText (this=, options=..., options@entry=...) at /workspace/build/src/Screen.cpp:1207 #17 0x7f3f6ad9ddaa in Konsole::Emulation::checkSelectedText (this=0x13cc700) at /workspace/build/src/Emulation.cpp:106 #18 0x7f3f676482a6 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc2c62a70, r=0x13cc700, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 #19 QMetaObject::activate (sender=0x163d970, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x0) at kernel/qobject.cpp:3754 #20 0x7f3f67648887 in QMetaObject::activate (sender=, m=m@entry=0x7f3f6b073060 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x0) at kernel/qobject.cpp:3633 #21 0x7f3f6ae22603 in Konsole::ScreenWindow::selectionChanged (this=) at /workspace/build/obj-x86_64-linux-gnu/src/moc_ScreenWindow.cpp:188 #22 0x7f3f6add0bc3 in Konsole::ScreenWindow::setSelectionStart (this=, column=, line=line@entry=659, columnMode=columnMode@entry=false) at
[kmymoney4] [Bug 370240] Not all icons at the left navbar - there are just 3 (e. g. overview)
https://bugs.kde.org/show_bug.cgi?id=370240 Flo <li...@wolke7.net> changed: What|Removed |Added CC||li...@wolke7.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362590] after login, it takes much time after starting the desktop
https://bugs.kde.org/show_bug.cgi?id=362590 --- Comment #1 from flo <flol2...@aol.com> --- I look at syslog and found this (maybe) interesting detail: KScreen seems to configure very often, unless there is "nothing" to configure (laptop connected with DisplayPort to monitor, but the login problem also happens when using the laptop-monitor): May 2 18:31:05 mylaptop org.kde.KScreen[1473]: kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) May 2 18:31:25 mylaptop org.kde.KScreen[1473]: message repeated 60 times: [ kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" )] May 2 18:31:25 mylaptop org.kde.KScreen[1473]: kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) May 2 18:31:25 mylaptop org.kde.KScreen[1473]: message repeated 18 times: [ kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" )] After this, there are some other logs. But also a lot of messages like this: May 2 18:31:33 mylaptop org.kde.KScreen[3012]: kscreen.xrandr: Connected output 67 to CRTC 63 May 2 18:31:33 mylaptop org.kde.KScreen[3012]: kscreen.xrandr: Connected output 70 to CRTC 64 I think KScreen wants to configure with xrandr the output and it seems to work?!. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362590] after login, it takes much time after starting the desktop
https://bugs.kde.org/show_bug.cgi?id=362590 flo <flol2...@aol.com> changed: What|Removed |Added CC||flol2...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362590] New: after login, it takes much time after starting the desktop
https://bugs.kde.org/show_bug.cgi?id=362590 Bug ID: 362590 Summary: after login, it takes much time after starting the desktop Product: plasmashell Version: 5.5.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: flol2...@aol.com CC: bhus...@gmail.com, plasma-b...@kde.org After login ( so type in user information on SSDM displaymanager), the loading bar enters very fast full state. Then it additional 30-40s to laod the Desktop. When the loading bar is full, I can press ALT+TAB to swtich between applications and I see for a few moments the status bar (for wlan, devices, clock etc.) I purged kde-connect, enabled and disabled wifi and bluetooth but nothing changed. System: Dell Latitude E7440 with Intel Wifi and Bluetooth wit fresh install of Kubuntu 16.04 Reproducible: Always Steps to Reproduce: 1. logout 2. login 3. Actual Results: it take a lot of time to login Expected Results: the login time does not take so much time -- You are receiving this mail because: You are watching all bug changes.
