[kwin] [Bug 482903] Separate screen focus not working
https://bugs.kde.org/show_bug.cgi?id=482903 --- Comment #9 from Emanuele --- > I'm sorry, my previous comment (#3) was incorrect: the line you should add > is ActiveMouseScreen=false, not true (and make sure the A is capitalised). I > just retested it after toggling this to true (doesn't work) then false again > (which works). I also confirm, with ActiveMouseScreen=false it works! Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482903] Separate screen focus not working
https://bugs.kde.org/show_bug.cgi?id=482903 --- Comment #6 from Emanuele --- (In reply to Muthanna from comment #5) > (In reply to Emanuele from comment #4) > > I have tried to add the key activeMouseScreen=true in the section [Windows] > > of file ~/.config/kwinrc and restart...without luck. > > Make sure both SeparateScreenFocus and activeMouseScreen are set to true. https://ibb.co/jzcW9Q3 Sorry, I don't know how to post (if it's allowed) image...I have set both keys (see image). Anyway, it's not a problem, I'll wait the fix of the bug...It's not too important one for me. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482903] Separate screen focus not working
https://bugs.kde.org/show_bug.cgi?id=482903 --- Comment #4 from Emanuele --- I have tried to add the key activeMouseScreen=true in the section [Windows] of file ~/.config/kwinrc and restart...without luck. Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482903] Separate screen focus not working
https://bugs.kde.org/show_bug.cgi?id=482903 Emanuele changed: What|Removed |Added CC||m1f5o...@duck.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 479997] New: Segmentation fault on 32bit arm checking programs built with -fstack-clash-protection or -fstack-check
https://bugs.kde.org/show_bug.cgi?id=479997
Bug ID: 479997
Summary: Segmentation fault on 32bit arm checking programs
built with -fstack-clash-protection or -fstack-check
Classification: Developer tools
Product: valgrind
Version: 3.20.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: e...@debian.org
Target Milestone: ---
Hi,
I found a small reproducer for the segmentation fault mentioned in
https://bugs.kde.org/show_bug.cgi?id=479699.
Please note that the error can be reproduced with either
-fstack-clash-protection or -fstack-check. This issue is similar to
https://bugs.kde.org/show_bug.cgi?id=479996 - but you need a larger buffer on
64 bit.
// example.c
void a_function() { char buf[8192]; }
int main() { a_function(); }
gcc -fstack-clash-protection example.c -o example && valgrind ./example
==2743356== Memcheck, a memory error detector
==2743356== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==2743356== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==2743356== Command: ./example
==2743356==
==2743356==
==2743356== Process terminating with default action of signal 11 (SIGSEGV)
==2743356== Access not within mapped region at address 0xFEF0CB04
==2743356==at 0x1084EA: a_function (in /tmp/example)
==2743356== If you believe this happened as a result of a stack
==2743356== overflow in your program's main thread (unlikely but
==2743356== possible), you can try to increase the size of the
==2743356== main thread stack using the --main-stacksize= flag.
==2743356== The main thread stack size used in this run was 8388608.
==2743356==
==2743356== HEAP SUMMARY:
==2743356== in use at exit: 0 bytes in 0 blocks
==2743356== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==2743356==
==2743356== All heap blocks were freed -- no leaks are possible
==2743356==
==2743356== For lists of detected and suppressed errors, rerun with: -s
==2743356== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 3)
Segmentation fault
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 479996] New: Segmentation fault on aarch64 checking programs built with -fstack-check
https://bugs.kde.org/show_bug.cgi?id=479996
Bug ID: 479996
Summary: Segmentation fault on aarch64 checking programs built
with -fstack-check
Classification: Developer tools
Product: valgrind
Version: 3.20.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: e...@debian.org
Target Milestone: ---
Hi,
On aarch64, using valgrind on the following program built with -fstack-check
results in a segmentation fault:
// example.c
void a_function() { char buf[10752]; }
int main() { a_function(); }
gcc -fstack-check example.c -o example && valgrind ./example
==2743238== Memcheck, a memory error detector
==2743238== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==2743238== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==2743238== Command: ./example
==2743238==
==2743238== Invalid write of size 8
==2743238==at 0x10873C: main (in /tmp/example)
==2743238== Address 0x1ffefff9c0 is on thread 1's stack
==2743238== 4112 bytes below stack pointer
==2743238==
==2743238== Invalid write of size 8
==2743238==at 0x108718: a_function (in /tmp/example)
==2743238==by 0x10874B: main (in /tmp/example)
==2743238== Address 0x1ffeffe9c0 is on thread 1's stack
==2743238== 8192 bytes below stack pointer
==2743238==
==2743238== Invalid write of size 8
==2743238==at 0x108720: a_function (in /tmp/example)
==2743238==by 0x10874B: main (in /tmp/example)
==2743238== Address 0x1ffeffdfc0 is not stack'd, malloc'd or (recently) free'd
==2743238==
==2743238==
==2743238== Process terminating with default action of signal 11 (SIGSEGV)
==2743238== Access not within mapped region at address 0x1FFEFFDFC0
==2743238==at 0x108720: a_function (in /tmp/example)
==2743238==by 0x10874B: main (in /tmp/example)
==2743238== If you believe this happened as a result of a stack
==2743238== overflow in your program's main thread (unlikely but
==2743238== possible), you can try to increase the size of the
==2743238== main thread stack using the --main-stacksize= flag.
==2743238== The main thread stack size used in this run was 8388608.
==2743238==
==2743238== HEAP SUMMARY:
==2743238== in use at exit: 0 bytes in 0 blocks
==2743238== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==2743238==
==2743238== All heap blocks were freed -- no leaks are possible
==2743238==
==2743238== For lists of detected and suppressed errors, rerun with: -s
==2743238== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
Segmentation fault
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 479699] New: Add support for stack-clash-protection on 32bit Arm
https://bugs.kde.org/show_bug.cgi?id=479699 Bug ID: 479699 Summary: Add support for stack-clash-protection on 32bit Arm Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: e...@debian.org Target Milestone: --- Hi, The ARM Architecture Procedure Call Standard relaxed the limitations on memory accesses below the stack pointer in 2018Q4: | 6.2.1.3 Stack probing | In order to ensure stack integrity a process may emit stack probes immediately | prior to allocating additional stack space (moving SP from SP_old to SP_new). | Stack probes must be in the region of [SP_new, SP_old - 1] and may be either | read or write operations. The minimum interval for stack probing is defined by | the target platform but must be a minimum of 4KBytes. No recoverable data can | be saved below the currently allocated stack region. See https://github.com/ARM-software/abi-aa/blob/2a70c42d62e9c3eb5887fa50b71257f20daca6f9/aapcs32/aapcs32.rst#6213stack-probing Currently, valgrind considers all memory accesses below SP as errors, see for example: https://lists.debian.org/debian-arm/2023/12/msg2.html GCC implements the AAPCS rules when using stack-clash protection, so please consider updating valgrind accordingly. Additionally, valgrind may segfault when debugging programs built with stack-clash-protection turned on. For example: valgrind --track-origins=yes --leak-check=full apt-get update [...] ==3102620== Process terminating with default action of signal 11 (SIGSEGV) ==3102620== Access not within mapped region at address 0xFEDCBDAC ==3102620==at 0x49476E8: ReadMessages(int, std::vector, std::allocator >, std::allocator, std::allocator > > >&) (strutl.cc:888) See https://people.debian.org/~ema/valgrind-segfault-apt-get-update.log for full output. Disassembled code at https://people.debian.org/~ema/apt-scp-armhf.log. The memory location pointed at by r12 is out of the stack. Another example of valgrind segfaulting when checking programs built with stack-clash-protection on 32bit arm is at https://bugzilla.redhat.com/show_bug.cgi?id=1522678 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 473504] New: Invalid request when authenticating to GDrive
https://bugs.kde.org/show_bug.cgi?id=473504 Bug ID: 473504 Summary: Invalid request when authenticating to GDrive Classification: Applications Product: kipiplugins Version: 5.9.0 Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: imaging-bugs-n...@kde.org Reporter: efabri...@gmail.com Target Milestone: --- Created attachment 161045 --> https://bugs.kde.org/attachment.cgi?id=161045=edit Error returned from Google Sign-in SUMMARY *** >From Spectacle, when exporting a screenshot to GDrive, the browser opens correctly trying to authenticate the google account, but it fails with the following message: invalid_request Details are in the screenshot. *** STEPS TO REPRODUCE 1. Open Spectacle 2. Take a screenshot 3. Choose to "Export -> More Online Services -> Export to Google Drive..." OBSERVED RESULT The browser opens loading a URL from accounts.google.com and it responds with "invalid_request". EXPECTED RESULT The browser opens loading a URL from accounts.google.com and it presents the list of accounts to choose from. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Google directs the developer to use Out-Of-Band (OOB) flow Migration with information at this URL: https://developers.google.com/identity/protocols/oauth2/resources/oob-migration It seems that since February 16, 2022 the authentication method had to change. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466759] Systemsettings crashes while accessing window decoration section
https://bugs.kde.org/show_bug.cgi?id=466759 Emanuele Spirito changed: What|Removed |Added CC|emaster...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466759] Systemsettings crashes while accessing window decoration section
https://bugs.kde.org/show_bug.cgi?id=466759 --- Comment #2 from Emanuele Spirito --- After the update to plasma 5.27.1 the bugs doesn't come out anymore. Thanks for your support and suggestion -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466759] Systemsettings crashes while accessing window decoration section
https://bugs.kde.org/show_bug.cgi?id=466759 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466759] New: Systemsettings crashes while accessing window decoration section
https://bugs.kde.org/show_bug.cgi?id=466759 Bug ID: 466759 Summary: Systemsettings crashes while accessing window decoration section Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- Created attachment 156948 --> https://bugs.kde.org/attachment.cgi?id=156948=edit Drkonqui crash log SUMMARY I cannot open Window decoration settings because it crashes. Here there is the backtrace: Application: Impostazioni di sistema (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f5a816dfe84 in KDecoration2::Decoration::shadow() const () from /lib64/libkdecorations2.so.5 #5 0x7f5a8126ba55 in KDecoration2::Preview::PreviewItem::hoverLeaveEvent(QHoverEvent*) () from /usr/lib64/qt5/qml/org/kde/kwin/private/kdecoration/libkdecorationprivatedeclarative.so #6 0x7f5ac6a96c28 in QQuickItem::event(QEvent*) () from /lib64/libQt5Quick.so.5 #7 0x7f5ac95aed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7f5ac88a81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f5ac6aae267 in QQuickWindowPrivate::sendHoverEvent(QEvent::Type, QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool) () from /lib64/libQt5Quick.so.5 #10 0x7f5ac6aaf44b in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #11 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #12 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #13 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #14 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #15 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #16 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #17 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #18 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #19 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #20 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #21 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #22 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #23 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #24 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #25 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #26 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #27 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #28 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #29 0x7f5ac6aaead1 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&,
[systemsettings] [Bug 466474] Windows decoration changed since last update, can't change them due to immediate crash when trying to open the settings app
https://bugs.kde.org/show_bug.cgi?id=466474 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 466525] Kile crashed after having PDFLatex compiled
https://bugs.kde.org/show_bug.cgi?id=466525 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 466525] New: Kile crashed after having PDFLatex compiled
https://bugs.kde.org/show_bug.cgi?id=466525
Bug ID: 466525
Summary: Kile crashed after having PDFLatex compiled
Classification: Applications
Product: kile
Version: 2.9.93
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: michel.lud...@gmail.com
Reporter: emaster...@gmail.com
Target Milestone: ---
Created attachment 156789
--> https://bugs.kde.org/attachment.cgi?id=156789=edit
DrKonqui report
SUMMARY
After having compiled a long tex code with pdflatex, Kile crashed. I could
reproduce the crash just one time, soon after that, with the same file and
making the same edits.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 36
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.6
Kernel Version: 6.1.11-100.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 15 5501
ADDITIONAL INFORMATION
Application: Kile (kile), signal: Aborted
[KCrash Handler]
#4 0x7fd9b9a8ebec in __pthread_kill_implementation () from
/lib64/libc.so.6
#5 0x7fd9b9a3e956 in raise () from /lib64/libc.so.6
#6 0x7fd9b9a287f4 in abort () from /lib64/libc.so.6
#7 0x7fd9b58e5411 in OutlineItem::open() [clone .cold] () from
/lib64/libpoppler.so.117
#8 0x7fd9b59bef0d in OutlineItem::hasKids() () from
/lib64/libpoppler.so.117
#9 0x7fd9841431c0 in
PDFGenerator::addSynopsisChildren(QVector const&,
QDomNode*) [clone .isra.0] () from
/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so
#10 0x7fd98412cfd2 in PDFGenerator::generateDocumentSynopsis() () from
/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so
#11 0x7fd9a0f5607c in TOC::notifySetup(QVector const&, int)
[clone .part.0] () from /usr/lib64/qt5/plugins/okularpart.so
#12 0x7fd9a0d4c7bc in Okular::Document::openDocument(QString const&, QUrl
const&, QMimeType const&, QString const&) () from /lib64/libOkular5Core.so.10
#13 0x7fd9a0ec3582 in Okular::Part::doOpenFile(QMimeType const&, QString
const&, bool*) () from /usr/lib64/qt5/plugins/okularpart.so
#14 0x7fd9a0ec4d85 in Okular::Part::openFile() () from
/usr/lib64/qt5/plugins/okularpart.so
#15 0x7fd9b9cd32d5 in KParts::ReadOnlyPartPrivate::openLocalFile() () from
/lib64/libKF5Parts.so.5
#16 0x7fd9b9cd7a7f in KParts::ReadOnlyPart::openUrl(QUrl const&) () from
/lib64/libKF5Parts.so.5
#17 0x7fd9a0ec4146 in Okular::Part::slotAttemptReload(bool, QUrl const&) ()
from /usr/lib64/qt5/plugins/okularpart.so
#18 0x7fd9a0ed52c4 in
QtPrivate::QFunctorSlotObject const&)::{lambda()#13}, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
from /usr/lib64/qt5/plugins/okularpart.so
#19 0x7fd9b70db9a6 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#20 0x7fd9b70ded2e in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib64/libQt5Core.so.5
#21 0x7fd9b70d2ad5 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#22 0x7fd9b7daed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#23 0x7fd9b70a81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#24 0x7fd9b70f83b1 in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5
#25 0x7fd9b70f8c8c in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5Core.so.5
#26 0x7fd9b4c73faf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#27 0x7fd9b4cc92c8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#28 0x7fd9b4c71940 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#29 0x7fd9b70f902a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#30 0x7fd9b70a6c1a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#31 0x7fd9b70aece2 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#32 0x7fd9ba025f5f in kdemain () from /lib64/libkdeinit5_kile.so
#33 0x7fd9b9a29510 in __libc_start_call_main () from /lib64/libc.so.6
#34 0x7fd9b9a295c9 in __libc_start_main_impl () from /lib64/libc.so.6
#35 0x563bce62d0a5 in _start ()
[Inferior 1 (process 132728) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 463267] Show the changelog of packages
https://bugs.kde.org/show_bug.cgi?id=463267 --- Comment #4 from Emanuele --- Thank you :-) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463267] Show the changelog of packages
https://bugs.kde.org/show_bug.cgi?id=463267 --- Comment #2 from Emanuele --- Created attachment 155063 --> https://bugs.kde.org/attachment.cgi?id=155063=edit Discover Yes and thanks for replying! I noticed that for flatpak APPs from flathub repository it shows changelogs, for "rpm" APPs it doesn't. I use Fedora 37 KDE. As you can see from the screenshot when there are system updates and I click on "Fedora Updates" it shows only the version number as a change, the same if I click on "more info". Discover: 5.26.4 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463267] New: Show the changelog of packages
https://bugs.kde.org/show_bug.cgi?id=463267 Bug ID: 463267 Summary: Show the changelog of packages Classification: Applications Product: Discover Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: emanu@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 154710 --> https://bugs.kde.org/attachment.cgi?id=154710=edit Screenshot When I get an update on Discover and I click "more info" it only shows the version number, for example : 1.4.29 > 1.4.30, no content about what changed. gnome-software when available you can view the changelog, attached a screenshot. This offers a convenience to see if those packages have high priority bugfixes or not, in order to decide whether to update now or delay the update. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462908] Application stuck on panel on startup creates a new instance
https://bugs.kde.org/show_bug.cgi?id=462908 --- Comment #4 from Emanuele --- (In reply to veggero from comment #3) > Uhm, that makes me think it's an issue of how flatpak installs chrome, > rather than plasma's fault? But I'm not sure. I don't know, but I don't have this problem on GNOME with the dash to dock extension -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462908] Application stuck on panel on startup creates a new instance
https://bugs.kde.org/show_bug.cgi?id=462908 --- Comment #2 from Emanuele --- (In reply to veggero from comment #1) > Hey, one question; I don't get from the video what exactly you mean by > "stuck on panel" or "blocked on the panel"? (Nel senso, intendi app pinnatta > come mostri, o è proprio "bloccata" in qualche senso?) App pinnata sul pannello, l'applicazione funziona senza problemi è solo un problema di coerenze. The application works without problems, it's just a consistency problem, in this case the problem is with the Google Chrome application from flathub, it also happens randomly with others. thank you -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462908] New: Application stuck on panel on startup creates a new instance
https://bugs.kde.org/show_bug.cgi?id=462908 Bug ID: 462908 Summary: Application stuck on panel on startup creates a new instance Classification: Plasma Product: plasmashell Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: emanu@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 154499 --> https://bugs.kde.org/attachment.cgi?id=154499=edit log As per the title, every time I start an application blocked on the panel it creates a new instance, this happens especially with Google Chrome from flathub. attached these are the logs that are generated when I start chrome. I hope it helps to improve the quality of KDE plasma. :-) OS: Fedora 37 KDE spin Session: Wayland plasma version: 5.26.3 KDE frameworks: 5.100.0 A short video that better explains visually: https://www.youtube.com/watch?v=xDAip74IQ3Y -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460257] New: Kioslave5 sometimes crashes when deleting files on desktop view
https://bugs.kde.org/show_bug.cgi?id=460257 Bug ID: 460257 Summary: Kioslave5 sometimes crashes when deleting files on desktop view Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- Created attachment 152713 --> https://bugs.kde.org/attachment.cgi?id=152713=edit DrKonqui crash log report SUMMARY Application: kioslave5 (kioslave5), signal: Segmentation fault [KCrash Handler] #4 0x7efe1d93162d in KIO::SlaveBase::setKillFlag() () from /lib64/libKF5KIOCore.so.5 #5 0x7efe1d92c203 in genericsig_handler () from /lib64/libKF5KIOCore.so.5 #6 #7 0x7efe1bdb0d65 in asn1_primitive_free[localalias] () from /lib64/libcrypto.so.1.1 #8 0x7efe1bdb7580 in asn1_template_free () from /lib64/libcrypto.so.1.1 #9 0x7efe1bdb6e96 in asn1_item_embed_free () from /lib64/libcrypto.so.1.1 #10 0x7efe1bdb7580 in asn1_template_free () from /lib64/libcrypto.so.1.1 #11 0x7efe1bdb6e96 in asn1_item_embed_free () from /lib64/libcrypto.so.1.1 #12 0x7efe1bdb7580 in asn1_template_free () from /lib64/libcrypto.so.1.1 #13 0x7efe1bdb6e96 in asn1_item_embed_free () from /lib64/libcrypto.so.1.1 #14 0x7efe1bdb7029 in ASN1_item_free () from /lib64/libcrypto.so.1.1 #15 0x7efe1cfef4d9 in QSslCertificatePrivate::~QSslCertificatePrivate() () from /lib64/libQt5Network.so.5 #16 0x7efe1cfed344 in QSslCertificate::~QSslCertificate() () from /lib64/libQt5Network.so.5 #17 0x7efe1cfef904 in QList::~QList() () from /lib64/libQt5Network.so.5 #18 0x7efe1cff28b6 in QSslConfigurationPrivate::~QSslConfigurationPrivate() () from /lib64/libQt5Network.so.5 #19 0x7efe1cffd481 in (anonymous namespace)::Q_QGS_globalData::innerFunction()::Holder::~Holder() () from /lib64/libQt5Network.so.5 #20 0x7efe1d166485 in __run_exit_handlers () from /lib64/libc.so.6 #21 0x7efe1d166600 in exit () from /lib64/libc.so.6 #22 0x7efe1d14eeb7 in __libc_start_call_main () from /lib64/libc.so.6 #23 0x7efe1d14ef60 in __libc_start_main_impl () from /lib64/libc.so.6 #24 0x55de82fc3705 in _start () [Inferior 1 (process 1854) detached] STEPS TO REPRODUCE 1. Have some file on desktop 2. In the desktop view select some of them 3. Delete them OBSERVED RESULT kioslave crashes and plasmashell restarts. The files are not deleted. EXPECTED RESULT Just deleting the files. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.2 Kernel Version: 5.19.9-100.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: Dell Inc. Product Name: Inspiron 15 5501 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460257] Kioslave5 sometimes crashes when deleting files on desktop view
https://bugs.kde.org/show_bug.cgi?id=460257 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452673] kwin_x11 sometimes crashes with iris mesa drivers
https://bugs.kde.org/show_bug.cgi?id=452673 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452790] Overwrite when trying to rename a file inside an archive
https://bugs.kde.org/show_bug.cgi?id=452790 Emanuele Spirito changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Emanuele Spirito --- This bug has been solved (my current version of ark is the same so something else has been fixed to enstablish the correct behaviour) -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 454084] Kvault fails closing after encrypting a folder in it
https://bugs.kde.org/show_bug.cgi?id=454084 --- Comment #1 from Emanuele Spirito --- I add that if I use the autostart feature of kgpg, this issue does not occur any more. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424022] Plasma crashed in QSGBatchRenderer::Renderer::renderBatches() after moving one taskbar panel beside another panel in the bottom of the screen
https://bugs.kde.org/show_bug.cgi?id=424022 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 458470] Kile doesn't show the cursor twice for the same line
https://bugs.kde.org/show_bug.cgi?id=458470 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 458470] New: Kile doesn't show the cursor twice for the same line
https://bugs.kde.org/show_bug.cgi?id=458470 Bug ID: 458470 Summary: Kile doesn't show the cursor twice for the same line Product: kile Version: 2.9.93 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@gmail.com Reporter: emaster...@gmail.com Target Milestone: --- Created attachment 151682 --> https://bugs.kde.org/attachment.cgi?id=151682=edit Screenrecord of the bug SUMMARY When live preview of the pdf is enabled using PDFLaTeX, you cannot see the cursor on the pdf a second time if the cursor on the editor is on the same line as the previous request of this feature. If you change line between the two requests, the feature works correctly. STEPS TO REPRODUCE 0. Enable live preview of the pdf 1. Select a line on the editor 2. Click the button to show the cursor position on the pdf 3. Scroll on the pdf using the mouse 4. Select the same line on the editor 5. Click the button to show the cursor position on the pdf OBSERVED RESULT The first time, after step 2, the pdf moves to the cursor position. The second time, after step 5, the pdf doesn't move at all. EXPECTED RESULT Each time the pdf moves to the cursor position. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.2 Kernel Version: 5.18.18-100.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: Dell Inc. Product Name: Inspiron 15 5501 ADDITIONAL INFORMATION I attached the screenrecord. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458234] Kwin crashes while using task switcher
https://bugs.kde.org/show_bug.cgi?id=458234 --- Comment #4 from Emanuele Spirito --- Created attachment 151549 --> https://bugs.kde.org/attachment.cgi?id=151549=edit Another crash log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458234] Kwin crashes while using task switcher
https://bugs.kde.org/show_bug.cgi?id=458234 --- Comment #3 from Emanuele Spirito --- Application: KWin (kwin_x11), signal: Aborted [KCrash Handler] #4 0x7f213e6a256c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7f213e655d16 in raise () at /lib64/libc.so.6 #6 0x7f213e6297f3 in abort () at /lib64/libc.so.6 #7 0x7f2129e1a712 in blorp_update_clear_color.part[cold] () at /usr/lib64/dri/iris_dri.so #8 0x7f212aa6ae19 in iris_fence_flush () at /usr/lib64/dri/iris_dri.so #9 0x7f2129e8a60d in st_context_flush () at /usr/lib64/dri/iris_dri.so #10 0x7f2129e2b205 in dri_flush () at /usr/lib64/dri/iris_dri.so #11 0x7f212b808f34 in loader_dri3_swap_buffers_msc () at /lib64/libGLX_mesa.so.0 #12 0x7f212b7fc1f5 in dri3_swap_buffers () at /lib64/libGLX_mesa.so.0 #13 0x7f212b852efa in QGLXContext::swapBuffers(QPlatformSurface*) () at /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #14 0x7f213db66604 in QSGRenderThread::syncAndRender(QImage*) () at /lib64/libQt5Quick.so.5 #15 0x7f213db6aa9d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #16 0x7f213f8b9546 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #17 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #18 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 23 (Thread 0x7f2115dec640 (LWP 10664) "kwin_x11:gdrv0"): #1 0x7f213e69fbc0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7f2129e3428b in util_queue_thread_func () at /usr/lib64/dri/iris_dri.so #3 0x7f2129e33edb in impl_thrd_routine () at /usr/lib64/dri/iris_dri.so #4 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #5 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 22 (Thread 0x7f20ebfff640 (LWP 9838) "QQmlThread"): #1 0x7f213fac42a9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f213fac56c4 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f213fa755f2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f213f8b834a in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f214069ed7c in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f213f8b9546 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #8 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 21 (Thread 0x7f20d27fc640 (LWP 9809) "vsync event mon"): #1 0x7f213fac42a9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f213fac56c4 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f213fa755f2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f213f8b834a in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f213f8b9546 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #7 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 20 (Thread 0x7f20d2ffd640 (LWP 9808) "kwin_x11:gdrv0"): #1 0x7f213e69fbc0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7f2129e3428b in util_queue_thread_func () at /usr/lib64/dri/iris_dri.so #3 0x7f2129e33edb in impl_thrd_routine () at /usr/lib64/dri/iris_dri.so #4 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #5 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 19 (Thread 0x7f20d37fe640 (LWP 9807) "kwin_x11:sh5"): #1 0x7f213e69fbc0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7f2129e3428b in util_queue_thread_func () at /usr/lib64/dri/iris_dri.so #3 0x7f2129e33edb in impl_thrd_routine () at /usr/lib64/dri/iris_dri.so #4 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #5 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 18 (Thread 0x7f20d3fff640 (LWP 9806) "kwin_x11:sh4"): #1 0x7f213e69fbc0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7f2129e3428b in util_queue_thread_func () at /usr/lib64/dri/iris_dri.so #3 0x7f2129e33edb in impl_thrd_routine () at /usr/lib64/dri/iris_dri.so #4 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #5 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 17 (Thread 0x7f20e8ff9640 (LWP 9805) "kwin_x11:sh3"): #1 0x7f213e69fbc0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7f2129e3428b in util_queue_thread_func () at /usr/lib64/dri/iris_dri.so #3 0x7f2129e33edb in impl_thrd_routine () at /usr/lib64/dri/iris_dri.so #4 0x7f213e6a0822 in start_thread () at /lib64/libc.so.6 #5 0x7f213e640450 in clone3 () at /lib64/libc.so.6 Thread 16 (Thread 0x7f20e97fa640 (LWP 9804) "kwin_x11:sh2"): #1 0x7f213e69fbc0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2
[frameworks-kwayland] [Bug 458237] Possibility of configuring gestures
https://bugs.kde.org/show_bug.cgi?id=458237 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458234] Kwin crashes while using task switcher
https://bugs.kde.org/show_bug.cgi?id=458234 --- Comment #2 from Emanuele Spirito --- Screenrecord of the bug: https://drive.google.com/drive/folders/1WcHA81wmIp8M__aBejL-9fZw1n7cjj7-?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458234] Kwin crashes while using task switcher
https://bugs.kde.org/show_bug.cgi?id=458234 --- Comment #1 from Emanuele Spirito --- Created attachment 151536 --> https://bugs.kde.org/attachment.cgi?id=151536=edit Crash log made by Dr Konqui I attach the crash log I've already put inside the previous comment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458234] Kwin crashes while using task switcher
https://bugs.kde.org/show_bug.cgi?id=458234 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458234] New: Kwin crashes while using task switcher
https://bugs.kde.org/show_bug.cgi?id=458234 Bug ID: 458234 Summary: Kwin crashes while using task switcher Product: kwin Version: 5.25.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- SUMMARY If I have at least three windows and I use task switcher by the shortcut Alt+Tab then Kwin crashes. It crashes several times if I continue to use that shortcut. STEPS TO REPRODUCE 1. open at least three windows 2. use task switcher (i.e. Alt+Tab) SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.2 Kernel Version: 5.18.18-100.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: Dell Inc. Product Name: Inspiron 15 5501 ADDITIONAL INFORMATION: Application: KWin (kwin_x11), signal: Aborted [KCrash Handler] #4 0x7fb40d18556c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7fb40d138d16 in raise () at /lib64/libc.so.6 #6 0x7fb40d10c7f3 in abort () at /lib64/libc.so.6 #7 0x7fb3f88fd712 in blorp_update_clear_color.part[cold] () at /usr/lib64/dri/iris_dri.so #8 0x7fb3f954dce9 in iris_fence_flush () at /usr/lib64/dri/iris_dri.so #9 0x7fb3f8ae2479 in fence_sync () at /usr/lib64/dri/iris_dri.so #10 0x7fb40f54f833 in KWin::WindowThumbnailItem::updateOffscreenTexture() () at /lib64/libkwin.so.5 #11 0x7fb40e58d7d9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #12 0x7fb40f52f784 in KWin::Scene::prePaint(KWin::Output*) () at /lib64/libkwin.so.5 #13 0x7fb40f482c63 in KWin::Compositor::prePaintPass(KWin::RenderLayer*) () at /lib64/libkwin.so.5 #14 0x7fb40f484fa5 in KWin::Compositor::composite(KWin::RenderLoop*) () at /lib64/libkwin.so.5 #15 0x7fb40f485a45 in KWin::X11Compositor::composite(KWin::RenderLoop*) () at /lib64/libkwin.so.5 #16 0x7fb40e58d7d9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #17 0x7fb40f449f46 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /lib64/libkwin.so.5 #18 0x7fb40f51cae7 in KWin::RenderLoopPrivate::dispatch() () at /lib64/libkwin.so.5 #19 0x7fb40e58d7d9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #20 0x7fb40e590a7e in QTimer::timeout(QTimer::QPrivateSignal) () at /lib64/libQt5Core.so.5 #21 0x7fb40e5842cf in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #22 0x7fb40d8e0443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #23 0x7fb40e559be8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #24 0x7fb40e5aa283 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #25 0x7fb40e5a8850 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #26 0x7fb3fafe94e2 in QXcbUnixEventDispatcher::processEvents(QFlags) () at /lib64/libQt5XcbQpa.so.5 #27 0x7fb40e5585f2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7fb40e560b34 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #29 0x561872c98398 in main () [Inferior 1 (process 11852) detached] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457863] Crash in baloo while editing many times a pdf
https://bugs.kde.org/show_bug.cgi?id=457863 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457863] New: Crash in baloo while editing many times a pdf
https://bugs.kde.org/show_bug.cgi?id=457863 Bug ID: 457863 Summary: Crash in baloo while editing many times a pdf Product: frameworks-baloo Version: 5.96.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- Created attachment 151313 --> https://bugs.kde.org/attachment.cgi?id=151313=edit Crash log by Dr Konqui SUMMARY I was editing a pdf, making annotations and things like that, and saving the file after every annotation. After one of that, baloo crashed. The pdf continued working. I could not reproduce because I can't remember the exact annotation I made before it crashed. I attached the crash log made by Dr. Konqui. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.2 Kernel Version: 5.18.16-100.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457368] Suggestion for adding the feature of panic firewall mode on
https://bugs.kde.org/show_bug.cgi?id=457368 --- Comment #5 from Emanuele Spirito --- (In reply to David from comment #3) > (In reply to David from comment #2) > > Created attachment 151050 [details] > > signature.asc > > > > Ora me ne occupo! > > Anche se francamente, mi sento un po' in imbarazzo... 藍 > > > > > I do apologize, this reply was not meant for this thread No problem at all -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457368] Suggestion for adding the feature of panic firewall mode on
https://bugs.kde.org/show_bug.cgi?id=457368 --- Comment #4 from Emanuele Spirito --- (In reply to Ivan Čukić from comment #1) > Can you explain the difference to killing all the connections? (I've never > used firewalld) There are many possible scenarios, for example one can have connections that are not included by the kill switch. Also one can have loopback or other internal connections.. Firewall panic ensures no packets go anywhere, either inbound or outbound -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 457368] Suggestion for adding the feature of panic firewall mode on
https://bugs.kde.org/show_bug.cgi?id=457368 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 457368] New: Suggestion for adding the feature of panic firewall mode on
https://bugs.kde.org/show_bug.cgi?id=457368 Bug ID: 457368 Summary: Suggestion for adding the feature of panic firewall mode on Product: kgpg Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: emaster...@gmail.com Target Milestone: --- SUMMARY I saw that while creating a new kvault one can choose to disable WiFi and Bluetooth connection during the period the kvault is open. I want to suggest a possible secure boost feature, that is adding the possibility to run the firewall in panic mode while the kvault is open. This should only require to run in Konsole a command similar to: sudo firewall-cmd panic-on -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455832] KDE Connect daemon crashed
https://bugs.kde.org/show_bug.cgi?id=455832 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com --- Comment #1 from Emanuele Spirito --- Version: kdeconnectd.x86_64 21.12.2-2.fc35 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455832] New: KDE Connect daemon crashed
https://bugs.kde.org/show_bug.cgi?id=455832 Bug ID: 455832 Summary: KDE Connect daemon crashed Product: kdeconnect Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: emaster...@gmail.com Target Milestone: --- Application: kdeconnectd (21.12.2) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.17.13-200.fc35.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I had my Android phone linked to KDE Connect service on my PC (all features of exchange active). I received two notifications from my phone with almost same argument and then the daemon crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Demone di KDE Connect (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f069c7b819d in KNotification::id() () from /lib64/libKF5Notifications.so.5 #5 0x7f069c7b83b2 in KNotificationManager::notifyPluginFinished(KNotification*) () from /lib64/libKF5Notifications.so.5 #6 0x7f069b4933e9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f069c7b3c43 in KNotificationPlugin::finished(KNotification*) () from /lib64/libKF5Notifications.so.5 #8 0x7f069b489f49 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f069bfcb443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #10 0x7f069b45f7d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7f069b462d46 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #12 0x7f069b4b1117 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #13 0x7f06998f30af in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #14 0x7f0699948308 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #15 0x7f06998f08a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #16 0x7f069b4b0bb8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f069b45e1e2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #18 0x7f069b466724 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #19 0x5613cf024fae in main () [Inferior 1 (process 1543) detached] The reporter indicates this bug may be a duplicate of or related to bug 454331, bug 449276. Possible duplicates by query: bug 455289, bug 454331, bug 454176, bug 454144, bug 454054. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 454084] Kvault fails closing after encrypting a folder in it
https://bugs.kde.org/show_bug.cgi?id=454084 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 454084] New: Kvault fails closing after encrypting a folder in it
https://bugs.kde.org/show_bug.cgi?id=454084 Bug ID: 454084 Summary: Kvault fails closing after encrypting a folder in it Product: kgpg Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: emaster...@gmail.com Target Milestone: --- Created attachment 149022 --> https://bugs.kde.org/attachment.cgi?id=149022=edit Behaviour of kvault SUMMARY I created a kvault using kgpg and inside it I have a subfolder. When I open the vault, zip the subfolder and then encrypt it with kgpg, after encryption I cannot close kvault (without forcing it) because it says that kgpg is blocking the closing of the kvault. If I close manually kgpg and then try to close the kvault, then it works. STEPS TO REPRODUCE 1. open a kvault (with kgpg) that contains subfolders in it (once opened); 2. compress one of the above mentioned subfolder; 3. encrypt the compressed file with kgpg with a symmetric key; 4. after encryption, close all your windows (so you are sure that Dolphin is not concerned in blocking the closing of the kvault); 5. block the kvault (in the system tray there is the button "Block kvault"); OBSERVED RESULT It can't close the kvault because "kgpg is using the kvault", even after having finished the encryption. EXPECTED RESULT The kvault closes because I have no jobs open that deal with the kvault. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics ADDITIONAL INFORMATION I attached a video to better explain the behaviour. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes
https://bugs.kde.org/show_bug.cgi?id=395023 Emanuele changed: What|Removed |Added CC||emanu@gmail.com --- Comment #4 from Emanuele --- I confirm on filesystem Btrfs, also reproduced on a filesystem FAT, is it expected? Test: Virt-Manager OS: Fedora 36 Dolphin 21.12.2 KDE Frameworks 5.91.0 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 453719] New: Crash after setting up user menu
https://bugs.kde.org/show_bug.cgi?id=453719 Bug ID: 453719 Summary: Crash after setting up user menu Product: kile Version: 2.9.93 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: emaster...@gmail.com Target Milestone: --- Created attachment 148780 --> https://bugs.kde.org/attachment.cgi?id=148780=edit Crash log of Kile SUMMARY I was setting up the "user menu" with personal shortcuts to insert text rapidly. I have chosen a combination like CTRL+MAIUSC+B which was already chosen by something. So I opened "shortcut keyboard menu" inside Kile and looked for CTRL+MAIUSC+B to see what was referring to and Kile crashed. STEPS TO REPRODUCE I tried to reproduce but I couldn't SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 453719] Crash after setting up user menu
https://bugs.kde.org/show_bug.cgi?id=453719 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349 --- Comment #20 from Emanuele Spirito --- > The most important information though is to find a reliable way to reproduce > the symptoms that a developer could reproduce then. > Until we don’t a way to reproduce or pinpoint the origin of the issue, we > are clueless. I know, I was trying to explain in the most complete way the issue so maybe any expert reading could find a clue to the solution I cannot see. > The recommended path to give actionable intel here, would be a trace using > gdb or https://github.com/KDAB/hotspot. Those technics require debugging > symbols. It might be out of your skill. I had a look to that link but I think you are right, this is quite hard for me. > It still helps to update bugs to inform devs which bugs are still > effectively hurting users and which ones are more common. > So thanks for the effort anyway. You are welcome, I'll stay tuned so if I can find the way to reproduce the bug I'll tell you. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 453236] When uninstalling an application, ask whether to delete the data
https://bugs.kde.org/show_bug.cgi?id=453236 --- Comment #2 from Emanuele --- Thanks for the work you do -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427471] Dolphin using up 100% CPU
https://bugs.kde.org/show_bug.cgi?id=427471 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com --- Comment #7 from Emanuele Spirito --- Maybe a duplicate of kde bug 411349? https://bugs.kde.org/show_bug.cgi?id=411349 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349 --- Comment #18 from Emanuele Spirito --- Created attachment 148590 --> https://bugs.kde.org/attachment.cgi?id=148590=edit Core usage returned normal Important: see (above left in the screen) that, respect to other screenshots, I changed Dolphin view from "icon view" to "detailed view" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349 --- Comment #17 from Emanuele Spirito --- Created attachment 148589 --> https://bugs.kde.org/attachment.cgi?id=148589=edit Another image of the core usage lasting in time -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349 --- Comment #16 from Emanuele Spirito --- Created attachment 148588 --> https://bugs.kde.org/attachment.cgi?id=148588=edit Core usage of Dolphin in system-monitor -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349 --- Comment #15 from Emanuele Spirito --- Created attachment 148587 --> https://bugs.kde.org/attachment.cgi?id=148587=edit Contents of the open Dolphin session while core usage became higher than normal -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349 --- Comment #14 from Emanuele Spirito --- Created attachment 148586 --> https://bugs.kde.org/attachment.cgi?id=148586=edit General configuration of Dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com --- Comment #13 from Emanuele Spirito --- Same problem on my system (Dolphin version 21.12.2.1-1.fc35). I have found a possible clue on the problem. During the 100% usage of a core, I tried different window views. I had no preview setting, no subfolder (I read the comment of @Tonurics). I had a file selected, but by deselecting it, nothing change. The core usage returned normal (near 2%) after I changed the view of Dolphin from "icon view" to "detailed view" (I tried also the "compact view" but that change didn't make anything in core usage). I've attached my screenshot so you can see this report in a visual media way. Other system information: Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453394] Present windows sometimes makes windows disappear
https://bugs.kde.org/show_bug.cgi?id=453394 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453394] New: Present windows sometimes makes windows disappear
https://bugs.kde.org/show_bug.cgi?id=453394 Bug ID: 453394 Summary: Present windows sometimes makes windows disappear Product: kwin Version: 5.24.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- SUMMARY It happens sometimes that when presenting windows with the present-windows feature of Kwin they all disappear, both in the grid view and while you come back to the "normal" desktop view (one window per time). See videos in this link: https://drive.google.com/drive/folders/1ukfOGwLJtaScw_JjvVPqIknazInOyDW-?usp=sharing STEPS TO REPRODUCE 1. (sometimes) activate present-windows 2. 3. OBSERVED RESULT See the screen recordings: https://drive.google.com/drive/folders/1ukfOGwLJtaScw_JjvVPqIknazInOyDW-?usp=sharing EXPECTED RESULT When I use present-window, I expect to see all windows in the grid and when coming back I expect to return to the desktop view, so one window per time. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 453236] New: When uninstalling an application, ask whether to delete the data
https://bugs.kde.org/show_bug.cgi?id=453236 Bug ID: 453236 Summary: When uninstalling an application, ask whether to delete the data Product: Discover Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: emanu@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- It is not a bug, but a request for functionality. Flatpak has a flag to uninstallation to delete application data: flatpak uninstall App --delete-data The advantage for the user is the saving of space on non usable data. On Gnome Software they have a Mackup: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/257 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418399] Pinned applications sometimes jump around when launched
https://bugs.kde.org/show_bug.cgi?id=418399 --- Comment #3 from Emanuele --- I'm on plasma 5.24.4 and I can't reproduce it, then looks solved with the latest versions? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 Emanuele Spirito changed: What|Removed |Added Version|Git (master)|5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 337656] Choosing a custom font for the message text does not work
https://bugs.kde.org/show_bug.cgi?id=337656 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 --- Comment #8 from Emanuele Spirito --- Still on kmail2 version: 5.19.2 (21.12.2) It can be similar to this other bug? https://bugs.kde.org/show_bug.cgi?id=337656 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451150] On X11, clicking the close button only works every other time
https://bugs.kde.org/show_bug.cgi?id=451150 --- Comment #9 from Emanuele Spirito --- I have the videorecording of the double-click needed to close the windows in this drive link: https://drive.google.com/drive/folders/1k5cL2s3UbpQUq4D4W9hNcUztSGX9CDZC?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451150] On X11, clicking the close button only works every other time
https://bugs.kde.org/show_bug.cgi?id=451150 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com --- Comment #8 from Emanuele Spirito --- I have the same issue on my system and the description Adam does is exactly what I see. System information: Kwin version: 5.24.4 Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452790] Overwrite when trying to rename a file inside an archive
https://bugs.kde.org/show_bug.cgi?id=452790 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452790] New: Overwrite when trying to rename a file inside an archive
https://bugs.kde.org/show_bug.cgi?id=452790 Bug ID: 452790 Summary: Overwrite when trying to rename a file inside an archive Product: ark Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: emaster...@gmail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- Created attachment 148262 --> https://bugs.kde.org/attachment.cgi?id=148262=edit Video recording of the unexpected behaviour SUMMARY When I try to rename a file or a folder while this is inside an archive, the name I write overwrites the previous name so it is very difficult to see what I am writing. STEPS TO REPRODUCE 1. Open an not-empty archive 2. Select a file 3. Choose "Rename" 4. Write the new name OBSERVED RESULT The new name, while writing it, is over the previous name. EXPECTED RESULT The new name, while writing it, is over blank text field. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 --- Comment #8 from Emanuele Spirito --- I changed the kmail version of the bug to my current version 5.19.2 (aka 21.12.2) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 Emanuele Spirito changed: What|Removed |Added Version|4.9.5 |5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 --- Comment #7 from Emanuele Spirito --- Created attachment 148261 --> https://bugs.kde.org/attachment.cgi?id=148261=edit Crash log made by KDE crash handler -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684
Emanuele Spirito changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC||emaster...@gmail.com
Resolution|UNMAINTAINED|---
Ever confirmed|0 |1
--- Comment #6 from Emanuele Spirito ---
It happened to me just today. I cannot reproduce the bug. It happened when I
forwarded an email and then tried to forward another email with same object
("topic" of email, under A,CC).
System Info:
Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 438237] Cannot match the cursor position after having scrolled in the editor
https://bugs.kde.org/show_bug.cgi?id=438237 Emanuele Spirito changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 437788] Kded5 asks to open kwallet everytime the system starts
https://bugs.kde.org/show_bug.cgi?id=437788 Emanuele Spirito changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Emanuele Constantini changed: What|Removed |Added CC||emanuelx...@gmail.com --- Comment #3 from Emanuele Constantini --- I can confirm it's still happening in KDE plasma 5.24.2 Here's a video about it. https://youtu.be/SJgooe5UHbM I didn't had anything opened in other workspaces at the time. But those flickering objects would show behind any application using blurred content in x11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 451420] Crash of Marble KDE after closing it
https://bugs.kde.org/show_bug.cgi?id=451420 --- Comment #1 from Emanuele Spirito --- Created attachment 147454 --> https://bugs.kde.org/attachment.cgi?id=147454=edit Another crash log generated by DrKonqui -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 451420] Crash of Marble KDE after closing it
https://bugs.kde.org/show_bug.cgi?id=451420 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com, ||kitt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 451420] New: Crash of Marble KDE after closing it
https://bugs.kde.org/show_bug.cgi?id=451420 Bug ID: 451420 Summary: Crash of Marble KDE after closing it Product: marble Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- Application: marble (2.2.20 (2.3 development version)) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.16.11-200.fc35.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I have modified some bookmarks on the OSM vectorial map, adding some icons of little dimension. Then I closed Marble KDE by clicking on the window exit button. - Custom settings of the application: Nothing. The crash can be reproduced every time. -- Backtrace: Application: Globo virtuale Marble (marble), signal: Aborted [KCrash Handler] #4 0x7fa6c0abd88c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7fa6c0a706a6 in raise () from /lib64/libc.so.6 #6 0x7fa6c0a5a7d3 in abort () from /lib64/libc.so.6 #7 0x7fa6c0ab1a07 in __libc_message () from /lib64/libc.so.6 #8 0x7fa6c0ac787c in malloc_printerr () from /lib64/libc.so.6 #9 0x7fa6c0ac917c in _int_free () from /lib64/libc.so.6 #10 0x7fa6c0acbc05 in free () from /lib64/libc.so.6 #11 0x7fa6c1144d71 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7fa6c284857d in KXmlGuiWindow::event(QEvent*) () from /lib64/libKF5XmlGui.so.5 #13 0x7fa6c1bef443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7fa6c111a7d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7fa6c111dd46 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #16 0x7fa6c116c117 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #17 0x7fa6bf40705f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7fa6bf45c2a8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #19 0x7fa6bf404853 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7fa6c116bbb8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7fa6c11191e2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7fa6c1121724 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #23 0x5601bcc5b3ce in main () [Inferior 1 (process 2332) detached] The reporter indicates this bug may be a duplicate of or related to bug 450368, bug 443144, bug 411571. Possible duplicates by query: bug 450368, bug 450212, bug 449584, bug 448108, bug 444978. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 437788] Kded5 asks to open kwallet everytime the system starts
https://bugs.kde.org/show_bug.cgi?id=437788 --- Comment #4 from Emanuele Spirito --- This bug is no more going. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 438237] Cannot match the cursor position after having scrolled in the editor
https://bugs.kde.org/show_bug.cgi?id=438237 --- Comment #7 from Emanuele Spirito --- The bug is no more going. I am quite sure because I use kile every day and I haven't noticed it for months. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 437402] Superposition in GUI for local archive encryption
https://bugs.kde.org/show_bug.cgi?id=437402 --- Comment #3 from Emanuele Spirito --- The issue is still going. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 438237] Cannot match the cursor position after having scrolled in the editor
https://bugs.kde.org/show_bug.cgi?id=438237 --- Comment #6 from Emanuele Spirito --- This bug is not coming up any more. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 437788] Kded5 asks to open kwallet everytime the system starts
https://bugs.kde.org/show_bug.cgi?id=437788 --- Comment #3 from Emanuele Spirito --- Lately, after the last update this issue is not coming up any more. -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 448600] KmPlot crashed after zoom out
https://bugs.kde.org/show_bug.cgi?id=448600 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com, ||kitt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 448600] KmPlot crashed after zoom out
https://bugs.kde.org/show_bug.cgi?id=448600 --- Comment #2 from Emanuele Spirito --- Created attachment 145548 --> https://bugs.kde.org/attachment.cgi?id=145548=edit Plot of the function I attached the screenshot of the plot of the function -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 448600] KmPlot crashed after zoom out
https://bugs.kde.org/show_bug.cgi?id=448600 --- Comment #1 from Emanuele Spirito --- Created attachment 145547 --> https://bugs.kde.org/attachment.cgi?id=145547=edit Another log by KCrash I repetead the sequence another time and the result was the same but I send you this new crash log. -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 448600] New: KmPlot crashed after zoom out
https://bugs.kde.org/show_bug.cgi?id=448600 Bug ID: 448600 Summary: KmPlot crashed after zoom out Product: kmplot Version: 1.3.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: cf...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- Created attachment 145546 --> https://bugs.kde.org/attachment.cgi?id=145546=edit Log of crash done by KCrash SUMMARY I asked KmPlot to plot a implicit function plot of (1−y^2)∙(2−y^2) − (1+cos(3∙x))= 0. Then he plotted correctly, when I tried to zoom out two times it crashed. I tried again and it happened again. I noticed that the backtrace was very long to achieve the first time (I mean 10 minutes). STEPS TO REPRODUCE 1. Open KmPlot 2. Plot a implicit function plot of (1−y^2)∙(2−y^2) − (1+cos(3∙x))= 0 3. Zoom out some times. OBSERVED RESULT Until 3. KmPlot plotted the function correctly but after 3. KmPlot crashes. EXPECTED RESULT No crashes. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.17-301.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 --- Comment #7 from Emanuele Spirito --- Errata: This doesn't happen until I toggle in the "View" panel the function "Use Fixed Font". Correct: The font I chose appears only when I toggle in the "View" panel the function "Use Fixed Font". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 --- Comment #6 from Emanuele Spirito --- (In reply to Laurent Montel from comment #5) > So you use html feature ok. > So if you activate "Use Fixed Font" for sure it will not use font from > composer but the font "fixed width font" defined in appearance settings > > Is it not ok ? As you can see at the beginning of the first video, both the "composer" (that you've just said is irrilevant because I am using html feature) and the "fixed width font" are set to DejaVu Sans Mono. When I create a new email, I expect to see the body font already set to DejaVu Sans Mono because it is my "fixed width font", but in fact I see "Noto Sans". This doesn't happen until I toggle in the "View" panel the function "Use Fixed Font". I mean, how can I change the default font of a new email, so that when I create a new email that starts with the font I have selected (in my case DejaVu Sans Mono)? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 --- Comment #4 from Emanuele Spirito --- Sorry for having cut the attached video into three parts, it's due to 4000 kB limit -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 --- Comment #3 from Emanuele Spirito --- Created attachment 143866 --> https://bugs.kde.org/attachment.cgi?id=143866=edit Recorded screen of the bug (part 3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 --- Comment #2 from Emanuele Spirito --- Created attachment 143865 --> https://bugs.kde.org/attachment.cgi?id=143865=edit Recorded screen of the bug (part 2) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 --- Comment #1 from Emanuele Spirito --- Created attachment 143864 --> https://bugs.kde.org/attachment.cgi?id=143864=edit Recorded screen of the bug (part 1) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com, ||kitt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445972] New: Cannot set the default font in composer
https://bugs.kde.org/show_bug.cgi?id=445972 Bug ID: 445972 Summary: Cannot set the default font in composer Product: kmail2 Version: Git (master) Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: emaster...@gmail.com Target Milestone: --- SUMMARY I want to change the default font I use in writing a new email (body message). As I recorded in the video attached, in appearance settings I set both composer and equal spacing font to DejaVu Sans Mono (font size 13). Then when I open a new email the body font is Noto Sans. When I open the "View" menu, if I select "Use Fixed Font", the font becomes the one I chose. Til now, all worked as expected. BUT when I create a new email, the font is yet Noto Sans (the default one, not the one I chose) and, when I open the "View" menu, the "Use Fixed Font" feature is already chosen, but if I deselect it, the font becomes the one I chose. So every time I want to use the font I chose in the Kmail Appearance Settings, I need to open the view menu and toggle the "Use Fixed Font" feature. STEPS TO REPRODUCE 1. Open Kmail 2. Open Kmail Settings -> Appearance 3. Choose the font you want in composer and fixed font 4. Create a new email OBSERVED RESULT The font is not the chosen one EXPECTED RESULT The font is the chosen one SOFTWARE/OS VERSIONS Kmail version: 5.17.3 (21.04.3) Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.17-301.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444723] Support for per-folder Defrag, Scrub, and Compress operations on BTRFS disks
https://bugs.kde.org/show_bug.cgi?id=444723 --- Comment #8 from Emanuele --- I created an example video: https://youtu.be/bjoj612HGsQ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444723] Support for per-folder Defrag, Scrub, and Compress operations on BTRFS disks
https://bugs.kde.org/show_bug.cgi?id=444723 --- Comment #7 from Emanuele --- Safely the frequency will be minor, compared to creating folders, but the problem is that creating a folder/subvolume in a specific location on the user's home is possible? Example: - I have the "Downloads" folder, I remove it and create it as a subvolume. - I go to any other folder of my user and create the subvolume/folder with a click To be clarified that so you create a nested subvolume with user permissions: you can remove it as any other folder, there is no need to specify mounting points on "fstab". On the Partition Manager, in my opinion, it's ok to add the functionality of creating BTRFS subvolume, but at the system level, to the Toplevel and Flat, in this case you need to specify the mount point, but this will be for a request for separate functionality, because Maybe a little more complex and with a good UX design. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444723] Support for per-folder Defrag, Scrub, and Compress operations on BTRFS disks
https://bugs.kde.org/show_bug.cgi?id=444723 --- Comment #5 from Emanuele --- Subvolumes behave like normal folders for users, is having them on Dolphin the best place? And you have the advantage of Btrfs if you use snapshot and btrfs send. If I have to create a folder I do it from Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444723] Best support on Btrfs filesystem
https://bugs.kde.org/show_bug.cgi?id=444723 --- Comment #3 from Emanuele --- Thank you for answering, you of KDE you are always so kind and helpful. I don't know in which place it is best to insert these options, maybe right click> Properties? Or in the right click list? - Create Subvolume Creating a separate subway has some advantages, mainly + that are excluded from the snapshots. Example from CLI: emanu@fedora ~> btrfs subvolume create test Create subvolume './test' emanu@fedora ~> ls -l | grep test drwxr-xr-x. 1 emanu emanu 0 8 nov 22.27 test - Defrag Select a folder, you can choose to make a Defrag, useful on the database or to comply files already written by selecting the algorithm. https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-filesystem#EXAMPLES - Scrub https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-scrub - Compress folder or file set Example, it can isolate you to create a suburb or set a folder with different compression algorithm, diablaiming compression etc. example: btrfs property set compression I was surprised, installing the BTRFS driver on Windows, to have all this in the file manager. Available here: https://github.com/maharmstone/btrfs Is it difficult for Dolphin to know if you are on a BTRFS filesystem and show these options? -- You are receiving this mail because: You are watching all bug changes.
