[calligracommon] [Bug 402885] kdeinit5 PID: 4598 Signal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=402885 Danil changed: What|Removed |Added CC||dd.style2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402885] kdeinit5 PID: 102994 Signal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=402885 Danil changed: What|Removed |Added Product|calligracommon |plasmashell Assignee|calligra-bugs-n...@kde.org |k...@davidedmundson.co.uk Platform|Fedora RPMs |Archlinux Packages Summary|kdeinit5 PID: 4598 Signal: |kdeinit5 PID: 102994 |Segmentation fault (11) |Signal: Segmentation fault ||(11) CC||plasma-b...@kde.org Version|unspecified |5.21.3 Target Milestone|--- |1.0 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434575] New: crash of kdeinit ( kdeinit5 PID: 151153 Сигнал завершения: Segmentation fault (11))
https://bugs.kde.org/show_bug.cgi?id=434575 Bug ID: 434575 Summary: crash of kdeinit ( kdeinit5 PID: 151153 Сигнал завершения: Segmentation fault (11)) Product: plasmashell Version: 5.21.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dd.style2...@gmail.com Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. open flameshot gui 2. copy the screenshot OBSERVED RESULT notify with crashing of kdeinit5 with segmentation fault EXPECTED RESULT nothing SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux 5.11.6-zen1-1-zen (available in About System) KDE Plasma Version: Plasma 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434575] crash of kdeinit ( kdeinit5 PID: 151153 Сигнал завершения: Segmentation fault (11))
https://bugs.kde.org/show_bug.cgi?id=434575 --- Comment #1 from Danil --- (In reply to Danil from comment #0) > SUMMARY > > > STEPS TO REPRODUCE > 1. open flameshot gui > 2. copy the screenshot > > OBSERVED RESULT > notify with crashing of kdeinit5 with segmentation fault > > EXPECTED RESULT > nothing > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Arch Linux 5.11.6-zen1-1-zen > (available in About System) > KDE Plasma Version: Plasma 5.21.3 > KDE Frameworks Version: 5.80.0 > Qt Version: 5.15.2 Flameshot version v0.9.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434575] crash of kdeinit ( kdeinit5 PID: 151153 Сигнал завершения: Segmentation fault (11))
https://bugs.kde.org/show_bug.cgi?id=434575 --- Comment #2 from Danil --- Crash on X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434575] crash of kdeinit ( kdeinit5 PID: 151153 Сигнал завершения: Segmentation fault (11))
https://bugs.kde.org/show_bug.cgi?id=434575 --- Comment #3 from Danil --- (In reply to Danil from comment #0) > SUMMARY > > > STEPS TO REPRODUCE > 1. open flameshot gui > 2. copy the screenshot > > OBSERVED RESULT > notify with crashing of kdeinit5 with segmentation fault > > EXPECTED RESULT > nothing > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Arch Linux 5.11.6-zen1-1-zen > (available in About System) > KDE Plasma Version: Plasma 5.21.3 > KDE Frameworks Version: 5.80.0 > Qt Version: 5.15.2 2. save the screenshot* -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 387413] Error when trying to apply diff
https://bugs.kde.org/show_bug.cgi?id=387413 --- Comment #2 from Danil --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! I can reproduce the issue with Kompare version 4.1.3 on Ubuntu version 16.04 (Kompare 4.1.3 does not have this issue on Ubuntu version 20.04) -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 387413] New: Error when trying to apply diff
https://bugs.kde.org/show_bug.cgi?id=387413 Bug ID: 387413 Summary: Error when trying to apply diff Product: kompare Version: 4.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: da...@luckyteam.co.uk Target Milestone: --- Issue: When comparing two files and trying to apply difference, an error occurs. Reproducible: Always Kompare version: 4.1.3 Ubuntu version: 16.04 Example: kompare /path_to_file_1 /path_to_file_2 An error message: Could not upload the temporary file to the destination location file://path_to_file_2. The temporary file is still available under: /tmp/kompare.n21119. You can manually copy it to the right place. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 359081] Error when comparing the two files and trying to save them
https://bugs.kde.org/show_bug.cgi?id=359081 Danil changed: What|Removed |Added CC||da...@luckyteam.co.uk --- Comment #2 from Danil --- I get the same error on Ubuntu 16.04 with Kompare 4.1.3 https://bugs.kde.org/show_bug.cgi?id=387413 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 426638] New: Wrong desktop render after session startup on xorg
https://bugs.kde.org/show_bug.cgi?id=426638 Bug ID: 426638 Summary: Wrong desktop render after session startup on xorg Product: KScreen Version: 5.19.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: chdanil...@gmail.com Target Milestone: --- Created attachment 131721 --> https://bugs.kde.org/attachment.cgi?id=131721&action=edit observed result SUMMARY Wrong desktop render after session startup on xorg STEPS TO REPRODUCE 1. Enable second display in kscreen 2. Shutdown session and login again 3. Wait till desktop loads OBSERVED RESULT *in attachments* EXPECTED RESULT Desktop and task panel renders normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux (5.8.9-zen2-1-zen) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Mesa: 20.1.7 ADDITIONAL INFORMATION Bug appeared after packages update (pacman -Syu). Bug not present with wayland session. Only with xorg. WORKGROUND Disable and enable again second display in kscreen after session login (works till session shutdown) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 299155] File ACLs don't update after changing them and reopening properties
https://bugs.kde.org/show_bug.cgi?id=299155 Danil Shein changed: What|Removed |Added CC||dsh...@altlinux.org --- Comment #7 from Danil Shein --- Still an issue in KDE Frameworks 5.70.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 299155] File ACLs don't update after changing them and reopening properties
https://bugs.kde.org/show_bug.cgi?id=299155
--- Comment #8 from Danil Shein ---
(In reply to Danil Shein from comment #7)
> Still an issue in KDE Frameworks 5.70.0
One suggestion about root cause from my experience with KPropertiesDialog
source code:
As far as I cold understand KPropertiesDialog receives KFileItem or
KFileItemList instance as input.
All ACLs related data is stored in and managed through related KFileItem
UDSEntry.
It looks like when you've reopen file properties dialog again after ACL changes
applied it is receive an KFileItem without appropriate UDSEntry and displays
ACL as inherited from regular UNIX permissions.
Can't say where and why it actually happens.
My suggestion is based on experience playing around with code:
path = "/home/dshein/src/tmp/1/2/share/1.txt";
KFileItem kfitem(QUrl::fromLocalFile(path));
KPropertiesDialog kpd(QString("File properties"), 0);
kpd.showDialog(kfitem, 0);
kpd.showDialog(QUrl::fromLocalFile(path), 0);
kpd.showDialog(kfitem, 0);
kpd.showDialog(QUrl::fromLocalFile(path), 0);
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 299155] File ACLs don't update after changing them and reopening properties
https://bugs.kde.org/show_bug.cgi?id=299155
--- Comment #9 from Danil Shein ---
(In reply to Danil Shein from comment #7)
> Still an issue in KDE Frameworks 5.70.0
One suggestion about root cause from my experience with KPropertiesDialog
source code:
As far as I cold understand KPropertiesDialog receives KFileItem or
KFileItemList instance as input.
All ACLs related data is stored in and managed through related KFileItem
UDSEntry.
It looks like when you've reopen file properties dialog again after ACL changes
applied it is receive an KFileItem without appropriate UDSEntry and displays
ACL as inherited from regular UNIX permissions.
Can't say where and why it actually happens.
My suggestion is based on experience playing around with code:
path = "/home/test/1.txt"; // file with ACL
KFileItem kfitem(QUrl::fromLocalFile(path));
KPropertiesDialog kpd(QString("File properties"), 0);
kpd.showDialog(kfitem, 0); // always display ACLs inherited from regular
permissions (incorrect)
kpd.showDialog(QUrl::fromLocalFile(path), 0); // always display consistent
file ACls
auto job = KIO::stat(url);
job->exec();
KIO::UDSEntry entry = job->statResult();
kfitem = KFileItem(entry, url);
kpd.showDialog(kfitem, 0); // display consistent file ACls
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 414149] New: Ark crash on close while loading archive
https://bugs.kde.org/show_bug.cgi?id=414149 Bug ID: 414149 Summary: Ark crash on close while loading archive Product: ark Version: 19.08.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: ddramb...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- Application: ark (19.08.2) (Compiled from sources) Qt Version: 5.12.5 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-gentoo-r1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: 1. Open large archive 2. Simply close app while archive is loading App running on gentoo, apps built with use flags: 1. ark "bzip2 lzma zip" 2. qtcore "icu systemd" 3. qtgui "dbus egl gif jpeg libinput png udev xcb" 4. plasma-desktop "fontconfig mouse semantic-desktop" The crash can be reproduced sometimes. -- Backtrace: Application: Ark (ark), signal: Segmentation fault (lldb) process attach --pid 3086 Process 3086 stopped * thread #1, name = 'ark', stop reason = signal SIGSTOP frame #0: 0x7f36adc8b7f3 libc.so.6`__poll + 115 libc.so.6`__poll: -> 0x7f36adc8b7f3 <+115>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36adc8b7f9 <+121>: ja 0x7f36adc8b823; <+163> 0x7f36adc8b7fb <+123>: movl %r8d, %edi 0x7f36adc8b7fe <+126>: movl %eax, 0x8(%rsp) thread #2, name = 'QXcbEventQueue', stop reason = signal SIGSTOP frame #0: 0x7f36adc8b7f3 libc.so.6`__poll + 115 libc.so.6`__poll: -> 0x7f36adc8b7f3 <+115>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36adc8b7f9 <+121>: ja 0x7f36adc8b823; <+163> 0x7f36adc8b7fb <+123>: movl %r8d, %edi 0x7f36adc8b7fe <+126>: movl %eax, 0x8(%rsp) thread #3, name = 'ark:cs0', stop reason = signal SIGSTOP frame #0: 0x7f36ad206ee5 libpthread.so.0`__pthread_cond_wait + 485 libpthread.so.0`__pthread_cond_wait: -> 0x7f36ad206ee5 <+485>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36ad206eeb <+491>: ja 0x7f36ad206f50; <+592> 0x7f36ad206eed <+493>: movl %r9d, %edi 0x7f36ad206ef0 <+496>: callq 0x7f36ad20ac30; __pthread_disable_asynccancel thread #4, name = 'ark:disk$0', stop reason = signal SIGSTOP frame #0: 0x7f36ad206ee5 libpthread.so.0`__pthread_cond_wait + 485 libpthread.so.0`__pthread_cond_wait: -> 0x7f36ad206ee5 <+485>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36ad206eeb <+491>: ja 0x7f36ad206f50; <+592> 0x7f36ad206eed <+493>: movl %r9d, %edi 0x7f36ad206ef0 <+496>: callq 0x7f36ad20ac30; __pthread_disable_asynccancel thread #5, name = 'ark:sh0', stop reason = signal SIGSTOP frame #0: 0x7f36ad206ee5 libpthread.so.0`__pthread_cond_wait + 485 libpthread.so.0`__pthread_cond_wait: -> 0x7f36ad206ee5 <+485>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36ad206eeb <+491>: ja 0x7f36ad206f50; <+592> 0x7f36ad206eed <+493>: movl %r9d, %edi 0x7f36ad206ef0 <+496>: callq 0x7f36ad20ac30; __pthread_disable_asynccancel thread #6, name = 'ark:sh1', stop reason = signal SIGSTOP frame #0: 0x7f36ad206ee5 libpthread.so.0`__pthread_cond_wait + 485 libpthread.so.0`__pthread_cond_wait: -> 0x7f36ad206ee5 <+485>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36ad206eeb <+491>: ja 0x7f36ad206f50; <+592> 0x7f36ad206eed <+493>: movl %r9d, %edi 0x7f36ad206ef0 <+496>: callq 0x7f36ad20ac30; __pthread_disable_asynccancel thread #7, name = 'ark:sh2', stop reason = signal SIGSTOP frame #0: 0x7f36ad206ee5 libpthread.so.0`__pthread_cond_wait + 485 libpthread.so.0`__pthread_cond_wait: -> 0x7f36ad206ee5 <+485>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36ad206eeb <+491>: ja 0x7f36ad206f50; <+592> 0x7f36ad206eed <+493>: movl %r9d, %edi 0x7f36ad206ef0 <+496>: callq 0x7f36ad20ac30; __pthread_disable_asynccancel thread #8, name = 'ark:shlo0', stop reason = signal SIGSTOP frame #0: 0x7f36ad206ee5 libpthread.so.0`__pthread_cond_wait + 485 libpthread.so.0`__pthread_cond_wait: -> 0x7f36ad206ee5 <+485>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36ad206eeb <+491>: ja 0x7f36ad206f50; <+592> 0x7f36ad206eed <+493>: movl %r9d, %edi 0x7f36ad206ef0 <+496>: callq 0x7f36ad20ac30; __pthread_disable_asynccancel thread #9, name = 'ark:shlo1', stop reason = signal SIGSTOP frame #0: 0x7f36ad206ee5 libpthread.so.0`__pthread_cond_wait + 485 libpthread.so.0`__pthread_cond_wait: -> 0x7f36ad206ee5 <+485>: cmpq $-0x1000, %rax; imm = 0xF000 0x7f36ad206eeb <+491>: ja
[kdeconnect] [Bug 493417] New: Kde Connect runs in the background and appears in the "Check background activity" menu.
https://bugs.kde.org/show_bug.cgi?id=493417 Bug ID: 493417 Summary: Kde Connect runs in the background and appears in the "Check background activity" menu. Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 14.x Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: pisklov-da...@outlook.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Created attachment 173924 --> https://bugs.kde.org/attachment.cgi?id=173924&action=edit The check background activity menu on Samsung One UI 6 (Android 14). The program does not stop being displayed in the menu "Check background activity" and continues to be an eyesore with the display that "I have some application running on my phone". If it was disconnected from another device and closed, but the process was running in normal mode. If it is possible to disable the display of background activity like in F-Droid or other applications? Thanks, Dan. -- You are receiving this mail because: You are watching all bug changes.
