[kapman] [Bug 475647] New: Uses CPU when idle
https://bugs.kde.org/show_bug.cgi?id=475647 Bug ID: 475647 Summary: Uses CPU when idle Classification: Applications Product: kapman Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: tg8...@yahoo.fr Reporter: jtam...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY *** When kapman is started, kapman is animated to open/close its mouth. This uses a non trivial amount of CPU, even when kapman is not the current application or the screen is locked. *** STEPS TO REPRODUCE 1. Just open kapman OBSERVED RESULT kapman starts eating without moving. EXPECTED RESULT To achieve KDE's Sustainable Software Goal, kapman should stay idle when non playing, just as when you change the level using the menu entry in game. -- You are receiving this mail because: You are watching all bug changes.
[libkdegames] [Bug 475623] New: After pressing Remember in the High Score window (with keyboard Enter), the close button should be the next default widget
https://bugs.kde.org/show_bug.cgi?id=475623 Bug ID: 475623 Summary: After pressing Remember in the High Score window (with keyboard Enter), the close button should be the next default widget Classification: Frameworks and Libraries Product: libkdegames Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kde-games-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY *** When you use the keyboard to press Remember in the High Score window (using Enter), you have to press Tab to be able to select the Close button with the keyboard. *** EXPECTED RESULT The close button is the default widget, therefore it is possible to close the high score window with just two Enter keystrokes, instead of Enter, Tab, Enter. (If you know how to move from widget to widget with the keyboard). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475599] New: An strange date information in the tooltip
https://bugs.kde.org/show_bug.cgi?id=475599 Bug ID: 475599 Summary: An strange date information in the tooltip Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: 1.0 Created attachment 162289 --> https://bugs.kde.org/attachment.cgi?id=162289=edit the tooltip shows "14 14e October 14e 2023" SUMMARY *** In the date tooltip there is a strange date information: "14 14e Octubre 14e 2023" *** STEPS TO REPRODUCE 1. Just show the tooltip in the digital clock SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-34-generic (64-bit) Graphics Platform: offscreen Processors: 4 × AMD Phenom(tm) II X6 1100T Processor Memory: 3.8 GiB of RAM Graphics Processor: llvmpipe -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 475596] New: A crop tool will be a good addition
https://bugs.kde.org/show_bug.cgi?id=475596 Bug ID: 475596 Summary: A crop tool will be a good addition Classification: Applications Product: Spectacle Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: jtam...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** When you have to do a whole screen screenshot (for tooltips, for example), but you want to show the tooltip, there is no visible way to crop the image to that rectangle, you have to use an external image editor. *** EXPECTED RESULT A crop tool is present. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-34-generic (64-bit) Graphics Platform: offscreen Processors: 4 × AMD Phenom(tm) II X6 1100T Processor Memory: 3.8 GiB of RAM Graphics Processor: llvmpipe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468195] Last task in multi-row Task Manager can overlap with adjacent panel widgets
https://bugs.kde.org/show_bug.cgi?id=468195 Jaime Torres changed: What|Removed |Added Platform|openSUSE|Neon Version|5.27.3 |master -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475359] New: [6-dev] The central scrollbar moves all the window after scrolling 2 seconds.
https://bugs.kde.org/show_bug.cgi?id=475359 Bug ID: 475359 Summary: [6-dev] The central scrollbar moves all the window after scrolling 2 seconds. Classification: Applications Product: systemsettings Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY *** You have the system-settings window not very big, 2 sections, and you use the central scrollbar to see other sections. After 2 seconds, the icon changes and it just moves the whole window. *** EXPECTED RESULT The central scrollbar only shows the parts hidden when it is kept pressed. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-34-generic (64-bit) Graphics Platform: offscreen Processors: 6 × AMD Phenom(tm) II X6 1100T Processor Memory: 3.0 GiB of RAM Graphics Processor: llvmpipe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475353] New: [6-dev] With Focus steal prevention set to extreme, the logout pre-screen is under the kickoff menu
https://bugs.kde.org/show_bug.cgi?id=475353 Bug ID: 475353 Summary: [6-dev] With Focus steal prevention set to extreme, the logout pre-screen is under the kickoff menu Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: 1.0 Created attachment 162155 --> https://bugs.kde.org/attachment.cgi?id=162155=edit the menu over the logout screen SUMMARY *** The pre-logout screen appears under the menu. You have to manually close the menu or wait 30 seconds. See the screenshot. *** STEPS TO REPRODUCE First set the focus steal prevention to extreme. Press the Sleep, Restart or Shutdown in the kickoff menu. OBSERVED RESULT The pre-logout screen appears under the menu. You have to manually close the menu or wait 30 seconds. EXPECTED RESULT The kickoff menu is closed as when any other application icon is used or the pre-logout screen is over the kickoff menu. SOFTWARE/OS VERSIONS The ones of neon updated the 08/10/2023. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469940] New: No undelete nor confirmation for the autostart items
https://bugs.kde.org/show_bug.cgi?id=469940 Bug ID: 469940 Summary: No undelete nor confirmation for the autostart items Classification: Applications Product: systemsettings Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: nicolas.fe...@gmx.de Reporter: jtam...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Just missed the properties icon and pressed the "-" icon and I've lost one autostart item. If you have good memory (or good backup), you could restore it, otherwise ... probably you'll miss it in the next sessions. STEPS TO REPRODUCE Have some autostart items Press the "-" icon of one of items EXPECTED RESULT There is a confirmation dialog to delete the item or an undo system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468195] Last task in multi-row Task Manager can overlap with adjacent panel widgets
https://bugs.kde.org/show_bug.cgi?id=468195 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Jaime Torres --- Yes, it overlapped any widget at the right of the taskbar. After changing the maximum number of rows, the problem is gone. I can not reproduce it any more. But I create another panel with a taskbar with the same configuration and another widget at the right and the problem is there only in the new taskbar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468195] Odd tasks in the task bar overlap the system tray (wayland)
https://bugs.kde.org/show_bug.cgi?id=468195 --- Comment #2 from Jaime Torres --- Created attachment 157901 --> https://bugs.kde.org/attachment.cgi?id=157901=edit Yes, it happens in X11 also The height in the X11 test was 62, the screen with is 1920*1080. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468195] New: Odd tasks in the task bar overlap the system tray (wayland)
https://bugs.kde.org/show_bug.cgi?id=468195 Bug ID: 468195 Summary: Odd tasks in the task bar overlap the system tray (wayland) Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: 1.0 Created attachment 157889 --> https://bugs.kde.org/attachment.cgi?id=157889=edit task overlapping SUMMARY When I have 13 tasks (or dialogs), one of them is out of the limits of the task bar and is over the system tray. I have manual order for the taskbars, two rows maximum, never group, fill the free space in the panel and using wayland STEPS TO REPRODUCE (I haven't tried in other configurations) 1. Have the status bar with two rows 2. Have 12 tasks in the task bar (6 in the first row and 6 in the second row) 3. Add another task. OBSERVED RESULT One of the tasks is over the system tray EXPECTED RESULT All the tasks are inside the space of the task bar SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230324 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 367726] File Synchronization
https://bugs.kde.org/show_bug.cgi?id=367726 Jaime Torres changed: What|Removed |Added CC||andrestberme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 464313] New: crash in peerId
https://bugs.kde.org/show_bug.cgi?id=464313
Bug ID: 464313
Summary: crash in peerId
Classification: Applications
Product: ktorrent
Version: 22.12.1
Platform: OpenSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: joris.guis...@gmail.com
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: ktorrent (22.12.1)
Qt Version: 5.15.8
Frameworks Version: 5.101.0
Operating System: Linux 6.1.4-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.26.5 [KCrashBackend]
-- Information about the crash:
After this crash, plasma in wayland also crashed.
Why, no idea, there was no interaction with the computer while it happened.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 std::__atomic_base::load(std::memory_order) const
(__m=std::memory_order_relaxed, this=0x10005645f4501900) at
/usr/include/c++/12/bits/atomic_base.h:488
#7 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:239
#8 QBasicAtomicInteger::loadRelaxed() const (this=0x10005645f4501900) at
/usr/include/qt5/QtCore/qbasicatomic.h:107
#9 QtPrivate::RefCount::deref() (this=0x10005645f4501900) at
/usr/include/qt5/QtCore/qrefcount.h:66
#10 QString::~QString() (this=0x5645f7fddf40, this=) at
/usr/include/qt5/QtCore/qstring.h:1311
#11 bt::PeerID::~PeerID() (this=0x5645f7fddf20, this=) at
/usr/src/debug/libktorrent-22.12.1/src/peer/peerid.cpp:63
#12 0x7fe7edcd8766 in bt::Authenticate::~Authenticate()
(this=0x5645f7fdde40, this=) at
/usr/src/debug/libktorrent-22.12.1/src/peer/authenticate.cpp:63
#13 0x7fe7edcd8819 in bt::Authenticate::~Authenticate()
(this=0x5645f7fdde40, this=) at
/usr/src/debug/libktorrent-22.12.1/src/peer/authenticate.cpp:63
#14 0x7fe7ebd07a1f in QObject::event(QEvent*) (this=0x5645f7fdde40,
e=0x5645f05d8840) at kernel/qobject.cpp:1334
#15 0x7fe7ec9a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5645f7fdde40, e=0x5645f05d8840) at
kernel/qapplication.cpp:3640
#16 0x7fe7ebcdc138 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5645f7fdde40, event=0x5645f05d8840) at
kernel/qcoreapplication.cpp:1064
#17 0x7fe7ebcdf0d1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x5645e754cda0) at
kernel/qcoreapplication.cpp:1821
#18 0x7fe7ebd34363 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x5645e75c6010) at kernel/qeventdispatcher_glib.cpp:277
#19 0x7fe7ea11ba90 in g_main_dispatch (context=0x7fe7e0005010) at
../glib/gmain.c:3454
#20 g_main_context_dispatch (context=context@entry=0x7fe7e0005010) at
../glib/gmain.c:4172
#21 0x7fe7ea11be48 in g_main_context_iterate
(context=context@entry=0x7fe7e0005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4248
#22 0x7fe7ea11bedc in g_main_context_iteration (context=0x7fe7e0005010,
may_block=1) at ../glib/gmain.c:4313
#23 0x7fe7ebd33b66 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5645e75c8be0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x7fe7ebcdabab in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffe545c46c0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#25 0x7fe7ebce2d16 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#26 0x7fe7ec16ed3c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#27 0x7fe7ec9a53c5 in QApplication::exec() () at
kernel/qapplication.cpp:2832
#28 0x5645e59c4278 in main(int, char**) (argc=,
argv=) at /usr/src/debug/ktorrent-22.12.1/ktorrent/main.cpp:251
[Inferior 1 (process 4805) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 463238] New: Feature to have a history of the top X cpu or io or memory processes
https://bugs.kde.org/show_bug.cgi?id=463238 Bug ID: 463238 Summary: Feature to have a history of the top X cpu or io or memory processes Classification: Plasma Product: plasma-systemmonitor Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: jtam...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY You can see a 100% cpu ussage or notice that some process is requesting too much memory but when you try to see which process was doing it, it is already behaving normally. Why not have an historic of the most cpu, io or memory (select one of them) processes, just the name, pid and cpu, io or memory, just like you can have an historic of anonymous cpu, io or memory. One way of showing that information can be done with area graphics and the information in the hover tip. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 394874] Preview of a broken symbolic link in trash: generates a broken symbolic link
https://bugs.kde.org/show_bug.cgi?id=394874 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Jaime Torres --- I'm not able to reproduce it. Good. -- You are receiving this mail because: You are watching all bug changes.
[libkdegames] [Bug 259006] kGameRenderer crash when doing QT_FATAL_WARNINGS=1 kmines
https://bugs.kde.org/show_bug.cgi?id=259006 Jaime Torres changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Jaime Torres --- Yes, the lack of initialization still affects this game, but only when the QT Warnings become errors. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375436] Unable to use python input('text:') inside kdevelop (windows)
https://bugs.kde.org/show_bug.cgi?id=375436 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #3 from Jaime Torres --- The output view is only output. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 346855] kded5 100% cpu usage and blocks plasma
https://bugs.kde.org/show_bug.cgi?id=346855 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Jaime Torres --- I haven't experienced it in more than 4 years. Considered fixed. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 348258] Only document styles are saved when no space left on /tmp
https://bugs.kde.org/show_bug.cgi?id=348258 Jaime Torres changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Jaime Torres --- Still present with calligra words compiled today (KDE frameworks Versión 5.100.0 and Qt 5.15.6). The contents of the saved .odt file when /tmp is full are: unzip ../prueba.odt Archive: ../prueba.odt extracting: mimetype inflating: settings.xml inflating: content.xml inflating: styles.xml inflating: meta.xml inflating: Thumbnails/thumbnail.png inflating: META-INF/manifest.xml But content.xml only contains the office:automatic-styles -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424056] Okular crashed in cryptotech::cpp::utils::ILogOutput() while closing signed document and using proprietary driver for CryptoTech smart cards
https://bugs.kde.org/show_bug.cgi?id=424056 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com --- Comment #7 from Jaime Torres --- I'm able to reproduce it with one of the dni readers and the pkcs#11 dnie library installed: Just connect any dnie reader to any usb, with or without any dni, and open any pdf with signatures, for example: /usr/bin/okular "https://www.tecxoft.com/samples/pdf_digital_signature_timestamp.pdf; In Valgrind: ==30095== Invalid read of size 4 ==30095==at 0x662CCC7: pthread_mutex_trylock@@GLIBC_2.34 (pthread_mutex_trylock.c:33) ==30095==by 0x21834709: NativeLockMutex(void*) (in /usr/lib64/libpkcs11-dnie.so) ==30095==by 0x21828C21: C_CloseAllSessions (in /usr/lib64/libpkcs11-dnie.so) ==30095==by 0x1569303E: UnknownInlinedFun (pk11slot.c:452) ==30095==by 0x1569303E: PK11_FreeSlot (pk11slot.c:489) ==30095==by 0x15695F0B: UnknownInlinedFun (pk11util.c:923) ==30095==by 0x15695F0B: SECMOD_DestroyModule (pk11util.c:885) ==30095==by 0x1565E1CC: UnknownInlinedFun (pk11util.c:969) ==30095==by 0x1565E1CC: UnknownInlinedFun (pk11util.c:984) ==30095==by 0x1565E1CC: UnknownInlinedFun (pk11util.c:68) ==30095==by 0x1565E1CC: nss_Shutdown (nssinit.c:1163) ==30095==by 0x1565EEAF: UnknownInlinedFun (nssinit.c:1221) ==30095==by 0x1565EEAF: NSS_Shutdown (nssinit.c:1200) ==30095==by 0x20F933F8: ??? (in /usr/lib64/libpoppler.so.124.0.0) ==30095==by 0x65DA0C4: __run_exit_handlers (exit.c:113) ==30095==by 0x65DA24F: exit (exit.c:143) ==30095==by 0x65C15B6: (below main) (libc_start_call_main.h:74) ==30095== Address 0x10 is not stack'd, malloc'd or (recently) free'd ==30095== Invalid read of size 4 ==30095==at 0x662D2B0: __pthread_mutex_unlock_full (pthread_mutex_unlock.c:114) ==30095==by 0x81B1349: QtWaylandClient::QWaylandDisplay::~QWaylandDisplay() (qwaylanddisplay.cpp:384) ==30095==by 0x81B1948: QtWaylandClient::QWaylandDisplay::~QWaylandDisplay() (qwaylanddisplay.cpp:385) ==30095==by 0x819FF68: QtWaylandClient::QWaylandIntegration::~QWaylandIntegration() (qwaylandintegration.cpp:132) ==30095==by 0x5764FC6: QGuiApplicationPrivate::~QGuiApplicationPrivate() (qguiapplication.cpp:1731) ==30095==by 0x50A9F58: QApplicationPrivate::~QApplicationPrivate() (qapplication.cpp:163) ==30095==by 0x11C255: main (main.cpp:103) In gdb: (thread 1) #0 ___pthread_mutex_trylock (mutex=0x0) at pthread_mutex_trylock.c:33 #1 0x7fffc683470a in NativeLockMutex(void*) () at /usr/lib64/libpkcs11-dnie.so #2 0x7fffc6828c22 in C_CloseAllSessions () at /usr/lib64/libpkcs11-dnie.so #3 0x7fffc732903f in PK11_DestroySlot (slot=) at ../pk11wrap/pk11slot.c:452 #4 PK11_FreeSlot (slot=slot@entry=0x558c9970) at ../pk11wrap/pk11slot.c:489 #5 0x7fffc732bf0c in SECMOD_DestroyModule (module=0x558f61c0) at ../pk11wrap/pk11util.c:923 #6 SECMOD_DestroyModule (module=0x558f61c0) at ../pk11wrap/pk11util.c:885 #7 0x7fffc72f41cd in SECMOD_DestroyModuleListElement (element=0x5603c6a0) at ../pk11wrap/pk11util.c:969 #8 SECMOD_DestroyModuleList (list=) at ../pk11wrap/pk11util.c:984 #9 SECMOD_Shutdown () at ../pk11wrap/pk11util.c:68 #10 nss_Shutdown () at /usr/src/debug/mozilla-nss-3.82-1.2.x86_64/nss/lib/nss/nssinit.c:1163 #11 0x7fffc72f4eb0 in NSS_Shutdown () at /usr/src/debug/mozilla-nss-3.82-1.2.x86_64/nss/lib/nss/nssinit.c:1221 #12 NSS_Shutdown () at /usr/src/debug/mozilla-nss-3.82-1.2.x86_64/nss/lib/nss/nssinit.c:1200 #13 0x7fffc76453f9 in shutdownNss() () at /usr/src/debug/poppler-22.09.0-1.1.x86_64/poppler/SignatureHandler.cc:268 #14 0x75e450c5 in __run_exit_handlers (status=0, listp=0x75fea820 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:113 #15 0x75e45250 in __GI_exit (status=) at exit.c:143 #16 0x75e2c5b7 in __libc_start_call_main (main=main@entry=0x55566ae0 , argc=argc@entry=2, argv=argv@entry=0x7fffd1e8) at ../sysdeps/nptl/libc_start_call_main.h:74 #17 0x75e2c679 in __libc_start_main_impl (main=0x55566ae0 , argc=2, argv=0x7fffd1e8, init=, fini=, rtld_fini=, stack_end=0x7fffd1d8) at ../csu/libc-start.c:381 #18 0x55568d45 in _start () at ../sysdeps/x86_64/start.S:115 (thread 2) #0 0x75f0ba8f in __GI___poll (fds=0x7fffec0053c0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x74d20d7e in g_main_context_poll (priority=, n_fds=3, fds=0x7fffec0053c0, timeout=, context=0x7fffec001cf0) at ../glib/gmain.c:4543 #2 g_main_context_iterate (context=context@entry=0x7fffec001cf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4233 #3 0x74d20e9c in g_main_context_iteration (context=0x7fffec001cf0, may_block=1) at ../glib/gmai
[kwin] [Bug 459777] New: Starting LibreOffice Calc is shown with a window of aprox. 10px*50px in wayland
https://bugs.kde.org/show_bug.cgi?id=459777 Bug ID: 459777 Summary: Starting LibreOffice Calc is shown with a window of aprox. 10px*50px in wayland Classification: Plasma Product: kwin Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: jtam...@gmail.com CC: isma...@gmail.com Target Milestone: --- Created attachment 152493 --> https://bugs.kde.org/attachment.cgi?id=152493=edit Too small to be noticed. SUMMARY LibreOffice Calc (almost everytime) starts with a window that is smaller than the minimum set in a rule for all windows, in fact once changed its size the rule is applied. I know the program is started and can change it's size, but other people do not see the mini window and try to start the program again and again. STEPS TO REPRODUCE 0. Using Plastik as window decoration (do not know if it affects or no). 1. Start LibreOffice Calc OBSERVED RESULT See the screen snapshot. EXPECTED RESULT At least the minimum size stablished in the minimum size rule for every window. SOFTWARE/OS VERSIONS KDE Frameworks : Version 5.98.0 Qt Version 5.15.5 (built against 5.15.5) The wayland windowing system -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455406] New: Unable to fill a Form from Hacienda
https://bugs.kde.org/show_bug.cgi?id=455406 Bug ID: 455406 Summary: Unable to fill a Form from Hacienda Product: okular Version: 22.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY Unable to fill the Model 145 of Hacienda. https://www.agenciatributaria.es/static_files/Sede/Procedimiento_ayuda/G603/mod145_es_es.pdf STEPS TO REPRODUCE 1. Open Okular, open file and use the url. 2. An error message appears: ESTE DOCUMENTO HA SIDO ALTERADO. No es posible abrir este documento. Recuerde que la AEAT facilita los documentos PDF "como están", y no está permitido realizar modificaciones a su estructura. 3. Press in Show Forms. Only the "Rellenar Formulario" button is clickable but does nothing. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 453820] New: Crash in bt::CircularBuffer::read
https://bugs.kde.org/show_bug.cgi?id=453820
Bug ID: 453820
Summary: Crash in bt::CircularBuffer::read
Product: ktorrent
Version: 22.04.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: joris.guis...@gmail.com
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: ktorrent (22.04.0)
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.18.0-rc5-2.g1b401d7-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Nothing special. It just crashed, probably because something received from
internet.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __memmove_sse2_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:592
#7 0x7f3e741c2b38 in memcpy (__len=384, __src=,
__dest=0x100055ab5af3b3bc) at /usr/include/bits/string_fortified.h:29
#8 bt::CircularBuffer::read(unsigned char*, unsigned int)
(this=0x55ab5ff001d0, ptr=0x100055ab5af3b3bc , max_len=) at
/usr/src/debug/libktorrent-22.04.0-1.1.x86_64/src/util/circularbuffer.cpp:38
#9 0x7f3e74256eff in utp::PacketBuffer::fillData(bt::CircularBuffer&,
unsigned int) (this=0x7f3e477fd540, cbuf=..., to_read=384) at
/usr/src/debug/libktorrent-22.04.0-1.1.x86_64/src/utp/packetbuffer.cpp:67
#10 0x7f3e7425399b in utp::Connection::sendPackets() (this=0x55ab5ff001a0)
at /usr/src/debug/libktorrent-22.04.0-1.1.x86_64/src/utp/connection.cpp:403
#11 0x7f3e74254018 in utp::Connection::handlePacket(utp::PacketParser
const&, QSharedPointer) (this=0x55ab5ff001a0, parser=...,
packet=...) at
/usr/src/debug/libktorrent-22.04.0-1.1.x86_64/src/utp/connection.cpp:171
#12 0x7f3e74254d16 in
utp::UTPServer::handlePacket(QSharedPointer, net::Address const&)
(this=0x55ab556cf340, buffer=..., addr=) at
/usr/src/debug/libktorrent-22.04.0-1.1.x86_64/src/utp/utpserver.cpp:321
#13 0x7f3e74250857 in
utp::UTPServer::Private::dataReceived(QSharedPointer, net::Address
const&) (this=0x55ab5568f040, buffer=..., addr=...) at
/usr/src/debug/libktorrent-22.04.0-1.1.x86_64/src/utp/utpserver.cpp:183
#14 0x7f3e741d6330 in net::ServerSocket::readyToRead(int)
(this=0x55ab556bf680) at
/usr/src/debug/libktorrent-22.04.0-1.1.x86_64/src/net/serversocket.cpp:133
#15 0x7f3e72311453 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7f3e477fd890, r=0x55ab556bf680, this=0x7f3e480147c0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x55ab556bf0c0,
signal_index=3, argv=0x7f3e477fd890) at kernel/qobject.cpp:3886
#17 0x7f3e7230a7af in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55ab556bf0c0, m=m@entry=0x7f3e725b0880
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f3e477fd890)
at kernel/qobject.cpp:3946
#18 0x7f3e7231483f in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
(this=this@entry=0x55ab556bf0c0, _t1=..., _t2=, _t3=...) at
.moc/moc_qsocketnotifier.cpp:178
#19 0x7f3e7231503b in QSocketNotifier::event(QEvent*) (this=0x55ab556bf0c0,
e=0x7f3e477fd9b0) at kernel/qsocketnotifier.cpp:302
#20 0x7f3e72fa5b0f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55ab556bf0c0, e=0x7f3e477fd9b0) at
kernel/qapplication.cpp:3632
#21 0x7f3e722dab5a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55ab556bf0c0, event=0x7f3e477fd9b0) at
kernel/qcoreapplication.cpp:1064
#22 0x7f3e72332e6d in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=source@entry=0x7f3e38004840) at
kernel/qeventdispatcher_glib.cpp:107
#23 0x7f3e7046e122 in g_main_dispatch (context=0x7f3e38000c30) at
../glib/gmain.c:3417
#24 g_main_context_dispatch (context=0x7f3e38000c30) at ../glib/gmain.c:4135
#25 0x7f3e7046e4b8 in g_main_context_iterate
(context=context@entry=0x7f3e38000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4211
#26 0x7f3e7046e56f in g_main_context_iteration (context=0x7f3e38000c30,
may_block=1) at ../glib/gmain.c:4276
#27 0x7f3e72332326 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3e38000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#28 0x7f3e722d955b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3e477fdbc0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7f3e720f4cce in QThread::exec() (this=) at
[kwin] [Bug 452726] 100% cpu usage of kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=452726 --- Comment #4 from Jaime Torres --- Another workaround, apart from disabling the cursor animation, seems to be changing the window decorations to plastik. Apparently it is not affected. The maximum peaks I get so far is 20% CPU usage.. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453220] New: Crash trying to change config of plugin execute command
https://bugs.kde.org/show_bug.cgi?id=453220
Bug ID: 453220
Summary: Crash trying to change config of plugin execute
command
Product: kde
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: kdeconnect-settings (22.04.0)
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.18.0-rc4-1.g4bd-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Just opening the Execute command to try to add another command, currently only
the suspend command is enabled.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Preferencias de KDE Connect (kdeconnect-settings), signal:
Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f483fd911c9 in std::__uniq_ptr_impl >::_M_ptr() const (this=) at /usr/include/c++/11/bits/unique_ptr.h:173
#7 std::unique_ptr >::get() const (this=)
at /usr/include/c++/11/bits/unique_ptr.h:422
#8 std::unique_ptr >::operator->() const (this=) at /usr/include/c++/11/bits/unique_ptr.h:416
#9 qGetPtrHelper >
const>(std::unique_ptr > const&) (ptr=) at
/usr/include/qt5/QtCore/qglobal.h:1143
#10 KSycocaEntry::d_func() const (this=) at
/usr/src/debug/kservice-5.93.0-1.1.x86_64/src/sycoca/ksycocaentry.h:139
#11 KSycocaEntry::property(QString const&) const (this=0x0, name=...) at
/usr/src/debug/kservice-5.93.0-1.1.x86_64/src/sycoca/ksycocaentry.cpp:104
#12 0x7f481f0b8424 in KdeConnectPluginKcm::KdeConnectPluginKcm(QWidget*,
QList const&, QString const&) (this=this@entry=0x55903cb53d30,
parent=parent@entry=0x55903c978ef0, args=..., componentName=...,
this=, parent=, args=,
componentName=) at
/usr/src/debug/kdeconnect-kde-22.04.0-1.1.x86_64/kcmplugin/kdeconnectpluginkcm.cpp:26
#13 0x7f481f102339 in RunCommandConfig::RunCommandConfig(QWidget*,
QList const&) (args=..., parent=0x55903c978ef0, this=0x55903cb53d30)
at
/usr/src/debug/kdeconnect-kde-22.04.0-1.1.x86_64/plugins/runcommand/runcommand_config.cpp:29
#14 KPluginFactory::createInstance(QWidget*,
QObject*, QList const&) (parentWidget=,
parent=, args=...) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:875
#15 0x7f483ff44ce2 in KPluginFactory::create(char const*, QWidget*,
QObject*, QList const&, QString const&) (this=0x55903cbef5f0,
iface=0x7f483f5e79a0 "KCModule",
parentWidget=0x55903c978ef0, parent=0x55903c978ef0, args=..., keyword=...) at
/usr/src/debug/kcoreaddons-5.93.0-1.1.x86_64/src/lib/plugin/kpluginfactory.cpp:232
#16 0x7f48400220d9 in KPluginFactory::create(QString const&,
QObject*, QList const&) (args=..., parent=0x55903c978ef0,
keyword=..., this=0x55903cbef5f0) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:936
#17 KCModuleLoader::loadModule(KPluginMetaData const&, QWidget*,
QList const&) (metaData=..., parent=0x55903c978ef0, args=...) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kcmoduleloader.cpp:98
#18 0x7f4840024cdd in KCModuleProxyPrivate::loadModule()
(this=0x7f48280055c0) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kcmoduleproxy.cpp:119
#19 0x7f4840025308 in KCModuleProxy::realModule() const (this=) at /usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kcmoduleproxy.cpp:59
#20 0x7f48400380c9 in PluginDelegate::configure(QModelIndex const&)
(this=this@entry=0x55903c7ee530, index=) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kpluginwidget.cpp:486
#21 0x7f484003887b in PluginDelegate::slotConfigureClicked()
(this=0x55903c7ee530) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kpluginwidget.cpp:471
#22 0x7f483eb11453 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffc009e96f0, r=0x55903c7ee530, this=0x55903c559930) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate(QObject*, int, void**) (sender=0x55903c86c3f0,
signal_index=9, argv=0x7ffc009e96f0) at kernel/qobject.cpp:3886
#24 0x7f483eb0a7af in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55903c86c3f0, m=m@entry=0x7f483fcc5180
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffc009e96f0)
at kernel/qobject.cpp:3946
#25 0x7f483f8990d2 in QAbstractButton::clicked(bool)
(this=this@entry=0x55903c86c3f0, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#26 0x7f483f89934a in QAbstractButtonPrivate::emitClicked()
(this=0x55903c842ab0) at widgets/qabstractbutton.cpp:415
#27 0x7f483f89af10 in QAbstractButtonPrivate::click() (this=0x55903c842ab0)
at widgets/qabstractbutton.cpp:408
#28 0x7f483f89b133 in QAbstractButton::mouseReleaseEvent(QMouseEvent*)
[kwin] [Bug 452726] 100% cpu usage of kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=452726 --- Comment #1 from Jaime Torres --- Created attachment 148215 --> https://bugs.kde.org/attachment.cgi?id=148215=edit The perf data in txt format -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452726] New: 100% cpu usage of kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=452726 Bug ID: 452726 Summary: 100% cpu usage of kwin_wayland Product: kwin Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY The elastic launch cursor animation for an application start makes kwin_wayland to use 100% of one cpu. I've changed the cursor to remove the animation and this 100% cpu issue is gone. STEPS TO REPRODUCE 1. have two wayland sessions with two different users (for example in Ctrl+Alt+F2 and Ctrl+Alt+F3) 2. have in the user of Ctrl+F2 firefox with several tabs and windows 3. have configured the elastic cursor animation for notification launching an app 4. have top or similar running in the other session. 5. launch firefox, and switch inmediately to the other session (Ctrl+Alt+F3) OBSERVED RESULT I get always 100% kwin_wayland cpu usage. EXPECTED RESULT Normal cpu usage. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220411 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.1-1.g47fa9ec-default (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Phenom(tm) II X6 1100T Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD JUNIPER ADDITIONAL INFORMATION Information from perf record -g -p pid and then perf report -s srcline Samples: 617K of event 'cycles', Event count (approx.): 343103171448 Children Self Source:Line + 93.26%41.66% ??:0 + + 25.04% 0.00% ppoll+139825755533488 + 19.92% 0.00% QSocketNotifier::qt_metacast+139825763225600 + 17.25% 0.00% recvmsg+139825755533409 + 15.87% 0.00% QEventDispatcherUNIXPrivate::~QEventDispatcherUNIXPrivate+139825763225600 +3.59% 0.00% QHashData::nextNode+139825763225627 +3.59% 3.59% qhash.cpp:595 + 3.06% 0.00% QSocketNotifier::activated+139825763225695 +2.67% 0.00% QEventDispatcherUNIX::processEvents+139825763226503 +2.32% 0.00% QEventDispatcherUNIX::processEvents+139825763225654 +1.73% 1.73% qobjectdefs_impl.h:411 + 1.72% 1.72% atomic_base.h:880 +1.53% 0.00% wl_display_flush_clients+139825749340195 +1.53% 1.53% wl_display_flush_clients+35 + 1.42% 0.00% wl_display_flush_clients+139825749340236 +1.42% 1.42% wl_display_flush_clients+76
[ktorrent] [Bug 452654] New: crash receiving a packet
https://bugs.kde.org/show_bug.cgi?id=452654 Bug ID: 452654 Summary: crash receiving a packet Product: ktorrent Version: 21.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: jtam...@gmail.com Target Milestone: --- Application: ktorrent (21.12.3) Qt Version: 5.15.2 Frameworks Version: 5.93.0 Operating System: Linux 5.18.0-rc2-3.gd8f6a40-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Nothing inusual, it was just waiting for a magnet and serving torrents. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault [KCrash Handler] #4 0x7f806d28bca2 in utp::RemoteWindow::packetReceived(utp::Header const*, utp::SelectiveAck const*, utp::Retransmitter*) (this=0x7f7fdc398700, hdr=0x7f80515fd608, sack=0x7f80515fd620, conn=0x564b17976160) at /usr/src/debug/libktorrent-21.12.3-1.1.x86_64/src/utp/remotewindow.cpp:58 #5 0x7f806d28de84 in utp::Connection::handlePacket(utp::PacketParser const&, QSharedPointer) (this=0x564b17976150, parser=..., packet=...) at /usr/src/debug/libktorrent-21.12.3-1.1.x86_64/src/utp/connection.cpp:120 #6 0x7f806d28e7e6 in utp::UTPServer::handlePacket(QSharedPointer, net::Address const&) (this=0x564b11fadce0, buffer=..., addr=) at /usr/src/debug/libktorrent-21.12.3-1.1.x86_64/src/utp/utpserver.cpp:321 #7 0x7f806d280de7 in utp::UTPServer::Private::dataReceived(QSharedPointer, net::Address const&) (this=0x564b11f6e120, buffer=..., addr=...) at /usr/src/debug/libktorrent-21.12.3-1.1.x86_64/src/utp/utpserver.cpp:183 #8 0x7f806d20c2e0 in net::ServerSocket::readyToRead(int) (this=0x564b11f77720) at /usr/src/debug/libktorrent-21.12.3-1.1.x86_64/src/net/serversocket.cpp:133 #9 0x7f806b311503 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7f80515fd850, r=0x564b11f77720, this=0x7f804800c0a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate(QObject*, int, void**) (sender=0x564b11fa13c0, signal_index=3, argv=0x7f80515fd850) at kernel/qobject.cpp:3886 #11 0x7f806b30a9cf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x564b11fa13c0, m=m@entry=0x7f806b5b0ac0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f80515fd850) at kernel/qobject.cpp:3946 #12 0x7f806b3148df in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x564b11fa13c0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #13 0x7f806b3150db in QSocketNotifier::event(QEvent*) (this=0x564b11fa13c0, e=0x7f80515fd970) at kernel/qsocketnotifier.cpp:302 #14 0x7f806bfa5a7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x564b11fa13c0, e=0x7f80515fd970) at kernel/qapplication.cpp:3632 #15 0x7f806b2dae3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x564b11fa13c0, event=0x7f80515fd970) at kernel/qcoreapplication.cpp:1064 #16 0x7f806b332f3d in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=source@entry=0x7f8034004840) at kernel/qeventdispatcher_glib.cpp:107 #17 0x7f8069471122 in g_main_dispatch (context=0x7f8034000c30) at ../glib/gmain.c:3417 #18 g_main_context_dispatch (context=0x7f8034000c30) at ../glib/gmain.c:4135 #19 0x7f80694714b8 in g_main_context_iterate (context=context@entry=0x7f8034000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4211 #20 0x7f806947156f in g_main_context_iteration (context=0x7f8034000c30, may_block=1) at ../glib/gmain.c:4276 #21 0x7f806b332384 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8034000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f806b2d983b in QEventLoop::exec(QFlags) (this=this@entry=0x7f80515fdb80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f806b0f4d7e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x7f806b0f5eef in QThreadPrivate::start(void*) (arg=0x564b11f6d500) at thread/qthread_unix.cpp:331 #25 0x7f806a8a42ba in start_thread (arg=) at pthread_create.c:442 #26 0x7f806a92e460 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 7 (Thread 0x7f8051dff640 (LWP 5146) "Qt bearer threa"): #1 0x7f806947144e in g_main_context_poll (priority=, n_fds=1, fds=0x7f80400029e0, timeout=, context=0x7f804c30) at ../glib/gmain.c:4516 #2 g_main_context_iterate (context=context@entry=0x7f804c30, block=block@entry=1,
[kdeconnect] [Bug 451190] New: Crash after coming back from another plasma session after one night
https://bugs.kde.org/show_bug.cgi?id=451190
Bug ID: 451190
Summary: Crash after coming back from another plasma session
after one night
Product: kdeconnect
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: kdeconnectd (21.12.2)
Qt Version: 5.15.2
Frameworks Version: 5.91.0
Operating System: Linux 5.17.0-rc5-1.ga9b2c1d-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I do not know who makes almost all X11 programs stop when there are two
sessions on the same display, something that didn't happen before systemd
times. (I've had to come back to X11 as Wayland likes to change to a display
frequency out of range and I do not know how to recover from there).
It crashed after coming back to one X11 (Ctrl+Alt+F7) plasma session from
another X11 plasma session (Ctrl+Alt+F8) after one night in the other X11
session (Ctrl+Alt+F8).
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Demonio de KDE Connect (kdeconnectd), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7eff05d662fc in std::__atomic_base::load(std::memory_order)
const (__m=std::memory_order_relaxed, this=0x81) at
/usr/include/c++/11/bits/atomic_base.h:481
#7 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=...)
at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#8 QBasicAtomicInteger::loadRelaxed() const (this=0x81) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#9 QtPrivate::RefCount::ref() (this=0x81) at
../../include/QtCore/../../src/corelib/tools/qrefcount.h:55
#10 QMap::QMap(QMap const&) (other=...,
this=0x7ffe9de58ce0) at ../../include/QtCore/../../src/corelib/tools/qmap.h:631
#11 qVariantToHelper > (handlerManager=,
d=) at kernel/qvariant.cpp:2665
#12 QVariant::toMap() const (this=0x55dbd62a22c8) at kernel/qvariant.cpp:2721
#13 0x7efef81af378 in () at
/usr/lib64/qt5/plugins/kdeconnect/kdeconnect_connectivity_report.so
#14 0x7eff072e6e01 in Device::privateReceivedPacket(NetworkPacket const&)
() at /lib64/libkdeconnectcore.so.21
#15 0x7eff05d4f503 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffe9de59150, r=0x55dbd6093d10, this=0x55dbd64bff70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x55dbd61f6d00,
signal_index=7, argv=0x7ffe9de59150) at kernel/qobject.cpp:3886
#17 0x7eff072d7bfd in LanDeviceLink::dataReceived() () at
/lib64/libkdeconnectcore.so.21
#18 0x7eff05d4f503 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffe9de59230, r=0x55dbd61f6d00, this=0x55dbd6265ab0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#19 doActivate(QObject*, int, void**) (sender=0x55dbd6475330,
signal_index=3, argv=0x7ffe9de59230) at kernel/qobject.cpp:3886
#20 0x7eff072d0114 in SocketLineReader::dataReceived() () at
/lib64/libkdeconnectcore.so.21
#21 0x7eff05d4f503 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffe9de59340, r=0x55dbd6475330, this=0x55dbd6437b90) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 doActivate(QObject*, int, void**) (sender=0x55dbd61f56d0,
signal_index=3, argv=0x7ffe9de59340) at kernel/qobject.cpp:3886
#23 0x7eff05d489cf in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55dbd61f56d0, m=m@entry=0x7eff05feb280
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3946
#24 0x7eff05c47250 in QIODevice::readyRead()
(this=this@entry=0x55dbd61f56d0) at .moc/moc_qiodevice.cpp:190
#25 0x7eff05470705 in QSslSocketBackendPrivate::transmit()
(this=0x55dbd5e59340) at ssl/qsslsocket_openssl.cpp:1162
#26 0x7eff05d4f538 in doActivate(QObject*, int, void**)
(sender=0x55dbd64ee2c0, signal_index=3, argv=0x7ffe9de5a4b0) at
kernel/qobject.cpp:3898
#27 0x7eff05d489cf in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55dbd64ee2c0, m=m@entry=0x7eff05feb280
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3946
#28 0x7eff05c47250 in QIODevice::readyRead()
(this=this@entry=0x55dbd64ee2c0) at .moc/moc_qiodevice.cpp:190
#29 0x7eff05427eef in QAbstractSocketPrivate::emitReadyRead(int)
(channel=0, this=0x55dbd619cd40) at socket/qabstractsocket.cpp:1323
#30 QAbstractSocketPrivate::canReadNotification() (this=0x55dbd619cd40) at
socket/qabstractsocket.cpp:748
#31
[kdeconnect] [Bug 449276] kdeconnectd intermittent crash while in the background
https://bugs.kde.org/show_bug.cgi?id=449276 --- Comment #4 from Jaime Torres --- Created attachment 146854 --> https://bugs.kde.org/attachment.cgi?id=146854=edit New crash information added by DrKonqi kdeconnectd (21.12.2) using Qt 5.15.2 - What I was doing when the application crashed: Some minutes before the crash I just disabled in Android the notification syncronization plugin. -- Backtrace (Reduced): #6 0x7f795a553314 in (anonymous namespace)::constData (d=...) at kernel/qvariant.cpp:361 #7 qVariantToHelper > (handlerManager=, d=) at kernel/qvariant.cpp:2669 #8 QVariant::toMap() const (this=0x7f795c930e68) at kernel/qvariant.cpp:2721 #9 0x7f794ce45378 in ConnectivityReportPlugin::receivePacket(NetworkPacket const&) (np=, this=) at /usr/src/debug/kdeconnect-kde-21.12.2-1.1.x86_64/plugins/connectivity-report/connectivity_reportplugin.cpp:44 #10 ConnectivityReportPlugin::receivePacket(NetworkPacket const&) (this=, np=) at /usr/src/debug/kdeconnect-kde-21.12.2-1.1.x86_64/plugins/connectivity-report/connectivity_reportplugin.cpp:40 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 449276] kdeconnectd intermittent crash while in the background
https://bugs.kde.org/show_bug.cgi?id=449276 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 450135] New: kio crash after a send file stopped by lack of wifi signal and tried to send it again
https://bugs.kde.org/show_bug.cgi?id=450135
Bug ID: 450135
Summary: kio crash after a send file stopped by lack of wifi
signal and tried to send it again
Product: kdeconnect
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: plasmoid
Assignee: albertv...@gmail.com
Reporter: jtam...@gmail.com
Target Milestone: ---
SUMMARY
Application: kioslave5 (kioslave5), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f4ee65152d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f4ee64c5356 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f4ee64ae7d3 in __GI_abort () at abort.c:79
#10 0x7f4ee6758fe7 in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal (this=this@entry=0x7ffce01bf2e0,
msg=msg@entry=0x7f4ee6d723f0 "Fatal Error: Got cmd %d, while waiting for an
answer!") at global/qlogging.cpp:893
#12 0x7f4ee6ca7ef8 in KIO::SlaveBase::waitForAnswer (this=,
expected1=, expected2=, data=..., pCmd=) at /usr/src/debug/kio-5.90.0-2.1.x86_64/src/core/slavebase.cpp:1112
#13 0x7f4ee6cd8b45 in KIO::SlaveBase::canResume
(this=this@entry=0x7ffce01bf7d0, offset=546619392) at
/usr/src/debug/kio-5.90.0-2.1.x86_64/src/core/slavebase.cpp:1079
#14 0x7f4ee6dd5c5f in FileProtocol::put (this=0x7ffce01bf7c0, url=...,
_mode=-1, _flags=...) at
/usr/src/debug/kio-5.90.0-2.1.x86_64/src/ioslaves/file/file.cpp:535
#15 0x7f4ee6cde502 in KIO::SlaveBase::dispatch (this=0x7ffce01bf7d0,
command=68, data=...) at
/usr/src/debug/kio-5.90.0-2.1.x86_64/src/core/slavebase.cpp:1252
#16 0x7f4ee6cd9d16 in KIO::SlaveBase::dispatchLoop (this=0x7ffce01bf7d0) at
/usr/src/debug/kio-5.90.0-2.1.x86_64/src/core/slavebase.cpp:334
#17 0x7f4ee6dd4559 in kdemain (argc=, argv=)
at /usr/src/debug/kio-5.90.0-2.1.x86_64/src/ioslaves/file/file.cpp:91
#18 0x7f4ee6e2e362 in main (argc=5, argv=0x7ffce01bfa68) at
/usr/src/debug/kio-5.90.0-2.1.x86_64/src/kioslave/kioslave.cpp:141
[Inferior 1 (process 7450) detached]
I haven't tried to reproduce it, but what I did was:
1. Send a video file from android to linux over wifi
2. Loss wifi signal, the file was not send right (it did notify in android,
but kept waiting in linux)
3. Try to send the same file again.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220210
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.17.0-rc3-1.g335402f-default (64-bit)
Graphics Platform: X11
Processors: 6 × AMD Phenom(tm) II X6 1100T Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD JUNIPER
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 448222] New: An Spanish tilde confuses variable detection
https://bugs.kde.org/show_bug.cgi?id=448222
Bug ID: 448222
Summary: An Spanish tilde confuses variable detection
Product: kdev-python
Version: 5.7.211201
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: jtam...@gmail.com
Target Milestone: ---
SUMMARY
In this example python file, kdevelop assigns the green colour to
nombre_apellido, except in the second and third print, after the text with ú,
where only ombre_apellido is green, and the first n is black. It is coloured as
expected when removing the ú and it increases the number of black letters with
the number of ú in the text.
# -*- coding: utf-8 -*-
nombre_apellido = "nombre y apellido"
print("normal", nombre_apellido)
print("en minúsculas:", nombre_apellido.tolower())
print("en mayúsculas:", nombre_apellido.toupper())
print("normal", nombre_apellido)
EXPECTED RESULT
All nombre_apellido are completely green (or the corresponding colour) even in
print("en mayúúúsculas:", nombre_apellido.toupper())
SOFTWARE/OS VERSIONS
Versión 5.7.211200 (21.12.0)
KDE Frameworks :Versión 5.89.0
Qt: Versión 5.15.2 (compilado con 5.15.2)
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-ktexteditor] [Bug 435628] Crash trying to open a displaced closed folding marker
https://bugs.kde.org/show_bug.cgi?id=435628 --- Comment #6 from Jaime Torres --- > But it should not crash and one should be able to unfold the stuff, that > works, doesn't it? Unfortunately is not what I can see with the little file (and bigger ones).. When I try to unfold the for loop, it folds the method definition and if I unfold the method, the for loop is still folded. Folding and unfolding other parts doesn't help also. I can only see the for loop in the preview of the folded method. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 435628] Crash trying to open a displaced closed folding marker
https://bugs.kde.org/show_bug.cgi?id=435628
Jaime Torres changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #4 from Jaime Torres ---
I've seen how to reproduce it.
Create a trivial python program, for example:
class Test:
# line added
def __init__(self):
a = '''
Some text
'''
def test(self):
# line added
# line added
for i in range(10):
print('hello world')
with open('test.py') as f:
lines = f.read()
fold it in the for loop
save the session and close kate
modify the file with another editor and insert one blank line where there was
already one:
class Test:
# line added
def __init__(self):
a = '''
Some text
'''
def test(self):
# line added
# line added
for i in range(10):
print('hello world')
with open('test.py') as f:
lines = f.read()
Open kate and the folding is gone crazy (like in the attached screenshot). But
can not easily reproduce the crash.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-ktexteditor] [Bug 435628] Crash trying to open a displaced closed folding marker
https://bugs.kde.org/show_bug.cgi?id=435628 --- Comment #3 from Jaime Torres --- Created attachment 145233 --> https://bugs.kde.org/attachment.cgi?id=145233=edit Folding gone crazy -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 447634] New: Crash parsing python
https://bugs.kde.org/show_bug.cgi?id=447634
Bug ID: 447634
Summary: Crash parsing python
Product: kdevelop
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: kdevelop (5.7.211200 (21.12.0))
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.8-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Restarting from a previous crash. Probably reloaded all the open files.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f94201b4323 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f9420164366 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f942014d7d3 in __GI_abort () at abort.c:79
#10 0x7f94203e6976 in __gnu_cxx::__verbose_terminate_handler() () at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x7f94203f20fc in __cxxabiv1::__terminate(void (*)())
(handler=) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#12 0x7f94203f2167 in std::terminate() () at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58
#13 0x7f9420610411 in qTerminate() () at global/qglobal.cpp:3349
#14 0x7f9420611da2 in QThreadPrivate::start(void*) (arg=) at
thread/qthread_unix.cpp:341
#15 0x7f94201b2427 in start_thread (arg=) at
pthread_create.c:435
#16 0x7f942023b810 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 16 (Thread 0x7f93b9507640 (LWP 10434) "Queue(0x56272f0"):
#1 0x7f9420204107 in __GI___nanosleep (req=, rem=) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x7f9420887b6d in qt_nanosleep(timespec) (amount=...) at
kernel/qelapsedtimer_unix.cpp:195
#3 0x7f942064b760 in QThread::usleep(unsigned long)
(usecs=usecs@entry=500) at thread/qthread_unix.cpp:512
#4 0x7f941f1de5f4 in KDevelop::DUChainLock::lockForWrite(unsigned int)
(this=, timeout=0) at
/usr/src/debug/kdevelop5-21.12.0-1.1.x86_64/kdevplatform/language/duchain/duchainlock.cpp:158
#5 0x7f941f1de7ac in KDevelop::DUChainWriteLocker::lock()
(this=0x7f93b9504fc0) at
/usr/src/debug/kdevelop5-21.12.0-1.1.x86_64/kdevplatform/language/duchain/duchainlock.cpp:265
#6 KDevelop::DUChainWriteLocker::lock() (this=0x7f93b9504fc0) at
/usr/src/debug/kdevelop5-21.12.0-1.1.x86_64/kdevplatform/language/duchain/duchainlock.cpp:257
#7 0x7f941f1e0a00 in
KDevelop::DUChainWriteLocker::DUChainWriteLocker(KDevelop::DUChainLock*,
unsigned int) (this=this@entry=0x7f93b9504fc0,
duChainLock=duChainLock@entry=0x0, timeout=timeout@entry=0, this=, duChainLock=, timeout=) at
/usr/src/debug/kdevelop5-21.12.0-1.1.x86_64/kdevplatform/language/duchain/duchainlock.cpp:249
#8 0x7f93c9aa6a10 in
Python::DeclarationBuilder::visitVariableDeclaration(Python::Identifier*,
KDevelop::Declaration*, KDevelop::TypePtr,
Python::DeclarationBuilder::VisitVariableFlags) [clone .constprop.0]
(this=this@entry=0x7f930806bf40, node=0x7f9345434330, type=...,
flags=Python::DeclarationBuilder::NoVisitVariableFlags, previous=) at
/usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/declarationbuilder.cpp:220
#9 0x7f93c9a97979 in
Python::DeclarationBuilder::visitArguments(Python::ArgumentsAst*)
(this=0x7f930806bf40, node=0x7f9344256060) at
/usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/declarationbuilder.cpp:1768
#10 0x7f93c9a891cb in
Python::ContextBuilder::visitFunctionArguments(Python::FunctionDefinitionAst*)
(this=0x7f930806bf40, node=0x7f930831fa10) at
/usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/contextbuilder.cpp:430
#11 0x7f93c9a9b310 in
Python::DeclarationBuilder::visitFunctionDefinition(Python::FunctionDefinitionAst*)
(this=0x7f930806bf40, node=0x7f930831fa10) at
/usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/declarationbuilder.cpp:1495
#12 0x7f93c9a93611 in non-virtual thunk to
Python::DeclarationBuilder::visitNode(Python::Ast*) () at
/usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/declarationbuilder.cpp:1860
#13 0x7f93c9a99a38 in
Python::AstVisitor::visitNodeList(QList const&)
(l=..., this=0x7f930806c128) at
/usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/parser/astvisitor.h:35
#14
Python::DeclarationBuilder::visitClassDefinition(Python::ClassDefinitionAst*)
(this=0x7f930806bf40,
[kdevelop] [Bug 415407] Kdevelop crash at start
https://bugs.kde.org/show_bug.cgi?id=415407 --- Comment #2 from Jaime Torres --- Created attachment 144923 --> https://bugs.kde.org/attachment.cgi?id=144923=edit New crash information added by DrKonqi kdevelop (5.7.211200 (21.12.0)) using Qt 5.15.2 - What I was doing when the application crashed: Restarting from another crash and probably reloading all the open files before duchain reached 100%. -- Backtrace (Reduced): #6 0x7ff849753e62 in KDevelop::IndexedIdentifier::identifier() const (this=0x722e6ff7ecc7373a) at /usr/src/debug/kdevelop5-21.12.0-1.1.x86_64/kdevplatform/language/duchain/identifier.cpp:1392 #7 0x7ff849741bf6 in KDevelop::Declaration::identifier() const (this=) at /usr/src/debug/kdevelop5-21.12.0-1.1.x86_64/kdevplatform/language/duchain/declaration.h:552 #8 0x7ff7effd8fd3 in Python::DeclarationBuilder::addArgumentTypeHints(Python::CallAst*, KDevelop::DUChainPointer) (this=this@entry=0x7ff7cccbb030, node=node@entry=0x7ff7ccb57e00, called=...) at /usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/declarationbuilder.cpp:1031 #9 0x7ff7effd9409 in Python::DeclarationBuilder::visitCall(Python::CallAst*) (this=0x7ff7cccbb030, node=0x7ff7ccb57e00) at /usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/declarationbuilder.cpp:1089 #10 0x7ff7effd9611 in non-virtual thunk to Python::DeclarationBuilder::visitNode(Python::Ast*) () at /usr/src/debug/kdevelop5-plugin-python3-21.12.0-1.1.x86_64/duchain/declarationbuilder.cpp:1860 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415407] Kdevelop crash at start
https://bugs.kde.org/show_bug.cgi?id=415407 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418300] Crash using keyboard to rename folder after folder
https://bugs.kde.org/show_bug.cgi?id=418300 --- Comment #3 from Jaime Torres --- FYI: I'm still unable to start dolphin under valgrind. At least I know where the problem is: The included PCRE versión in Qt5, which uses previous versions of https://github.com/zherczeg/sljit which causes, with development version of valgrind, the errors: ==32395== Conditional jump or move depends on uninitialised value(s) ==32395==at 0xF034DED: ??? (in /memfd:sljit (deleted)) ==32395==by 0xDF671F9: ??? before crashing. Any other Qt program that doesn't uses PCRE just runs as it used to. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 445565] New: crash while editing python
https://bugs.kde.org/show_bug.cgi?id=445565
Bug ID: 445565
Summary: crash while editing python
Product: kdevelop
Version: 5.6.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: kdevelop (5.6.2)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-2-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I was just editing a member, deleting something old and starting to write
something new.
I noticed that it stopped to refresh and react to keystrokes, and then the
crash.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x1008) at
/usr/include/c++/11/bits/atomic_base.h:836
#7 std::atomic::load
(__m=std::memory_order_relaxed, this=0x1008) at
/usr/include/c++/11/atomic:570
#8
QAtomicOps::loadRelaxed
(_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#9 QBasicAtomicPointer::loadRelaxed
(this=0x1008) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#10 QObjectPrivate::isSignalConnected (this=this@entry=0x557013836f00,
signalIndex=signalIndex@entry=0, checkDeclarative=checkDeclarative@entry=true)
at kernel/qobject.cpp:459
#11 0x7fa7165b33d8 in QObject::~QObject (this=this@entry=0x557013836ea0,
__in_chrg=) at kernel/qobject.cpp:991
#12 0x7fa714edce7d in
KDevelop::PersistentMovingRangePrivate::~PersistentMovingRangePrivate
(this=, this=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/build/kdevplatform/language/KDevPlatformLanguage_autogen/3HAKN7MTYQ/../../../../../kdevplatform/language/editor/persistentmovingrangeprivate.h:30
#13 KDevelop::PersistentMovingRangePrivate::~PersistentMovingRangePrivate
(this=, this=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/build/kdevplatform/language/KDevPlatformLanguage_autogen/3HAKN7MTYQ/../../../../../kdevplatform/language/editor/persistentmovingrangeprivate.h:30
#14 0x7fa6b742e803 in
QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer
(this=, this=) at
/usr/include/qt5/QtCore/qshareddata.h:184
#15
QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer
(this=, this=) at
/usr/include/qt5/QtCore/qshareddata.h:184
#16 QList
>::node_destruct (to=0x5570139749f0, from=0x5570139610b0, this=)
at /usr/include/qt5/QtCore/qlist.h:526
#17 QList
>::dealloc(QListData::Data*) [clone .constprop.0] (data=0x5570139610a0,
this=) at /usr/include/qt5/QtCore/qlist.h:921
#18 0x7fa6b74295d8 in
QList >::~QList
(this=, this=) at
/usr/include/qt5/QtCore/qlist.h:871
#19 QList
>::~QList (this=, this=) at
/usr/include/qt5/QtCore/qlist.h:871
#20 ViewHighlights::~ViewHighlights (this=, this=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/plugins/contextbrowser/contextbrowser.h:85
#21 QMapNodeBase::callDestructorIfNecessary (t=...) at
/usr/include/qt5/QtCore/qmap.h:100
#22 QMapNode::destroySubTree
(this=0x557002d87060) at /usr/include/qt5/QtCore/qmap.h:125
#23 QMapData::destroy (this=0x556ffe5b5e70)
at /usr/include/qt5/QtCore/qmap.h:249
#24 0x7fa6b741fa25 in QMap::~QMap
(this=, this=) at
/usr/include/qt5/QtCore/qmap.h:338
#25 QMap::operator= (other=...,
this=0x556ff4d8ef40) at /usr/include/qt5/QtCore/qmap.h:349
#26 QMap::clear (this=0x556ff4d8ef40) at
/usr/include/qt5/QtCore/qmap.h:656
#27 ContextBrowserPlugin::updateForView (this=this@entry=0x556ff4d8ef00,
view=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/plugins/contextbrowser/contextbrowser.cpp:839
#28 0x7fa6b7420b5c in ContextBrowserPlugin::updateViews
(this=0x556ff4d8ef00) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/plugins/contextbrowser/contextbrowser.cpp:925
#29 0x7fa7165b5043 in QtPrivate::QSlotObjectBase::call (a=0x7ffe48e07ef0,
r=0x556ff4d8ef00, this=0x556ff4e08dd0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#30 doActivate (sender=0x556ff4e08d10, signal_index=3,
argv=0x7ffe48e07ef0) at kernel/qobject.cpp:3886
#31 0x7fa7165ae50f in QMetaObject::activate (sender=,
m=m@entry=0x7fa716854c00 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe48e07ef0)
at kernel/qobject.cpp:3946
#32 0x7fa7165b8efa in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#33 0x7fa7165aaf0f in QObject::event (this=0x556ff4e08d10,
e=0x7ffe48e08070) at kernel/qobject.cpp:1336
#34 0x7fa717310a7f in QApplicationPrivate::notify_helper (this=, receiver=0x556ff4e08d10, e=0x7ffe48e08070) at
[akregator] [Bug 445038] New: Lost articles status when akregator is not closed ordered
https://bugs.kde.org/show_bug.cgi?id=445038 Bug ID: 445038 Summary: Lost articles status when akregator is not closed ordered Product: akregator Version: 5.18.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY When akregator is closed not in the right way, for example an interrupted session, a lot of already read articles are marked again as new, making it really hard to know which were already read. EXPECTED RESULT To lost as less articles states as possible. If I had only 10 new, after a session restore or not session restore, doesn't seem to matter, I can have more than 100 unread. KDE Frameworks Version 5.87.0 Qt Version 5.15.2 (built against 5.15.2) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 444732] New: Crash closing Marble while traveling around the world in the guided tour
https://bugs.kde.org/show_bug.cgi?id=444732
Bug ID: 444732
Summary: Crash closing Marble while traveling around the world
in the guided tour
Product: marble
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: marble-b...@kde.org
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: marble (2.2.20 (2.3 development version))
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.11-2-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
traveling around the world with the guided tour a second time.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Globo virtual Marble (marble), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7ff2862b in
qDeleteAll::const_iterator> (end=...,
begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320
#7 qDeleteAll > (c=..., c=...) at
/usr/include/qt5/QtCore/qalgorithms.h:328
#8 Marble::GeoDataContainerPrivate::~GeoDataContainerPrivate (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataContainer_p.h:39
#9 Marble::GeoDataDocumentPrivate::~GeoDataDocumentPrivate (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument_p.h:25
#10 Marble::GeoDataDocumentPrivate::~GeoDataDocumentPrivate (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument_p.h:25
#11 0x7ff28bbe13d9 in Marble::GeoDataFeature::~GeoDataFeature
(this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataFeature.cpp:76
#12 0x7ff28bbb81cd in Marble::GeoDataDocument::~GeoDataDocument
(this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument.cpp:50
#13 0x7ff28bbb822d in non-virtual thunk to
Marble::GeoDataDocument::~GeoDataDocument() () at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument.cpp:50
#14 0x7ff2862e in
qDeleteAll::const_iterator> (end=...,
begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320
#15 qDeleteAll > (c=..., c=...) at
/usr/include/qt5/QtCore/qalgorithms.h:328
#16 Marble::GeoDataContainerPrivate::~GeoDataContainerPrivate (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataContainer_p.h:39
#17 Marble::GeoDataDocumentPrivate::~GeoDataDocumentPrivate (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument_p.h:25
#18 Marble::GeoDataDocumentPrivate::~GeoDataDocumentPrivate (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument_p.h:25
#19 0x7ff28bbe13d9 in Marble::GeoDataFeature::~GeoDataFeature
(this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataFeature.cpp:76
#20 0x7ff28bbb81cd in Marble::GeoDataDocument::~GeoDataDocument
(this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument.cpp:50
#21 0x7ff28bcbfca8 in Marble::GeoDataDocument::~GeoDataDocument
(this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/geodata/data/GeoDataDocument.cpp:48
#22 Marble::GeoDataTreeModel::Private::~Private (this=,
this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/GeoDataTreeModel.cpp:89
#23 Marble::GeoDataTreeModel::~GeoDataTreeModel (this=,
this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/GeoDataTreeModel.cpp:117
#24 0x7ff28bc7397a in Marble::MarbleModelPrivate::~MarbleModelPrivate
(this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/MarbleModel.cpp:121
#25 Marble::MarbleModel::~MarbleModel (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/MarbleModel.cpp:202
#26 0x7ff28bc6744b in Marble::MarbleWidgetPrivate::~MarbleWidgetPrivate
(this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/MarbleWidget.cpp:111
#27 Marble::MarbleWidget::~MarbleWidget (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/MarbleWidget.cpp:162
#28 0x7ff28bc67499 in Marble::MarbleWidget::~MarbleWidget (this=, this=) at
/usr/src/debug/marble-21.08.2-1.1.x86_64/src/lib/marble/MarbleWidget.cpp:163
#29 0x7ff28a17a6de in QObjectPrivate::deleteChildren
(this=this@entry=0x559e1f60) at kernel/qobject.cpp:2104
#30 0x7ff28ad3ceb6 in QWidget::~QWidget (this=this@entry=0x559e1f871f10,
__in_chrg=) at kernel/qwidget.cpp:1522
#31 0x559e1eb9fd93 in Marble::ControlView::~ControlView
[kate] [Bug 440583] The editor window becomes unusable in wayland
https://bugs.kde.org/show_bug.cgi?id=440583
--- Comment #3 from Jaime Torres ---
A crash closing kate after reloading the view.
[KCrash Handler]
#6 0x55ff3106e373 in
qDeleteAll<__gnu_cxx::__normal_iterator > > >
(end=..., begin=0x55ff33a223f0) at /usr/include/qt5/QtCore/qalgorithms.h:320
#7 qDeleteAll > > (c=std::vector of length 1, capacity 16
= {...}) at /usr/include/qt5/QtCore/qalgorithms.h:328
#8 KateMDI::MainWindow::~MainWindow (__vtt_parm=,
this=, this=, __vtt_parm=) at
/usr/src/debug/kate-21.08.0-1.1.x86_64/kate/katemdi.cpp:778
#9 KateMainWindow::~KateMainWindow (this=, this=) at /usr/src/debug/kate-21.08.0-1.1.x86_64/kate/katemainwindow.cpp:203
#10 0x55ff31064340 in KateMainWindow::~KateMainWindow (this=, this=) at
/usr/src/debug/kate-21.08.0-1.1.x86_64/kate/katemainwindow.cpp:181
#11 KateApp::~KateApp (this=, this=) at
/usr/src/debug/kate-21.08.0-1.1.x86_64/kate/kateapp.cpp:113
#12 0x55ff3105ded4 in main (argc=, argv=) at
/usr/src/debug/kate-21.08.0-1.1.x86_64/kate/main.cpp:689
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 441524] Being able to have the favourites bar at the right.
https://bugs.kde.org/show_bug.cgi?id=441524 --- Comment #1 from Jaime Torres --- Created attachment 141031 --> https://bugs.kde.org/attachment.cgi?id=141031=edit the ability to swap pannels by configuration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441524] New: Being able to have the favourites bar at the right.
https://bugs.kde.org/show_bug.cgi?id=441524 Bug ID: 441524 Summary: Being able to have the favourites bar at the right. Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: jtam...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Sometimes the host does strange things to a virtual machine, and the upper left corner becomes inaccessible by mouse. Therefore, I have moved the Cascade Menu to the upper right corner. Sometimes clicking in the favourite icon becomes hard work as the mouse tends to pass over the menus first. If it is possible to move the favourites bar at the right of the menu (configurable, of course), this problem vanish. SOFTWARE/OS VERSIONS plasmashell 5.22.4 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 441463] New: There is an uncaught exception that stops ktorrent
https://bugs.kde.org/show_bug.cgi?id=441463 Bug ID: 441463 Summary: There is an uncaught exception that stops ktorrent Product: ktorrent Version: 21.08.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY There is an uncaugth exception somewhere (unfortunately I do not know the exception) and ktorrent freezes. It usually happens after 2 or 3 days running. msg=msg@entry=0x7f7e1c16ecf0 "Qt has caught an exception thrown from an event handler. Throwing\nexceptions from an event handler is not supported in Qt.\nYou must not let any exception whatsoever propagate through Qt code.\nIf that "...) at global/qlogging.cpp:656 SOFTWARE/OS VERSIONS KDE Frameworks 5.85.0 Qt 5.15.2 (compilado con 5.15.2) El sistema de ventanas wayland -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440583] The editor window becomes unusable in wayland
https://bugs.kde.org/show_bug.cgi?id=440583 --- Comment #1 from Jaime Torres --- Created attachment 140504 --> https://bugs.kde.org/attachment.cgi?id=140504=edit Strange behaviour -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440583] New: The editor window becomes unusable in wayland
https://bugs.kde.org/show_bug.cgi?id=440583 Bug ID: 440583 Summary: The editor window becomes unusable in wayland Product: kate Version: Git Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY The editor window becomes unusable STEPS TO REPRODUCE 1. Open a text file 2. Have some lines in the text file 3. Modify the file outside kate 4. Once you press reload on the "Documents modified on Disk" dialog, kate becomes unusable. OBSERVED RESULT * some lines are only rendered with the upper half part of the font. * some lines are fixed in the bottom of the editor window * I can't see the cursor any more. EXPECTED RESULT It works as before the file is modified outside kate. SOFTWARE/OS VERSIONS KDE Frameworks 5.85.0 Qt 5.15.2 (built against 5.15.2) The wayland windowing system kate Version 21.11.70 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439963] Crash in Breeze exiting kdevelop
https://bugs.kde.org/show_bug.cgi?id=439963 Jaime Torres changed: What|Removed |Added Product|kdevelop|Breeze Component|general |general Assignee|kdevelop-bugs-n...@kde.org |plasma-b...@kde.org Version|5.6.2 |5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439963] New: Crash in Breeze exiting kdevelop
https://bugs.kde.org/show_bug.cgi?id=439963 Bug ID: 439963 Summary: Crash in Breeze exiting kdevelop Product: kdevelop Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- Application: kdevelop (5.6.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.13.0-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was exiting kdevelop (in wayland). Kdevelop window became longer (vertical) than the screen. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fefee743040 (LWP 4742))] [KCrash Handler] #6 QMapDataBase::freeNodeAndRebalance (this=this@entry=0x5579c4fac100, z=z@entry=0x5579c8411f40) at tools/qmap.h:95 #7 0x7fefe40f07bb in QMapData >::deleteNode (z=0x5579c8411f40, this=0x5579c4fac100) at /usr/include/qt5/QtCore/qmap.h:281 #8 QMap >::erase (this=, it=...) at /usr/include/qt5/QtCore/qmap.h:967 #9 0x7fefe40f92b4 in Breeze::BaseDataMap::unregisterWidget (key=0x5579c82e7a10, this=0x5579c4ce8108) at /usr/src/debug/breeze-5.22.3-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezedatamap.h:84 #10 Breeze::WidgetStateEngine::unregisterWidget (object=0x5579c82e7a10, this=0x5579c4ce8090) at /usr/src/debug/breeze-5.22.3-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezewidgetstateengine.h:118 #11 Breeze::WidgetStateEngine::unregisterWidget (object=0x5579c82e7a10, this=0x5579c4ce8090) at /usr/src/debug/breeze-5.22.3-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezewidgetstateengine.h:112 #12 Breeze::WidgetStateEngine::qt_static_metacall (_o=0x5579c4ce8090, _a=0x7ffd34ee2140, _id=, _c=) at /usr/src/debug/breeze-5.22.3-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/moc_breezewidgetstateengine.cpp:74 #13 0x7ff00211cfe8 in doActivate (sender=0x5579c82e7a10, signal_index=0, argv=0x7ffd34ee2140) at kernel/qobject.cpp:3898 #14 0x7ff00211647f in QMetaObject::activate (sender=sender@entry=0x5579c82e7a10, m=m@entry=0x7ff0023ada40 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd34ee2140) at kernel/qobject.cpp:3946 #15 0x7ff00211652f in QObject::destroyed (this=this@entry=0x5579c82e7a10, _t1=, _t1@entry=0x5579c82e7a10) at .moc/moc_qobject.cpp:219 #16 0x7ff002ea5123 in QWidget::~QWidget (this=0x5579c82e7a10, __in_chrg=) at kernel/qwidget.cpp:1497 #17 0x7ff00301da89 in QStackedWidget::~QStackedWidget (this=0x5579c82e7a10, __in_chrg=) at widgets/qstackedwidget.cpp:147 #18 0x7ff00211067e in QObjectPrivate::deleteChildren (this=this@entry=0x5579c826b7a0) at kernel/qobject.cpp:2104 #19 0x7ff002ea4e66 in QWidget::~QWidget (this=this@entry=0x5579c82e7aa0, __in_chrg=) at kernel/qwidget.cpp:1522 #20 0x7ff0004037ad in KateViewBar::~KateViewBar (this=, this=) at /usr/src/debug/ktexteditor-5.83.0-1.2.x86_64/src/view/kateviewhelpers.h:495 #21 KateViewBar::~KateViewBar (this=, this=) at /usr/src/debug/ktexteditor-5.83.0-1.2.x86_64/src/view/kateviewhelpers.h:495 #22 0x7ff0020f1a5b in QMetaMethod::invoke (this=, object=0x5579c504ecb0, connectionType=Qt::DirectConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:2303 #23 0x7ff0020f6776 in QMetaObject::invokeMethod (obj=0x5579c504ecb0, member=member@entry=0x7ff0005f58ff "deleteViewBar", type=type@entry=Qt::DirectConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1515 #24 0x7ff0005571c9 in QMetaObject::invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::DirectConnection, member=0x7ff0005f58ff "deleteViewBar", obj=) at /usr/include/qt5/QtCore/qobjectdefs.h:444 #25 KTextEditor::MainWindow::deleteViewBar (this=, view=) at /usr/src/debug/ktexteditor-5.83.0-1.2.x86_64/src/utils/mainwindow.cpp:122 #26 0x7ff0004dc8f3 in KTextEditor::ViewPrivate::~ViewPrivate (this=, this=) at /usr/src/debug/ktexteditor-5.83.0-1.2.x86_64/src/view/kateview.cpp:257 #27 0x7ff0004dcd49 in KTextEditor::ViewPrivate::~ViewPrivate (this=, this=) at /usr/src/debug/ktexteditor-5.83.0-1.2.x86_64/src/view/kateview.cpp:263 #28 0x7ff0006eeeb7 in Sublime::View::~View (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.8.x86_64/kdevplatform/sublime/view.cpp:67 #29
[valgrind] [Bug 435299] vex amd64->IR: unhandled instruction bytes: 0xF1 0xF 0x86 0x3C 0x0 0x0 0x0 0x48 0xF 0xB7
https://bugs.kde.org/show_bug.cgi?id=435299 --- Comment #1 from Jaime Torres --- Apparently, the dissasembly of 0xF1 0xF 0x86 0x3C 0x0 0x0 0x0 0x48 0xF 0xB7 could be, according to https://onlinedisassembler.com/odaweb/: f1 icebp 0f863c0 jbe loc_043 48 dec eax 0f byte 0xf b7 byte 0xb7 where icebp is a replacement for int 01, according to http://rcollins.org/secrets/opcodes/ICEBP.html -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 436117] New: Crash in contextbrowser
https://bugs.kde.org/show_bug.cgi?id=436117 Bug ID: 436117 Summary: Crash in contextbrowser Product: kdevelop Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- Application: kdevelop (5.6.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.11-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I've been renaming some python methods and was about to rename another one. It crashed with the rename dialog open. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f40cd9f6bb1 in QScopedPointerDeleter::cleanup (pointer=0x556fce34df40) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:52 #5 QScopedPointer >::~QScopedPointer (this=0x556fce34dee8, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #6 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:972 #7 0x7f40cc35e12d in ?? () from /usr/lib64/libKDevPlatformLanguage.so.56 #8 0x7f407d419863 in QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer (this=, this=) at /usr/include/qt5/QtCore/qshareddata.h:184 #9 QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer (this=, this=) at /usr/include/qt5/QtCore/qshareddata.h:184 #10 QList >::node_destruct (to=0x556fce341dc8, from=0x556fce339620, this=) at /usr/include/qt5/QtCore/qlist.h:526 #11 QList >::dealloc(QListData::Data*) [clone .constprop.0] (data=0x556fce339610, this=) at /usr/include/qt5/QtCore/qlist.h:921 #12 0x7f407d414778 in QList >::~QList (this=, this=) at /usr/include/qt5/QtCore/qlist.h:871 #13 QList >::~QList (this=, this=) at /usr/include/qt5/QtCore/qlist.h:871 #14 ViewHighlights::~ViewHighlights (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/contextbrowser/contextbrowser.h:85 #15 QMapNodeBase::callDestructorIfNecessary (t=...) at /usr/include/qt5/QtCore/qmap.h:100 #16 QMapNode::destroySubTree (this=0x556fc7eea080) at /usr/include/qt5/QtCore/qmap.h:125 #17 QMapData::destroy (this=0x556fcce4b020) at /usr/include/qt5/QtCore/qmap.h:245 #18 0x7f407d40ab55 in QMap::~QMap (this=, this=) at /usr/include/qt5/QtCore/qmap.h:334 #19 QMap::operator= (other=..., this=0x556fbfd87db0) at /usr/include/qt5/QtCore/qmap.h:345 #20 QMap::clear (this=0x556fbfd87db0) at /usr/include/qt5/QtCore/qmap.h:652 #21 ContextBrowserPlugin::updateForView (this=this@entry=0x556fbfd87d70, view=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/contextbrowser/contextbrowser.cpp:839 #22 0x7f407d40bcbc in ContextBrowserPlugin::updateViews (this=0x556fbfd87d70) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/contextbrowser/contextbrowser.cpp:925 #23 0x7f40cd9f8946 in QtPrivate::QSlotObjectBase::call (a=0x7ffe5b870fc0, r=0x556fbfd87d70, this=0x556fc160de30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #24 doActivate (sender=0x556fc160dd70, signal_index=3, argv=argv@entry=0x7ffe5b870fc0) at kernel/qobject.cpp:3886 #25 0x7f40cd9f1c60 in QMetaObject::activate (sender=, m=m@entry=0x7f40cdca6ba0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe5b870fc0) at kernel/qobject.cpp:3946 #26 0x7f40cd9fc85a in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #27 0x7f40cd9ee28f in QObject::event (this=0x556fc160dd70, e=0x7ffe5b871130) at kernel/qobject.cpp:1336 #28 0x7f40ce7404ff in QApplicationPrivate::notify_helper (this=, receiver=0x556fc160dd70, e=0x7ffe5b871130) at kernel/qapplication.cpp:3632 #29 0x7f40cd9c232a in QCoreApplication::notifyInternal2 (receiver=0x556fc160dd70, event=0x7ffe5b871130) at kernel/qcoreapplication.cpp:1063 #30 0x7f40cda18c83 in QTimerInfoList::activateTimers (this=0x556fbf887f60) at kernel/qtimerinfo_unix.cpp:643 #31 0x7f40cda1953c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #32 idleTimerSourceDispatch (source=source@entry=0x556fbf887510) at kernel/qeventdispatcher_glib.cpp:230 #33 0x7f40ca03df57 in g_main_dispatch (context=0x7f40b4005000) at ../glib/gmain.c:3325 #34 g_main_context_dispatch (context=0x7f40b4005000) at ../glib/gmain.c:4043 #35 0x7f40ca03e2d8 in g_main_context_iterate (context=context@entry=0x7f40b4005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4119 #36 0x7f40ca03e38f in g_main_context_iteration (context=0x7f40b4005000, may_block=may_block@entry=1) at ../glib/gmain.c:4184 #37 0x7f40cda198bf in QEventDispatcherGlib::processEvents (this=0x556fbf889a60,
[kdevelop] [Bug 435628] New: Crash trying to open a displaced closed folding marker
https://bugs.kde.org/show_bug.cgi?id=435628 Bug ID: 435628 Summary: Crash trying to open a displaced closed folding marker Product: kdevelop Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- Application: kdevelop (5.6.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.11-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Working in a python module with several classes and methods, in a previuos session I folded/closed several classes, kept working on the last class and exited kdevelop cleanly. When I started it again, the folding markers are displaced and the classes are folded in strange ways. Trying to open one of them created the crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (LWP 8973)] [KCrash Handler] #6 0x7fa14c445efe in QString::insert (s=..., i=223, this=0x558729621c68) at ../../include/QtCore/../../src/corelib/text/qstring.h:542 #7 QTextEngine::validate (this=0x55872b024fe0) at text/qtextengine.cpp:2077 #8 QTextEngine::validate (this=0x55872b024fe0) at text/qtextengine.cpp:2059 #9 0x7fa14c44caba in QTextEngine::itemize (this=0x55872b024fe0) at text/qtextengine.cpp:2082 #10 0x7fa14c45565c in QTextLayout::beginLayout (this=this@entry=0x5587297a8ab0) at text/qtextlayout.cpp:659 #11 0x7fa14a1c5c18 in KateRenderer::layoutLine (this=0x7fffce03c4e0, this@entry=0x55872a6a0f40, lineLayout=..., maxwidth=maxwidth@entry=1251, cacheLayout=) at /usr/src/debug/ktexteditor-5.80.0-1.1.x86_64/src/render/katerenderer.cpp:998 #12 0x7fa14a1c64b1 in KateLayoutCache::line (this=0x7fffce03c7b8, this@entry=0x55872a6a0e00, realLine=realLine@entry=1285, virtualLine=virtualLine@entry=1285) at /usr/src/debug/ktexteditor-5.80.0-1.1.x86_64/src/render/katelayoutcache.cpp:284 #13 0x7fa14a1c6ea2 in KateLayoutCache::updateViewCache (this=0x55872a6a0e00, startPos=..., newViewLineCount=, viewLinesScrolled=) at /usr/src/debug/ktexteditor-5.80.0-1.1.x86_64/src/render/katelayoutcache.cpp:258 #14 0x7fa14a2164da in KateViewInternal::tagLines (this=0x55872a684580, start=..., end=..., realCursors=) at /usr/src/debug/ktexteditor-5.80.0-1.1.x86_64/src/view/kateviewinternal.cpp:2378 #15 0x7fa14be3a946 in QtPrivate::QSlotObjectBase::call (a=0x7fffce03c9e0, r=0x55872a6835f0, this=0x55872a7f40c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x558728ceb660, signal_index=3, argv=0x7fffce03c9e0) at kernel/qobject.cpp:3886 #17 0x7fa0e74397c2 in ProblemReporterPlugin::updateHighlight (this=this@entry=0x5587281a3330, url=...) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/problemreporterplugin.cpp:180 #18 0x7fa0e7439f3b in ProblemReporterPlugin::updateOpenedDocumentsHighlight (this=0x5587281a3330) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/problemreporterplugin.cpp:257 #19 0x7fa14be3a946 in QtPrivate::QSlotObjectBase::call (a=0x7fffce03cbb0, r=0x5587281a3330, this=0x5587281b2010) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate (sender=0x558727844740, signal_index=6, argv=0x7fffce03cbb0) at kernel/qobject.cpp:3886 #21 0x7fa14be3a946 in QtPrivate::QSlotObjectBase::call (a=0x7fffce03cc90, r=0x558727844740, this=0x5587281acb40) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #22 doActivate (sender=0x5587281aa670, signal_index=26, argv=0x7fffce03cc90) at kernel/qobject.cpp:3886 #23 0x7fa14be3a946 in QtPrivate::QSlotObjectBase::call (a=0x7fffce03cd70, r=0x5587281aa670, this=0x5587281ac4b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #24 doActivate (sender=0x5587281a3300, signal_index=4, argv=0x7fffce03cd70) at kernel/qobject.cpp:3886 #25 0x7fa0e743cd67 in ProblemReporterModel::rebuildProblemList (this=0x5587281aa670) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/problemreportermodel.cpp:166 #26 0x7fa14be3a946 in QtPrivate::QSlotObjectBase::call (a=0x7fffce03cea0, r=0x5587281aa670, this=0x5587281ac970) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #27 doActivate (sender=0x5587281a3300, signal_index=3, argv=0x7fffce03cea0) at kernel/qobject.cpp:3886 #28 0x7fa14be3a946 in QtPrivate::QSlotObjectBase::call (a=0x7fffce03cf80, r=0x5587281a3300, this=0x55872ac9c6e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #29 doActivate
[valgrind] [Bug 435299] New: vex amd64->IR: unhandled instruction bytes: 0xF1 0xF 0x86 0x3C 0x0 0x0 0x0 0x48 0xF 0xB7
https://bugs.kde.org/show_bug.cgi?id=435299 Bug ID: 435299 Summary: vex amd64->IR: unhandled instruction bytes: 0xF1 0xF 0x86 0x3C 0x0 0x0 0x0 0x48 0xF 0xB7 Product: valgrind Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: callgrind Assignee: josef.weidendor...@gmx.de Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY Everytime I try to use callgrind with kate/kwrite, the same error: vex amd64->IR: unhandled instruction bytes: 0xF1 0xF 0x86 0x3C 0x0 0x0 0x0 0x48 0xF 0xB7 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==26062== valgrind: Unrecognised instruction at address 0x11953e05 STEPS TO REPRODUCE valgrind --tool=callgrind --instr-atstart=no --collect-atstart=yes --collect-jumps=yes --collect-bus=yes --cacheuse=yes /usr/bin/kwrite ==26062== Callgrind, a call-graph generating cache profiler ==26062== Copyright (C) 2002-2017, and GNU GPL'd, by Josef Weidendorfer et al. ==26062== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==26062== Command: /usr/bin/kwrite ==26062== --26062-- warning: L3 cache found, using its data for the LL simulation. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210330 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 6 × AMD Phenom(tm) II X6 1100T Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD JUNIPER I guess this started when opensuse changed gcc to versions 9 or greater. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 432304] crash parsing python project
https://bugs.kde.org/show_bug.cgi?id=432304 --- Comment #3 from Jaime Torres --- Oh, yes, sorry. Yes, I have another open project with some Qml, not opened in the editor. The crash happens randomly, yesterday, after the crash, and Kdevelop recreate its cache, It worked without further problems. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 432304] crash parsing python project
https://bugs.kde.org/show_bug.cgi?id=432304 --- Comment #1 from Jaime Torres --- Created attachment 135299 --> https://bugs.kde.org/attachment.cgi?id=135299=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 432304] New: crash parsing python project
https://bugs.kde.org/show_bug.cgi?id=432304 Bug ID: 432304 Summary: crash parsing python project Product: kdevelop Version: 5.6.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- Application: kdevelop (5.6.1) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.7-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Kdevelop was opened a few minutes before the crash, just created a new class, a new method and crash. -- Backtrace (Reduced): #4 0x7fe3d0506700 in KDevelop::Declaration::isAutoDeclaration() const () from /usr/lib64/libKDevPlatformLanguage.so.56 #5 0x7fe3d04eff30 in KDevelop::DUContext::cleanIfNotEncountered(QSet const&) () from /usr/lib64/libKDevPlatformLanguage.so.56 #6 0x7fe371182f0b in KDevelop::AbstractContextBuilder::closeContext (this=0x7fe264d858b0) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:474 #7 0x7fe37119412a in DeclarationBuilder::endVisit (node=, this=0x7fe264d858b0) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/plugins/qmljs/duchain/declarationbuilder.cpp:690 #8 DeclarationBuilder::endVisit (this=0x7fe264d858b0, node=) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/plugins/qmljs/duchain/declarationbuilder.cpp:684 Possible duplicates by query: bug 409178, bug 405368, bug 377973, bug 376586, bug 374145. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344706] KMenu won't show sometimes (multi-monitor setup)
https://bugs.kde.org/show_bug.cgi?id=344706 --- Comment #49 from Jaime Torres --- I'm trying the new code and it works for me, after removing the kwin rule I use with the distributed plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 171221] Tiny SVG file crashes konqueror, stalls system
https://bugs.kde.org/show_bug.cgi?id=171221 --- Comment #8 from Jaime Torres --- If konqueror uses ksvg, okular or kate part, there is no problem at all. If konqueror uses khtml or webkit part, the problem is still there. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 391580] stack overflow using gwenview browsing a zip file over fish:
https://bugs.kde.org/show_bug.cgi?id=391580 Jaime Torres changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Jaime Torres --- No crash for me using fish:// protocol, I shows the images inside the .zip file as expected. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398613] crash parsing a currently being modified .cpp file
https://bugs.kde.org/show_bug.cgi?id=398613 Jaime Torres changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Jaime Torres --- I haven't seen this bug in a long time. Lets assume it has been fixed. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 400166] Crash in thumbnailer, probably a badly imported emf file
https://bugs.kde.org/show_bug.cgi?id=400166 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Jaime Torres --- It is still an issue for me, with this backtrace: #4 0x7f36488c9c1a in QVector::at (i=, this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:455 #5 convertIndexedToARGB32PM (buffer=0x7ffc75889eb0, count=33, clut=0x0) at painting/qdrawhelper.cpp:710 #6 0x7f36488dd646 in fetchTransformed<(TextureBlendType)2, (QPixelLayout::BPP)0> (buffer=0x7ffc75889eb0, data=0x5612c0e30f98, y=, x=, length=33) at painting/qdrawhelper.cpp:2258 #7 0x7f36488eed9e in BlendSrcGeneric::fetch (len=, y=0, x=0, this=0x7ffc75887e10) at painting/qdrawhelper.cpp:4750 #8 handleSpans (count=count@entry=11, spans=spans@entry=0x7ffc75893fc0, data=data@entry=0x5612c0e30f98, handler=...) at painting/qdrawhelper.cpp:4694 #9 0x7f36488ed2ad in blend_src_generic_rgb64 (count=11, spans=0x7ffc75893fc0, userData=0x5612c0e30f98) at painting/qdrawhelper.cpp:4816 #10 0x7f36489e in fillRect_normalized (r=..., data=0x5612c0e30f98, pe=0x7ffc75893fc0) at painting/qpaintengine_raster.cpp:1542 #11 0x7f364892832e in QRasterPaintEngine::drawImage (this=0x5612c0f98b20, r=..., img=..., sr=...) at painting/qpaintengine_raster.cpp:2480 #12 0x7f3648944671 in QPainter::drawImage (this=0x7ffc75894f70, targetRect=..., image=..., sourceRect=..., flags=...) at painting/qpainter.cpp:5562 #13 0x7f362c8e3c79 in Libemf::OutputPainterStrategy::stretchDiBits(Libemf::StretchDiBitsRecord&) () from /usr/lib64/libkovectorimage.so.17 #14 0x7f362c8e6898 in Libemf::Parser::readRecord(QDataStream&) () from /usr/lib64/libkovectorimage.so.17 #15 0x7f362c8e70d4 in Libemf::Parser::loadFromStream(QDataStream&) () from /usr/lib64/libkovectorimage.so.17 #16 0x7f362c8e97c6 in Libemf::Parser::load(QByteArray const&) () from /usr/lib64/libkovectorimage.so.17 -- You are receiving this mail because: You are watching all bug changes.
[calligrachart] [Bug 289376] Second backtrace from a chart Second backtrace from a chart [@ KDChart::CartesianDiagramDataCompressor::retrieveModelData]
https://bugs.kde.org/show_bug.cgi?id=289376 Jaime Torres changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Jaime Torres --- Also fixed in Version 3.2.1 -- You are receiving this mail because: You are watching all bug changes.
[calligrachart] [Bug 289375] crash choosing a business chart type
https://bugs.kde.org/show_bug.cgi?id=289375 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Jaime Torres --- I can't reproduce the bug in Version 3.2.1. -- You are receiving this mail because: You are watching all bug changes.
[libkdegames] [Bug 259006] kGameRenderer crash when doing QT_FATAL_WARNINGS=1 kmines
https://bugs.kde.org/show_bug.cgi?id=259006 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- --- Comment #3 from Jaime Torres --- I had a patch that fixed this warning/error. It is available in https://phabricator.kde.org/D9198 Unfortunately, it can be reproduced just launching QT_FATAL_WARNINGS=1 kmines -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 400360] No warning of big file when the file has been modified in the disk
https://bugs.kde.org/show_bug.cgi?id=400360 --- Comment #3 from Jaime Torres --- It can be seen as another case of the other means in #351362, yes. * Dropping the file * Command line * Reopened because it has been modified. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388881] When renaming inline in a long file name and pressing up key, sometimes does not move the cursor up
https://bugs.kde.org/show_bug.cgi?id=31 Jaime Torres changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Jaime Torres --- I've been able to reproduce it only once in several attempts. Not as frequently as I remember. It works for me. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426380] Okular forgets the open documents when closed normally and reopened
https://bugs.kde.org/show_bug.cgi?id=426380 --- Comment #2 from Jaime Torres --- Just answering the question Why do I close Okular at all then? Web browsers sometimes do stuff like that, I don’t really understand why. Sometimes I need to run some memory hungry programs, therefore I close almost all the other programs and then reopen them again. I guess I can not get the same effect with Activities. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426380] New: Okular forgets the open documents when closed normally and reopened
https://bugs.kde.org/show_bug.cgi?id=426380 Bug ID: 426380 Summary: Okular forgets the open documents when closed normally and reopened Product: okular Version: 1.11.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY When the session is closed and reopened, okular remembers the open documents and everything is restored as if nothing happened. But if I close and open again in the same session, okular forgets the previous open documents and I have to restore them manually from the recent documents (if they are still there). STEPS TO REPRODUCE 1. Close normally okular 2. Open normally okular OBSERVED RESULT The opened documents are lost, okular is empty EXPECTED RESULT The opened documents are there, okular is restored like in the session start. SOFTWARE/OS VERSIONS KDE Frameworks 5.73.0 Qt 5.15.0 (compilado con 5.15.0) El sistema de ventanas xcb -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 425898] New: The list of magnetic links is lost after a crash
https://bugs.kde.org/show_bug.cgi?id=425898 Bug ID: 425898 Summary: The list of magnetic links is lost after a crash Product: ktorrent Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY Having created a long list of magnetic links to download, and some of them take more than two days to start the download. If ktorrent is not exited normally and entered again, the list of magnetic links is lost if a crash happens. STEPS TO REPRODUCE 1. Try to download some magnetic links with no known active seeder 2. make ktorrent crash (a signal is enougth) 3. start again ktorrent. No magnetic links. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Frameworks 5.72.0 Qt 5.15.0 (compilado con 5.15.0) El sistema de ventanas xcb ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423289] Settings Module Crash on opening "Configure Window Manager" in window context menu
https://bugs.kde.org/show_bug.cgi?id=423289 --- Comment #2 from Jaime Torres --- Or from command line: /usr/bin/kcmshell5 --icon preferences-system-windows --desktopfile /usr/share/kservices5/kwinfocus.desktop kwindecoration kwinactions kwinfocus kwinmoving kwinadvanced kwinrules kwincompositing kwineffects kwintabbox kwinscreenedges kwinscripts Caused by: ==22198== Invalid read of size 8 ==22198==at 0x5DD0B97: load (atomic_base.h:747) ==22198==by 0x5DD0B97: load (atomic:523) ==22198==by 0x5DD0B97: loadAcquire (qatomic_cxx11.h:251) ==22198==by 0x5DD0B97: loadAcquire (qbasicatomic.h:255) ==22198==by 0x5DD0B97: operator QBasicAtomicPointer::Type (qbasicatomic.h:251) ==22198==by 0x5DD0B97: QObjectPrivate::setParent_helper(QObject*) (qobject.cpp:2157) ==22198==by 0x149C74FE: KWinOptionsSettings::KWinOptionsSettings(QObject*) (kwinoptions_settings.cpp:9) ==22198==by 0x149C4E13: UnknownInlinedFun (main.cpp:54) ==22198==by 0x149C4E13: QObject* KPluginFactory::createInstance(QWidget*, QObject*, QList const&) (kpluginfactory.h:520) ==22198==by 0x4BE2C51: KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) (kpluginfactory.cpp:133) ==22198==by 0x48CB5DC: KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) (kpluginfactory.h:569) ==22198==by 0x48CBFA3: KCModuleProxyPrivate::loadModule() (kcmoduleproxy.cpp:94) ==22198==by 0x48CC637: KCModuleProxy::realModule() const (kcmoduleproxy.cpp:67) ==22198==by 0x48CCAC1: KCMultiDialog::addModule(KCModuleInfo const&, KPageWidgetItem*, QStringList const&) (kcmultidialog.cpp:496) ==22198==by 0x10FEDF: main (main.cpp:309) ==22198== Address 0xba is not stack'd, malloc'd or (recently) free'd -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423289] Settings Module Crash on opening "Configure Window Manager" in window context menu
https://bugs.kde.org/show_bug.cgi?id=423289 Jaime Torres changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||jtam...@gmail.com --- Comment #1 from Jaime Torres --- I suffer the same bug with the same backtrace following the same steps. Qt Version: 5.15.0 Frameworks Version: 5.71.0 Operating System: Linux 5.7.1-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418300] Crash using keyboard to rename folder after folder
https://bugs.kde.org/show_bug.cgi?id=418300 --- Comment #2 from Jaime Torres --- As soon as I can use valgrind again I'll try to reproduce it. Lately valgrind always crashes dolphin (and other kde programs) before showing any window. Application: Dolphin (memcheck-amd64-linux), signal: Segmentation fault vgModuleLocal_do_syscall_for_client_WRK () at ../../coregrind/m_syswrap/syscall-amd64-linux.S:171 171 POP_di_si_dx_cx_8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418300] New: Crash using keyboard to rename folder after folder
https://bugs.kde.org/show_bug.cgi?id=418300 Bug ID: 418300 Summary: Crash using keyboard to rename folder after folder Product: dolphin Version: 19.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jtam...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (19.12.2) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.4-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was adding metainformation to several folders (rating) and then renaming then one by one. After one rename, the folder became the last in the view, so I used keyboard to go to the top of the view to rename the next one, after 5 times, speeding time after time, dolphin crashed. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f43fd66a800 (LWP 4864))] Thread 10 (Thread 0x7f43e5d62700 (LWP 5056)): #0 __GI___libc_read (nbytes=10, buf=0x7f43e5d61bde, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=28, buf=0x7f43e5d61bde, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f43fdc380f1 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #3 0x7f43fed62a0e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #4 0x7f43fed634b0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #5 0x7f43fed63570 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #6 0x7f43fed71439 in ?? () from /usr/lib64/libpulse.so.0 #7 0x7f43fdc65c78 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #8 0x7f43fede4efa in start_thread (arg=) at pthread_create.c:477 #9 0x7f440254a3bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f43e759a700 (LWP 5285)): #0 0x7f43fe3995e9 in g_mutex_lock (mutex=mutex@entry=0x7f43c8000c20) at ../glib/gthread-posix.c:1363 #1 0x7f43fe34d707 in g_main_context_prepare (context=context@entry=0x7f43c8000c20, priority=priority@entry=0x7f43e7599c60) at ../glib/gmain.c:3427 #2 0x7f43fe34e21b in g_main_context_iterate (context=context@entry=0x7f43c8000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:3897 #3 0x7f43fe34e40f in g_main_context_iteration (context=0x7f43c8000c20, may_block=may_block@entry=1) at ../glib/gmain.c:3978 #4 0x7f440053bc6b in QEventDispatcherGlib::processEvents (this=0x7f43c8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f44004e3bfb in QEventLoop::exec (this=this@entry=0x7f43e7599da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f440030e62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f440030f6f8 in QThreadPrivate::start (arg=0x564d597e7680) at thread/qthread_unix.cpp:342 #8 0x7f43fede4efa in start_thread (arg=) at pthread_create.c:477 #9 0x7f440254a3bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f43f1d3d700 (LWP 4894)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x564d5932fc18) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564d5932fbc8, cond=0x564d5932fbf0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564d5932fbf0, mutex=0x564d5932fbc8) at pthread_cond_wait.c:638 #3 0x7f43f86e3deb in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7f43f86e3cc7 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7f43fede4efa in start_thread (arg=) at pthread_create.c:477 #6 0x7f440254a3bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f43f253e700 (LWP 4893)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x564d5932fc18) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564d5932fbc8, cond=0x564d5932fbf0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564d5932fbf0, mutex=0x564d5932fbc8) at pthread_cond_wait.c:638 #3 0x7f43f86e3deb in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7f43f86e3cc7 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7f43fede4efa in start_thread (arg=) at pthread_create.c:477 #6 0x7f440254a3bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f43f2d3f700 (LWP 4892)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x564d5932fc18) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common
[akregator] [Bug 417785] New: Don't change table view when using + or - with non full width
https://bugs.kde.org/show_bug.cgi?id=417785 Bug ID: 417785 Summary: Don't change table view when using + or - with non full width Product: akregator Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY Using akregator with the window allowing the feeds tree and only part of the title to be seen, if I click on the next title, I still see the beginning of the title, but if I use + or -, the title view is displaced to the middle, making it harder to read sort titles. EXPECTED RESULT The feed view doesn't change to the middle of the title, behave like clicking on other SOFTWARE/OS VERSIONS KDE Frameworks 5.66.0 Qt 5.14.0 (built against 5.14.0) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415383] This is the look after a fresh installation in a w10
https://bugs.kde.org/show_bug.cgi?id=415383 Jaime Torres changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Jaime Torres --- Thank you. That fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415385] New: Have a collection of high level effects that users can contribute and others use
https://bugs.kde.org/show_bug.cgi?id=415385 Bug ID: 415385 Summary: Have a collection of high level effects that users can contribute and others use Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY Most of the effects are in a way low-level. They do one thing and they do it right. But imagine I want to do an Star Curtain (like Homer). Right now it is quite hard to do, but if someone who knows how to do it can program it and offer it from hotnewstuff with a simple configuration, it will make this task a lot easier. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415383] New: This is the look after a fresh installation in a w10
https://bugs.kde.org/show_bug.cgi?id=415383 Bug ID: 415383 Summary: This is the look after a fresh installation in a w10 Product: kdenlive Version: 19.12.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jtam...@gmail.com Target Milestone: --- Created attachment 124609 --> https://bugs.kde.org/attachment.cgi?id=124609=edit The screen in windows SUMMARY It is unusable.. STEPS TO REPRODUCE 1. Install it from https://files.kde.org/kdenlive/release/kdenlive-19.12.0.exe in a folder that is not Program Files and run it OBSERVED RESULT The attached image. At least I can tell that the menu is there, invisible, but there. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 Screen resolution: 1920x1080 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 413801] There is no protection against huge memory usage
https://bugs.kde.org/show_bug.cgi?id=413801 --- Comment #2 from Jaime Torres --- Unfortunately, I don't have the time. I've been tying to create a single simple patch for 3 months, and I still don't have it. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 413801] New: There is no protection against huge memory usage
https://bugs.kde.org/show_bug.cgi?id=413801 Bug ID: 413801 Summary: There is no protection against huge memory usage Product: kio-extras Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: jtam...@gmail.com Target Milestone: --- SUMMARY A single malicious file makes the plugin use all available memory until it is killed by lack of more memory. STEPS TO REPRODUCE 1. Download and expand the image from https://www.bamsoftware.com/hacks/deflate.html in any folder 2. wait until dolphin/konqueror updates the thumbnail of that image. OBSERVED RESULT It is killed by the oom killer. EXPECTED RESULT It has some protection against those kind of files, like DecompressionBombWarning in https://pillow.readthedocs.io/en/3.1.x/reference/Image.html SOFTWARE/OS VERSIONS KDE Frameworks 5.63.0 Qt 5.13.1 (built against 5.13.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 272535] Add "Select All" action in Detailed Memory Information
https://bugs.kde.org/show_bug.cgi?id=272535 Jaime Torres changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Keywords||triaged CC||jtam...@gmail.com --- Comment #1 from Jaime Torres --- Ctrl+A select all text in the Detailed Memory Information window in Version 5.16.5 using KDE Frameworks 5.62.0 Qt 5.13.1 (built against 5.13.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 75161] Logarithmic scaling option for bar-graph and signal plotter
https://bugs.kde.org/show_bug.cgi?id=75161 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com Keywords||triaged --- Comment #3 from Jaime Torres --- I haven't seen any way to enable a logarithmic scale or any logarithmic sensor. Version 5.16.5 with KDE Frameworks 5.62.0 Qt 5.13.1 (built against 5.13.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 147920] ksysguard applet does not recover ssh connections
https://bugs.kde.org/show_bug.cgi?id=147920 Jaime Torres changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||jtam...@gmail.com Keywords||triaged --- Comment #4 from Jaime Torres --- In Version 5.16.5, the auto reconnect is working. At least on the tests I've done. I've created a page with several sensors of another machine over ssh, disconnected the network cable for 1 minute (the meters just stops and no error icon) and reconnected it again, the sensors came back to life. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397558] Guides ignore change of canvas shape
https://bugs.kde.org/show_bug.cgi?id=397558 --- Comment #3 from Jaime Torres --- Hi, in krita 4.2.5 the guides already rotate with the rotating canvas. In my opinion: If the block guides option is selected, they don't change in any resize (image or canvas) or image rotation. If the block guides option is not selected, they change according to canvas resize following their previous position in the rule. For example, assuming the canvas is not rotated, if an horizontal guide was in 100 of 1000 in the rule and the canvas is resized, no matter at what side, to 2000 in the rule, the guide should be in 200. Is this is useful? I don't know. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399279] crash changing Scaling Mode (Windows)
https://bugs.kde.org/show_bug.cgi?id=399279 Jaime Torres changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #5 from Jaime Torres --- Can't reproducem either because the forced environment patches or because today nightly release has it fixed. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 407222] New: Ability to use clang for windows
https://bugs.kde.org/show_bug.cgi?id=407222 Bug ID: 407222 Summary: Ability to use clang for windows Product: Craft Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Core Assignee: vonr...@kde.org Reporter: jtam...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY The clang free compiler is available for windows as prebuilt-binaries in: http://releases.llvm.org/download.html And it uses much less disk space than any (free to test) Visual Studio. Craft can only use (from the setup): Welcome to the Craft setup wizard! Select compiler [0] Mingw-w64, [1] Microsoft Visual Studio 2017, [2] Microsoft Visual Studio 2019 (Experimental) (Default is Microsoft Visual Studio 2017): -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #17 from Jaime Torres --- >> What decoration are you using? Breeze? >I use an adapted "Krita - dark". Just changed some of the colors. It is more important in this case what you have configured in: SystemSettings -> Application Style -> Widget Style : Widget Style. For example: Breeze, CDE, CleanLooks, ... Whitout deleting the .fontconfig folders, just move them to another name, for example: mv .fontconfig fontconfig.testing, if it is possible, outside the plasma session, and see if this makes any difference after restarting plasma and dolphin. If this doesn't have any effect, you can move them back. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #15 from Jaime Torres --- What decoration are you using? Breeze? Just asking because of these detected memory leaks using "valgrind --show-reachable=yes --leak-check=full --trace-children=yes --log-file=dolphin.log dolphin" changed to /tmp and waited 5 minutes: ==6992== 81,920 bytes in 48 blocks are indirectly lost in loss record 2,315 of 2,318 ==6992==at 0x4839F1B: realloc (vg_replace_malloc.c:836) ==6992==by 0x6A8319A: reserve (qdatabuffer_p.h:119) ==6992==by 0x6A8319A: add (qdatabuffer_p.h:98) ==6992==by 0x6A8319A: QBezier::addToPolygon(QDataBuffer&, double) const (qbezier.cpp:182) ==6992==by 0x6B1E28B: QOutlineMapper::curveTo(QPointF const&, QPointF const&, QPointF const&) (qoutlinemapper.cpp:93) ==6992==by 0x6B20357: QOutlineMapper::convertPath(QVectorPath const&) (qoutlinemapper.cpp:168) ==6992==by 0x6B47E50: QRasterPaintEngine::fill(QVectorPath const&, QBrush const&) (qpaintengine_raster.cpp:1834) ==6992==by 0x6B2BF64: QPaintEngineEx::draw(QVectorPath const&) (qpaintengineex.cpp:599) ==6992==by 0x6B2DE62: QPaintEngineEx::drawEllipse(QRectF const&) (qpaintengineex.cpp:831) ==6992==by 0x6B472B2: QRasterPaintEngine::drawEllipse(QRectF const&) (qpaintengine_raster.cpp:3394) ==6992==by 0x6B575F6: QPainter::drawEllipse(QRectF const&) (qpainter.cpp:4265) ==6992==by 0xE096CA2: Breeze::Helper::renderDecorationButton(QPainter*, QRect const&, QColor const&, Breeze::ButtonType, bool) const (breezehelper.cpp:1339) ==6992==by 0xE0B300F: Breeze::Style::titleBarButtonIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.cpp:7116) ==6992==by 0xE0B37EA: Breeze::Style::standardIconImplementation(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.cpp:1389) ==6992== ==6992== 132,224 bytes in 40 blocks are indirectly lost in loss record 2,316 of 2,318 ==6992==at 0x483780F: malloc (vg_replace_malloc.c:309) ==6992==by 0x692CC47: QImageData::create(QSize const&, QImage::Format) (qimage.cpp:152) ==6992==by 0x692CD4A: QImage::QImage(QSize const&, QImage::Format) (qimage.cpp:772) ==6992==by 0x692CD84: QImage::QImage(int, int, QImage::Format) (qimage.cpp:756) ==6992==by 0x696EE8B: QRasterPlatformPixmap::resize(int, int) (qpixmap_raster.cpp:112) ==6992==by 0x696E328: QPlatformPixmap::create(int, int, QPlatformPixmap::PixelType) (qplatformpixmap.cpp:65) ==6992==by 0x6965536: QPixmap::doInit(int, int, int) (qpixmap.cpp:95) ==6992==by 0x6965632: QPixmap::QPixmap(int, int) (qpixmap.cpp:128) ==6992==by 0xE0B2FAB: Breeze::Style::titleBarButtonIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.cpp:7111) ==6992==by 0xE0B37EA: Breeze::Style::standardIconImplementation(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.cpp:1389) ==6992==by 0xE0B752C: Breeze::Style::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.h:182) ==6992==by 0x63C1D34: QDockWidgetPrivate::updateButtons() (qdockwidget.cpp:737) ==6992== ==6992== 132,224 bytes in 40 blocks are indirectly lost in loss record 2,317 of 2,318 ==6992==at 0x483780F: malloc (vg_replace_malloc.c:309) ==6992==by 0x692CC47: QImageData::create(QSize const&, QImage::Format) (qimage.cpp:152) ==6992==by 0x692CD4A: QImage::QImage(QSize const&, QImage::Format) (qimage.cpp:772) ==6992==by 0x692CD84: QImage::QImage(int, int, QImage::Format) (qimage.cpp:756) ==6992==by 0x696EE8B: QRasterPlatformPixmap::resize(int, int) (qpixmap_raster.cpp:112) ==6992==by 0x696E328: QPlatformPixmap::create(int, int, QPlatformPixmap::PixelType) (qplatformpixmap.cpp:65) ==6992==by 0x6965536: QPixmap::doInit(int, int, int) (qpixmap.cpp:95) ==6992==by 0x6965632: QPixmap::QPixmap(int, int) (qpixmap.cpp:128) ==6992==by 0xE0B2FAB: Breeze::Style::titleBarButtonIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.cpp:7111) ==6992==by 0xE0B37EA: Breeze::Style::standardIconImplementation(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.cpp:1389) ==6992==by 0xE0B752C: Breeze::Style::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const (breezestyle.h:182) ==6992==by 0x63C1E43: QDockWidgetPrivate::updateButtons() (qdockwidget.cpp:746) The other memory/cpu eater eater in my case is just fontconfig if I have some local configuration in .fontconfig folder. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 357522] 16-bit B TIFF files saved as uncompressed 24bit sRGB after rotation
https://bugs.kde.org/show_bug.cgi?id=357522 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com --- Comment #3 from Jaime Torres --- Created attachment 119156 --> https://bugs.kde.org/attachment.cgi?id=119156=edit tiff 1 bit Tiff of 1bit depth. original size 32KiB, rotated and saved 229KiB. Image from https://github.com/mike-lischke/GraphicEx/blob/master/TestSuite%20original/TIFF/Official%20test%20images/fax2d.tiff Tested with gwenview 18.12.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402821] Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=402821 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Jaime Torres --- Hi, According to the backtrace, you just did a folder rename. Best Regards. *** This bug has been marked as a duplicate of bug 401552 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 401552] Dolphin crash when renaming a directory
https://bugs.kde.org/show_bug.cgi?id=401552 Jaime Torres changed: What|Removed |Added CC||k...@trummer.xyz --- Comment #12 from Jaime Torres --- *** Bug 402821 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 401552] Dolphin crash when renaming a directory
https://bugs.kde.org/show_bug.cgi?id=401552 Jaime Torres changed: What|Removed |Added Latest Commit||https://commits.kde.org/kio ||/211c3a680ea762ec3a674f2f29 ||de5bbf7ae36d8e Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Jaime Torres --- Git commit 211c3a680ea762ec3a674f2f29de5bbf7ae36d8e by Jaime Torres Amate. Committed on 24/12/2018 at 08:34. Pushed by jtamate into branch 'master'. Change the path for every item of the subdirectories in a directory rename Summary: As only the items in subdirectories of the renamed one are modified, if all the items are changed the same part of the path with the same new value, the order is preserved, therefore modify the path directly in the list. Test Plan: Can't reproduce the bug. Passes kdirmodeltest and kdirlistertest (and many others). Reviewers: dfaure, #frameworks Reviewed By: dfaure Subscribers: elvisangelaccio, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D17619 M +55 -0autotests/kdirlistertest.cpp M +1-0autotests/kdirlistertest.h M +4-3src/core/kcoredirlister.cpp https://commits.kde.org/kio/211c3a680ea762ec3a674f2f29de5bbf7ae36d8e -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 402038] New: Allow the use of LLVM compilers
https://bugs.kde.org/show_bug.cgi?id=402038 Bug ID: 402038 Summary: Allow the use of LLVM compilers Product: Craft Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Core Assignee: vonr...@kde.org Reporter: jtam...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- Craft (as of today) doesn't allow the use of the now installable LLVM compilers in windows. It only presents the following options: Select compiler [0] Mingw-w64, [1] Microsoft Visual Studio 2015, [2] Microsoft Visual Studio 2017 (Default is Microsoft Visual Studio 2017): -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 388110] Problems installing in w$ 10
https://bugs.kde.org/show_bug.cgi?id=388110 Jaime Torres changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Jaime Torres --- After some time and some w$ updates, in a fresh installation, it works for me. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377493] Music staff notation is often impossible to read due to object placement and line spacing
https://bugs.kde.org/show_bug.cgi?id=377493 Jaime Torres changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #6 from Jaime Torres --- Oh, I can see now that the problem is still there (two different notes on the same vertical space), specially when the zoom is lower than 100% (I didn't saw it last time, I need new glasses). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377493] Music staff notation is often impossible to read due to object placement and line spacing
https://bugs.kde.org/show_bug.cgi?id=377493 --- Comment #5 from Jaime Torres --- Created attachment 116412 --> https://bugs.kde.org/attachment.cgi?id=116412=edit As another reference. The same pdf as rendered by chrome pdfjs viewer -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 367959] Okular mangles some characters (non embedded fonts)
https://bugs.kde.org/show_bug.cgi?id=367959 --- Comment #7 from Jaime Torres --- Created attachment 116379 --> https://bugs.kde.org/attachment.cgi?id=116379=edit The demo file rendered by okular (with arial font installed) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 381405] Link to different document does not launch a new instance of Okular, but replaces current open document
https://bugs.kde.org/show_bug.cgi?id=381405 Jaime Torres changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Keywords||triaged CC||jtam...@gmail.com --- Comment #1 from Jaime Torres --- Reproduced with okular 1.6.70 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 380092] Collapsing of "Reviews" sidetab
https://bugs.kde.org/show_bug.cgi?id=380092 Jaime Torres changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||triaged CC||jtam...@gmail.com --- Comment #1 from Jaime Torres --- Reproduced with okular 1.6.70 -- You are receiving this mail because: You are watching all bug changes.
