https://bugs.kde.org/show_bug.cgi?id=402242
vialav changed:
What|Removed |Added
CC||d...@bk.ru
--- Comment #2 from vialav ---
@Juraj
https://bugs.kde.org/show_bug.cgi?id=408175
Bug ID: 408175
Summary: Vertical Tabs: unload crashes the master-branch Falkon
Product: Falkon
Version: 3.1.0
Platform: Compiled Sources
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=408176
Bug ID: 408176
Summary: Alternative initialisation? Sagemath (= 8.6-6) on
python 2 (unicode issue?) crashes on: exec
sage-ipython -i --simple-prompt
Product: cantor
Vers
https://bugs.kde.org/show_bug.cgi?id=408179
Bug ID: 408179
Summary: Alternative initialisation? The properly patched Julia
v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
Product: cantor
Version: unspecified
Platform:
https://bugs.kde.org/show_bug.cgi?id=408175
vialav changed:
What|Removed |Added
Summary|Vertical Tabs: unload |Tab Mnager: unload crashes
|crashes
https://bugs.kde.org/show_bug.cgi?id=408175
vialav changed:
What|Removed |Added
Summary|Tab Mnager: unload crashes |Tab Manager: unload crashes
|the
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #2 from vialav ---
Hi, Nikita,
Thanks for your attention to this report. I run the following:
$ which sage
/usr/bin/sage
$ dpkg -l sagemath
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #5 from vialav ---
Hi, Nikita,
I am puzzled… Are we both using:
Cantor v19.07.70+git20190523
# master branch, merged into Applications/19.04 (are you verifying the same?)
Aren't there 'exception_in_transit&#
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #6 from vialav ---
Yes, I was rebuilding Cantor after each Julia headers upgrade, with no specific
manipulations.
The version(s) of Julia I was using were simply the prepared receipt of:
https://packages.debian.org/src:julia
# list of
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #5 from vialav ---
Hi, Antonio, the below is the step-by-step procedure of `sage-ipython -i
--simple-prompt`. Please note, that `sage -python` or `sage --notebook=jupyter`
(unconveniently opens the browser) otherwise both work as expected
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #4 from vialav ---
Created attachment 120477
--> https://bugs.kde.org/attachment.cgi?id=120477&action=edit
sage-ipython invocation crash
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402242
--- Comment #4 from vialav ---
Hi, Juraj,
Mine was rather the (unhelpful) ID of my local merge commit, sorry. It was
shown in 'About'…
You reply gives me a hope, that a number of thing might, actually, work. Among
which are also non-workin
https://bugs.kde.org/show_bug.cgi?id=402242
--- Comment #5 from vialav ---
So here is my Falkon version, it was compiled from a commit of May 20.
$ dpkg -l falkon
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #8 from vialav ---
Nikita, I mistook my reverted patch for the direct one (I couldn't have
compiled the said backend with the wrong one), sorry for not checking.
So, true:
>> Future Julia versions since v1.
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #8 from vialav ---
Thank you for a suggestion. I gave it a try:
$ /usr/share/cantor/sagebackend/sage
/usr/share/cantor/sagebackend/sage: line 244:
/usr/share/cantor/sagebackend/sage-env: No such file or directory
Error setting environment
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #11 from vialav ---
Thank you, I'll try it now and will be shortly back.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #9 from vialav ---
// So, my memory reminded me where I was tracking down it to Python 2 and:
$ cd /usr/lib/python2.7/dist-packages/IPython && grep -rnw simple_prompt
terminal/interactiveshell.py:106:simple_promp
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #12 from vialav ---
Created attachment 120481
--> https://bugs.kde.org/attachment.cgi?id=120481&action=edit
Calculating…
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #13 from vialav ---
Created attachment 120482
--> https://bugs.kde.org/attachment.cgi?id=120482&action=edit
build log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #14 from vialav ---
I did everything as being told, and there is no difference in the end result…
Usually I don't need to set JULIA_EXECUTABLE, as it is in the default path:
-DJULIA_EXECUTABLE=/usr/bin/julia
> Also, it's hel
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #16 from vialav ---
Ok, that 'None' did come from Debian 'automagic', I didn't set it on purpose.
However, the second (for me the only one) -DCMAKE_BUILD_TYPE=debug shadows
(rewrites anew) ehm… the CMAKE_BUILD_
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #19 from vialav ---
I'm turning all the optimization off, commenting out, and will post the result.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #20 from vialav ---
Ok, because compiling with the only flag:
# see FEATURE AREAS in dpkg-buildflags(1)
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
…I've got essentially the same results, again, then it must me the main
su
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #21 from vialav ---
Might it be a compiler (gcc-9 in my case, I may try it with clang)? I turned
off all the optimizations, hardening, and explicitly requested
export DEB_BUILD_MAINT_OPTIONS = noopt
… -DCMAKE_BUILD_TYPE=debug
Running
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #22 from vialav ---
So, it is, likely, how I've got a source?…
with clang-9:
#0 0x in ()
#1 0x7633b77f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #24 from vialav ---
ok, thanks for a hint
As a sidenote:
No, it is not the way I've got the source. Following the standard procedure of
'git-cloning' (with no merging), and compiling with clang-9 in this last case
(wit
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #25 from vialav ---
Your suggestion was timely:
My system has exported:
QT_LOGGING_RULES=*.debug=false
But that was meant essentially to preserve the only debug output. It puzzles me
what the 'debug' output was that or
https://bugs.kde.org/show_bug.cgi?id=408179
vialav changed:
What|Removed |Added
Summary|Alternative initialisation? |Alternative initialisation?
|Julia
https://bugs.kde.org/show_bug.cgi?id=408179
vialav changed:
What|Removed |Added
Summary|Alternative initialisation? |Alternative initialisation?
|The
https://bugs.kde.org/show_bug.cgi?id=408179
vialav changed:
What|Removed |Added
Summary|Alternative initialisation? |Alternative initialisation?
|Julia
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #29 from vialav ---
> What about cantor_juliaserver process?
I run a watcher, and cantor_juliaserver does never show up, at any stage. Yes,
it is present on my system:
$ objdump -p $(which cantor_juliaserver) # yields a normal objd
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #32 from vialav ---
$ julia
_
_ _ _(_)_ | Documentation: https://docs.julialang.org
(_) | (_) (_)|
_ _ _| |_ __ _ | Type "?" for help, "]
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #33 from vialav ---
> In 1e144559c034ff70b23b3d6b5c1b7b28dbf8af18 on master I had made a few
> improvments of Julia backend.
I will be shortly back and give it a try. Thank you for working on this.
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #34 from vialav ---
$ cantor
QObject::connect: signal not found in KSelectAction
QObject::connect: signal not found in KToggleAction
QObject::connect: signal not found in QAction
QObject::connect: signal not found in QAction
QObject
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #39 from vialav ---
I've just recompiled Cantor, and the buttons still does'nt work. If I install
the previous version, the buttons work, however. Cleaning the installation is
ensured by the Debian packaging for 100%, and I w
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #40 from vialav ---
I can swiftly report that the buttons still don't work with the latest code
(the same symptoms). About Python refactoring I may open a new ticket, if
needed, but both the python(s) backend(s) stopped working, seem
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #41 from vialav ---
…and cantor_python(s) were present in the processes after exiting Cantor.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #42 from vialav ---
…one last addition, because I think it would be useful:
The just described first mouse-only clicking segfaulting behaviour to execute
the cell ('Hello' example, or, indeed, any other) in Cantor under Python
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #44 from vialav ---
I see one more commit about the Python backend, with which I want to re-compile
Cantor, and then sort out the tickets. Here I just want to clarify, that my
system has a single system-wide Python2/3 installation(s
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #45 from vialav ---
dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package cantor
dpkg-buildpackage: info: source version
4:19.07.70+git20190603-0ubuntu1+mkl~18.04.2
dpkg-buildpackage: info: source distribution bionic
dpkg
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #46 from vialav ---
[ 10%] Building CXX object
src/lib/CMakeFiles/cantorlibs.dir/directives/plotdirectives.cpp.o
cd /home/cantor/cantor-19.07.70+git20190603/obj-x86_64-linux-gnu/src/lib &&
/usr/bin/c++ -DKCOREADDONS_LIB -DQT_CONCUR
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #47 from vialav ---
[ 32%] Generating ui_settings.h
cd
/home/ubuntu/src/salsa.debian.org/qt-kde-team/cantor-19.07.70+git20190603/cantor-19.07.70+git20190603/obj-x86_64-linux-gnu/src/backends/octave
&& /usr/b
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #48 from vialav ---
/home/cantor/cantor-19.07.70+git20190603/src/backends/octave/octavesyntaxhelpobject.cpp:
In member function ‘void OctaveSyntaxHelpObject::fetchingDone
(Cantor::Expression::Status)’:
/home/cantor/cantor-19.07.70
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #49 from vialav ---
In file included from
/home/cantor/cantor-19.07.70+git20190603/src/backends/R/rextensions.h:24,
from
/home/cantor/cantor-19.07.70+git20190603/src/backends/R/rbackend.cpp:24:
/home/cantor/cantor-19.07.70
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #50 from vialav ---
In file included from
/home/cantor/cantor-19.07.70+git20190603/src/backends/R/rextensions.h:24,
from
/home/cantor/cantor-19.07.70+git20190603/src/backends/R/rbackend.cpp:24:
/home/cantor/cantor-19.07.70
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #51 from vialav ---
/home/cantor/cantor-19.07.70+git20190603/src/backends/R/rcompletionobject.cpp:
In member function ‘void RCompletionObject::receiveCompletions(Cantor::
Expression::Status)’:
/home/cantor/cantor-19.07.70+git20190603/src
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #52 from vialav ---
I'm testing Cantor now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #53 from vialav ---
I hardly could make a better report than the following:
[This block shortly appears before any further session, and goes away]:
QObject::connect: signal not found in KSelectAction
QObject::connect: signal not found in
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #54 from vialav ---
$ gdb cantor
…
>>> run
─── Output
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #55 from vialav ---
$ gdb --args cantor -b julia
…
>>> run
─── Output
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #56 from vialav ---
$ gdb --args cantor -b python2
─── Output/messages
https://bugs.kde.org/show_bug.cgi?id=408240
Bug ID: 408240
Summary: The Qt buttons no longer work (Qt signals problem)
after the code change from 1 June
Product: cantor
Version: 19.04
Platform: Other
OS: Lin
https://bugs.kde.org/show_bug.cgi?id=408241
Bug ID: 408241
Summary: Python2/3 backends hung on "Calculating…" after the
code change from 1 June
Product: cantor
Version: 19.04
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=397264
vialav changed:
What|Removed |Added
CC||d...@bk.ru
--- Comment #9 from vialav ---
FYI: I&#
https://bugs.kde.org/show_bug.cgi?id=397264
vialav changed:
What|Removed |Added
CC|d...@bk.ru |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=397264
vialav changed:
What|Removed |Added
CC||d...@bk.ru
--- Comment #10 from vialav ---
…I have
https://bugs.kde.org/show_bug.cgi?id=407362
vialav changed:
What|Removed |Added
CC||d...@bk.ru
--- Comment #5 from vialav ---
Confirmed
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #3 from vialav ---
(For being slow and late I'm sorry, starting from Monday I have much less time
for reporting.)
There were no doubts that it it the system-wide Qt installation, so to confirm:
$ pwd
/home/cantor/cantor-19.
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #4 from vialav ---
> If the signals and cmake use proper system qt, that will means, what your qt
> broken from June 1, for example, by update.
That could also mean the difference from Qt on your system and mine. I doubt
you use Qt
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #5 from vialav ---
…then run
git checkout $your_version
and
git log -p $the_file_in_question # down to Qt v5.9.5
Those were my thougts, if it is about a subtle particular change in API.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #8 from vialav ---
Oh, Nikita, that Qt v5.9.5 installation on your system too came as a positive
surprise to me! Which KDE frameworks are you using, if I may ask? I had to,
very-very selectively get rid of the specific Qt 5.10.0 very-very
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #9 from vialav ---
Alternatively, you may temporary 'spice over' the code with multiple debug
breakpoints/messages, which I would be happy to test on my system.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #10 from vialav ---
As a last measure I'll reinstall qtbase5-dev (remove and install again the same
package), so to ensure it is the same.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #13 from vialav ---
_ It is just to report, that I've re-installed qtbase5-dev, and re-compiled
Cantor which still has the reported issue _
If you succeed with KDE 5.58.0 + Qt 5.11.1 and Cantor under those with no
issues, I'll s
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #15 from vialav ---
Have you build KDE 5.58.0 and got the working Cantor? I meant 'if you succeed
with KDE 5.58.0'.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #17 from vialav ---
Ok, thank you. Because Cantor is on Ubuntu's eoan, and it has those KDE's. So,
there could be "underwater stones" ahead of a new Cantor release if this issue
remains latent. Best to you with getting
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #20 from vialav ---
Congrats. So, the issue has been narrowed to my backporting to Qt 5.9.5. You
have confidently demonstrated that Cantor is compatible with the latest KDE.
I would be grateful for some guidance which lines of code in
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #22 from vialav ---
I have built Cantor outside the Debian/Ubuntu packaging, and… it works as
intended. No issues whatsoever, and all the buttons work. Thanksfully to your
hint with the recent KDE frameworks, it turns out it was never the
https://bugs.kde.org/show_bug.cgi?id=408240
vialav changed:
What|Removed |Added
Summary|The Qt buttons no longer|Cantor is not compatible
|work (Qt
https://bugs.kde.org/show_bug.cgi?id=408240
vialav changed:
What|Removed |Added
Summary|Cantor is not compatible|Cantor is not compatible
|with LTO
https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #23 from vialav ---
(just a one-liner: could you check if you have the backends icons in File ->
New under your normal developing environment [Qt 5.9.5], it seems we've lost
them in transition; it would be also convenient to have t
https://bugs.kde.org/show_bug.cgi?id=408335
Bug ID: 408335
Summary: Plots are not visible [benchmark: the Lorenz example]
Product: cantor
Version: 19.04
Platform: Compiled Sources
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=408335
--- Comment #1 from vialav ---
It appears that *only* the Lorenz example is affected,
octave_examples_{2d,3d}_plots.cws, as well as Maxima's examples show their
respective plots.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=408335
--- Comment #4 from vialav ---
Yes, indeed, removing that line with `view` has brought the plot back to my
screen. Interesting to know that the white space to the left hid behind it.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=408335
--- Comment #5 from vialav ---
UPDATE:
1. Remove the line with `view`
2. Press 'Evaluate Worksheet' # should be OK
3. Restart the backend # should be OK
4. Press 'Evaluate Worksheet' again # Segfault:
Thread 1 "cantor
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #10 from vialav ---
FYI: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852780
The bug is still here though.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #11 from vialav ---
Also Bug #375467
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #12 from vialav ---
$ ipython
Python 2.7.15+ (default, Nov 27 2018, 23:36:35)
Type "copyright", "credits" or "license" for more information.
IPython 5.8.0 -- An enhanced Interactive Python.
? -
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #13 from vialav ---
UPDATE: The cause of errors has been identified and half-successfully dealt
with:
https://github.com/ipython/ipython/issues/11485# IPython crashes at launch
(closed, no action)
https://github.com/powerline/powerline
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #15 from vialav ---
If `sage-ipython -i --simple-prompt` is inevitable for initialization of the
backend, then yes.
`sage -python` doesn't have this problem, and the Sage environment is being
loaded properly ($SAGE_ROOT and fr
https://bugs.kde.org/show_bug.cgi?id=408176
--- Comment #18 from vialav ---
(as a matter of Statistics and to have as many methods of initialization as
possible in your arsenal, the following guy is initializing Python under Julia
programmatically, but with its own set of issues):
https
https://bugs.kde.org/show_bug.cgi?id=409288
Bug ID: 409288
Summary: Mayavi's plots don't show up/work in Cantor
Product: cantor
Version: 19.04
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=409288
--- Comment #2 from vialav ---
> mayavi works only with `qt5`, and crash, if I try to use `qt4` or `wx`
Qt4: yes, the above happens because your and my tools **are Qt5-compiled** what
clashes with Qt4 implementation (either of them, but not both).
https://bugs.kde.org/show_bug.cgi?id=409357
Bug ID: 409357
Summary: non-bug QUESTION, what is: cantor-sygnms
Product: cantor
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Sever
https://bugs.kde.org/show_bug.cgi?id=409288
--- Comment #3 from vialav ---
(BTW, you need vtk-$version.egg-info directory (create it manualy if it doesn't
exist in your distribution) for trying M. with any VTK 6/7/8, it seems to be a
bug, as it couldn't find it. Mayavi no longer nee
https://bugs.kde.org/show_bug.cgi?id=409357
vialav changed:
What|Removed |Added
Summary|non-bug QUESTION, what is: |non-bug QUESTION, what is:
|cantor
https://bugs.kde.org/show_bug.cgi?id=409288
--- Comment #4 from vialav ---
```python
from traits.etsconfig.api import ETSConfig
ETSConfig.toolkit = 'wx'
```
#https://stackoverflow.com/questions/52930781/qt-api-environment-variable
```python
import os
os.environ["QT_API&quo
https://bugs.kde.org/show_bug.cgi?id=409288
--- Comment #6 from vialav ---
yeah, I vaguely remember smth like that
On a slightly unrelated note:
In addition to modifying pyface/qt/__init__.py it make sense also modify
pyface/base_toolkit.py, adding `'qt': -3,` in TOOLKIT_PRIORITIES
t
https://bugs.kde.org/show_bug.cgi?id=409288
--- Comment #7 from vialav ---
- for `wx` to work in Python 3 you have to install
https://packages.ubuntu.com/src:wxpython4.0 python3-package (not tested with
Mayavi 4.6.2, tested with 4.7.0)
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=409288
--- Comment #8 from vialav ---
`wx` works under IDLE (not under Cantor though)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409288
--- Comment #9 from vialav ---
with my pre-last edit suggestion I've almost got the `wx` backend working in
cantor, running it additionally and "over-ensurely" through `ETS_TOOLKIT=wx
cantor`
It has produced the non-interactive pictur
https://bugs.kde.org/show_bug.cgi?id=409288
vialav changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=408175
--- Comment #3 from vialav ---
bug persist with the latest compiled version; see also Bug 409486
─── Output/messages
https://bugs.kde.org/show_bug.cgi?id=409486
Bug ID: 409486
Summary: 'Unloader' crashes Python 3.6 with "no member named
ma_keys"
Product: Falkon
Version: 3.1.0
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=409495
Bug ID: 409495
Summary: [Run Actions]: crashes Falkon with a weird reference
to Python2
Product: Falkon
Version: 3.1.0
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=409520
Bug ID: 409520
Summary: Too much journalctl-noise under Python 3 (none under
Python 2)
Product: cantor
Version: 19.04
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=409520
--- Comment #2 from vialav ---
ok, I'll keep an eye on my logs for now...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409523
Bug ID: 409523
Summary: Python2 backend crashes if the first cell first time
is executed by a mouse click on a 'green trinagle'
Product: cantor
Version: 19.04
Platform: Compiled S
https://bugs.kde.org/show_bug.cgi?id=409523
vialav changed:
What|Removed |Added
Summary|Python2 backend crashes if |Python2 backend crashes if
|the
https://bugs.kde.org/show_bug.cgi?id=409520
vialav changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
1 - 100 of 130 matches
Mail list logo
