[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 --- Comment #15 from Stas --- It is nearly unbelivable that this issue is solved ;) Thank you very much! No I will be able to use Korganizer again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397540] New: STARTTLS Connection does nto send Email
https://bugs.kde.org/show_bug.cgi?id=397540 Bug ID: 397540 Summary: STARTTLS Connection does nto send Email Product: kmail2 Version: 5.8.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: stas.kaz...@googlemail.com Target Milestone: --- Hello, I have the following settings which I need to use in order to connect to my email server to send emails: Type: SMTP STMP-server: smtp2.mis.mpg.de Port: 587 Encryption type: SSL (STARTTLS) Everything works in Thunderbird and Geary but I cannot connect to the sending server with Kmail. My settings are: Encryption: TLS Port: 587 Authentication: LOGIN However, I have tries various combinations and nothing worked for me. Thunderbird uses: Encryption: STARTTLS Port: 587 Does someone have an idea what is wrong here? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397540] STARTTLS Connection does nto send Email
https://bugs.kde.org/show_bug.cgi?id=397540 Stas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Stas --- Sorry, have to use 'sent via' because I have two accounts. Even if I use another identity. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389297] plasmashell does not show a panel and layout settings cannot be changed
https://bugs.kde.org/show_bug.cgi?id=389297 Stas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #18 from Stas --- For me the file was in /usr/share/plasma/plasmoids/kpluginindex.json And yes, deleting it solved the problem. Thanks for the solution. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391745] New: Shortcut for last used tool/tag
https://bugs.kde.org/show_bug.cgi?id=391745 Bug ID: 391745 Summary: Shortcut for last used tool/tag Product: digikam Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: stas.kaz...@googlemail.com Target Milestone: --- Hello, it would be great if there would be a shortcut to use the last tool again. Cases, where it would help speed up the workflow are: 1. Add face regions manually on photos where the faces are not recognized properly. 2. Assign a special tag to multiple photos without the need of retyping it. 3. ... Especially the first case is really important, since go to the tool bar each time you want to draw a new face region is inconvenient. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389297] Networkmanager aswell as other system items (volume) not shown in the system tray
https://bugs.kde.org/show_bug.cgi?id=389297
--- Comment #6 from Stas ---
I still have problems with 5.12 version.
When i start systemsettings5 from console and go to layout, I get the following
errors:
[code]
KActivities: Database connection:
"kactivities_db_resources_139926662121472_readonly"
query_only: QVariant(qlonglong, 1)
journal_mode:QVariant(QString, "wal")
wal_autocheckpoint: QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 0)
Nothing to load - the client id is empty
Nothing to load - the client id is empty
Error: QSqlError("11", "Unable to fetch row", "database disk image is
malformed")
Error: QSqlError("11", "Unable to fetch row", "database disk image is
malformed")
org.kde.kcoreaddons: Error loading plugin "kcm_lookandfeel" "The shared library
was not found."
Plugin search paths are ("/usr/lib/qt/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
KActivitiesStats( 0x55e06f4e2e20 ) ResultModelPrivate::onResultScoreUpdated
result added: "kcm:kcm_lookandfeel.desktop" score: 0 last: 1518176817 first:
4294967295
file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml:190:
ReferenceError: needsSave is not defined
file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml:190:
ReferenceError: needsSave is not defined
[/code]
I still cannot add new panels or change the wallpaper. The 'Extra Items' in the
system tray are additional but not the main problem I think.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 389297] plasmashell does not show a panel and layout settings cannot be changed
https://bugs.kde.org/show_bug.cgi?id=389297 Stas changed: What|Removed |Added Version|5.11.5 |5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389297] plasmashell does not show a panel and layout settings cannot be changed
https://bugs.kde.org/show_bug.cgi?id=389297 Stas changed: What|Removed |Added Summary|Networkmanager aswell as|plasmashell does not show a |other system items (volume) |panel and layout settings |not shown in the system |cannot be changed |tray| -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 Stas changed: What|Removed |Added CC||stas.kaz...@googlemail.com --- Comment #9 from Stas --- What is the state of this bug? Could someone at least state if this will be resolved soon. Very annoying bug and the only one which makes KOrganizer unusable for me. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 389297] New: Networkmanager aswell as other system items (volume) not shown in the system tray
https://bugs.kde.org/show_bug.cgi?id=389297 Bug ID: 389297 Summary: Networkmanager aswell as other system items (volume) not shown in the system tray Product: plasma-nm Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: stas.kaz...@googlemail.com Target Milestone: --- Hello, I have updated my plasma desktop packages to 5.11.5 yesterday from arch linux repositories and now in the system tray everything except "non system" trays like telegram or thunderbird is gone. So, I have not networkmanager, no volume control, no notifications, no device manager and so on. However, each of then is now available as a separate widget for the panel. Since I have not found the right place for a question about system tray as such, maybe someone here knows the answer: is it a bug (how to fix) or a design change. In the second case, how can I then d let them hide until they are needed, like the device tray shows up only if I plug in e.g. a USB stick into the computer. And you can forward this question further to the right forum if you like. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389297] Networkmanager aswell as other system items (volume) not shown in the system tray
https://bugs.kde.org/show_bug.cgi?id=389297 --- Comment #1 from Stas --- A short addition: the "extra items" list in system tray settings is empty. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389297] Networkmanager aswell as other system items (volume) not shown in the system tray
https://bugs.kde.org/show_bug.cgi?id=389297 --- Comment #3 from Stas --- Created attachment 110113 --> https://bugs.kde.org/attachment.cgi?id=110113&action=edit Screenshot. Settings get stucked in this view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389297] Networkmanager aswell as other system items (volume) not shown in the system tray
https://bugs.kde.org/show_bug.cgi?id=389297 --- Comment #4 from Stas --- Yes, the same happens for a new user. Even more: I cannot change anything in system tray settings. I get stuck with the window attached above and with the message: "Layout changes must be applied before other changes can be made." I cannot switch to other menu entries nor does anything happen by pressing "Apply". Maybe this is a hint about what is going wrong here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389297] Networkmanager aswell as other system items (volume) not shown in the system tray
https://bugs.kde.org/show_bug.cgi?id=389297 --- Comment #5 from Stas --- Here the same behavior is described: https://forums.opensuse.org/showthread.php/529253-Configure-Desktop-seems-not-to-work-now So at least I am not the only one and it is a wider issue than just system tray. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 387024] New: manually update live preview and separate it from editor
https://bugs.kde.org/show_bug.cgi?id=387024 Bug ID: 387024 Summary: manually update live preview and separate it from editor Product: kile Version: 2.9.91 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: stas.kaz...@googlemail.com Target Milestone: --- 1. It would be great to have an option to update live preview only manually but still show it all the time. While writing I often save my document after each sentence (just to be sure everything is saved when a crash happens, it is an old automatic behavior ;) ) but I do not want to compile my live preview each time I save a document. Often it is even a bad idea to compile after saving only one file (e. g. when I have a text file where I need a new command which I want to declare in the preamble). So adding a shortcut or a button for live preview while disable it on saving would be rely convenient. 2. It is related to the first part. How about make a temporary copy of the actual project and compile from that. In this way one could save a file and continue typing while the live preview will update to the saved version. For now the live preview just breaks when a file is modified while compiling. This feature could also solve the first problem I mentioned. Thanks for such great software. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 387024] manually update live preview and separate it from editor
https://bugs.kde.org/show_bug.cgi?id=387024 --- Comment #2 from Stas --- Hello, thank you for the suggestion. However, this is not the same thing, as in case of normal compilation I loose the synchronization between source and preview. I want the preview to synchronize the position in the code and vice versa. To the save statement. The save for back-up is not the only issue. I often define new commands and they are in an extra mycommands.tex file. Now, when the live preview is enabled when I switch from the mycommands.tex file back to the text file, everything gets saved and the compilation of the live preview starts. But there is no need for me to update the preview as I have only added a commands without actually changing the real text. So I start to type in the text.tex file and the compilation breaks up Giving me some errors as output. Sometimes after such an error I have to run the live preview twice in order to have the preview compiled. You see, there is more than just "saving" behind this wishlist. I I can imagine that implementing this feature would not be a big deal as the functionality already exists and only a b´new button with a command has to be created. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373345] New: After return from preview view the album view scroll the selected image to the top
https://bugs.kde.org/show_bug.cgi?id=373345 Bug ID: 373345 Summary: After return from preview view the album view scroll the selected image to the top Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: AlbumsView Assignee: digikam-de...@kde.org Reporter: stas.kaz...@googlemail.com Target Milestone: --- Hello, the following issue is very uncomfortable. After I select a picture in the album view and look at it in the preview and then go back to the album view, the album view scrolls in such a way, that the selected picture is in the first top line. However, it is preferable that the album view stays as it was before the preview. Otherwise I have no overview over how many pictures were scrolled and whether I have to go back to look at them, e.g., when choosing the photos for print from a large amount I usually scroll in the album view and when I see a possible choice I quickly go to preview to see it. Afterwards I want to return to the same point, as I was before... I cannot say, whether it is a new behaviour or not but certainly I have mentioned it in the actual version. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373345] After return from preview view the album view scrolls the selected image to the top
https://bugs.kde.org/show_bug.cgi?id=373345 Stas changed: What|Removed |Added Summary|After return from preview |After return from preview |view the album view scroll |view the album view scrolls |the selected image to the |the selected image to the |top |top -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373345] After return from preview view the album view scrolls the selected image to the top
https://bugs.kde.org/show_bug.cgi?id=373345 --- Comment #2 from Stas --- Yes, it is still present in the 5.4.0 appimage version. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373345] After return from preview view the album view scrolls the selected image to the top
https://bugs.kde.org/show_bug.cgi?id=373345 --- Comment #5 from Stas --- I am at Arch Linux and use the actual plasma framework (KDE5). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384917] New: Focus in face text field after adding a face manually should NOT affect Arrow Up and Down function
https://bugs.kde.org/show_bug.cgi?id=384917 Bug ID: 384917 Summary: Focus in face text field after adding a face manually should NOT affect Arrow Up and Down function Product: digikam Version: 5.7.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: stas.kaz...@googlemail.com Target Milestone: --- Hello, I recently updated to 5.7.0 and now an old bug comes up again. It was discussed here: https://bugs.kde.org/show_bug.cgi?id=351866 and the contrarily behavior was discussed here: https://bugs.kde.org/show_bug.cgi?id=345184 Let me summarize: 1. I add a new face rectangle and the focus highlights the word "Unknown". 2. After this I cannot navigate through the view. Nether with Right and Left nor with Up and Down keys. 3. I have to manually deselect the text field to go to the next picture. In 5.6.0 Right and Left where not working but at least Up and Down keys kept their functionality. Please make this behavior optional and let the user decide. You can even find a patch in https://bugs.kde.org/show_bug.cgi?id=351866 I need this because of my workflow: first assign face regions to all faces and then select all faces from one person and tag them. I just don't work out, when I cannot navigate through the pictures quickly. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 384123] New: Default Syntax Highlighting with custom XML file with higher priority not working
https://bugs.kde.org/show_bug.cgi?id=384123 Bug ID: 384123 Summary: Default Syntax Highlighting with custom XML file with higher priority not working Product: kile Version: 2.9.60 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: editor Assignee: michel.lud...@kdemail.net Reporter: stas.kaz...@googlemail.com Target Milestone: --- Hello, I have a custom XML file located at ~/.local/share/org.kde.syntax-highlighting/syntax/ This file has a higher priority for .tex files than the default one an should be chosen for highlighting .tex files by default when open new files. This behavior is correctly performed by kate on my system. All .tex file choose my XML file for highlighting when I open them. However, kile does not. It always chooses the default settings and not my custom ones. I can switch to my highlighting scheme manually but this has to be done for each file separately which can be very annoying for a larger project. Can someone look into that, please. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 --- Comment #9 from Stas Egorov --- (In reply to Andreas Sturmlechner from comment #8) > Please test with 21.08.1. There is no difference in behavior from previous versions. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544
--- Comment #5 from Stas Egorov ---
(In reply to Nikos Chantziaras from comment #4)
> I have the same issue with 21.08.0. I downgraded yakuake to 21.04.3 and it
> works fine again.
>
> [...]
>
> The commit that introduces the bug is
> 9202df97322ae2f58104e387e914de15b06644ff ("Fix Yakuake icon appearing in
> taskbar through Qt::Tool window flag").
But I wrote this bugreport in April, and the commit you mentioned was added in
May.
--
You are receiving this mail because:
You are watching all bug changes.
[yakuake] [Bug 435542] Show button in taskbar
https://bugs.kde.org/show_bug.cgi?id=435542 Stas Egorov changed: What|Removed |Added Version|3.0.5 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435542] Show button in taskbar
https://bugs.kde.org/show_bug.cgi?id=435542 Stas Egorov changed: What|Removed |Added URL||https://invent.kde.org/util ||ities/yakuake/-/issues/3 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] New: Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 Bug ID: 435544 Summary: Application focus issue Product: yakuake Version: 3.0.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: obiw...@vivaldi.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open Yakuake console 2. Switch to any other application 3. Minimize this application 4. Try to input any text OBSERVED RESULT No text is entered into the Yakuake window EXPECTED RESULT The text must be entered into the Yakuake window. Upon closer inspection, it turns out that the Yakuake window is out of focus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux with latest updates KDE Plasma Version: - KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Sometimes Yakuake stays in the foreground even if another window is in focus. Because of this, when you enter a command into the console, it is entered into the window that is in the background. This is very confusing. At the same time, of course, the checkbox "always stay at the top" is removed. I have it reproduced in 100% of cases when opening/minimizing another window from the system tray if Yakuake was opened before. I use Xfwm & LXQt environment, maybe this is the case? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 Stas Egorov changed: What|Removed |Added URL||https://invent.kde.org/util ||ities/yakuake/-/issues/2 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 --- Comment #13 from Stas Egorov --- It looks like the behavior depends on the window manager. On Xfwm and KWin this bug is reproducible. Not reproduce on Openbox. That being said, I'm using lxqt as my desktop environment. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 --- Comment #3 from Stas Egorov --- X11 WM is Xfwm 4.16 Compose extension is disabled -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 418756] New: MAP_FIXED_NOREPLACE mmap flag unsupported
https://bugs.kde.org/show_bug.cgi?id=418756 Bug ID: 418756 Summary: MAP_FIXED_NOREPLACE mmap flag unsupported Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: st...@yandex.ru Target Milestone: --- SUMMARY valgrind doesn't support MAP_FIXED_NOREPLACE mmap flag, causing the programs that use it, to misbehave. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] New: uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 Bug ID: 398445 Summary: uninitialized memory false reports on shared memory Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: s...@list.ru Target Milestone: --- Created attachment 114868 --> https://bugs.kde.org/attachment.cgi?id=114868&action=edit test case Hello. The attached test-case demonstrates the problem. It creates 2 pages of shared memory, uninitializes one page and initializes another. Even though both pages contain valid values, valgrind doesn't understand shared memory and reports an error. I have the program that uses shared memory a lot, and gets hundreds of false errors from valgrind. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 Stas Sergeev changed: What|Removed |Added Version|unspecified |3.13.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #2 from Stas Sergeev --- Created attachment 114889 --> https://bugs.kde.org/attachment.cgi?id=114889&action=edit 2-process test-case Hi, thanks for your reply. Here is the test-case that does the same thing but with 2 processes scheme. Same valgrind error. While the first test-case represents my real program more, I really see no difference. As for the difficulty of fixing this - yes, I perfectly understand it. While I can think of some ugly work-arounds (like, for example, checking if the values have changed, and consider them initialized in that case), nothing good can probably be done. How about downgrading the error to warning if it comes from the shared mem? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #4 from Stas Sergeev --- Created attachment 114906 --> https://bugs.kde.org/attachment.cgi?id=114906&action=edit 2 processes and VALGRIND_MAKE_MEM_DEFINED (In reply to Philippe Waroquiers from comment #3) > It is not very clear to me what is the reason > to map twice the same file. Mapping file twice may not be needed, but mapping shared memory twice (which is what my test-case does) allows you to create the mem aliases with different access rights. Consider writing the JIT. I am sure you, as a valgrind developer, write JIT every day actually. :) To trap self-modified code, you would execute the JITted code in PROT_EXEC window (no PROT_WRITE), and the JIT itself will access it via PROT_READ|PROT_WRITE window (very rough picture, it functions differently of course, but multiple windows with different perms are needed). But I would suggest to forget this exotic case and assume I use 2 processes as my second test-case does. This is because I simply don't see any difference. If you explain me why 2 processes+shmem are safe, I guess I'll deal with the rest on my own. Since valgrind doesn't know how the actions on shmem in one process affects another, it just exactly the same way doesn't know how writes within a single process can affect another mem window in the same process. > At my work, we are using shared memory between > several processes. We just declare the shared memory > as initialised just after mmap. See my next test-case where I did exactly that. I don't think it was needed, as AFAIK mmap()ed memory is always zeroed and valgrind knows this already, but I did that to follow your suggestion. > There is no concept of 'undefined error' and 'undefined warning', > and introducing this distinction seems not too desirable > (e.g. impact on suppression files, etc). Then you should at least document the possible sources of false-positives, including this one. I spent many hours trying to understand what valgrind is up to. A very long route was passed to track things back to the shared memory use (--track-origins just points to the stack allocation that didn't give me any clue). If that would have been documented, I would immediately understand that I hit exactly that case. > or disable error reporting for the mmap-ed address > range using > VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE Thanks. If nothing else, I can do that. But since I don't want to deal with valgrind instrumentation headers, I can as well add an extra initializers just to silence down the errors. So basically I _will_ find the ways to silence down the errors, but getting things improved (or at least documented) on valgrind side would be a good result after my many-hours research of those false-positives. :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #5 from Stas Sergeev --- Think of the following use-case. Consider a very silly shm IPC that uses just one large struct with many input and output fields. Client fills in the output fields and copies the entire struct to the shm buffer. Server reads it, fills in the input fields and puts it back to shm. Client reads the struct back with all fields now properly initialized. valgrind in this scenario would still think some fields are uninitialized because it can't understand that server have already replaced the entire content in this buffer. This is what my test-case is trying to demonstrate. It doesn't matter whether the server is in the same process or another, as valgrind will behave the same way in both cases. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #8 from Stas Sergeev --- (In reply to Philippe Waroquiers from comment #7) > If mmap would necessarily zero out memory, then > that would create major difficulties to use > shared memory. > I think that what the kernel guarantees is that > the first process that creates new memory > with mmap gets zero-ed memory Yes but I don't think valgrind knows if this shm page is mapped first time or N-th time. It simply doesn't have such info, unless I am missing something obvious. So it should probably assume the memory is initialized. Or does it check if the mapping is MAP_SHARED and assumes uninitialized only in that case? In either case, my latest test-case does mmap() then VALGRIND_MAKE_MEM_DEFINED() then fork(). No second mapping any more. > Initialising yourself the memory via one ptr > but accessing it via another mapping > is not the same as declaring the memory > defined after *each* mmap. > In the first case, valgrind can just detect that > the memory at ptr1 address is initialised, > but it cannot see this initialisation via > the second mapping. Well, my last test-case does only one mmap() and then fork(). So even if I think hard I don't see how can I satisfy your current suggestion. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #9 from Stas Sergeev --- (In reply to Ivo Raisr from comment #6) > Yes, indeed. That's why we have syscall and ioctl wrappers in Valgrind. > They describe what the other side (kernel) expects from the buffers sent > there > and in what shape they come back with buffers received. > > It should be quite easy to extend this mechanism to an arbitrary > client-server protocol, be it via shm, sockets or any other IPC. I don't see a big use of it. Unlike the kernel ioctls, in this case users will have to create these protocol wrappers on their own for every prog. I don't think too many people would be interested in doing so. I think the mission of valgrind is to make it easier for the people to track the source of the problem. As in this case the source of the problem is valgrind itself, I think the adequate help for people would be the proper documentation. It will allow them to track the problems to valgrind instead of poking their own code in vain. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #11 from Stas Sergeev --- (In reply to Philippe Waroquiers from comment #10) > If you declare the memory initialised before forking, > using VALGRIND_MAKE_MEM_DEFINED() ... which is what my latest test-case already does. Please suggest how to improve the test-case. > But in any case, as you suggested, we should > improve the doc to mention the multi-mapping. > > Any suggestion where to put this information ? > (or asked otherwise, where did you search in > the doc ?) In google, of course. :) "valgrind memcheck false positives" or "valgrind uninitialized false positives" etc. google will find it in a wiki or in off-line docs, so whatever place you prefer, is only a question of the valgrind-established practices. google will find it anywhere. Since valgrind knows that the error comes from the shared mem, it can print more description itself, referring to the docs. In this case the user will certainly not miss it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #13 from Stas Sergeev --- Will it help to print an additional warning when the uninitialized mem is copied to the shared region? The chances are very high this will result in a false-positives later, so maybe catching it at that stage would be better? If such warning is printed, valgrind may just consider them initialized from now on, to avoid the false-positive error later. What do you think about such strategy? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #15 from Stas Sergeev --- (In reply to Philippe Waroquiers from comment #14) > So, IMO, the easiest is to use the client requests Which ones? I did all the modifications you asked for, they all in my latest test-case. > (the downside of this is that this implies modification of the code). No, that downside is that you didn't suggest any further modifications. :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #17 from Stas Sergeev --- (In reply to Philippe Waroquiers from comment #16) > That might not be straightforward to do, in particular if you have > multiple threads (you probably need a critical section around the > write operations) or processes (this will even be more complex, as you > will probably need a side channel to inform all other processes about what > was done). Exactly, that's the point. You need a side-channel that also knows about the relationship between the pointers to shm in different processes - something only the kernel knows about normally (a bit simpler if shm is mapped before fork() - then the pointers are equal, but this is not always the case). Thant's why I think VALGRIND_MAKE_MEM_DEFINED doesn't actually work for this case, and yet you suggested it all along the way here (and I was updating the test-case) and also in the docs. So I think there is some mistake. This all seems to suggest it might be better to enable the errors from shm with some extra command-line switch, leaving it disabled by default... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392477] Cannot create new investment
https://bugs.kde.org/show_bug.cgi?id=392477 Stas Ashirov changed: What|Removed |Added CC||stas.ashi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385852] New: Okular ignored non-ascii characters in inline notes
https://bugs.kde.org/show_bug.cgi?id=385852 Bug ID: 385852 Summary: Okular ignored non-ascii characters in inline notes Product: okular Version: 1.1.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: stas-fo...@yandex.ru Target Milestone: --- Created attachment 108401 --> https://bugs.kde.org/attachment.cgi?id=108401&action=edit Screenshot of the problem Okular strips all non-ascii characters showing in inline notes. * Editing inline note — OK * Hanging note — OK * But when Okular shows this inline note — they stripped. See attachement. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
Stas changed:
What|Removed |Added
CC||administra...@mysmart.ie
--- Comment #125 from Stas ---
Hi,
I'm using Fedora 23 with plasma-desktop v.5.6.5 (current in repo) and this
issue consistently reproducing since upgrade to F23. From comments above it
seems plasma 5.7 does not resolve the problem in full, therefore i think it
worth to describe my use case too:
My setup is two monitors always connected to desktop. I want to have panel on
the bottom of each screen showing in task bar applications from the current
screen only. This is easy to configure. But every time when i [re]starting
desktop session i'm getting both panels placed on the left screen, one hidden
under another, so i have to move panel manually to proper screen edge manually
each time (which has additional difficulty because interface would randomly
consider mouse button depressed - usually when i moving panel between screens).
This is what i have in ~/.config/plasma-org.kde.plasma.desktop-appletsrc after
panels set properly:
[Containments][154]
activityId=
formfactor=2
immutability=1
lastScreen=1
location=4
plugin=org.kde.panel
wallpaperplugin=org.kde.image
[Containments][47]
activityId=
formfactor=2
immutability=1
lastScreen=0
location=4
plugin=org.kde.panel
wallpaperplugin=org.kde.image
After restarting session both entries lastScreen are set to value of 0.
I've tried approach discussed above - updated lastScreen manually (actually i
have saved proper config file and copied it over) and then did cycle "kquitapp5
plasmashell; /usr/bin/plasmashell &". But on some stage plasmashell have
updated lastScreen to 0 again!
The only difference was the lastScreen updated and lastReloadedMsJson field:
$ diff plasma-org.kde.plasma.desktop-appletsrc.20160703
plasma-org.kde.plasma.desktop-appletsrc
53c53
< lastScreen=1
---
> lastScreen=0
144c144
<
lastReloadedMsJson={"cache_5a5440a6c6026f3e61c6aee598cae8dc":1462710062827,"cache_761e1446448b87deea060bb141bf243a":1465518513510,"cache_014c0e783e7b5536bcb3099441062a3f":1467668406526}
---
> lastReloadedMsJson={"cache_5a5440a6c6026f3e61c6aee598cae8dc":1462710062827,"cache_761e1446448b87deea060bb141bf243a":1465518513510,"cache_014c0e783e7b5536bcb3099441062a3f":1467678325274}
OK, so i've copied it again and set R/O permissions on file: chmod a-w
plasma-org.kde.plasma.desktop-appletsrc
What could be simpler: now plasmashell does not update the
plasma-org.kde.plasma.desktop-appletsrc file and one of panels still having
lastScreen=1 set... But this didn't help to work around the issue and both
panels was palced on the left screen again!
And i even haven't found anywhere in the plasmashell 's output not writable
file error logged to at least let me match in which moment it was trying to
update it (it is tons of errors logged there, some of them are probably
relevant to this issue).
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 369060] New: Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar
https://bugs.kde.org/show_bug.cgi?id=369060 Bug ID: 369060 Summary: Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: stas.kaz...@googlemail.com CC: plasma-b...@kde.org Hello, I have noticed a strange behaviour. I do not use the group windows option in my taskbar. However, when I start some software and then open additional windows from this software, they do not appear as a new window but only the first task manager element remains. E.g. when I open digikam I get a new window "digikam" in the task manager. Then I open the import dialog. Normally a second window in the taskbar should appear. But It does not. Instead the "digikam" window now represent both windows. When hiding it, both get hided and so on. A second example is Rosegarden. There I have the main window. When I open the Track editor a new window should appear, but same thing as described above happens. This is very annoying and I cannot figure out what is going wrong. The titles of the windows are not the same. Would be great, when this could be fixed. Reproducible: Always Steps to Reproduce: 1. Open e.g. digikam 2. in digikam, open import dialog Actual Results: only one digikam window is in the taskbar Expected Results: For each window a separate window should be seen in the taskbar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369060] Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar
https://bugs.kde.org/show_bug.cgi?id=369060 Stas changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WONTFIX |--- --- Comment #2 from Stas --- But this behaviour was not presented in the mentioned software in KDE4. I cannot imagine, that this was an intended decision from both software developer teams at the same time. Anyway this windows are meant to be opened at the same time (at least for rosegarden, where this is a essential feature to open the track editor beside the main window). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369062] New: Task manager with the option "sort manually" initially sort new windows by application.
https://bugs.kde.org/show_bug.cgi?id=369062 Bug ID: 369062 Summary: Task manager with the option "sort manually" initially sort new windows by application. Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: stas.kaz...@googlemail.com CC: plasma-b...@kde.org When I use the "sort manually" option in the task manager an I open new windows, the get sorted by the application. This leads to confusion as they should appear as last elements in the taskbar. I open a new window and expect it to be the last one and not to be moved somewhere in between already opened windows. At least not with the "sort manually" option enabled. Reproducible: Always Steps to Reproduce: 1. Set task manager to sort the windows manually 2. Open a terminal 3. Open some other applications 4. Open a new terminal Actual Results: The terminal which was opened in step 4. is placed beside the first terminal window. Expected Results: The new terminal should be the last window in the taskbar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369060] Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar
https://bugs.kde.org/show_bug.cgi?id=369060 --- Comment #5 from Stas --- The mentioned windows were not modal ones in KDE4 where I was able e.g. to open the import dialog in digikam then start the download and return to the main window while the import dialog remains open. This cannot be done with modal windows as described in the article you have linked previously. Also now, with plasma 5, I still can switch between the different windows as I want except that only one taskbar window is shown for both windows... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369060] Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar
https://bugs.kde.org/show_bug.cgi?id=369060 --- Comment #6 from Stas --- (In reply to Eike Hein from comment #4) > Where do I find this Track Editor? Start a new rosegarden session, then create a track with the pencil tool in the main window (draw a yellow coloured strip. Then double -click on it. This will open the score editor (or track editor as I have called it before). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369060] Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar
https://bugs.kde.org/show_bug.cgi?id=369060 --- Comment #8 from Stas --- (In reply to Eike Hein from comment #7) > Created attachment 101178 [details] > Rosegarden Task Manager > > I get three Task Manager entries ... it's 5.8 code, but it hasn't changed > since 5.7.5 for this. Can you check it with ungrouped windows in the taskbar? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369062] Task manager with the option "sort manually" initially sort new windows by application.
https://bugs.kde.org/show_bug.cgi?id=369062 --- Comment #2 from Stas --- Ok, I cannot reproduce it now, too. I have changed the settings multiple times (cannot reproduce now in which order) and now this behaviour is gone... Strange. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369060] Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar
https://bugs.kde.org/show_bug.cgi?id=369060 --- Comment #10 from Stas --- Ok, but at least I am sure now, that it is not the apriori behaviour of the software. Can you imagine from where this behaviour can come? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369060] Some windows does not appear as a separate window but rather multiple windows are represented by one element in the taskbar
https://bugs.kde.org/show_bug.cgi?id=369060 --- Comment #12 from Stas --- Maybe we can wait for some other people to have a look at it, because it still happens to me permanently. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366897] New: detailed progress window cannot be hidden properly
https://bugs.kde.org/show_bug.cgi?id=366897 Bug ID: 366897 Summary: detailed progress window cannot be hidden properly Product: digikam Version: 5.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ProgressManager Assignee: digikam-de...@kde.org Reporter: stas.kaz...@googlemail.com Hello, when I assign labels to my photos every time the detailed progress window appears above at the right of the status bar. When the operation is long enough, I can hit the arrow to hide this details and they disappear into the status bar as a percentage bar. But the next time I start a new job (as assigning labels) the detailed view is back again. This bug was not present in 4.x versions. This is an annoying behaviour as it shows me information which are not important at this workflow stage. Would be nice, when it can be set permanently to hidden. Best option would be even a tickle in the settings. Thanks. Reproducible: Always Steps to Reproduce: 1. do an longer operation (e.g. assign labels to 30 photos) and hide the detailed progress view 2. do it for a second time Actual Results: the detailed progress window popups again Expected Results: the detailed progress window stays hidden -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 356775] Kile causes Dolphin to freeze
https://bugs.kde.org/show_bug.cgi?id=356775 Stas changed: What|Removed |Added CC||stas.kaz...@googlemail.com --- Comment #1 from Stas --- Hello, for me this bug also happens permanently on my Arch Linux system and is very annoying. Would be great if it could be fixed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359223] New: [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)
https://bugs.kde.org/show_bug.cgi?id=359223 Bug ID: 359223 Summary: [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin) Product: okular Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: stas.kaz...@googlemail.com Hello, I have updated my oukular-frameworks-git AUR package and now I have a problem, that I cannot ope pdf files which contain spaces in the path or name. It does not work from terminal aud from Dolphin. However, I can open those file from within okular with the open dialog. The Error I get is the following: QCommandLineParser: option not defined: "raise" So I think something is going wrong with the QT5 libraries and okular combination?! Would be nice, when you could have a look at that bug, okular is a program I use all the time ;) And thanks for the great job by the way. Reproducible: Always Steps to Reproduce: 1. Try to open pdf with spaces in name or path 2. "Could not open" - error -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359223] [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)
https://bugs.kde.org/show_bug.cgi?id=359223 --- Comment #1 from Stas --- Ok, just checked: the error occurs even when a pdf file is opened (contains no spaces) so it is not the relevant information. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359223] [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)
https://bugs.kde.org/show_bug.cgi?id=359223 Stas changed: What|Removed |Added CC||stas.kaz...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359223] [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)
https://bugs.kde.org/show_bug.cgi?id=359223 --- Comment #6 from Stas --- Hello, from AUR site I got this hint to patch the bug: https://git.reviewboard.kde.org/r/126192/ See the comments here: https://aur.archlinux.org/packages/okular-frameworks-git/ Would be great, if it could be fixed in the git branch... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 253657] missing some amd64 to let wine/amd64 run on valgrind/amd64
https://bugs.kde.org/show_bug.cgi?id=253657 --- Comment #16 from Stas Sergeev --- Created attachment 97737 --> https://bugs.kde.org/attachment.cgi?id=97737&action=edit a test case Sorry for delay. Here's the segregs test case. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361740] Disable warning "The document requested to be launched in presentation mode" on document reload
https://bugs.kde.org/show_bug.cgi?id=361740 Stas Fomin changed: What|Removed |Added Summary|Command line option to |Disable warning "The |disable presentation mode |document requested to be |and warning "The document |launched in presentation |requested to be launched in |mode" on document reload |presentation mode"" | --- Comment #2 from Stas Fomin --- OK. I will try to patch it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361740] Disable warning "The document requested to be launched in presentation mode" on document reload
https://bugs.kde.org/show_bug.cgi?id=361740 --- Comment #4 from Stas Fomin --- Yes, demo https://github.com/belonesox/demo-of-beamer-problem-for-okular- Need texlive/pdflatex. run demo.sh -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361740] Disable warning "The document requested to be launched in presentation mode" on document reload
https://bugs.kde.org/show_bug.cgi?id=361740 --- Comment #5 from Stas Fomin --- Full URL should be «https://github.com/belonesox/demo-of-beamer-problem-for-okular-», bugzilla did not hyperlink correctly in prev.comment. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361740] New: Command line option to disable presentation mode and warning "The document requested to be launched in presentation mode""
https://bugs.kde.org/show_bug.cgi?id=361740
Bug ID: 361740
Summary: Command line option to disable presentation mode and
warning "The document requested to be launched in
presentation mode""
Product: okular
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: stas-fo...@yandex.ru
When using Okular as previewer in PDFTex workflow, preparing beamer slides,
the following usability hell occured:
* LaTex/Beamer slides should be compiled to PDF with metadata "StartFullScreen"
* But while editing, on every PDF change/and reload, user got a modal popup
"The document requested to be launched in presentation mode." "Do you
want to allow it?"
(See part.cpp)
* This make typical Slide/LaTeX/Beamer editing workflow completely unusable.
I see several options how to handle it.
* Should be commandline options ("--disablefullscreen" or like this), and
Okular launched from Kile with this option should ignore all this
"StartFullScreen" metadata.
* Global preference "Disable Presentation Mode". And if the OS is used to LaTex
editing workflow, the owner possible can swith Okular in Presentation Mode.
* Completelety disable this warning on reload of the changed document.
--
You are receiving this mail because:
You are watching all bug changes.
