[kwin] [Bug 419193] New: Resizing a maximized window from borders/grip does not (seem to) update maximization status
https://bugs.kde.org/show_bug.cgi?id=419193 Bug ID: 419193 Summary: Resizing a maximized window from borders/grip does not (seem to) update maximization status Product: kwin Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- SUMMARY I use a tiling script and have the issue that resizing maximized windows from borders or grip (hence unmaximizing the window) breaks tiling because kwin does not seem to update the maximization status (it seems to retain the maximized status even when the window is clearly not maximized anymore) Original report of the issue to the tiling script: https://github.com/Jazqa/kwin-quarter-tiling/issues/81#issuecomment-603441988 STEPS TO REPRODUCE 1. Enable a tiling script 2. Maximize a window 3. Resize the window from borders or grip OBSERVED RESULT The (non-maximized) window is not tiled EXPECTED RESULT The (non-maximized) window should be tiled Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-42-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418938] New: Gain focus when clicking the maximization button
https://bugs.kde.org/show_bug.cgi?id=418938 Bug ID: 418938 Summary: Gain focus when clicking the maximization button Product: kwin Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- SUMMARY I am using click to focus in Kwin and I think clicking the maximization button should also automatically gain focus (assumed the window didn't have it). Perhaps it's just me but I find default Kwin's behavior quite counterintuitive maximizing without gaining focus. STEPS TO REPRODUCE 1. Open two windows 2. Set focus on one 3. Click the maximization button of the other OBSERVED RESULT The Maximized window does not automatically gain focus and appears below the window under focus EXPECTED RESULT The maximized window would also gain focus (to be on top of the other window). Also, under Kwin's logic to focus on click, shouldn't the click on the maximization button also count as a focus on click? For obvious reasons, this does not apply to minimization and close buttons, but I think it would make sense for all other clicks in the window (including other buttons), and especially for maximization. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417434] Latte-dock repeatedly crashes at startup after updating Plasma to 5.18
https://bugs.kde.org/show_bug.cgi?id=417434 --- Comment #1 from avlas --- This seems to be related to the Buttons applet using Sierra Breeze Enhanced decorations. It would be great if Latte would be resilient to applet crashes but I guess this is not easy. I fixed it the Latte crash by recompiling Sierra Breeze Enhanced, however Buttons are not yet displayed. When I tried recompiling Buttons I get the following error: applet-window-buttons/libappletdecoration/previewbridge.cpp:75:83: error: invalid new-expression of abstract class type ‘Decoration::Applet::PreviewClient’ auto ptr = std::unique_ptr(new PreviewClient(client, decoration)); libappletdecoration/CMakeFiles/appletdecorationplugin.dir/build.make:179: recipe for target 'libappletdecoration/CMakeFiles/appletdecorationplugin.dir/previewbridge.cpp.o' failed make[2]: *** [libappletdecoration/CMakeFiles/appletdecorationplugin.dir/previewbridge.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs CMakeFiles/Makefile2:453: recipe for target 'libappletdecoration/CMakeFiles/appletdecorationplugin.dir/all' failed make[1]: *** [libappletdecoration/CMakeFiles/appletdecorationplugin.dir/all] Error 2 Makefile:140: recipe for target 'all' failed make: *** [all] Error 2 This is however and error in Buttons, so perhaps I should report it there... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417434] New: Latte-dock repeatedly crashes at startup after updating Plasma to 5.18
https://bugs.kde.org/show_bug.cgi?id=417434 Bug ID: 417434 Summary: Latte-dock repeatedly crashes at startup after updating Plasma to 5.18 Product: lattedock Version: 0.9.8.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jsar...@gmail.com Target Milestone: --- Application: latte-dock (0.9.8.1) Qt Version: 5.13.2 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-28-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: Latte-dock is not able to launch. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e15819800 (LWP 2798))] Thread 21 (Thread 0x7f1d3e5ed700 (LWP 2892)): #0 0x7f1e0ea08bf9 in __GI___poll (fds=0x55f0e66dbf00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1e089045c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1e089046dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1e0f6f9acb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1e0f699f9a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1e0f4b53aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1e0f4b6b52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1e0b9dd6db in start_thread (arg=0x7f1d3e5ed700) at pthread_create.c:463 #8 0x7f1e0ea1588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f1d3edee700 (LWP 2891)): #0 0x7f1e0ea08bf9 in __GI___poll (fds=0x55f0e46587f0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1e089045c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1e089046dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1e0f6f9acb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1e0f699f9a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1e0f4b53aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1e0f4b6b52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1e0b9dd6db in start_thread (arg=0x7f1d3edee700) at pthread_create.c:463 #8 0x7f1e0ea1588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f1d3700 (LWP 2874)): #0 0x7f1e0ea08bf9 in __GI___poll (fds=0x7f1d34004710, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1e089045c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1e089046dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1e0f6f9acb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1e0f699f9a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1e0f4b53aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1e0f4b6b52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1e0b9dd6db in start_thread (arg=0x7f1d3700) at pthread_create.c:463 #8 0x7f1e0ea1588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f1d44ffe700 (LWP 2873)): #0 0x7f1e0b9e39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f1d861ca058) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1e0b9e39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f1d861ca008, cond=0x7f1d861ca030) at pthread_cond_wait.c:502 #2 0x7f1e0b9e39f3 in __pthread_cond_wait (cond=0x7f1d861ca030, mutex=0x7f1d861ca008) at pthread_cond_wait.c:655 #3 0x7f1e0f13a86c in std::condition_variable::wait(std::unique_lock&) () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x7f1dd8136f37 in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #5 0x7f1dd8896c1c in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #6 0x7f1dd88986bc in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #7 0x7f1dd81397f8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #8 0x7f1dd815dd0a in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #9 0x7f1e0b9dd6db in start_thread (arg=0x7f1d44ffe700) at pthread_create.c:463 #10 0x7f1e0ea1588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f1d3cffe700 (LWP 2872)): #0 0x7f1e0ea08bf9 in __GI___poll (fds=0x7f1d38003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1
[frameworks-kio] [Bug 415484] Filter bar does not apply to subfolders
https://bugs.kde.org/show_bug.cgi?id=415484 --- Comment #2 from avlas --- (In reply to Kai Uwe Broulik from comment #1) > That's why it was originally called "file type" because it is *not* a plain > view filter like in Dolphin. Fair enough, but the issue is not really about the name; it is about the functionality. In my original report I mentioned a use-case in which this functionality is particularly relevant. If this was implemented in Dolphin I assume some KDE devs thought that this functionality was important, and this issue is about having that also in Open/Save dialogs. I know, however, that KDE devs are very busy and that you have many things in your plate, so this might not be a priority. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 415484] New: Filter bar does not apply to subfolders
https://bugs.kde.org/show_bug.cgi?id=415484 Bug ID: 415484 Summary: Filter bar does not apply to subfolders Product: frameworks-kio Version: 5.65.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: jsar...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Filtering within a folder that has many subfolders in open/save dialogs is not very useful at the moment because the filter only applies to files. It should be applied also to subfolders in addition to files, just as how it works in dolphin. STEPS TO REPRODUCE 1. Open a open/save dialog 2. Go to a folder that has tens of subfolders 3. Filter the result OBSERVED RESULT The filter applies to files only EXPECTED RESULT The filter should apply to all files and subfolders SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 415030] Konqueror is banned from this website (bugs.kde.org)
https://bugs.kde.org/show_bug.cgi?id=415030 avlas changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 415030] Konqueror is banned from this website (bugs.kde.org)
https://bugs.kde.org/show_bug.cgi?id=415030 --- Comment #1 from avlas --- It seems it was a cookie problem that I fixed removing the cookies from this site. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 415030] New: Konqueror is banned from this website (bugs.kde.org)
https://bugs.kde.org/show_bug.cgi?id=415030 Bug ID: 415030 Summary: Konqueror is banned from this website (bugs.kde.org) Product: konqueror Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- When I try to open bugs.kde.org in konqueror I see the following error: Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. Apache/2.4.29 (Ubuntu) Server at komaci.kde.org Port 443 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 379346] webengine part can not activate fullscreen video on youtube
https://bugs.kde.org/show_bug.cgi?id=379346 --- Comment #1 from avlas --- This works with Falkon and as far as I know it uses same webengine renderer, so there may be some tweak or something that Konqueror is missing. It would be great if that tweak is ported from Falkon to Konqueror. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 414208] New: Cannot restore specific session
https://bugs.kde.org/show_bug.cgi?id=414208 Bug ID: 414208 Summary: Cannot restore specific session Product: konqueror Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: session restore Assignee: edu...@gmail.com Reporter: jsar...@gmail.com Target Milestone: --- SUMMARY I want to open a session from terminal with `--session ` as directed in man konqueror STEPS TO REPRODUCE 1. Save a Konqueror session, e.g. "current" 2. Close Koqueror 3. In Konsole, execute "Konqueror --session current" OBSERVED RESULT The following message is displayed in Konsole: `org.kde.konqueror: Unknown class "" in session saved data!` And konqueror does not open EXPECTED RESULT Konqueror should open and load the "current" session ADDITIONAL INFORMATION I realized that if I manually copy the session content from its location to the autosave folder, then opening konqueror loads the session. This I think means two things: - There is nothing wrong in the saved session and what fails is in the code restoring saved sessions, but not in the code that restores the autosaved session that works fine - Adding the so claimed and popular feature request of restoring last open tabs in konqueror seems quite straightforward simply by implementing the two following steps: 1. Avoid removing the content of the autosave folder on exit (if the option of reopening tabs is enabled) 2. Exiting Konqueror (and its shortcut Ctrl+Q) should close the entire application (all konqueror windows) instead of the active window, which should rather be closed with Ctrl+Shift+W as in Firefox/Chromium. This step is important because otherwise the session is changing while closing the different Konqueror windows, and then a user could restore no more than a single window. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 413992] New: Inconsitent zoom to DPI setting
https://bugs.kde.org/show_bug.cgi?id=413992 Bug ID: 413992 Summary: Inconsitent zoom to DPI setting Product: konqueror Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- SUMMARY I need to move from webengine to webkit and back again to webengine to have a page scaled properly to the setting STEPS TO REPRODUCE 1. Enable zoom to DPI 2. Close Konqueror 3. Open a website OBSERVED RESULT Zoom is not applied EXPECTED RESULT Zoom to DPI should be applied SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.0.0-34-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #4 from avlas --- (In reply to keitalbame from comment #3) > You are right. > When I read "directory tree is not created", remembered about the bug I > mentioned because when I first saw the issue, the folders where not being > created in the filesystem. I found out later that they where created on a > different (incorrect) path. I see. It might still be the same underlying issue, but it's not obvious. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #2 from avlas --- It doesn't seem related, as this one doesn't have anything to do with local mail, but not sure. At some point I found an alternative way to add an email account in Kmail that did work. This was some months ago, so I don't totally recall. But for the case other users suffer this, they could explore alternative ways to create the account, as it seems based on my experience that one is troublesome and the other is not. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397463] okular session management
https://bugs.kde.org/show_bug.cgi?id=397463 --- Comment #21 from avlas --- (In reply to Nate Graham from comment #20) > Ah I see what you mean. > > I guess what I implemented is a precursor to it then. :) and very much appreciated! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397463] okular session management
https://bugs.kde.org/show_bug.cgi?id=397463 --- Comment #19 from avlas --- > Please don't get me wrong, I am very happy about your fix. But IMO, the > session manager would really make a difference. In other words, your fix seems to me like "solving a bug" because session restoration should in principle be expected, whereas accounting for session management is not really fixing any bug (as it is not necessarily expected) but would be an extremely cool feature and a remarkable difference with respect to all other PDF viewers, with great benefit to all users that heavily go through PDF documents. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397463] okular session management
https://bugs.kde.org/show_bug.cgi?id=397463 --- Comment #18 from avlas --- Thank you Nathan for the great work! This is very much wanted and needed. However, this seems to be a fix "only" for session restoration, but not for session management (as in Kate), which is what the issue ultimately is about, and all Okular users here are so excited about. Am I wrong? Please don't get me wrong, I am very happy about your fix. But IMO, the session manager would really make a difference. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] AllScreens tracking is disabled after startup phase
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #11 from avlas --- (In reply to Michail Vourlakos from comment #10) > ok... I found it... > > Windows Tracking in v0.9 has been enhanced in a major value... All windows > tracking even for the mentioned applets is taking place in Latte. That will > give you major benefits in multi-screen environments... The issue was that > you had the left panel that was NOT requesting windows tracking and the top > one that it does. Latte faulty because of the left panel was NOT requesting > tracking during startup it was disabling the ALLSCREENS tracking for your > layout. > > > Solution: > A. you wait for to 0.9.3 > B. or a workaround could be the following, activate for your left latte > panel the option "Behavior, Drag and maximize/restore active window" Awesome, thanks! That workaround indeed fixed the issue :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #7 from avlas --- (In reply to avlas from comment #6) > (In reply to Michail Vourlakos from comment #4) > > send me your layout please to check it out > > was on it :) Btw, I think I said in reddit when I first mention this, but this was long time ago and I forgot to mention here. The faulty behavior emerged when I moved from latte v0.8 to latte v0.9. So I guess that for whatever reason, latte v0.9 didn't "like" my < v0.9 layout. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #6 from avlas --- (In reply to Michail Vourlakos from comment #4) > send me your layout please to check it out was on it :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #5 from avlas --- Created attachment 122523 --> https://bugs.kde.org/attachment.cgi?id=122523=edit my layout In the file, I modified my username to "username" -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #3 from avlas --- Created attachment 122522 --> https://bugs.kde.org/attachment.cgi?id=122522=edit debug info Please note that I have two latte panels -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] New: faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout
https://bugs.kde.org/show_bug.cgi?id=411670 Bug ID: 411670 Summary: faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout Product: lattedock Version: 0.9.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jsar...@gmail.com Target Milestone: --- I suffer a very weird issue. Your applets for window title, menu and buttons don't work as expected at first launch (or restart) of latte (details of this appear below), and I need to change in latte to another layout (e.g., OSX, Plasma, Unity or Default) and back again to my specific one, for these applets to work properly as expected and configured. By not working as expected I mean that the window menu applet does not appear and same happens for buttons, whereas the title applet only shows the activity name and nothing else. Other applets don't seem to be affected. Weirdly enough, all the applets are shown as expected when I enter into the settings mode, but the problem persists once out of settings. [Sorry for the delay in reporting, I've been out of town for a while. I had some hopes that version 0.9.2 might fix the issue, but didn't happen] SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-27-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] New: regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 Bug ID: 411647 Summary: regression: adding a new imap account prompts no error but no directory tree is created Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- I tried to add a new imap account. The process triggers no errors and everything seems fine. However, the directory tree (inbox, sent, etc) is not created. Tried several times with same result every time. This is an office 365 account, analogous to another I configured few months before with no issue, so I suppose this is some sort of regression. Also, adding the account to Trojita works just fine, so it doesn't seem to be something internal to the servers. Could you please try to add a new imap account to see if you can reproduce the issue in your system? Not sure if the issue in kmail is specific for office365 imap accounts or general. Any help is more than appreciated! SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-27-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 393118] m4a audio files are not considered
https://bugs.kde.org/show_bug.cgi?id=393118 avlas changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411147] IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147 --- Comment #3 from avlas --- (In reply to Laurent Montel from comment #2) > see > https://www.dvratil.cz/2019/08/kontact-google-integration-issue/ Thank you Laurent. I got bitten by this issue, even though I had my account configured successfully, (I think) after I manually cancelled Kmail synchronization due to a extremely slow internet connection. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411147] IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 --- Comment #6 from avlas --- This happens to me (in KDE neon) most of the times after "Accepting a Google Calendar Invitation Request" in my gmail account. The email that is sent (not always but very frequently, I would say 80% of the times or more) gets stuck and then no more emails can be sent from any account (gmail and others). Saying because if you could reproduce this behavior, it may help to debug and fix the issue. [Note: I have the feeling that this happens more frequently if the akonadi process has been running for a while] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409551] Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 --- Comment #3 from avlas --- (In reply to Michael Weghorn from comment #2) > As far as I understand, this would require the Qt file dialog to be > non-modal here. > Don't know whether that's easily possible, but even if it was, I see this > issue: Okular can not only show but also edit documents (e.g. insert > annotations into PDF documents). If the user could interact with the > document and edit it while the save dialog is open, what version of the > document would be saved? > > I'm currently not aware of any program/editor that does have a non-modal > save dialog (at least kate, gedit, libreoffice also have modal ones). Not sure I understand. I don't see much of a problem, in other words, where the conflict is. Opening a dialog makes no action, right? The action occurs when the button (e.g. save) is clicked and this cannot happen at once with another action, can it? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409551] New: Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 Bug ID: 409551 Summary: Usability bug: make "Save/Save As" dialogs use their own process Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Let me give a bit of context on the use case. For research I frequently open PDF articles from the browser, take a look to them and decide (or not) saving them for further reading and/or later consultation and reference. Near 100% of the times that decision happens when I am not at page 1, so details of authors and title are not accessible (information I need to organize the bunch of PDFs I have). Therefore I need to close the Save/Save As dialog opened by intuition, go back to page 1, and proceed to save (again). If this would happen once, I would not care, but when this happens tens of times every day, it feels a bit unpleasant and breaks the flow. I am not sure about the technicalities, but I think this could be solved if the "Save/Save As" dialog would be in its own process, so even if open, I would still be able to scroll up the main window that appears behind. This is how it works in PDFs opened in the embedded viewer in Chromium for instance, and that is the feature request here. This may be a bug against kio instead of okular, not sure. Perhaps other use cases (other applications such as Kate, and other dialogs such as Open) might also benefit from this feature as well if extended to them. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409240] warning messages stop execution
https://bugs.kde.org/show_bug.cgi?id=409240 --- Comment #7 from avlas --- (In reply to Nikita Sirgienko from comment #6) > Git commit 4bc20243ad683c0f828e1a605adf75d4ddf331d5 by Nikita Sirgienko. > Committed on 05/07/2019 at 22:03. > Pushed by sirgienko into branch 'master'. > > [Python] Show Python warnings not as errors, but as text results > FIXED-IN: 19.08 > > M +6-0src/backends/python/pythonexpression.cpp > M +1-0src/backends/python/pythonexpression.h > M +12 -1src/backends/python/pythonserver.cpp > M +3-1src/backends/python/pythonserver.h > M +2-0src/backends/python/pythonservermain.cpp > M +12 -3src/backends/python/pythonsession.cpp > M +9-0src/backends/python2/testpython2.cpp > M +2-0src/backends/python2/testpython2.h > M +9-0src/backends/python3/testpython3.cpp > M +2-0src/backends/python3/testpython3.h > > https://commits.kde.org/cantor/4bc20243ad683c0f828e1a605adf75d4ddf331d5 Perfect! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409240] warning messages stop execution
https://bugs.kde.org/show_bug.cgi?id=409240 --- Comment #5 from avlas --- (In reply to Nikita Sirgienko from comment #4) > I can't say, that I use python often, but according your words the problem > more important, that I have thought befor, so I give it more priority. Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409240] warning messages stop execution
https://bugs.kde.org/show_bug.cgi?id=409240 --- Comment #3 from avlas --- I was wondering if there is any progress on this issue. Asking because there is a use case that I have identified that deviates from regular python, IPython, etc. It's about a code that removes columns from a panda dataframe: - In regular python, a warning is displayed (only the first time) and columns are removed. Invoking the same instruction again triggers an error because these columns are present no more. - In Cantor, the warning is treated as an error, so the columns are not removed, and the user needs to run the instruction twice to get it done. After that, invoking the instruction again fails as one would expect. In this context, I think a Python user that is not aware of the issue will not understand what is really going on under the hood. More generally, I would encourage to treat all warning as messages to be displayed in Cantor. I think this would also be more consistent with Jupyter Notebooks (btw, I look forward to trying the import/export functionality between notebooks and cantor from the GSoC!). -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409533] Cantor crashes every time I execute a Python3 instruction from a saved CWS file
https://bugs.kde.org/show_bug.cgi?id=409533 --- Comment #9 from avlas --- (In reply to Nikita Sirgienko from comment #8) > Git commit b441bebce8ad6b9ef33f0a49f2c2599bc73962d1 by Nikita Sirgienko. > Committed on 05/07/2019 at 16:03. > Pushed by sirgienko into branch 'master'. > > [Python] Urgent server side fix > FIXED-IN: 19.08 > > M +1-1src/backends/python/pythonservermain.cpp > > https://commits.kde.org/cantor/b441bebce8ad6b9ef33f0a49f2c2599bc73962d1 Wow, that was fast, thank you! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409533] Cantor crashes every time I execute a Python3 instruction from a saved CWS file
https://bugs.kde.org/show_bug.cgi?id=409533 avlas changed: What|Removed |Added Summary|Cantor crashes every time I |Cantor crashes every time I |execute a Python3 |execute a Python3 |instruction |instruction from a saved ||CWS file -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409533] Cantor crashes every time I execute a Python3 instruction
https://bugs.kde.org/show_bug.cgi?id=409533 --- Comment #6 from avlas --- I think it's an incompatibility issue as crash does not happen unless I load a previously saved cws file -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409533] Cantor crashes every time I execute a Python3 instruction
https://bugs.kde.org/show_bug.cgi?id=409533
--- Comment #5 from avlas ---
(In reply to Nikita Sirgienko from comment #4)
> Add "-DCMAKE_BUILD_TYPe=debug"
Done:
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends"
Creating MaximaBackend
Creating NullBackend
Creating PythonBackend
Creating PythonBackend
Creating SageBackend
Creating ScilabBackend
dir: "/usr/bin/cantor/backends"
Backend "Python 3" offers extensions: ("LinearAlgebraExtension",
"PackagingExtension", "PlotExtension", "ScriptExtension",
"VariableManagementExtension")
PythonSession(0x5599333f1240)
Cantor::VariableManagementExtension(0x5599334314c0, name =
"VariableManagementExtension")
PythonHighlighter constructor
PythonKeywords constructor
new worksheetaccess interface
loading assistants...
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/assistants"
plugin "GràficAvançat" is not supported by "Python 3"
plugin "Crea una matriu" is supported by "Python 3" , requires extensions
("LinearAlgebraExtension")
plugin "Deriva" is not supported by "Python 3"
plugin "Valors propis (autovalors)" is not supported by "Python 3"
plugin "Vectors propis (autovectors)" is not supported by "Python 3"
plugin "Importació de paquet" is supported by "Python 3" , requires
extensions ("PackagingExtension")
plugin "Integra" is not supported by "Python 3"
plugin "Inverteix una matriu" is not supported by "Python 3"
plugin "Plot2d" is supported by "Python 3" , requires extensions
("PlotExtension")
plugin "Plot3d" is supported by "Python 3" , requires extensions
("PlotExtension")
plugin "Gràfic de Qalculate" is not supported by "Python 3"
plugin "ExecutaScript" is supported by "Python 3" , requires extensions
("ScriptExtension")
plugin "Resol" is not supported by "Python 3"
dir: "/usr/bin/cantor/assistants"
loading panel plugins for session of type "Python 3"
Requesting capabilities of Python3Session
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/panels"
plugin "Ajuda" is supported, requires extensions ("")
plugin "Gestor de variables" is supported, requires extensions
("VariableManagementExtension")
dir: "/usr/bin/cantor/panels"
Requesting capabilities of Python3Session
Entry Appended
adding panel for "Ajuda"
adding panel for "Gestor de variables"
PythonSession(0x559933a925f0)
Cantor::VariableManagementExtension(0x5599334314c0, name =
"VariableManagementExtension")
loading entries
Entry Appended
Entry Appended
setting result to a type 1 result
update Entry
Entry Appended
Entry Appended
setting result to a type 1 result
update Entry
Entry Appended
setting result to a type 1 result
update Entry
Entry Appended
setting result to a type 1 result
update Entry
Entry Appended
PythonHighlighter constructor
loading assistants...
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/assistants"
plugin "GràficAvançat" is not supported by "Python 3"
plugin "Crea una matriu" is supported by "Python 3" , requires extensions
("LinearAlgebraExtension")
plugin "Deriva" is not supported by "Python 3"
plugin "Valors propis (autovalors)" is not supported by "Python 3"
plugin "Vectors propis (autovectors)" is not supported by "Python 3"
plugin "Importació de paquet" is supported by "Python 3" , requires
extensions ("PackagingExtension")
plugin "Integra" is not supported by "Python 3"
plugin "Inverteix una matriu" is not supported by "Python 3"
plugin "Plot2d" is supported by "Python 3" , requires extensions
("PlotExtension")
plugin "Plot3d" is supported by "Python 3" , requires extensions
("PlotExtension")
plugin "Gràfic de Qalculate" is not supported by "Python 3"
plugin "ExecutaScript" is supported by "Python 3" , requires extensions
("ScriptExtension")
plugin "Resol" is not supported by "Python 3"
dir: "/usr/bin/cantor/assistants"
loading panel plugins for session of type "Python 3"
Requesting capabilities of Python3Session
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/panels"
plugin "Ajuda" is supported, requires extensions ("")
plugin "Gestor de variables&quo
[cantor] [Bug 409533] Cantor crashes every time I execute a Python3 instruction
https://bugs.kde.org/show_bug.cgi?id=409533 --- Comment #3 from avlas --- It even happens parsing a python comment, so nothing is really executed -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409533] Cantor crashes every time I execute a Python3 instruction
https://bugs.kde.org/show_bug.cgi?id=409533 --- Comment #2 from avlas --- (In reply to Nikita Sirgienko from comment #1) > Could you please attache debug output from Cantor? How do I do that? I tried removing "-DCMAKE_BUILD_TYPE=Release -Wnodev" from cmake, but all I can get in the output is: QObject::disconnect: Unexpected null parameter KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = cantor path = /usr/bin pid = 13042 KCrash: Arguments: /usr/bin/cantor KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 > Also, could you uninstall installed Cantor, rebuild the app, and install it > again? Did that already, same behavior (and output) -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409533] New: Cantor crashes every time I execute a Python3 instruction
https://bugs.kde.org/show_bug.cgi?id=409533 Bug ID: 409533 Summary: Cantor crashes every time I execute a Python3 instruction Product: cantor Version: 19.04 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: python3-backend Assignee: cantor-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- SUMMARY After commit 2329f29edc8d83b4823995a184ed454b580f0809 ([Python] Don't use Qt in pythonserver executable for avoding problems with PyQt5), Cantor crashes every time I run python code. ADDITIONAL INFORMATION I don't think the backtrace will be very informative but I couldn't make it any better: Application: Cantor (cantor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb0a6444780 (LWP 30265))] Thread 4 (Thread 0x7fb09132d700 (LWP 30268)): #0 0x7fb0abc989f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e1e73be828) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e1e73be7d8, cond=0x55e1e73be800) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e1e73be800, mutex=0x55e1e73be7d8) at pthread_cond_wait.c:655 #3 0x7fb091dcf3da in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fb091dcf107 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fb0abc926db in start_thread (arg=0x7fb09132d700) at pthread_create.c:463 #6 0x7fb0af89688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fb099f37700 (LWP 30267)): #0 0x7fb0af8850b4 in __GI___libc_read (fd=7, buf=0x7fb099f36be0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fb0aa438c81 in g_wakeup_acknowledge () from /home/jsardid/Documents/al3/cantor/cantor-python-lib/libglib-2.0.so.0 #2 0x7fb0aa3f2788 in g_main_context_check () from /home/jsardid/Documents/al3/cantor/cantor-python-lib/libglib-2.0.so.0 #3 0x7fb0aa3f2c56 in g_main_context_iterate.isra () from /home/jsardid/Documents/al3/cantor/cantor-python-lib/libglib-2.0.so.0 #4 0x7fb0aa3f2dce in g_main_context_iteration () from /home/jsardid/Documents/al3/cantor/cantor-python-lib/libglib-2.0.so.0 #5 0x7fb0afe43dcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb0afde503a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb0afc0c4ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb0acc6e015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fb0afc0dc72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb0abc926db in start_thread (arg=0x7fb099f37700) at pthread_create.c:463 #11 0x7fb0af89688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fb0a2be7700 (LWP 30266)): #0 0x7fb0af889bf9 in __GI___poll (fds=0x7fb0a2be6d28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb0a8e70fc0 in _xcb_conn_wait () from /home/jsardid/Documents/al3/cantor/cantor-python-lib/libxcb.so.1 #2 0x7fb0a8e72a4b in xcb_wait_for_event () from /home/jsardid/Documents/al3/cantor/cantor-python-lib/libxcb.so.1 #3 0x7fb0a5b1f578 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fb0afc0dc72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb0abc926db in start_thread (arg=0x7fb0a2be7700) at pthread_create.c:463 #6 0x7fb0af89688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fb0a6444780 (LWP 30265)): [KCrash Handler] #6 0x7fb0afd63a80 in QProcess::kill() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb0871bf98b in PythonSession::logout() () from /usr/x86_64-linux-gnu/qt5/libcantor_pythonbackend.so #8 0x7fb0871bdb64 in PythonSession::reportServerProcessError(QProcess::ProcessError) () from /usr/x86_64-linux-gnu/qt5/libcantor_pythonbackend.so #9 0x7fb0afe1698f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb0afd61c21 in QProcess::errorOccurred(QProcess::ProcessError) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb0afd6894e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fb0afd68ac9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb0afe16875 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fb0afe23178 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fb0afe23532 in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fb0b0be265c
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 --- Comment #2 from avlas --- (In reply to Laurent Montel from comment #1) > yep pim-setting-exporter but that's only settings, right? as I understand it, there is no way one can export (import) everything to (from) a single compressed file -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409306] no access to local modules/files
https://bugs.kde.org/show_bug.cgi?id=409306 avlas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from avlas --- It worked (even for the last instruction). Thank you! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409304] restart python3 with no confirmation does not work
https://bugs.kde.org/show_bug.cgi?id=409304 --- Comment #3 from avlas --- (In reply to Nikita Sirgienko from comment #2) > Git commit 74e5ddad96b1959914606fccaba2db1b46b734e3 by Nikita Sirgienko. > Committed on 30/06/2019 at 07:12. > Pushed by sirgienko into branch 'Applications/19.04'. > > Minor UI logic improvment > FIXED-IN: 19.04.3 > > M +6-4src/cantor_part.cpp > > https://commits.kde.org/cantor/74e5ddad96b1959914606fccaba2db1b46b734e3 Excellent -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409306] New: no access to local modules/files
https://bugs.kde.org/show_bug.cgi?id=409306
Bug ID: 409306
Summary: no access to local modules/files
Product: cantor
Version: 19.04
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: python3-backend
Assignee: cantor-b...@kde.org
Reporter: jsar...@gmail.com
Target Milestone: ---
- I created a file called test_cantor.py and its only content is "print('Hello
World!')"
- All the following instructions work in Python 3 but fail in Cantor:
import test_cantor
import importlib
importlib.import_module('test_cantor')
import importlib
importlib.reload('test_cantor')
import runpy
runpy.run_module(mod_name='test_cantor')
import runpy
runpy.run_path('test_cantor.py')
- This bug can be workarounded in Cantor (with the exception of last
instruction that continues triggering an error) if I manually append the local
directory to sys.path:
import sys
flag_append_local_dir = True
for path in sys.path:
if path == '.':
flag_append_local_dir = False
break
if flag_append_local_dir:
sys.path.append('.')
for path in sys.path:
print(path)
- But this is not necessary in Python 3, so I think that Cantor is internally
moving to a different folder and can't see local modules/files.
- Could you please try to reproduce the issue and hopefully fix it?
- Please note that the error for "runpy.run_path('test_cantor.py')" seems
different as it cannot be workarounded. This is the output I get for the case
it is useful to fix this second issue:
Traceback (most recent call last):
File "/home/username/test_cantor.cws", line 1, in
File "/home/miniconda/envs/cenv1/lib/python3.7/runpy.py", line 263, in
run_pathpkg_name=pkg_name, script_name=fname)
File "/home/miniconda/envs/cenv1/lib/python3.7/runpy.py", line 93, in
_run_module_code
with _TempModule(mod_name) as temp_module, _ModifiedArgv0(fname):
File "/home/miniconda/envs/cenv1/lib/python3.7/runpy.py", line 54, in
__enter__
self._saved_value = sys.argv[0]
IndexError: list index out of range
--
You are receiving this mail because:
You are watching all bug changes.
[cantor] [Bug 409304] New: restart python3 with no confirmation does not work
https://bugs.kde.org/show_bug.cgi?id=409304 Bug ID: 409304 Summary: restart python3 with no confirmation does not work Product: cantor Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: python3-backend Assignee: cantor-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- by default restarting python 3 within cantor requires confirmation and works as expected, but if I removed confirmation in settings, it stops working not sure other backends (e.g. python 2) are affected -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409137] display variable size instead of ""
https://bugs.kde.org/show_bug.cgi?id=409137 --- Comment #5 from avlas --- (In reply to Nikita Sirgienko from comment #3) > (In reply to avlas from comment #2) > > (In reply to Nikita Sirgienko from comment #1) > > Would you consider adding this functionality to the backend languages for > > which this computation seems rather simple? Thinking about > > R/Octave/Scilab/Julia/Python, maybe others. > > I am thinking about it, and I'll see what i can do For those backends for which this may be possible, do you think it would be better/easier to show three columns (Name, Size and Values)? [Now that I think about it, should we add Type as well?] Ideally the columns for Size and Values (and Type if considered) could be enabled optionally. I would very much like to have sizes (and maybe types) at sight to better understand the data and code in mutual context, to ease debugging, etc. I don't feel that (an incomplet) list of values are that important, at least for my workflow. Also, having a bunch of Values is a bit distracting, for instance column arrays hide a lot of other variables in the workspace. [Side note: this behavior (how values are displayed) could also be changed. An example of this could be how latest stable versions of Octave display values in the workspace, and perhaps cantor could consider adding a specific variable display panel similar to Octave's variable editor (although this would be a more sophisticated/complicated add)] -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409240] warning messages stop execution
https://bugs.kde.org/show_bug.cgi?id=409240 --- Comment #2 from avlas --- (In reply to Nikita Sirgienko from comment #1) > Myabe i could catch warning and not threat them as error That would be great -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409240] New: warning messages stop execution
https://bugs.kde.org/show_bug.cgi?id=409240 Bug ID: 409240 Summary: warning messages stop execution Product: cantor Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: python3-backend Assignee: cantor-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Would you consider displaying warnings without breaking execution? This is how it works upstream in contrast to errors. I recall this option was implemented in Octave recently. Could you please port it to Python? Maybe other backends are affected as well. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409138] "Open recent" is missing
https://bugs.kde.org/show_bug.cgi?id=409138 --- Comment #3 from avlas --- (In reply to Nikita Sirgienko from comment #2) > I haven't maked icon in the toolbar, because I think, that this is function > won't be used a lot, so only File menu. Thank you! Actually, the icon option is there as well, only not by default. One can edit the toolbar and add it :) -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409137] display variable size instead of ""
https://bugs.kde.org/show_bug.cgi?id=409137 --- Comment #4 from avlas --- (In reply to Nikita Sirgienko from comment #3) > (In reply to avlas from comment #2) > > (In reply to Nikita Sirgienko from comment #1) > > Would you consider adding this functionality to the backend languages for > > which this computation seems rather simple? Thinking about > > R/Octave/Scilab/Julia/Python, maybe others. > > I am thinking about it, and I'll see what i can do Thank you -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409139] Right sided comments (comments appearing after some code) make the full line appear in gray
https://bugs.kde.org/show_bug.cgi?id=409139 --- Comment #4 from avlas --- (In reply to Nikita Sirgienko from comment #3) > Git commit c26b559c33ed99e311059d525f987b61a8d5a237 by Nikita Sirgienko. > Committed on 26/06/2019 at 19:21. > Pushed by sirgienko into branch 'Applications/19.04'. > > [Python] Fix highlighting bug > FIXED-IN: 19.04.3 > > M +1-1src/backends/python/pythonhighlighter.cpp > > https://commits.kde.org/cantor/c26b559c33ed99e311059d525f987b61a8d5a237 Thanks! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409137] display variable size instead of ""
https://bugs.kde.org/show_bug.cgi?id=409137 --- Comment #2 from avlas --- (In reply to Nikita Sirgienko from comment #1) > I sure, that ability to calculate object size is pretty strict for backends. > For example, I am not sure, that Lua could do it without overhead. I see. I was not aware of these technicalities. Would you consider adding this functionality to the backend languages for which this computation seems rather simple? Thinking about R/Octave/Scilab/Julia/Python, maybe others. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409139] Right sided comments (comments appearing after some code) make the full line appear in gray
https://bugs.kde.org/show_bug.cgi?id=409139 --- Comment #2 from avlas --- Python3 (Sorry, I thought it could be sth general) -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409139] New: Right sided comments (comments appearing after some code) make the full line appear in gray
https://bugs.kde.org/show_bug.cgi?id=409139 Bug ID: 409139 Summary: Right sided comments (comments appearing after some code) make the full line appear in gray Product: cantor Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- When adding a comment after some code, the full line appears in gray as if all the line was a comment. Gray style should remain instead only for the comment, while the code on the left side remain highlighted as code. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409138] New: "Open recent" is missing
https://bugs.kde.org/show_bug.cgi?id=409138 Bug ID: 409138 Summary: "Open recent" is missing Product: cantor Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- It would be great to have a list for easy access to recent cantor worksheets, both in the File menu as well as an icon in the toolbar. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409137] New: display variable size instead of ""
https://bugs.kde.org/show_bug.cgi?id=409137 Bug ID: 409137 Summary: display variable size instead of "" Product: cantor Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- In the panel of variable management, the value column should perhaps be renamed to "content", and the variable size should be displayed instead of the uninformative "" when appropriate. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408642] plasma 5.16 notifications are not displayed
https://bugs.kde.org/show_bug.cgi?id=408642 avlas changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #12 from avlas --- (In reply to Michail Vourlakos from comment #11) > (In reply to avlas from comment #9) > > (In reply to Michail Vourlakos from comment #6) > > > > > Please try Kai's proposal with the following command: > > "QT_LOGGING_RULES=org.kde.plasma.notifications=true latte-dock -d" > > and report back anything related to org.kde.plasma.notifications debug output It's weird, after setting notifications in plasmashell and removing them and setting them back to latte, not sure how many times, 2-3-4, it seems everything went back to normal and I can enjoy new plasma 5.16 notifications in latte just fine. No idea what went wrong before and how it got fixed, but anyways. Closing this as fixed. I may reopen if this fails again, but hopefully it's not going to happen. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 407454] konqueror crash on shutdown
https://bugs.kde.org/show_bug.cgi?id=407454
--- Comment #8 from avlas ---
(In reply to Johannes Hirte from comment #3)
> This can't work. s_cookieJar is declared static, but QWebEngineProfile *prof
> is set as parent QObject, that will try to delete it on shutdown. Following
> patch fixed it for me:
>
> diff --git a/webenginepart/src/webenginepart.cpp
> b/webenginepart/src/webenginepart.cpp
> index bfd16ff4a..eaadda781 100644
> --- a/webenginepart/src/webenginepart.cpp
> +++ b/webenginepart/src/webenginepart.cpp
> @@ -95,7 +95,7 @@ WebEnginePart::WebEnginePart(QWidget *parentWidget,
> QObject *parent,
> prof->installUrlSchemeHandler("error", new
> WebEnginePartErrorSchemeHandler(prof));
> prof->installUrlSchemeHandler("help", new
> WebEnginePartKIOHandler(prof));
> }
> -static WebEnginePartCookieJar s_cookieJar(prof, prof);
> +static WebEnginePartCookieJar s_cookieJar(prof, nullptr);
> KAboutData about = KAboutData(QStringLiteral("webenginepart"),
>i18nc("Program Name", "WebEnginePart"),
>/*version*/ QStringLiteral("1.3.0"),
This worked for me
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 408642] plasma 5.16 notifications are not displayed
https://bugs.kde.org/show_bug.cgi?id=408642 --- Comment #9 from avlas --- (In reply to Michail Vourlakos from comment #6) > > Rule) Notifications can be ONLY in Latte or in Plasma (You can not have both > worlds, that also applies to the plasma systray of course) Sure > So, in my system: > 1. There are NO Plasma panels > 2. There are NO Plasma applets in the desktop > 3. Notifications applet is found only a Latte Dock > 4. Restarting and relogin, notifications work just fine in plasma 5.16 In my system w/ Latte 0.8.8: 1. Same 2. I do have some, but anything related to system tray / notifications 3. Same 4. It doesn't work -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408642] plasma 5.16 notifications are not displayed
https://bugs.kde.org/show_bug.cgi?id=408642 --- Comment #8 from avlas --- (In reply to Michail Vourlakos from comment #6) > (In reply to avlas from comment #5) > > (In reply to Michail Vourlakos from comment #3) > > > (In reply to avlas from comment #0) > > > > To reproduce that they don't work you need to start your session from > > scratch because otherwise notifications appear because they were part of > > plasmashell. > > > > Try it out yourself, removing all instances of notifications in plasmashell, > > and restart your session to see it... > > > > [ I also got confused by that before ] > > nope, this is not my case... > > Rule) Notifications can be ONLY in Latte or in Plasma (You can not have both > worlds, that also applies to the plasma systray of course) > > So, in my system: > 1. There are NO Plasma panels > 2. There are NO Plasma applets in the desktop > 3. Notifications applet is found only a Latte Dock > 4. Restarting and relogin, notifications work just fine in plasma 5.16 Are you using version 0.8.8? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408642] plasma 5.16 notifications are not displayed
https://bugs.kde.org/show_bug.cgi?id=408642 --- Comment #5 from avlas --- (In reply to Michail Vourlakos from comment #3) > (In reply to avlas from comment #0) > > Plasma 5.16 notifications are not displayed in latte (i.e., the > > notifications applet is in a system tray in a latte panel) > > just checked, they work... > > 1. Remove all plasma panels > 2. Open Latte > 3. Add a notification applet in Latte > 4. Run through terminal "notify-send hello" > 5. notification is shown in the notification list > > On the other hand trying to open notifications applet settings I get: > > '' > /home/master/kde/usr/bin/kcmshell5: /usr/lib64/libQt5Core.so.5: version > `Qt_5_PRIVATE_API' not found (required by > /home/master/kde/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5) > '' To reproduce that they don't work you need to start your session from scratch because otherwise notifications appear because they were part of plasmashell. Try it out yourself, removing all instances of notifications in plasmashell, and restart your session to see it... [ I also got confused by that before ] -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408642] plasma 5.16 notifications are not displayed
https://bugs.kde.org/show_bug.cgi?id=408642 --- Comment #2 from avlas --- (In reply to Michail Vourlakos from comment #1) > New notification system probably does not function with Latte I hope you can port that functionality back to Latte -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408642] New: plasma 5.16 notifications are not displayed
https://bugs.kde.org/show_bug.cgi?id=408642 Bug ID: 408642 Summary: plasma 5.16 notifications are not displayed Product: lattedock Version: 0.8.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jsar...@gmail.com Target Milestone: --- Plasma 5.16 notifications are not displayed in latte (i.e., the notifications applet is in a system tray in a latte panel) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #17 from avlas --- (In reply to Michail Vourlakos from comment #16) > (In reply to avlas from comment #15) > > (In reply to Michail Vourlakos from comment #11) > > > Git commit ec284dbfa8d7f00083e506e1f9a87eb37f835192 by Michail Vourlakos. > > > Committed on 12/06/2019 at 20:39. > > > Pushed by mvourlakos into branch 'v0.8'. > > > > > > blacklist plasma notifications in heuristics > > > > > > --plasma notification applet has become more complex > > > lets blacklist it in order to provide the real > > > plasma experience and see how it goes > > > FIXED-IN: 0.8.9 > > > > > > M +2-1containment/package/contents/code/AppletIdentifier.js > > > > > > https://commits.kde.org/latte-dock/ec284dbfa8d7f00083e506e1f9a87eb37f835192 > > > > Mmm, after applying this change, I don't see any notification anymore :( > (In reply to avlas from comment #15) > > (In reply to Michail Vourlakos from comment #11) > > > Git commit ec284dbfa8d7f00083e506e1f9a87eb37f835192 by Michail Vourlakos. > > > Committed on 12/06/2019 at 20:39. > > > Pushed by mvourlakos into branch 'v0.8'. > > > > > > blacklist plasma notifications in heuristics > > > > > > --plasma notification applet has become more complex > > > lets blacklist it in order to provide the real > > > plasma experience and see how it goes > > > FIXED-IN: 0.8.9 > > > > > > M +2-1containment/package/contents/code/AppletIdentifier.js > > > > > > https://commits.kde.org/latte-dock/ec284dbfa8d7f00083e506e1f9a87eb37f835192 > > > > Mmm, after applying this change, I don't see any notification anymore :( > > How is this relevant to notification applet not been visible? Not relevant, sorry, got confused. Will open a new bug -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #15 from avlas --- (In reply to Michail Vourlakos from comment #11) > Git commit ec284dbfa8d7f00083e506e1f9a87eb37f835192 by Michail Vourlakos. > Committed on 12/06/2019 at 20:39. > Pushed by mvourlakos into branch 'v0.8'. > > blacklist plasma notifications in heuristics > > --plasma notification applet has become more complex > lets blacklist it in order to provide the real > plasma experience and see how it goes > FIXED-IN: 0.8.9 > > M +2-1containment/package/contents/code/AppletIdentifier.js > > https://commits.kde.org/latte-dock/ec284dbfa8d7f00083e506e1f9a87eb37f835192 Mmm, after applying this change, I don't see any notification anymore :( -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #6 from avlas --- Same thing here. Also, https://bugs.kde.org/show_bug.cgi?id=407919 in Arch seems a duplicate of this one. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 408622] New: Konqueror crashed when exiting
https://bugs.kde.org/show_bug.cgi?id=408622 Bug ID: 408622 Summary: Konqueror crashed when exiting Product: konqueror Version: 5.0.97 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 5.0.0-16-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Konqueror does not quit gracefully and crashes when the last tab is closed The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8da16aedc0 (LWP 30895))] Thread 20 (Thread 0x7f8d44936700 (LWP 30937)): #0 0x7f8da0efb6ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f8da0efd474 in ___fprintf_chk (fp=0x7f8da11b88b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f8d691b76a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f8d6919f9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f8d6919fb44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f8d691a146c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f8d69197114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f8d6c39dc79 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d6c3382db in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d6c36a311 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d6c39a561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8d960266db in start_thread (arg=0x7f8d44936700) at pthread_create.c:463 #11 0x7f8da0eec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f8d45137700 (LWP 30924)): #0 0x7f8d9602c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f8d45136c48) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f8d9602c9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f8d45136bf8, cond=0x7f8d45136c20) at pthread_cond_wait.c:502 #2 0x7f8d9602c9f3 in __pthread_cond_wait (cond=0x7f8d45136c20, mutex=0x7f8d45136bf8) at pthread_cond_wait.c:655 #3 0x7f8d6c397a49 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8d6c398478 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8d6c39850f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8d6c358fc8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d6c35b7f6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d6c35bb34 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d6c39a561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8d960266db in start_thread (arg=0x7f8d45137700) at pthread_create.c:463 #11 0x7f8da0eec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f8d45b38700 (LWP 30923)): #0 0x7f8d9602ced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f8d45b37a50, expected=0, futex_word=0x7f8d45b37c38) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f8d9602ced9 in __pthread_cond_wait_common (abstime=0x7f8d45b37af0, mutex=0x7f8d45b37be8, cond=0x7f8d45b37c10) at pthread_cond_wait.c:533 #2 0x7f8d9602ced9 in __pthread_cond_timedwait (cond=0x7f8d45b37c10, mutex=0x7f8d45b37be8, abstime=0x7f8d45b37af0) at pthread_cond_wait.c:667 #3 0x7f8d6c397b17 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8d6c39846a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8d6c398552 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8d6c358fb1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d6c35b4c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d6c35bab4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d6c39a561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8d960266db in start_thread (arg=0x7f8d45b38700) at pthread_create.c:463 #11 0x7f8da0eec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f8d46973700 (LWP 30922)): #0 0x7f8d9602a4a7 in __pthread_mutex_unlock_full (mutex=0x55b763d2df70, decr=) at pthread_mutex_unlock.c:274 #1 0x7f8d505cc5fe in pa_mutex_unlock () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f8d58067473 in () at
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #6 from avlas --- (In reply to Michail Vourlakos from comment #4) > I wouldn't be surprised if Latte heuristics broke in plasma 5.16 Please take a look at https://bugs.kde.org/show_bug.cgi?id=407757#c21 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407757] Notifications from kdeconnect all display in the centre of the screen on top of each other
https://bugs.kde.org/show_bug.cgi?id=407757 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #24 from avlas --- Is the location issue related to https://bugs.kde.org/show_bug.cgi?id=408566#c5? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #5 from avlas --- (In reply to Michail Vourlakos from comment #4) > I wouldn't be surprised if Latte heuristics broke in plasma 5.16 It works for my in Latte 0.8.8 after removing and re-adding notification in latte's system tray. However, notifications are displayed in the center of the screen. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 332117] Feature request: more flexibility in inline notes
https://bugs.kde.org/show_bug.cgi?id=332117 avlas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #10 from avlas --- I think so -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 avlas changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #34 from avlas --- (In reply to Nikita Sirgienko from comment #33) > Nice, that we solve this problem, should I close this bugreport? I would say so. [ Ideally, one would modify this in Cantor's settings, but this doesn't seem possible at all, so I guess there are no easier options than this solution ] -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #32 from avlas --- (In reply to Nikita Sirgienko from comment #27) > I freaked out of it, if we want to working with conda qt libraries, we also > need build QtDbus 5.12 and build all cantor KF5 dependency for this qt > version.(In reply to avlas from comment #26) > > I think it would work for me if there would be a way to explicitly indicate > > the location of the Qt5 library, similarly to what we do with python3 libs > > I don't think so: as I see, if we want use conda qt library, we need also > build QtDbus 5.12 and build all cantor KF5 dependency. It a lot of work. > > Well, that about this? > 0. cd /home/miniconda/envs/cenv1/lib/ > 1. mkdir cantor-python-dir > 2. cd cantor-python-dir > 3. ln -s /home/miniconda/envs/cenv1/lib/libpython3.7m.so.1.0 > libpython3.7m.so.1.0 > 4. LD_LIBRARY_PATH=/home/miniconda/envs/cenv1/lib/cantor-python-dir cantor > -b python3 By the way, thanks a lot for the workaround :) -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #31 from avlas --- (In reply to Nikita Sirgienko from comment #30) > (In reply to avlas from comment #28) > > (In reply to Nikita Sirgienko from comment #27) > > > > I think it would work for me if there would be a way to explicitly > > > > indicate > > > > the location of the Qt5 library, similarly to what we do with python3 > > > > libs > > > > > > I don't think so: as I see, if we want use conda qt library, we need also > > > build QtDbus 5.12 and build all cantor KF5 dependency. It a lot of work. > > > > I meant systems Qt5 library, because the error comes from cantor using > > conda's library instead. But it may not be possible, don't know... > > > > > > > Well, that about this? > > > 0. cd /home/miniconda/envs/cenv1/lib/ > > > 1. mkdir cantor-python-dir > > > 2. cd cantor-python-dir > > > 3. ln -s /home/miniconda/envs/cenv1/lib/libpython3.7m.so.1.0 > > > libpython3.7m.so.1.0 > > > 4. LD_LIBRARY_PATH=/home/miniconda/envs/cenv1/lib/cantor-python-dir cantor > > > -b python3 > > > > I'll check it out, but I think it won't fix the issue with the Qt5 libraries > > (conda's Qt5 libs are < 5.12) > > In `cantor-python-dir` directory you need have Cantor builded with system qt > libraries (cmake without CMAKE_PREFIX_PATH). > This variant actually fix the problem, that when we use LD_LIBRARY_PATH, we > add path to python library, but also path to conda qt libraries, which > conflicts with system qt libraries. Only with libpython3.7m.so* does not work as it may be internally relying on other libs of the same folder, so I linked all libraries and then removed the link to libQt5* libs in that folder and worked :) By the way, that folder can be anywhere, so I created it within cantor folder instead of in conda's. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #29 from avlas --- (In reply to avlas from comment #28) > (In reply to Nikita Sirgienko from comment #27) > > > I think it would work for me if there would be a way to explicitly > > > indicate > > > the location of the Qt5 library, similarly to what we do with python3 libs > > > > I don't think so: as I see, if we want use conda qt library, we need also > > build QtDbus 5.12 and build all cantor KF5 dependency. It a lot of work. > > I meant systems Qt5 library, because the error comes from cantor using > conda's library instead. But it may not be possible, don't know... > > > > Well, that about this? > > 0. cd /home/miniconda/envs/cenv1/lib/ > > 1. mkdir cantor-python-dir > > 2. cd cantor-python-dir > > 3. ln -s /home/miniconda/envs/cenv1/lib/libpython3.7m.so.1.0 > > libpython3.7m.so.1.0 > > 4. LD_LIBRARY_PATH=/home/miniconda/envs/cenv1/lib/cantor-python-dir cantor > > -b python3 > > I'll check it out, but I think it won't fix the issue with the Qt5 libraries > (conda's Qt5 libs are < 5.12) Oh, I see the logic now, will check -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #28 from avlas --- (In reply to Nikita Sirgienko from comment #27) > > I think it would work for me if there would be a way to explicitly indicate > > the location of the Qt5 library, similarly to what we do with python3 libs > > I don't think so: as I see, if we want use conda qt library, we need also > build QtDbus 5.12 and build all cantor KF5 dependency. It a lot of work. I meant systems Qt5 library, because the error comes from cantor using conda's library instead. But it may not be possible, don't know... > Well, that about this? > 0. cd /home/miniconda/envs/cenv1/lib/ > 1. mkdir cantor-python-dir > 2. cd cantor-python-dir > 3. ln -s /home/miniconda/envs/cenv1/lib/libpython3.7m.so.1.0 > libpython3.7m.so.1.0 > 4. LD_LIBRARY_PATH=/home/miniconda/envs/cenv1/lib/cantor-python-dir cantor > -b python3 I'll check it out, but I think it won't fix the issue with the Qt5 libraries (conda's Qt5 libs are < 5.12) -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #26 from avlas --- I think it would work for me if there would be a way to explicitly indicate the location of the Qt5 library, similarly to what we do with python3 libs -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #25 from avlas --- Sorry last sentence didn't make much sense. I meant, I guess I don't fully understand what makes python so special in comparison to other cantor backends, but it is how it is :/ -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #24 from avlas --- (In reply to Nikita Sirgienko from comment #23) > Could you try this variant, with proper paths? > > cmake -DCMAKE_PREFIX_PATH=/home/1998/anaconda3 > -DPYTHONLIBS3_LIBRARY=/home/1998/anaconda3/lib/libpython3.7m.so > -DPYTHONLIBS3_INCLUDE_DIR=/home/1998/anaconda3/include/python3.7m .. there are lots of cmake warnings, and then there are make errors complaining about Qt 5.12 undefined references: /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.12.0: undefined reference to `qt_version_tag@Qt_5.12' /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.12.0: undefined reference to `QString::arg(QLatin1String, int, QChar) const@Qt_5' collect2: error: ld returned 1 exit status . . . /usr/include/KF5/KTextEditor/ktexteditor/editor.h:255:46: error: ‘QStringView’ does not name a type; did you mean ‘QStringList’? I recognized that this is trickier than I anticipated. I guess I don't fully understand what makes:/ -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #22 from avlas --- (In reply to Nikita Sirgienko from comment #20) > Okey, I got it, maybe moving libraries was not good idea. > We actually could ignore cmake warning them, we use LD_LIBRARY_PATH to point > python library (and also to all libraries in this directory). > So, we could not do steps 0 and 1, but in this case, we loose any system > settings (like icons theme, fonts) as I see. Unfortunately there is no difference, same thing happens even if one omits steps 0 and 1. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #19 from avlas --- (In reply to Nikita Sirgienko from comment #18) > I don't understand correctly, you make a mistake only in the message, or > also when build cantor? Only in what I pasted here. The procedure was correct. In summary, this recipe only works if Qt libraries are not present in conda's library. Once they are set back in their folder, cantor crashes because it does not like Qt libs < 5.12 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #17 from avlas --- Sorry, point 1 above should read "mv libQt5* ../" (I copied "mv ../libQt5* .", which is how I put them back, by mistake) -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #16 from avlas --- (In reply to avlas from comment #15) > (In reply to Nikita Sirgienko from comment #14) > > It's actually strange: for using the libraries in cantor, cmake need found > > them first. Could you cleanup build directory with 'rm -rf *' (or something > > like that) before cmake run? Is it solve the problem? > > And did you install new cantor build? I mean, cantor could work only > > installed, so you need somethink like 'make && make install && cantor -b > > python3'. > > That's exactly what I did. > > I think it's because "LD_LIBRARY_PATH=/home/miniconda/envs/cenv1/lib/" sets > the path for the Qt libraries as well, and them being different than Qt 5.12 > trigger the error... If you want me to be more explicit, I did: 0. cd /home/miniconda/envs/cenv1/lib/ 1. mv ../libQt5* . 2. cd to cantor build directory 3. rm -rf * 4. cmakekde5 -DPYTHONLIBS3_LIBRARY=/home/miniconda/envs/cenv1/lib/libpython3.7m.so -DPYTHONLIBS3_INCLUDE_DIR=/home/miniconda/envs/cenv1/include/python3.7m 5. make -j9 6. sudo make install 7. LD_LIBRARY_PATH=/home/miniconda/envs/cenv1/lib/ cantor -b python3 If libQt5* libs are moved back to /home/miniconda/envs/cenv1/lib/ before executing point 7 above, the error is triggered -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #15 from avlas --- (In reply to Nikita Sirgienko from comment #14) > It's actually strange: for using the libraries in cantor, cmake need found > them first. Could you cleanup build directory with 'rm -rf *' (or something > like that) before cmake run? Is it solve the problem? > And did you install new cantor build? I mean, cantor could work only > installed, so you need somethink like 'make && make install && cantor -b > python3'. That's exactly what I did. I think it's because "LD_LIBRARY_PATH=/home/miniconda/envs/cenv1/lib/" sets the path for the Qt libraries as well, and them being different than Qt 5.12 trigger the error... -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #13 from avlas --- (In reply to Nikita Sirgienko from comment #12) > Some clarification: after moving qt libs from anaconda3/lib directory, you > need clean up your build directory and rerun cmake. I did. I reran cmake and make, and then get those libraries back. The error appeared anyway. However, if I keep the libraries away, cantor and its python3 backend in the conda environment work. Unfortunately, permanently removing those libraries is not an option for having conda working properly... -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200
--- Comment #11 from avlas ---
(In reply to Nikita Sirgienko from comment #9)
> About hidden library, I solved this in ugly, but effective, way: moving all
> libQt5 shared libraries ("mv /home/1998/anaconda3/lib/libQt5*
> /home/1998/anaconda3", for example) and cmake directory ("mv
> /home/1998/anaconda3/lib/cmake /home/1998/anaconda3/") before
> building (and return all files back after build).
Weird. Even after doing this, I get the error:
"cantor: /home/miniconda/envs/cenv1/lib/libQt5Core.so.5: version `Qt_5.12' not
found (required by /usr/x86_64-linux-gnu/qt5/libcantorlibs.so.21)"
--
You are receiving this mail because:
You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #10 from avlas --- Will give a try, thank you -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #6 from avlas --- With the static library ".a" I get a compilation error. With the dynamic library ".so", cmake warns about Qt5 libraries may be hidden in miniconda lib. An example: "runtime library [libQt5Widgets.so.5] in /usr/lib/x86_64-linux-gnu may be hidden by files in: /home/miniconda/envs/cenv1/lib" But I can build cantor with no error. However, the backend does not seem to work. I get the following error: The name org.kde.Cantor.Python3-0 was not provided by any .service files -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #4 from avlas --- (In reply to Alexander Semke from comment #3) > You can provide hints here by setting the environment > variables PYTHONLIBS3_INCLUDEDIR and PYTHONLIBS3_LIBDIR in your shell. Just > point these variables to your conda installation and it should work. I tried but it doesn't seem to work -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 --- Comment #2 from avlas --- (In reply to Alexander Semke from comment #1) > The only way to achieve this at the moment is to recompile Cantor with > python headers and libs from the conda environment. So, cantor has to be > linked against this environment... It would be great if this could be easily modified from settings (as it can be done for other backends). I thought that just replacing which python is used could be enough, but I guess I was too optimistic. This is a workaround I could use as I'm actually compiling Cantor myself because of bug https://bugs.kde.org/show_bug.cgi?id=406712 Could you please let me know how to build linking to Conda instead? I tried compiling Cantor from scratch inside Conda's environment but this is creating lots of cmake errors because of things that are not python related. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 407200] New: cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 Bug ID: 407200 Summary: cantor python backends are hardcoded to the system Product: cantor Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: python3-backend Assignee: nlmin...@gmail.com Reporter: jsar...@gmail.com CC: alexander.se...@web.de, fil...@kde.org Target Milestone: --- I'd like to use python3 (and its packages, etc) in cantor within my conda environment, but that doesn't seem to be possible. It is somehow hardcoded to use system's python version: /usr/lib/python3 -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #18 from avlas --- (In reply to Laurent Montel from comment #17) > now we can define the size of image (using =x) Nice! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 406712] applications associated with cantor backends should not be strong dependencies but recommendations
https://bugs.kde.org/show_bug.cgi?id=406712 avlas changed: What|Removed |Added Resolution|NOT A BUG |INTENTIONAL --- Comment #5 from avlas --- Another notorious example to compare to: Online accounts in system settings displaying ownCloud and Twitter. With respect to the decision about Cantor, this doesn't seem to be very coherent: - ownCloud is presented as an option even if nothing related to it is installed in my system. You click on it and it opens a menu so you can configure it (exactly what I request for Cantor). Only that if you cancel, instead of quitting gracely, it breaks system settings awaiting a response that never happens. - twitter: no idea what this is, I clicked on it, and nothing happens beyond the indicator that system settings is stuck awaiting for something... which sounds like the "twitter" component is "breaking" system settings. Anyways, I decided to build Cantor on my own instead of using neon packages and having to change dependencies all the time. I mark this bug as resolved intentional instead because I think it is better classified. Not a bug is arguable, but intentional is very clear, you don't have the intention to modify this following your fuzzy logic, which I respect even though I don't share. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407008] Can't access my GDrive anymore since 19.04.0 apps update
https://bugs.kde.org/show_bug.cgi?id=407008 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #16 from avlas --- (In reply to Laurent Montel from comment #15) > (In reply to avlas from comment #14) > > (In reply to Laurent Montel from comment #13) > > > Git commit 137430312149daa2a95109160d236ad7c70d14a6 by Laurent Montel. > > > Committed on 25/04/2019 at 07:11. > > > Pushed by mlaurent into branch 'master'. > > > > > > Fix Bug 406334 - Markdown addon: embedded images (attached to the email) > > > are > > > not displayed > > > FIXED-IN: 5.12.0 > > > > > > M +6-5 > > > kmail/editorconvertertextplugins/markdown/markdowninterface.cpp > > > > > > https://commits.kde.org/kdepim-addons/ > > > 137430312149daa2a95109160d236ad7c70d14a6 > > > > Great, thanks! > > > > Do you think there could be a way to apply styling? I think it would be the > > last missing piece > > It's still on my todo list (+ some others fix/improvement) > > See you if I will find a fix for it too :) Very much appreciated! -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #14 from avlas --- (In reply to Laurent Montel from comment #13) > Git commit 137430312149daa2a95109160d236ad7c70d14a6 by Laurent Montel. > Committed on 25/04/2019 at 07:11. > Pushed by mlaurent into branch 'master'. > > Fix Bug 406334 - Markdown addon: embedded images (attached to the email) are > not displayed > FIXED-IN: 5.12.0 > > M +6-5 > kmail/editorconvertertextplugins/markdown/markdowninterface.cpp > > https://commits.kde.org/kdepim-addons/ > 137430312149daa2a95109160d236ad7c70d14a6 Great, thanks! Do you think there could be a way to apply styling? I think it would be the last missing piece -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 406712] applications associated with cantor backends should not be strong dependencies but recommendations
https://bugs.kde.org/show_bug.cgi?id=406712 --- Comment #4 from avlas --- (In reply to Harald Sitter from comment #1) > That would also allow "breaking" cantor, which as far as the deb dependency > line-up is concerned is not something that should be allowed. Mixing the > stack like this simply isn't going to work I expect, it'd mean that the > various distributions mechanism needs to be aware of one another (which they > are not) or to allow the distribution mechanisms of disobeying requirements > (which they should not). Would you please reconsider your decision once Cantor 19.08 is released? Please see https://bugs.kde.org/show_bug.cgi?id=406779#c2 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 406779] Do not filter out backends as missing, they may just need proper configuration
https://bugs.kde.org/show_bug.cgi?id=406779 --- Comment #3 from avlas --- (In reply to Nikita Sirgienko from comment #2) > Git commit 731fa7186d80f330bf7d7fed8a86b9c2cff4172f by Nikita Sirgienko. > Committed on 24/04/2019 at 21:48. > Pushed by sirgienko into branch 'master'. > > Improve logic of backend showing: > - Now, all installed backends showed, even disabled > - For backends with missing requirements, Cantor shows information from > backends, about what user needs to do to enable backend. > Also increase soversion of Cantor library, because we break ABI. > FIX-IN: 19.08 > > M +25 -6src/backendchoosedialog.cpp > M +2-1src/backendchoosedialog.h > M +11 -2src/backends/R/rbackend.cpp > M +1-1src/backends/R/rbackend.h > M +11 -4src/backends/julia/juliabackend.cpp > M +1-1src/backends/julia/juliabackend.h > M +18 -2src/backends/lua/luabackend.cpp > M +1-1src/backends/lua/luabackend.h > M +18 -3src/backends/maxima/maximabackend.cpp > M +1-1src/backends/maxima/maximabackend.h > M +18 -2src/backends/octave/octavebackend.cpp > M +1-1src/backends/octave/octavebackend.h > M +19 -4src/backends/sage/sagebackend.cpp > M +1-1src/backends/sage/sagebackend.h > M +18 -3src/backends/scilab/scilabbackend.cpp > M +2-2src/backends/scilab/scilabbackend.h > M +1-1src/lib/CMakeLists.txt > M +2-1src/lib/backend.cpp > M +2-1src/lib/backend.h > > https://commits.kde.org/cantor/731fa7186d80f330bf7d7fed8a86b9c2cff4172f Excellent, thank you! -- You are receiving this mail because: You are watching all bug changes.
