[Falkon] [Bug 411197] Unable to compile, error: ‘const class QString’ has no member named ‘chopped’

2019-09-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=411197 vialav changed: What|Removed |Added CC||d...@bk.ru --- Comment #1 from vialav --- Hi

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-08-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 vialav changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-08-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 --- Comment #11 from vialav --- > Dolphin no longer shows inotify_add_watch("~/.dropbox/aggregation.dbx") > failed: "No such file or directory" in the console output Surely, however, isn't it the same file, in (possi

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-08-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 --- Comment #9 from vialav --- > I wonder if it's the Dropbox integration plugin that's doing it. Does the > message go away if you disable the Dropbox service (if you have it installed > and enabled)? I have no doubts about it. D

[frameworks-kio] [Bug 410354] kf5.kio.core: "Could not enter folder tags:/."

2019-08-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410354 vialav changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-08-06 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 vialav changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO

[frameworks-kio] [Bug 410354] kf5.kio.core: "Could not enter folder tags:/."

2019-08-06 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410354 vialav changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-08-06 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 --- Comment #5 from vialav --- $ ll --tree $HOME/.dropbox # (it's a custom 'll') ├──  command_socket ├──  dropbox.pid └──  events/ ├──  host.db ├──  iface_socket ├──  info.json └──

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-08-06 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 --- Comment #4 from vialav --- $ find $HOME/.dropbox -name aggregation.dbx ~/.dropbox/instance4/aggregation.dbx -- You are receiving this mail because: You are watching all bug changes.

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-08-06 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 vialav changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO

[Falkon] [Bug 409486] 'Unloader' crashes Python 3.6 with "no member named ma_keys"

2019-08-01 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409486 vialav changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[Falkon] [Bug 410482] [RunActions] Failed to parse dictionary.desktop: 'PyFalkon.DesktopFile' called with wrong argument type str (not supported)

2019-08-01 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410482 --- Comment #1 from vialav --- ─── Output/messages

[Falkon] [Bug 410482] New: [RunActions] Failed to parse dictionary.desktop: 'PyFalkon.DesktopFile' called with wrong argument type str (not supported)

2019-08-01 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410482 Bug ID: 410482 Summary: [RunActions] Failed to parse dictionary.desktop: 'PyFalkon.DesktopFile' called with wrong argument type str (not supported) Product: Falkon Versi

[cantor] [Bug 409520] Too much journalctl-noise under Python 3 (none under Python 2)

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409520 vialav changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|INTENTIONAL

[Falkon] [Bug 409486] 'Unloader' crashes Python 3.6 with "no member named ma_keys"

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409486 --- Comment #2 from vialav --- Sorry for a delay, and next issues, if any, will go to GitHub instead. What I wanted to add here, is that the following python extensions along Unloader are enabled in my Falcon configuration and they work without

[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 vialav changed: What|Removed |Added Summary|inotify_add_watch("/home/kh |inotify_add_watch("~/.dropb

[dolphin] [Bug 410355] inotify_add_watch("/home/khalak/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 --- Comment #1 from vialav --- $ env QT_MESSAGE_PATTERN="%{appname} - %{message}" kdeinit5 $ env QT_MESSAGE_PATTERN="%{appname} - %{message}" dolphin kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/tags.so

[frameworks-kio] [Bug 410354] kf5.kio.core: "Could not enter folder tags:/."

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410354 --- Comment #1 from vialav --- $ env QT_MESSAGE_PATTERN="%{appname} - %{message}" kdeinit5 $ env QT_MESSAGE_PATTERN="%{appname} - %{message}" dolphin kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/tags.so

[dolphin] [Bug 410355] New: inotify_add_watch("/home/khalak/.dropbox/aggregation.dbx") failed: "No such file or directory"

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410355 Bug ID: 410355 Summary: inotify_add_watch("/home/khalak/.dropbox/aggregation.d bx") failed: "No such file or directory" Product: dolphin Version: 19.07.80 Platform: Compiled Sourc

[frameworks-kio] [Bug 410354] New: kf5.kio.core: "Could not enter folder tags:/."

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410354 Bug ID: 410354 Summary: kf5.kio.core: "Could not enter folder tags:/." Product: frameworks-kio Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED

[frameworks-kcoreaddons] [Bug 410340] (the report has been closed as invalid)

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410340 vialav changed: What|Removed |Added Assignee|fa...@kde.org |mp...@kde.org Product|frameworks-kio

[frameworks-kio] [Bug 410340] New: D22638: Port internal usage of KIO::suggestName has NO kfileutils.h

2019-07-29 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=410340 Bug ID: 410340 Summary: D22638: Port internal usage of KIO::suggestName has NO kfileutils.h Product: frameworks-kio Version: git master Platform: Compiled Sources

[cantor] [Bug 408240] Cantor is not compatible with LTO after 1 June [was: the Qt buttons no longer work (Qt signals problem)]

2019-07-14 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=408240 --- Comment #26 from vialav --- https://bugreports.qt.io/browse/QTBUG-43556 -- You are receiving this mail because: You are watching all bug changes.

[cantor] [Bug 409520] Too much journalctl-noise under Python 3 (none under Python 2)

2019-07-10 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409520 vialav changed: What|Removed |Added Resolution|NOT A BUG |INTENTIONAL --- Comment #6 from vialav --- Ok, I&#x

[cantor] [Bug 409580] Cantor crashes upon python2 backend interruption after showing the Mayavi demo

2019-07-08 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409580 vialav changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[cantor] [Bug 409520] Too much journalctl-noise under Python 3 (none under Python 2)

2019-07-08 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409520 vialav changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution

[cantor] [Bug 409580] Cantor crashes upon python2 backend interruption after showing the Mayavi demo

2019-07-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409580 --- Comment #1 from vialav --- ah, forgot the backtrace: #dmesg: [Sun Jul 7 01:08:56 2019] cantor_python2s[23918]: segfault at 8 ip 778e5440 sp 7fffc708 error 4 in libpython2.7.so.1.0[777b4000+2e2000] #journalctl: Jul 07 15:26:46

[cantor] [Bug 409580] Cantor crashes upon python2 backend interruption after showing the Mayavi demo

2019-07-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409580 vialav changed: What|Removed |Added Summary|Cantor crashes upon python2 |Cantor crashes upon python2

[cantor] [Bug 409580] New: Cantor crashes upon python2 backend interruption after showin the Mayavi demo

2019-07-07 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409580 Bug ID: 409580 Summary: Cantor crashes upon python2 backend interruption after showin the Mayavi demo Product: cantor Version: 19.04 Platform: Compiled Sources OS:

[cantor] [Bug 409520] Too much journalctl-noise under Python 3 (none under Python 2)

2019-07-05 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409520 vialav changed: What|Removed |Added Component|python3-backend |general --- Comment #4 from vialav --- On the other

[cantor] [Bug 409520] Too much journalctl-noise under Python 3 (none under Python 2)

2019-07-05 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409520 vialav changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED

[cantor] [Bug 409523] Python2 backend crashes if the first cell first time is executed by a mouse click on a 'green triangle'

2019-07-05 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409523 vialav changed: What|Removed |Added Summary|Python2 backend crashes if |Python2 backend crashes if |the

[cantor] [Bug 409523] New: Python2 backend crashes if the first cell first time is executed by a mouse click on a 'green trinagle'

2019-07-05 Thread vialav
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

[cantor] [Bug 409520] Too much journalctl-noise under Python 3 (none under Python 2)

2019-07-05 Thread vialav
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.

[cantor] [Bug 409520] New: Too much journalctl-noise under Python 3 (none under Python 2)

2019-07-05 Thread vialav
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

[Falkon] [Bug 409495] New: [Run Actions]: crashes Falkon with a weird reference to Python2

2019-07-04 Thread vialav
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

[Falkon] [Bug 409486] New: 'Unloader' crashes Python 3.6 with "no member named ma_keys"

2019-07-04 Thread vialav
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

[Falkon] [Bug 408175] Tab Manager: unload crashes the master-branch Falkon

2019-07-04 Thread vialav
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

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=409288 vialav changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
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

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
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.

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
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

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
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

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
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

[cantor] [Bug 409357] non-bug QUESTION, what is: cantor-sygnm

2019-07-01 Thread vialav
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

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
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

[cantor] [Bug 409357] New: non-bug QUESTION, what is: cantor-sygnms

2019-07-01 Thread vialav
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

[cantor] [Bug 409288] Mayavi's plots don't show up/work in Cantor

2019-07-01 Thread vialav
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).

[cantor] [Bug 409288] New: Mayavi's plots don't show up/work in Cantor

2019-06-28 Thread vialav
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

[cantor] [Bug 408176] Alternative initialisation? Sagemath (= 8.6-6) on python 2 (unicode issue?) crashes on: exec sage-ipython -i --simple-prompt

2019-06-06 Thread vialav
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

[cantor] [Bug 408176] Alternative initialisation? Sagemath (= 8.6-6) on python 2 (unicode issue?) crashes on: exec sage-ipython -i --simple-prompt

2019-06-06 Thread vialav
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

[cantor] [Bug 408176] Alternative initialisation? Sagemath (= 8.6-6) on python 2 (unicode issue?) crashes on: exec sage-ipython -i --simple-prompt

2019-06-06 Thread vialav
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

[cantor] [Bug 408176] Alternative initialisation? Sagemath (= 8.6-6) on python 2 (unicode issue?) crashes on: exec sage-ipython -i --simple-prompt

2019-06-05 Thread vialav
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. ? -

[cantor] [Bug 408176] Alternative initialisation? Sagemath (= 8.6-6) on python 2 (unicode issue?) crashes on: exec sage-ipython -i --simple-prompt

2019-06-05 Thread vialav
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.

[cantor] [Bug 408176] Alternative initialisation? Sagemath (= 8.6-6) on python 2 (unicode issue?) crashes on: exec sage-ipython -i --simple-prompt

2019-06-05 Thread vialav
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.

[cantor] [Bug 408335] Plots are not visible [benchmark: the Lorenz example]

2019-06-05 Thread vialav
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

[cantor] [Bug 408335] Plots are not visible [benchmark: the Lorenz example]

2019-06-05 Thread vialav
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

[cantor] [Bug 408335] Plots are not visible [benchmark: the Lorenz example]

2019-06-05 Thread vialav
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

[cantor] [Bug 408335] New: Plots are not visible [benchmark: the Lorenz example]

2019-06-05 Thread vialav
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

[cantor] [Bug 408240] Cantor is not compatible with LTO after 1 June [was: the Qt buttons no longer work (Qt signals problem)]

2019-06-05 Thread vialav
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

[cantor] [Bug 408240] Cantor is not compatible with LTO after 1 June [was: the Qt buttons no longer work (Qt signals problem)]

2019-06-05 Thread vialav
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

[cantor] [Bug 408240] Cantor is not compatible with LTO [was: the Qt buttons no longer work (Qt signals problem)]

2019-06-05 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-05 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-04 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-04 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-04 Thread vialav
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.

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-04 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-04 Thread vialav
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.

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-04 Thread vialav
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.

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-04 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-03 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-03 Thread vialav
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

[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-03 Thread vialav
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.

[cantor] [Bug 407362] python3 backend broke down when calling matplotlib.pyplot.plot()

2019-06-03 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=407362 vialav changed: What|Removed |Added CC||d...@bk.ru --- Comment #5 from vialav --- Confirmed

[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot

2019-06-03 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=397264 vialav changed: What|Removed |Added CC||d...@bk.ru --- Comment #10 from vialav --- …I have

[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot

2019-06-03 Thread vialav
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

[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot

2019-06-03 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=397264 vialav changed: What|Removed |Added CC||d...@bk.ru --- Comment #9 from vialav --- FYI: I&#

[cantor] [Bug 408241] New: Python2/3 backends hung on "Calculating…" after the code change from 1 June

2019-06-03 Thread vialav
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

[cantor] [Bug 408240] New: The Qt buttons no longer work (Qt signals problem) after the code change from 1 June

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #56 from vialav --- $ gdb --args cantor -b python2 ─── Output/messages

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #55 from vialav --- $ gdb --args cantor -b julia … >>> run ─── Output

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #54 from vialav --- $ gdb cantor … >>> run ─── Output

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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.

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-03 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
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.

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
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

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #32 from vialav --- $ julia _ _ _ _(_)_ | Documentation: https://docs.julialang.org (_) | (_) (_)| _ _ _| |_ __ _ | Type "?" for help, "]

[cantor] [Bug 408179] Alternative initialisation? Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend hungs on Calculating…

2019-06-02 Thread vialav
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

  1   2   >