[dolphin] [Bug 484982] Show close button on split view
https://bugs.kde.org/show_bug.cgi?id=484982 --- Comment #2 from Michi --- (In reply to Felix Ernst from comment #1) > Hi, we are aware of this problem. However, the solution I currently favour > is that we would show a big red "X" spanning the whole view whenever the > user hovers the mouse cursor over the "Close [Split View]" button. This way > we wouldn't need extra space by default only to show a close button. Would > an indicator on hover in your opinion also fix your problem? First of all thx for your time. In my opinion I do not like the idea. It only shows more prominently that I am trying to do the wrong thing. So in the end I still have to "refocus" - literally. And honestly, the places panel, the console panel, all have a close button. I don't understand what's different about the split view? Hope this makes sense ... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484982] New: Show close button on split view
https://bugs.kde.org/show_bug.cgi?id=484982 Bug ID: 484982 Summary: Show close button on split view Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split view Assignee: dolphin-bugs-n...@kde.org Reporter: wosk...@yahoo.de CC: kfm-de...@kde.org Target Milestone: --- No matter which closing behaviour I configure, I always end up messing with which side of the split view gets closed. Also the icon doesn't help much. To begin with, you have to realize that it indicates which side of the view will be closed. But even then, you always have to think twice what you have to do. My suggestion would be a simple close button on each side of the view. There's no mental burden attached to it and you don't need extra icons, nor do you need the extra config parameter. thx Michi -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 Michi changed: What|Removed |Added CC|wosk...@yahoo.de| -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 Michi changed: What|Removed |Added CC||wosk...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 399232] Add linux pass backend to KDE Wallet service
https://bugs.kde.org/show_bug.cgi?id=399232 --- Comment #6 from Michi --- (In reply to michaelk83 from comment #5) > (In reply to michaelk83 from comment #4) > > What you want here is a separate daemon that exposes the pass backend > > through the Secret Service API. > Actually, this already exists: > https://github.com/mdellweg/pass_secret_service > Should've googled first. I think we're talking about different things. As far as I understood that change from 5.97, it made passwords stored in kwallet accessible through the Secret Service API. What we want is the other way round, using passwords from other password stores in KDE apps. And that's still not possible. Please correct me if I'm wrong. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385321] Screen locker 'unable to unlock, use loginctl instead' randomly when system is locked
https://bugs.kde.org/show_bug.cgi?id=385321 Michi changed: What|Removed |Added CC||wosk...@yahoo.de --- Comment #10 from Michi --- I'm hit by this as well. But what I think is even more concerning, why on earth do we need another screen/action to actually unlock the screen? Why not just enter the password and that's it - as it was before? bye Mchi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 450907] New: kdeconnect crashes on network changes
https://bugs.kde.org/show_bug.cgi?id=450907 Bug ID: 450907 Summary: kdeconnect crashes on network changes Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: wosk...@yahoo.de Target Milestone: --- Application: kdeconnectd (21.12.2) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.16.4-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I think I disabled wifi when the crash happened. One thing to note is, that I was trying out the iwd backend (which btw does absolutely not work) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7fcc6f9a1324 in (anonymous namespace)::constData (d=...) at kernel/qvariant.cpp:361 #5 qVariantToHelper > (handlerManager=..., d=...) at kernel/qvariant.cpp:2669 #6 QVariant::toMap (this=0x564dc6a91088) at kernel/qvariant.cpp:2721 #7 0x7fcc68006378 in ConnectivityReportPlugin::receivePacket (np=..., this=) at /usr/src/debug/kdeconnect-kde-21.12.2-1.2.x86_64/plugins/connectivity-report/connectivity_reportplugin.cpp:44 #8 ConnectivityReportPlugin::receivePacket (this=, np=...) at /usr/src/debug/kdeconnect-kde-21.12.2-1.2.x86_64/plugins/connectivity-report/connectivity_reportplugin.cpp:40 #9 0x7fcc70f21e01 in Device::privateReceivedPacket (this=0x564dc69d1b20, np=...) at /usr/src/debug/kdeconnect-kde-21.12.2-1.2.x86_64/core/device.cpp:398 #10 0x7fcc6f98a503 in QtPrivate::QSlotObjectBase::call (a=0x7ffe5d5b6850, r=0x564dc69d1b20, this=0x564dc6c87a30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x564dc6c6d430, signal_index=7, argv=0x7ffe5d5b6850) at kernel/qobject.cpp:3886 #12 0x7fcc6f9839cf in QMetaObject::activate (sender=sender@entry=0x564dc6c6d430, m=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffe5d5b6850) at kernel/qobject.cpp:3946 #13 0x7fcc70f12bfd in DeviceLink::receivedPacket (_t1=..., this=0x564dc6c6d430) at /usr/src/debug/kdeconnect-kde-21.12.2-1.2.x86_64/build/core/kdeconnectcore_autogen/CSWKE6ESUK/moc_devicelink.cpp:225 #14 LanDeviceLink::dataReceived (this=0x564dc6c6d430) at /usr/src/debug/kdeconnect-kde-21.12.2-1.2.x86_64/core/backends/lan/landevicelink.cpp:135 #15 0x7fcc6f98a503 in QtPrivate::QSlotObjectBase::call (a=0x7ffe5d5b6930, r=0x564dc6c6d430, this=0x564dc6c86630) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x564dc6c6d9b0, signal_index=3, argv=0x7ffe5d5b6930) at kernel/qobject.cpp:3886 #17 0x7fcc70f0b114 in SocketLineReader::dataReceived (this=0x564dc6c6d9b0) at /usr/src/debug/kdeconnect-kde-21.12.2-1.2.x86_64/core/backends/lan/socketlinereader.cpp:29 #18 0x7fcc6f98a503 in QtPrivate::QSlotObjectBase::call (a=0x7ffe5d5b6a40, r=0x564dc6c6d9b0, this=0x564dc6b74010) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate (sender=0x564dc6a97ab0, signal_index=3, argv=0x7ffe5d5b6a40) at kernel/qobject.cpp:3886 #20 0x7fcc6f9839cf in QMetaObject::activate (sender=sender@entry=0x564dc6a97ab0, m=m@entry=0x7fcc6fc26280 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #21 0x7fcc6f882250 in QIODevice::readyRead (this=this@entry=0x564dc6a97ab0) at .moc/moc_qiodevice.cpp:190 #22 0x7fcc6f0ab705 in QSslSocketBackendPrivate::transmit (this=0x564dc6aea250) at ssl/qsslsocket_openssl.cpp:1162 #23 0x7fcc6f98a538 in doActivate (sender=0x564dc6a78900, signal_index=3, argv=0x7ffe5d5b7bb0) at kernel/qobject.cpp:3898 #24 0x7fcc6f9839cf in QMetaObject::activate (sender=sender@entry=0x564dc6a78900, m=m@entry=0x7fcc6fc26280 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #25 0x7fcc6f882250 in QIODevice::readyRead (this=this@entry=0x564dc6a78900) at .moc/moc_qiodevice.cpp:190 #26 0x7fcc6f062eef in QAbstractSocketPrivate::emitReadyRead (channel=0, this=0x564dc6a32700) at socket/qabstractsocket.cpp:1323 #27 QAbstractSocketPrivate::canReadNotification (this=0x564dc6a32700) at socket/qabstractsocket.cpp:748 #28 0x7fcc6f078ca1 in QReadNotifier::event (this=, e=) at socket/qnativesocketengine.cpp:1274 #29 0x7fcc70598a7f in QApplicationPrivate::notify_helper (this=, receiver=0x564dc6b50280, e=0x7ffe5d5b7cf0) at kernel/qapplication.cpp:3632 #30 0x7fcc6f953e3a in QCoreApplication::notifyInternal2 (receiver=0x564dc6b50280, event=0x7ffe5d5b7cf0) at kernel/qcoreapplication.cpp:1064 #31 0x7fcc6f9abf3d in
[Akonadi] [Bug 414829] Subscribing to public Folders and other Users Calendars
https://bugs.kde.org/show_bug.cgi?id=414829 Michi changed: What|Removed |Added CC||wosk...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 393898] Kmail2 EWS does not load contacts - version 17.12.3
https://bugs.kde.org/show_bug.cgi?id=393898 Michi changed: What|Removed |Added CC||wosk...@yahoo.de --- Comment #10 from Michi --- this problem still exists in 21.12.0, although EWS now runs smoother than before for calendar and email -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 399232] Add linux pass backend to KDE Wallet service
https://bugs.kde.org/show_bug.cgi?id=399232 Michi changed: What|Removed |Added CC||wosk...@yahoo.de --- Comment #2 from Michi --- I have to second that ... -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407382] axis and data do not relate to each other
https://bugs.kde.org/show_bug.cgi?id=407382 --- Comment #9 from Michi --- (In reply to Alexander Semke from comment #8) > well, I asked you to provide the project file almost one year ago, soon > after you reported this issue. We could have fixed this problem fast and > avoid any kind of frustration. This is an open-source project developed by > people in their spare time and we also need user's feedback to improve the > software. Not providing the information the developer has kindly asked for > and report after this frustration is not the feedback that helps us. Hi Alex, alright, I did not provide the project file - my bad. I think there were some company specific information in it and I wanted to remove that first, and then I forgot ... What added to my decision though was Bug 403304 which is more of a biggy, for me as a user, and as it seems for you as a developer as well. So, my appologies if I was hurting your feelings, it was definitely not my intention. I really appreciate what you are doing. bye Michi -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407382] axis and data do not relate to each other
https://bugs.kde.org/show_bug.cgi?id=407382 --- Comment #7 from Michi --- (In reply to Alexander Semke from comment #6) > Can you please attach your project file? Hi Alex, sorry, but I have moved on and I'm currently not using labplot anymore, it was too frustrating. I couldn't trust the diagrams anymore. bye Michi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359331] Multiple Kontact and KMail Instances upon start
https://bugs.kde.org/show_bug.cgi?id=359331 Michi changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Michi --- long gone -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380078] Mouse remote control does not work using Wayland
https://bugs.kde.org/show_bug.cgi?id=380078 --- Comment #7 from Michi --- (In reply to Nicolas Fella from comment #6) > (In reply to Michi from comment #5) > > this is not limited to gnome! I have the exact same issue with kwin/wayland. > > With kwin/X11 backend it's working though. > > > > bye Michi > > Which version of Plasma are you using? latest from git (openSUSE) -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407382] axis and data do not relate to each other
https://bugs.kde.org/show_bug.cgi?id=407382 --- Comment #4 from Michi --- Created attachment 120030 --> https://bugs.kde.org/attachment.cgi?id=120030=edit it's not about precision the precision has been manually adjusted according to advice, but it does not touch the core of the problem. In this screenshot one can see one and the same data set. The range of the y-axis of the scatter plot has been manually adjusted, which I assume should have consequences on how the data set(s) are displayed, but that doesn't happen. Instead the y-axis shows labels which I can't make any sense of; setting the range from 1.5 to 1.7 removes all labels, for instance. Btw. the x-axis should intersect at 1.65 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380078] Mouse remote control does not work using Wayland
https://bugs.kde.org/show_bug.cgi?id=380078 Michi changed: What|Removed |Added Summary|Mouse remote control does |Mouse remote control does |not work on Gnome Shell |not work using Wayland |using Wayland | -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380078] Mouse remote control does not work on Gnome Shell using Wayland
https://bugs.kde.org/show_bug.cgi?id=380078 Michi changed: What|Removed |Added CC||wosk...@yahoo.de --- Comment #5 from Michi --- this is not limited to gnome! I have the exact same issue with kwin/wayland. With kwin/X11 backend it's working though. bye Michi -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407382] axis and data do not relate to each other
https://bugs.kde.org/show_bug.cgi?id=407382 --- Comment #1 from Michi --- Created attachment 119944 --> https://bugs.kde.org/attachment.cgi?id=119944=edit exmple 1 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407382] axis and data do not relate to each other
https://bugs.kde.org/show_bug.cgi?id=407382 --- Comment #2 from Michi --- Created attachment 119945 --> https://bugs.kde.org/attachment.cgi?id=119945=edit example 2 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407382] New: axis and data do not relate to each other
https://bugs.kde.org/show_bug.cgi?id=407382 Bug ID: 407382 Summary: axis and data do not relate to each other Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: wosk...@yahoo.de Target Milestone: --- I just came to realize that the axis values do not align with the data sets. I'll send some screenshots where all ranges have been selected to 'auto'. In those screenshots the axis should be placed at 0.218, but the screenshots give a different picture ... When I adjust the ranges manually the axis values do things that I don't really understand. For me as a stupid user this is all incomprehensible. bye Michi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407199] cannot start Wayland session on neon dev unstable. coredumpctl indicates kwin_wayland crash.
https://bugs.kde.org/show_bug.cgi?id=407199 Michi changed: What|Removed |Added CC||wosk...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 394319] sasl plugin for xoauth2 not properly registered(?)
https://bugs.kde.org/show_bug.cgi?id=394319 --- Comment #2 from Michi --- (In reply to Daniel Vrátil from comment #1) > The problem was in the soname (or the missing soname symlinks) if I recall > correctly, this should be fixed now, though. > > Is this still reproducible? I haven't heard anything from opensuse packagers > in a while about this. it is indeed working now bye Michi -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #27 from Michi --- (In reply to Stefan Gerlach from comment #26) > here is the latest package including the current code: > https://theorie.physik.uni-konstanz.de/gerlach/labplot/labplot-2.6.0rc15- > 64bit-setup.exe and this one works as well now. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #25 from Michi --- I can confirm that it's working on my linux box -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #24 from Michi --- (In reply to Stefan Gerlach from comment #23) > I can not reproduce the crash with the latest code on Windows. Here is an up > to date package: > https://theorie.physik.uni-konstanz.de/gerlach/labplot/labplot-2.6.0rc14- > 64bit-setup.exe > > Can you try this new package? this one doesn't crash, but it seems it doesn't have the fix yet. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #21 from Michi --- (In reply to Alexander Semke from comment #20) > (In reply to Michi from comment #14) > > (In reply to Alexander Semke from comment #11) > > > There are three different problems here: > > > 1. the curve is not updated after "recalculate" > > > 2. crash in XYCurvePrivate::recalcLogicalPoints() when loading the saved > > > project you attached > > > 3. crash when creating a new xy-plot > > > > > > Thank you for reporting these problems. On windows I can only reproduce > > > the > > > third problem. On linux none of them. In case you also have these issues > > > on > > > linux, can you please compile the debug build (simply execute > > > ./compile_debug) and paste here the crash call-stack. > > > > on linux there is no crash. as for 1. & 2. it was simply the wrong file :( > > I just did a fix for the problem with the curve updates. Can you please pull > the current code and try again? OBS is currently doing a build. > > As for other issues, the crash on windows when creating a new xy-plot is > reproducible. Something is broken in the build. We'll check this. For the > crash in XYCurvePrivate::recalcLogicalPoint(), can you please send me that > project file leading to the crash? Independent on how wrong that file is, we > shouldn't crash... you don't actually need a file. just try to create a fresh new plot and that's it. and thanks so far for the quick resolution -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #15 from Michi --- (In reply to Michi from comment #13) > Created attachment 118014 [details] > this is not working on my linux box > > after some time of changing settings of the xy-plots the recalculate button > stopped working (on linux) e.g. changing x,max of the 3rd plot -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #14 from Michi --- (In reply to Alexander Semke from comment #11) > There are three different problems here: > 1. the curve is not updated after "recalculate" > 2. crash in XYCurvePrivate::recalcLogicalPoints() when loading the saved > project you attached > 3. crash when creating a new xy-plot > > Thank you for reporting these problems. On windows I can only reproduce the > third problem. On linux none of them. In case you also have these issues on > linux, can you please compile the debug build (simply execute > ./compile_debug) and paste here the crash call-stack. on linux there is no crash. as for 1. & 2. it was simply the wrong file :( -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #13 from Michi --- Created attachment 118014 --> https://bugs.kde.org/attachment.cgi?id=118014=edit this is not working on my linux box after some time of changing settings of the xy-plots the recalculate button stopped working (on linux) -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #12 from Michi --- Comment on attachment 117978 --> https://bugs.kde.org/attachment.cgi?id=117978 test file this was the wrong file -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #10 from Michi --- (In reply to Alexander Semke from comment #8) > (In reply to Michi from comment #7) > > just verified that it also happens on my linux computer where I follow the > > git master. > the crash happens if you load a saved project. This is another problem. I > cannot reproduce this, neither. Can you please send me your project you're > testing with? it also crashes as soon as you try to create an xy-plot > > As to the original problem, do you still have that problem with the curve > being not recalculated on that windows build or on the current master on > linux? So, if you create a new project and produce such an equation curve, > do you still have this problem with the current code? I do. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #9 from Michi --- Created attachment 117978 --> https://bugs.kde.org/attachment.cgi?id=117978=edit test file -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #7 from Michi --- just verified that it also happens on my linux computer where I follow the git master. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #6 from Michi --- Hi Alex, this build crashes when creating an xy plot: 1 XYCurvePrivate::recalcLogicalPoints() 0x4f7722 2 XYCurveSetXColumnCmd::finalize() 0xa7b97a 3 AbstractAspect::exec(QUndoCommand *) 0x426e19 4 XYCurve::setXColumn(AbstractColumn const *) 0x4f5d80 5 XYEquationCurve::init() 0x5019d5 6 XYEquationCurve::XYEquationCurve(QString const&) 0x502672 7 CartesianPlot::load(XmlStreamReader *, bool) 0x4c2652 8 Worksheet::load(XmlStreamReader *, bool) 0x494aa9 9 Folder::readChildAspectElement(XmlStreamReader *, bool) 0x425464 10 Project::load(XmlStreamReader *, bool) 0x436e9f 11 Project::load(QString const&, bool) 0x43362d 12 MainWin::openProject(QString const&) 0x40a858 13 MainWin::openRecentProject(QUrl const&) 0x40aa3e 14 MainWin::qt_static_metacall(QObject *, QMetaObject::Call, int, void * *) 0x5d7729 15 QMetaObject::activate(QObject *, int, int, void * *) 0x68a62174 16 KRecentFilesAction::qt_static_metacall(QObject *, QMetaObject::Call, int, void * *) 0x6a91f875 17 QMetaObject::activate(QObject *, int, int, void * *) 0x68a62174 18 KSelectAction::actionTriggered(QAction *) 0x701bd1a9 19 QMetaObject::activate(QObject *, int, int, void * *) 0x68a622fb 20 QActionGroup::hovered(QAction *) 0x1804ce2 ... -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #4 from Michi --- Created attachment 117839 --> https://bugs.kde.org/attachment.cgi?id=117839=edit video capture -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 --- Comment #2 from Michi --- I tried on 2 machines with a couple of sine functions from 0..2pi. same problem on both systems. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403561] New: plot from mathematical equation does not update when doing a 'Recalculate'
https://bugs.kde.org/show_bug.cgi?id=403561 Bug ID: 403561 Summary: plot from mathematical equation does not update when doing a 'Recalculate' Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: wosk...@yahoo.de Target Milestone: --- the first time you create a plot from a mathematical equation everything works fine. But as soon as you change something in the equation and press recalculate nothing happens. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403304] New: Can't figure out how to plot data against second y-axis
https://bugs.kde.org/show_bug.cgi?id=403304 Bug ID: 403304 Summary: Can't figure out how to plot data against second y-axis Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: wosk...@yahoo.de Target Milestone: --- although an xy-plot can have multiple x- and y-axis I can't find a way how to map certain data to either of those axis. It could also be my ignorance of course thx Michi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 282132] mail replies are shown in the message list without sender (aka from:) information
https://bugs.kde.org/show_bug.cgi?id=282132 --- Comment #9 from Michi <wosk...@yahoo.de> --- I no longer see this happening -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 394319] New: sasl plugin for xoauth2 not properly registered(?)
https://bugs.kde.org/show_bug.cgi?id=394319 Bug ID: 394319 Summary: sasl plugin for xoauth2 not properly registered(?) Product: libkgapi Version: GIT Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: dvra...@kde.org Reporter: wosk...@yahoo.de Target Milestone: --- Created attachment 112684 --> https://bugs.kde.org/attachment.cgi?id=112684=edit sasl plugins since updating to the latest git version I can no longer connect to the gmail server. akonadictl says: org.kde.pim.kimap: sasl_client_start failed with: -4 "SASL(-4): no mechanism available: No worthy mechs found" now, if I call pluginviewer from cyrus-sasl it shows me the list of registered plugins which I will upload as an attachment. Note that libkdexoauth2.so.3.0.0 is installed under /usr/lib64/sasl2/ together with all the other sasl plugins. I assume it has to do with commmit 2af9da57a20f041f55fcff5ccdf6d687b9d99510 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 385547] Ugly scaling of text and icons in QML apps that use QtQuickControls1
https://bugs.kde.org/show_bug.cgi?id=385547 --- Comment #11 from Michi <wosk...@yahoo.de> --- Created attachment 110708 --> https://bugs.kde.org/attachment.cgi?id=110708=edit screenshot for test case -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 385547] Ugly scaling of text and icons in QML apps that use QtQuickControls1
https://bugs.kde.org/show_bug.cgi?id=385547 Michi <wosk...@yahoo.de> changed: What|Removed |Added CC||wosk...@yahoo.de --- Comment #10 from Michi <wosk...@yahoo.de> --- Created attachment 110707 --> https://bugs.kde.org/attachment.cgi?id=110707=edit test case -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 251222] First entry is not checked when something is copied by CTRL-C or mouse selection, even after choosing it in klipper window after copy
https://bugs.kde.org/show_bug.cgi?id=251222 --- Comment #20 from Michi <wosk...@yahoo.de> --- (In reply to Lubos Lunak from comment #19) I can confirm that things have changed for the better. I'm so relieved that this is working again. ... well mostly. I've found that konsole/yakuake does not grab the last entry from the clipboard. The second situation comes from using kde-connect; while the clipboards get properly synchronized, the mouse action still does not pick up the right entry. nonetheless, thanks a lot for the fix -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 282132] mail replies are shown in the message list without sender (aka from:) information
https://bugs.kde.org/show_bug.cgi?id=282132 --- Comment #7 from Michi <wosk...@yahoo.de> --- sorry Kevin, I should have been more precise. With now I mean a recent snapshot from git master (~ a week old). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 282132] mail replies are shown in the message list without sender (aka from:) information
https://bugs.kde.org/show_bug.cgi?id=282132 --- Comment #5 from Michi <wosk...@yahoo.de> --- for more than 5 years now. It's an account on a Strato server. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 310037] updated events have mangled date information
https://bugs.kde.org/show_bug.cgi?id=310037 --- Comment #2 from Michi <wosk...@yahoo.de> --- as you can see here https://bugs.kde.org/show_bug.cgi?id=257723#c13, the whole invitation handling is broken, I can't verify whether the problem still exists. I can't even add an invitation to my calender in the first place. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 330041] kontact crashes when closing app while IMAP operation is still ongoing
https://bugs.kde.org/show_bug.cgi?id=330041 --- Comment #2 from Michi <wosk...@yahoo.de> --- seems to be fixed -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 257723] Invitation replies are always sent immediately
https://bugs.kde.org/show_bug.cgi?id=257723 --- Comment #13 from Michi <wosk...@yahoo.de> --- (In reply to Denis Kurz from comment #12) it's even worse now. The only action shown in an invitation now is "check my calender" which only opens the korganizer; I would expect to see a marker where the event would be, but see nothing. but back to the original problem, since I can't reply at all, there's no way how "replies are always sent immediately" - bug resolved ;-) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 314783] slow IMAP connection hogs the preview pane
https://bugs.kde.org/show_bug.cgi?id=314783 --- Comment #4 from Michi <wosk...@yahoo.de> --- (In reply to Denis Kurz from comment #3) this still exists. Generally, this is the case after a lost network connection (e.g. after the computer went into sleep mode). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 282132] mail replies are shown in the message list without sender (aka from:) information
https://bugs.kde.org/show_bug.cgi?id=282132 --- Comment #3 from Michi <wosk...@yahoo.de> --- I still have this problem, but only with one particular mail account. All my other accounts do not exhibit this behavior. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356431] no address autocompletion
https://bugs.kde.org/show_bug.cgi?id=356431 --- Comment #5 from Michi <wosk...@yahoo.de> --- just recently I realized that auto-completion started to work again as expected. I can't make out any particular reason, but I have Qt 5.7.1 and a very fresh snapshot of the fleet of KDE software/libraries, provided by the openSUSE build servers. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 364691] viewer does not render HTML content
https://bugs.kde.org/show_bug.cgi?id=364691 Michi <wosk...@yahoo.de> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Michi <wosk...@yahoo.de> --- sorry, I still had an old version of grantlee installed. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 364691] New: viewer does not render HTML content
https://bugs.kde.org/show_bug.cgi?id=364691 Bug ID: 364691 Summary: viewer does not render HTML content Product: kdepim Version: GIT (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: messageviewer Assignee: kdepim-b...@kde.org Reporter: wosk...@yahoo.de the content area of the message viewer remains empty when an email is in HTML format. plain text works fine though. I have just updated to a git snapshot from June 23th. Qt is version 5.7. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359331] New: Multiple Kontact and KMail Instances upon start
https://bugs.kde.org/show_bug.cgi?id=359331 Bug ID: 359331 Summary: Multiple Kontact and KMail Instances upon start Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: wosk...@yahoo.de Application: kmail (5.1.49 pre) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1.g1d8e94b-default x86_64 Distribution: "openSUSE Tumbleweed (20160126) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: For a couple of days now, whenever I open Kontact for thefirst time after session start I get 2 instances (windows) of Kontact and and additional KMail window, which then crashes. I think it started after I tried to send a document directly from inside LibreOffice, but I'm not sure. I've installed a snapshot from today from OBS. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8e9ff82940 (LWP 2744))] Thread 16 (Thread 0x7f8e7b1f1700 (LWP 2749)): #0 0x7f8e9cfc924d in poll () at /lib64/libc.so.6 #1 0x7f8e90023432 in () at /usr/lib64/libxcb.so.1 #2 0x7f8e90025007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f8e7cf19e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f8e9d8d19df in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8e930f04a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8e9cfd1bdd in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f8e70fd3700 (LWP 2778)): #0 0x7f8e9cfc924d in poll () at /lib64/libc.so.6 #1 0x7f8e92bce494 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e92bce59c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e9daf73bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8e9daa146a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8e9d8ccb9c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e9d8d19df in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8e930f04a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8e9cfd1bdd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f8e6a5de700 (LWP 3260)): #0 0x7f8e9cfc522d in read () at /lib64/libc.so.6 #1 0x7f8e92c106b0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e92bcdfc4 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e92bce438 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8e92bce59c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8e9daf73bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e9daa146a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8e9d8ccb9c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f8e9d8d19df in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8e930f04a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8e9cfd1bdd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f8e6addf700 (LWP 3262)): #0 0x7f8e9cfc924d in poll () at /lib64/libc.so.6 #1 0x7f8e92bce494 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e92bce59c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e9daf73bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8e9daa146a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8e9d8ccb9c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e9d8d19df in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8e930f04a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8e9cfd1bdd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f8e6bfff700 (LWP 3264)): #0 0x7f8e930f607f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8e8de8a3bb in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f8e8de8a3f9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f8e930f04a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f8e9cfd1bdd in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f8e6b7fe700 (LWP 3265)): #0 0x7f8e9daf549b in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #1 0x7f8e9daf681e in () at /usr/lib64/libQt5Core.so.5 #2 0x7f8e92bcdabd in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e92bce3c3 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8e92bce59c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8e9daf73bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e9daa146a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8e9d8ccb9c
[kmail2] [Bug 356431] New: no address autocompletion
https://bugs.kde.org/show_bug.cgi?id=356431 Bug ID: 356431 Summary: no address autocompletion Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: wosk...@yahoo.de When I enter the address field and start typing some characters, there are no suggestions. At some stage I realised that when I type in at least 1 or 2 characters, delete them again using backspace, and then trying to type the characters anew, then autocompletion starts working. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
