[konversation] [Bug 428470] New: Won't accept certificate forever without being prompted
https://bugs.kde.org/show_bug.cgi?id=428470 Bug ID: 428470 Summary: Won't accept certificate forever without being prompted Product: konversation Version: Git Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: encryption Assignee: wordsiz...@gmail.com Reporter: net...@gmail.com CC: konversation-de...@kde.org Target Milestone: --- SUMMARY Accepting a server certificate forever without being prompted still prompts again when reconnecting. STEPS TO REPRODUCE 1. Connect to server with self-signed certificate 2. Press Continue 3. Press Forever 4. Right-click server in server list and click Reconnect OBSERVED RESULT Prompted again to accept certificate. EXPECTED RESULT Not prompted again to accept certificate. SOFTWARE/OS VERSIONS Konversation_Nightly_win64 Build 560 - konversation-master-560-windows-msvc2019_64-cl.exe Windows 10 20H2 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 427984] Windows 10 Startup Error using Build konversation-master-548, 549, 550
https://bugs.kde.org/show_bug.cgi?id=427984 --- Comment #6 from Jonathan Liu --- You could also use Wine to test the Windows packages.(In reply to Eli MacKenzie from comment #3) > (In reply to ralfhick...@yahoo.com from comment #0) > > Created attachment 132564 [details] > > error1 > > > > On a Windows 10 clean build I installed Konversation and received the follow > > errors: > > > > "the code execution cannot proceed because KF5NewStuff.dll was not found" > > "the code execution cannot proceed because KF5NewStuffCore.dll was not > > found" > > > > I tried this with versions 548, 549 and 550. > > I've updated the recipe, but as I don't have Windows with which to test an > immediate build we'll have to wait for the next nightly. Perhaps it can be tested using Wine? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 427984] Windows 10 Startup Error using Build konversation-master-548, 549, 550
https://bugs.kde.org/show_bug.cgi?id=427984 Jonathan Liu changed: What|Removed |Added CC||net...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427851] GIMP internal screenshot tool broken by 5.20 release
https://bugs.kde.org/show_bug.cgi?id=427851 --- Comment #1 from Jonathan Liu --- Arch Linux bug report: https://bugs.archlinux.org/task/68311 GIMP issue: https://gitlab.gnome.org/GNOME/gimp/-/issues/5785 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427851] GIMP internal screenshot tool broken by 5.20 release
https://bugs.kde.org/show_bug.cgi?id=427851 Jonathan Liu changed: What|Removed |Added CC||net...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #42 from Jonathan Liu --- (In reply to Erik Kurzinger from comment #41) > It might be quicker for you to submit the Qt patch if you don't mind. We > need to go through some bureaucracy at NVIDIA to get approval before > contributing to open source projects which can delay things a bit. > > It should be possible to detect a PRIME setup using RandR, specifically the > XRRGetProviderResources and XRRGetProviderInfo calls. If we're using the > NVIDIA driver for OpenGL, but the NVIDIA-0 provider doesn't advertise the > "sink output" capability, that should be sufficient to infer a PRIME system. It is possible for NVIDIA-0 provider to advertise the "sink output" capability but the user is using PRIME (see comment 25 for such a configuration where NVIDIA is used on desktop system for rendering but Intel is used for monitor output). This could be to workaround bugs in the NVIDIA driver or to take advantage of the additional monitor outputs on the Intel graphics. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #25 from Jonathan Liu --- It is reproducible using NVIDIA Optimus on Intel desktop system too if the CPU has Intel HD graphics, IGPU multi-monitor is enabled in BIOS (so both integrated and NVIDIA graphics card are both enabled) and the monitor is plugged into the monitor port on the motherboard instead of the NVIDIA graphics card. kernel options: nvidia-drm.modeset=1 kernel modules: nvidia nvidia_modeset nvidia_uvm nvidia_drm /etc/X11/xorg.conf: Section "ServerLayout" Identifier "layout" Screen 0 "nvidia" Inactive "intel" EndSection Section "Device" Identifier "nvidia" Driver "nvidia" BusID "" EndSection Section "Screen" Identifier "nvidia" Device "nvidia" Option "AllowEmptyInitialConfiguration" EndSection Section "Device" Identifier "intel" Driver "modesetting" EndSection Section "Screen" Identifier "intel" Device "intel" BusID "" EndSection /usr/share/sddm/scripts/Xsetup: xrandr --setprovideroutputsource modesetting NVIDIA-0 xrandr --auto -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 Jonathan Liu changed: What|Removed |Added CC||net...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356937] Xembed icons have black background
https://bugs.kde.org/show_bug.cgi?id=356937 Jonathan Liu changed: What|Removed |Added CC||net...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 400274] Follow end of plot
https://bugs.kde.org/show_bug.cgi?id=400274 Jonathan Liu changed: What|Removed |Added CC||netterfield@astro.utoronto. ||ca -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 400274] New: Follow end of plot
https://bugs.kde.org/show_bug.cgi?id=400274 Bug ID: 400274 Summary: Follow end of plot Product: kst Version: 2.0.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plotting Assignee: k...@kde.org Reporter: net...@gmail.com Target Milestone: --- I would like the ability to toggle following the end of the plot without having to use the "Change Data Samples" dialog to change the data range. This would keep the newest data sample at the right side of the plot. Often it is useful to show the plot scrolling in realtime and I currently do this by constraining the data range to a number of samples from the end. However, I would also like to be able to zoom out and see the entire data range without having to reload the entire file. Currently I need to open "Change Data Samples" dialog and change from "Count from end" to "Read to end" and this can take quite a bit of time depending on the size of the file. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395375] Pop-up palette rotates with canvas if using external ring
https://bugs.kde.org/show_bug.cgi?id=395375 --- Comment #7 from Jonathan Liu --- I have submitted a patch to fix the bug: https://phabricator.kde.org/D13703 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395375] Pop-up palette rotates with canvas if using external ring
https://bugs.kde.org/show_bug.cgi?id=395375 Jonathan Liu changed: What|Removed |Added CC||net...@gmail.com --- Comment #6 from Jonathan Liu --- I get this issue with Krita 4.0.4 with both 32-bit and 64-bit Windows versions if "Canvas Graphics Acceleration" is disabled or unavailable (for example if the graphics hardware does not support OpenGL version higher than 1.4...) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394421] Can't remove brush from My Favorites tag
https://bugs.kde.org/show_bug.cgi?id=394421 Jonathan Liu changed: What|Removed |Added CC||net...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 394844] New: Don't open window if pointer touches screen edge while mouse button held down
https://bugs.kde.org/show_bug.cgi?id=394844 Bug ID: 394844 Summary: Don't open window if pointer touches screen edge while mouse button held down Product: yakuake Version: 3.0.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: net...@gmail.com Target Milestone: --- Yakuake can open unexpectedly when dragging a window to the top screen edge to maximize it. It would be better if Yakuake could identify if any mouse buttons were held down when the screen edge was touched and if so, not open Yakuake and ignore any screen edge triggering until the mouse is moved away from the screen edge. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 394843] New: Scroll down/up when mouse at top screen edge to open/retract Yakuake
https://bugs.kde.org/show_bug.cgi?id=394843 Bug ID: 394843 Summary: Scroll down/up when mouse at top screen edge to open/retract Yakuake Product: yakuake Version: 3.0.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: net...@gmail.com Target Milestone: --- I think it would be neat to have the ability to scroll down/up while mouse is at the top screen edge to open/retract Yakuake. This could be implemented by showing a 1 pixel high window when the mouse touches the top screen edge which would receive the mouse up/down events. If there is no mouse down event within a certain period of time, it will timeout and automatically close the 1 pixel high window. -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 376122] New: Vertical markers to indicate events
https://bugs.kde.org/show_bug.cgi?id=376122 Bug ID: 376122 Summary: Vertical markers to indicate events Product: kst Version: 2.0.8 Platform: unspecified OS: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: plotting Assignee: k...@kde.org Reporter: net...@gmail.com Target Milestone: --- I think it would be good to have a feature where you can have vertical marker lines added to XY plot from file, kind of like colored bookmarks. The markers can be used to indicate an event at a specific point in time and have text associated with it. For example, you may be measuring temperature and the markers can be used to indicate when a heater was turned on/off. Hovering over these markers would show the text associated with it. Different colors can be used to indicate different kinds of events. These could be a dialog for quickly going to a marker point with ability to filter marks by text. -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 --- Comment #10 from Jonathan Liu <net...@gmail.com> --- (In reply to Jonathan Liu from comment #9) > How about having the default column names C1, C2, C3, etc.? Of course we also need a fallback for compatibility with older session files. -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 --- Comment #9 from Jonathan Liu <net...@gmail.com> --- How about having the default column names C1, C2, C3, etc.? -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 --- Comment #7 from Jonathan Liu <net...@gmail.com> --- I think the following would be desirable: - Make the session file data the same regardless of the current Kst locale, could standardize on English - Just because a German user creates a Kst session file without manually specifying labels, an English user opening the Kst session file shouldn't see automatic German labels but should see the corresponding automatic English labels -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 --- Comment #5 from Jonathan Liu <net...@gmail.com> --- Created attachment 103683 --> https://bugs.kde.org/attachment.cgi?id=103683=edit German session file -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 --- Comment #4 from Jonathan Liu <net...@gmail.com> --- Created attachment 103682 --> https://bugs.kde.org/attachment.cgi?id=103682=edit English session file -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 --- Comment #3 from Jonathan Liu <net...@gmail.com> --- Created attachment 103681 --> https://bugs.kde.org/attachment.cgi?id=103681=edit Sample Data File -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 --- Comment #1 from Jonathan Liu <net...@gmail.com> --- This can be tested from a command prompt: 1. cd "C:\Program Files (x86)\Kst-2.0.8\bin" 2. set LANG=de_DE 3. kst2.exe 4. Create plot and save session, exit Kst. 5. set LANG=en_US 6. kst2.exe 7. Open the saved session -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 375612] New: Session files not portable between different system locales
https://bugs.kde.org/show_bug.cgi?id=375612 Bug ID: 375612 Summary: Session files not portable between different system locales Product: kst Version: 2.0.8 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@kde.org Reporter: net...@gmail.com Target Milestone: --- Kst session files saved on Windows 7 with English locale don't open properly on Windows 7 with German locale. This is because when using German locale, it expects to find items in the session file with German names instead of English names. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367701] New: Crash occurs sometimes after closing a window
https://bugs.kde.org/show_bug.cgi?id=367701 Bug ID: 367701 Summary: Crash occurs sometimes after closing a window Product: plasmashell Version: 5.7.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: net...@gmail.com CC: plasma-b...@kde.org Sometimes when closing a window (e.g. if I close a Konsole with Ctrl-D), plasmashell would crash and restart itself. Reproducible: Sometimes Steps to Reproduce: I have a dual monitor setup and it sometimes occurs when closing a Konsole window with Ctrl-D. Actual Results: plasmashell crashed and restarted itself. Expected Results: plasmashell should keep running. Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7afc627800 (LWP 933))] Thread 7 (Thread 0x7f7a33267700 (LWP 1311)): #0 0x7f7af5cf848d in poll () from /usr/lib/libc.so.6 #1 0x7f7af0fa7fd6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7af0fa80ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f7af661a5ab in QEventDispatcherGlib::processEvents (this=0x7f7a2c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7af65c40ea in QEventLoop::exec (this=this@entry=0x7f7a33266d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f7af63e70f3 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f7a357990d7 in KCupsConnection::run() () from /usr/lib/libkcupslib.so #7 0x7f7af63ebd78 in QThreadPrivate::start (arg=0x50c5340) at thread/qthread_unix.cpp:344 #8 0x7f7af54fb454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f7af5d017df in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f7a455a2700 (LWP 1012)): #0 0x7f7af0fec044 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f7af0fa6f5e in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0 #2 0x7f7af0fa7e85 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f7af0fa80ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f7af661a5ab in QEventDispatcherGlib::processEvents (this=0x7f7a48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7af65c40ea in QEventLoop::exec (this=this@entry=0x7f7a455a1d50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f7af63e70f3 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f7afa2e78a6 in ?? () from /usr/lib/libQt5Quick.so.5 #8 0x7f7af63ebd78 in QThreadPrivate::start (arg=0x2beb3c0) at thread/qthread_unix.cpp:344 #9 0x7f7af54fb454 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f7af5d017df in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f7ad27aa700 (LWP 990)): #0 0x7f7af550110f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f7afbd77ac4 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f7afbd77b09 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f7af54fb454 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f7af5d017df in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f7ad3fff700 (LWP 974)): #0 0x7ffc42bcaa48 in clock_gettime () #1 0x7f7af5d0e6b6 in clock_gettime () from /usr/lib/libc.so.6 #2 0x7f7af6491191 in qt_clock_gettime (ts=0x7f7ad3ffeb00, clock=) at tools/qelapsedtimer_unix.cpp:109 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:164 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:173 #5 0x7f7af6618249 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f7acc002ed0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f7af66187f5 in QTimerInfoList::timerWait (this=0x7f7acc002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f7af6619b7e in timerSourcePrepareHelper (timeout=0x7f7ad3ffebd4, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 timerSourcePrepare (source=, timeout=0x7f7ad3ffebd4) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7f7af0fa750d in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #10 0x7f7af0fa7efb in ?? () from /usr/lib/libglib-2.0.so.0 #11 0x7f7af0fa80ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #12 0x7f7af661a5ab in QEventDispatcherGlib::processEvents (this=0x7f7acc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7f7af65c40ea in QEventLoop::exec (this=this@entry=0x7f7ad3ffeda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #14 0x7f7af63e70f3 in QThread::exec (this=) at thread/qthread.cpp:507 #15 0x7f7af9748445 in ?? () from /usr/lib/libQt5Qml.so.5 #16 0x7f7af63ebd78 in QThreadPrivate::start (arg=0x24974f0) at thread/qthread_unix.cpp:344 #17 0x7f7af54fb454 in start_thread () from /usr/lib/libpthread.so.0 #18 0x7f7af5d017df in clone ()
[drkonqi] [Bug 363838] drkonqi crashed before bugzilla login page
https://bugs.kde.org/show_bug.cgi?id=363838 --- Comment #2 from Jonathan Liu <net...@gmail.com> --- Note that I have "Enable the KDE wallet subsystem" unchecked in the KDE Wallet System Settings Module. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 363838] drkonqi crashed before bugzilla login page
https://bugs.kde.org/show_bug.cgi?id=363838 --- Comment #1 from Jonathan Liu <net...@gmail.com> --- I got a similar crash on Arch Linux 64-bit with 5.7.3. Seems to be a null pointer dereference. Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc34a2587c0 (LWP 17413))] Thread 3 (Thread 0x7fc32f280700 (LWP 17419)): #0 0x7fc3458c54ed in read () from /usr/lib/libc.so.6 #1 0x7fc341bb8c80 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fc341b75ab4 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fc341b75f74 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fc341b760ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fc3461eb5ab in QEventDispatcherGlib::processEvents (this=0x7fc3280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fc3461950ea in QEventLoop::exec (this=this@entry=0x7fc32f27fdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7fc345fb80f3 in QThread::exec (this=this@entry=0x7fc347805d20 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #8 0x7fc347594645 in QDBusConnectionManager::run (this=0x7fc347805d20 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #9 0x7fc345fbcd78 in QThreadPrivate::start (arg=0x7fc347805d20 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #10 0x7fc343875454 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fc3458d27df in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fc337909700 (LWP 17414)): #0 0x7fc3458c948d in poll () from /usr/lib/libc.so.6 #1 0x7fc340bf58e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fc340bf7679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fc33984a469 in QXcbEventReader::run (this=0x1fc6950) at qxcbconnection.cpp:1337 #4 0x7fc345fbcd78 in QThreadPrivate::start (arg=0x1fc6950) at thread/qthread_unix.cpp:344 #5 0x7fc343875454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fc3458d27df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fc34a2587c0 (LWP 17413)): [KCrash Handler] #5 QScopedPointer<QObjectData, QScopedPointerDeleter >::data (this=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:141 #6 qGetPtrHelper<QScopedPointer > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:980 #7 QDBusAbstractInterface::d_func (this=) at qdbusabstractinterface.h:158 #8 QDBusAbstractInterface::asyncCallWithArgumentList (this=0x0, method=..., args=...) at qdbusabstractinterface.cpp:519 #9 0x7fc348ce1511 in KWallet::Wallet::isOpen(QString const&) () from /usr/lib/libKF5Wallet.so.5 #10 0x004559fe in BugzillaLoginPage::openWallet (this=0x2629120) at /tmp/plasma-workspace/src/plasma-workspace-5.7.3/drkonqi/bugzillaintegration/reportassistantpages_bugzilla.cpp:177 #11 0x00457e38 in BugzillaLoginPage::walletLogin (this=0x2629120) at /tmp/plasma-workspace/src/plasma-workspace-5.7.3/drkonqi/bugzillaintegration/reportassistantpages_bugzilla.cpp:187 #12 0x7fc3461cf306 in QtPrivate::QSlotObjectBase::call (a=0x7ffe4e0737c0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:130 #13 QSingleShotTimer::timerEvent (this=0x29d6010) at kernel/qtimer.cpp:317 #14 0x7fc3461c3313 in QObject::event (this=0x29d6010, e=) at kernel/qobject.cpp:1285 #15 0x7fc346e76e3c in QApplicationPrivate::notify_helper (this=, receiver=0x29d6010, e=0x7ffe4e073aa0) at kernel/qapplication.cpp:3799 #16 0x7fc346e7e5b1 in QApplication::notify (this=0x7ffe4e073f50, receiver=0x29d6010, e=0x7ffe4e073aa0) at kernel/qapplication.cpp:3556 #17 0x7fc346196c90 in QCoreApplication::notifyInternal2 (receiver=0x29d6010, event=event@entry=0x7ffe4e073aa0) at kernel/qcoreapplication.cpp:988 #18 0x7fc3461ea52e in QCoreApplication::sendEvent (event=0x7ffe4e073aa0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #19 QTimerInfoList::activateTimers (this=0x1ff10b0) at kernel/qtimerinfo_unix.cpp:644 #20 0x7fc3461eaa51 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #21 0x7fc341b75dd7 in g_main_cont
[drkonqi] [Bug 363838] drkonqi crashed before bugzilla login page
https://bugs.kde.org/show_bug.cgi?id=363838 Jonathan Liu <net...@gmail.com> changed: What|Removed |Added CC||net...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345741] Unable to reorder entries in favorites menu after scrolling down
https://bugs.kde.org/show_bug.cgi?id=345741 --- Comment #3 from Jonathan Liu <net...@gmail.com> --- Patch submitted for review: https://phabricator.kde.org/D2310 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345741] Unable to reorder entries in favorites menu after scrolling down
https://bugs.kde.org/show_bug.cgi?id=345741 Jonathan Liu <net...@gmail.com> changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
