[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files

[Angelo]

https://bugs.kde.org/show_bug.cgi?id=346403

Angelo  changed:

   What|Removed |Added

 CC||angel...@gmail.com

--- Comment #11 from Angelo  ---
Seems i have same issue, in kdevelop 5.0.1 and also in previous version:

Step to reproduce:
1) if open a file in arch/arm/boot/dts/
2) close kdevelop
3) reopen it so that file is already visible
4) when the dialog file path already point to (a linux source tree) some file
in "arch/arm/boot/dts/" so if do open and same path is auto-selected

i have to wait at least 20 seconds with dialog as freezed, un-scrollable and
un-selectable.

I break gdb while waiting, the backtrace is below:

$ gdb kdevelop
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kdevelop...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/kdevelop 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffda57c700 (LWP 2485)]
[New Thread 0x7fffd8fc7700 (LWP 2486)]
[New Thread 0x7fffd120d700 (LWP 2488)]
[New Thread 0x7fffc97be700 (LWP 2489)]
[New Thread 0x7fffbdfde700 (LWP 2490)]
[New Thread 0x7fffbcb21700 (LWP 2501)]
Not loading plugin named "KDevNinjaBuilder" because it has been disabled!
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permesso
negato
Invalid return type in method "core"
Invalid return type in method "extensions"
[New Thread 0x7fffb60e5700 (LWP 2573)]
[New Thread 0x7fffb58e4700 (LWP 2575)]
Not loading plugin named "KDevNinjaBuilder" because it has been disabled!
Invalid return type in method "core"
Invalid return type in method "extensions"
[New Thread 0x7fffb4c5b700 (LWP 2600)]
[New Thread 0x7fffa3fff700 (LWP 2601)]
[New Thread 0x7fffa37fe700 (LWP 2602)]
[New Thread 0x7fffa2ffd700 (LWP 2603)]
[New Thread 0x7fffa27fc700 (LWP 2604)]
[New Thread 0x7fffa1ffb700 (LWP 2605)]
[New Thread 0x7fffa17fa700 (LWP 2607)]
[New Thread 0x7fffa0ff9700 (LWP 2608)]
[New Thread 0x7fff83fff700 (LWP 2609)]
[New Thread 0x7fff837fe700 (LWP 2610)]
[Thread 0x7fff837fe700 (LWP 2610) exited]
^C
Thread 1 "kdevelop" received signal SIGINT, Interrupt.
0x7585c780 in operator new(unsigned long) () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x7585c780 in operator new(unsigned long) () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x75d29722 in QUrl::detach() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x75d29a97 in QUrl::setScheme(QString const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x75d2c9f8 in QUrl::fromLocalFile(QString const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7131a875 in KFileItem::mostLocalUrl(bool*) const () from
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#5  0x7131f893 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#6  0x7131fa0b in KFileItem::overlays() const () from
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#7  0x71947d98 in KDirModel::data(QModelIndex const&, int) const ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#8  0x75d96f29 in QSortFilterProxyModel::data(QModelIndex const&, int)
const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x718f944c in
KFileItemDelegate::Private::decoration(QStyleOptionViewItem const&, QModelIndex
const&) const () from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#10 0x718f9998 in
KFileItemDelegate::Private::initStyleOption(QStyleOptionViewItem*, QModelIndex
const&) const () from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#11 0x718fa2ea in KFileItemDelegate::sizeHint(QStyleOptionViewItem
const&, QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#12 0x769b5e49 in QTreeViewPrivate::widthHintForIndex(QModelIndex
const&, int, QStyleOptionViewItem const&, int) const () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x769b8dcf 

[systemsettings] [Bug 466915] New: Disable Ctrl+Alt+MouseWheel keybind

[Angelo]

https://bugs.kde.org/show_bug.cgi?id=466915

Bug ID: 466915
   Summary: Disable Ctrl+Alt+MouseWheel keybind
Classification: Applications
   Product: systemsettings
   Version: 5.27.2
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_workspace
  Assignee: plasma-b...@kde.org
  Reporter: mrtng...@gmail.com
  Target Milestone: ---

Disable Ctrl+Alt+MouseWheel keybind

It changes Virtual Desktops by default. I can't seem to find an option to
configure it in the Plasma menu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 466915] Odd Ctrl+Alt+MouseWheel default shortcut

[Angelo]

https://bugs.kde.org/show_bug.cgi?id=466915

--- Comment #2 from Angelo  ---
Can't find an option even in Kwin, I just want to disable it because it
interferes with other applications like for example Reaper DAW

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 489265] New: "Shake Cursor" duplicates cursor when zoomed in

[angelo]

https://bugs.kde.org/show_bug.cgi?id=489265

Bug ID: 489265
   Summary: "Shake Cursor" duplicates cursor when zoomed in
Classification: Plasma
   Product: kwin
   Version: git-stable-Plasma/6.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: thegrapes...@proton.me
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. zoom in (is easier to see when really zoomed in or when the cursor becomes a
caret)
2. shake cursor

OBSERVED RESULT
The cursor PNG created on top of the original one is very noticeable 

EXPECTED RESULT
The cursor effect shouldn't be noticeable when zoomed in

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 489265] "Shake Cursor" duplicates cursor when zoomed in

[angelo]

https://bugs.kde.org/show_bug.cgi?id=489265

angelo  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 489265] "Shake Cursor" duplicates cursor when zoomed in

[angelo]

https://bugs.kde.org/show_bug.cgi?id=489265

angelo  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|FIXED   |---
Version|git-stable-Plasma/6.1   |6.1.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 489340] New: Discover app page has extra space to the right

[angelo]

https://bugs.kde.org/show_bug.cgi?id=489340

Bug ID: 489340
   Summary: Discover app page has extra space to the right
Classification: Applications
   Product: Discover
   Version: 6.1.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: thegrapes...@proton.me
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
Opening an app page and then scrolling to the right with a trackpad shows extra
space

STEPS TO REPRODUCE
1. Open an app
2. After it loaded, scroll right with a trackpad

OBSERVED RESULT
I'm able to scroll to the right showing extra space

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 489358] New: Media controls in YouTube Music don't reset correctly

[angelo]

https://bugs.kde.org/show_bug.cgi?id=489358

Bug ID: 489358
   Summary: Media controls in YouTube Music don't reset correctly
Classification: Plasma
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Firefox
  Assignee: k...@privat.broulik.de
  Reporter: thegrapes...@proton.me
  Target Milestone: ---

SUMMARY
When a new song starts the progress bar doesn't reset correctly

STEPS TO REPRODUCE
1. Play a song in YouTube Music and wait for a new one to start

OBSERVED RESULT
The progress bar doesn't reset. As the song plays, it starts jumping backwards
but never back to the beginning. 
When manually placed at the beginning, it starts playing the last song for a
couple seconds before stopping. 

EXPECTED RESULT
Once the music ends, the bar should reset.

Plasma Browser Integration Version: 1.9.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 489358] Media controls in YouTube Music don't reset correctly

[angelo]

https://bugs.kde.org/show_bug.cgi?id=489358

--- Comment #2 from angelo  ---
I was talking about the media player widget, sorry if I wasn't clear enough.
Here's a videos of the bug: https://streamable.com/ammdwi

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 489358] progress bar on "Media Player" widget don't reset correctly in Youtube Music

[angelo]

https://bugs.kde.org/show_bug.cgi?id=489358

angelo  changed:

   What|Removed |Added

Summary|Media controls in YouTube   |progress bar on "Media
   |Music don't reset correctly |Player" widget don't reset
   ||correctly in Youtube Music

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 428708] New: Kdenlive freezes computer when exporting MP4

[Angelo]

https://bugs.kde.org/show_bug.cgi?id=428708

Bug ID: 428708
   Summary: Kdenlive freezes computer when exporting MP4
   Product: kdenlive
   Version: 20.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: oiangelod...@gmail.com
  Target Milestone: ---

SUMMARY

Kdenlive crashes when exporting a MP4 video. Tried exporting WEBM and it worked
fine.

The file has a few mp4 videos that are joined in the sequence. When I select
the rendering type and it starts rendering, it keeps loading until about 70%,
then the whole computer freezes.

The first time it happened I was using the computer with other software (like
chrome). The other times the software was running withou my interaction. I
tried:

- Exporting MP4, crashed
- Exporting WEBM, succesful
- Exporting MP4 via scrip, crashed
- Exporting WEBM then MP4 via scrip, succesfull then, on MP4, crashed

Project settings: Vertical HD 60fps
Export settings: MP4 - the dominating format (h264/aac)


STEPS TO REPRODUCE
1. Load a few mp4 files into the project and organize them in the timeline
2. Hit export with the aforementioned configuration
3. Wait until the computer freezes


OBSERVED RESULT
Computer entirely freezes without any error messages, can't see any log, have
to reset.

EXPECTED RESULT
Video is exported succesfully


SOFTWARE/OS VERSIONS

 OS: Pop 20.04 focal
 Kernel: x86_64 Linux 5.8.0-7625-generic
 DE: GNOME 3.38.0
 CPU: Intel Core i7-4790 @ 8x 4GHz [32.0°C]
 GPU: GeForce GTX 1660 Ti
 RAM: 4086MiB / 15914MiB


ADDITIONAL INFORMATION

I followed the steps in "how to get backtrace" and, when I run *gdb kdenlive
run*, it gives me *File or directory not found*

-- 
You are receiving this mail because:
You are watching all bug changes.

[kid3] [Bug 428981] New: Existem duas ações que querem usar o mesmo atalho.

[Angelo]

https://bugs.kde.org/show_bug.cgi?id=428981

Bug ID: 428981
   Summary: Existem duas ações que querem usar o mesmo atalho.
   Product: kid3
   Version: 3.8.x
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: uflei...@users.sourceforge.net
  Reporter: amaral.ang...@gmail.com
  Target Milestone: ---

Created attachment 133238
  --> https://bugs.kde.org/attachment.cgi?id=133238&action=edit
Tela da mensagem de erro.

Existem duas ações (Substituir..., Recarregar) que querem usar o mesmo atalho
(Ctrl+R). Isto provavelmente é um erro. Relate ele em bugs.kde.org.

Eu uso o Ubuntu 20.04.1 TLS.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 375821] New: debug assembly/registers window

[Angelo]

https://bugs.kde.org/show_bug.cgi?id=375821

Bug ID: 375821
   Summary: debug assembly/registers window
   Product: kdevelop
   Version: 5.0.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: angel...@gmail.com
  Target Milestone: ---

Dear all,
launching gdb, with a remote target (openocd driver for coldfire/m68k cpu), the
driver sends to gdb the proper registers list, as per gdb/features xml
"org.gnu.gdb.coldfire.core". Btw, the coldfire assembly code is visible, but
the cpu registers window stays grayed.

gdb "info registers" or "info all-registers" works fine. Also initial registers
request seems to work properly

(gdb) 20-data-disassemble -s "$pc" -e "$pc+1" -- 0
20^done,asm_insns=[{address="0x8400",func-name="_start",offset="0",inst="movew
#9984,%sr"}]
(gdb) 21-data-list-register-names
21^done,register-names=["d0","d1","d2","d3","d4","d5","d6","d7","a0","a1","a2","a3","a4","a5","fp","sp","ps","pc","","","","","","","","","","",""]

I attach an image.

Tested codeblocks, register windows is shown fine.

Same issue in kdevelop 5.0.1 or 5.0.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 375821] debug assembly/registers window

[Angelo]

https://bugs.kde.org/show_bug.cgi?id=375821

--- Comment #1 from Angelo  ---
Created attachment 103741
  --> https://bugs.kde.org/attachment.cgi?id=103741&action=edit
screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 455489] New: Window Open/Close Animation cannot trigger right away when just switching to another virtual desktop

[Angelo Fallaria]

https://bugs.kde.org/show_bug.cgi?id=455489

Bug ID: 455489
   Summary: Window Open/Close Animation cannot trigger right away
when just switching to another virtual desktop
   Product: kwin
   Version: 5.25.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ba.falla...@gmail.com
  Target Milestone: ---

Created attachment 149861
  --> https://bugs.kde.org/attachment.cgi?id=149861&action=edit
Shows the animations not playing for a few seconds after switching virtual
desktops

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

When I switch to another virtual desktop, the window open/close animations do
not trigger when I open/close a window for around three seconds after
switching. They only start to trigger once I'm in the virtual desktop for more
than three seconds. This is inconvenient as I switch between virtual desktops
all the time in my workflow.

STEPS TO REPRODUCE
1. Set a Window Open/Close Animation in Desktop Effects settings
1. Switch from one virtual desktop to another
2. Open/close a window within ~2-3 seconds from switching

OBSERVED RESULT

Windows do not trigger their open/close animations, as if no open/close
animation was set in the settings.

EXPECTED RESULT

Windows trigger their open/close animations as usual.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Artix Linux 5.18.3-zen1-1-zen (64-bit)
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION

Graphics Platform: Wayland
Mesa version: 22.1.1-2
CPU/GPU: Ryzen 7 5700G

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 455489] Window Open/Close Animation cannot trigger right away when just switching to another virtual desktop

[Angelo Fallaria]

https://bugs.kde.org/show_bug.cgi?id=455489

--- Comment #1 from Angelo Fallaria  ---
Update: I've narrowed down the cause of the bug. When the virtual desktop
switching effect (Fade/Slide) is still active, the window open/close effects do
not play. If I disable the switching effects, the open/close animations trigger
as usual.

So right now, I think the bug is that the virtual desktop switching effects and
window open/close effects cannot play at the same time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 469928] Session no longer being saved

[Angelo Campos]

https://bugs.kde.org/show_bug.cgi?id=469928

Angelo Campos  changed:

   What|Removed |Added

 CC||noobi...@protonmail.com

--- Comment #1 from Angelo Campos  ---
It also doesn't save your last session tabs etc if you open it trough the
terminal, application menu or Panel.

IF you use the open dolphin shortcut (keybind) it opens the last session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 484377] At Login neochat fails to connect because kwallet starts later

[Angelo Naselli]

https://bugs.kde.org/show_bug.cgi?id=484377

--- Comment #2 from Angelo Naselli  ---
Which is the latest version, just out of curiosity? 23.04.3 is still affected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 484377] New: At Login neochat fails to connect because kwallet starts later

[Angelo Naselli]

https://bugs.kde.org/show_bug.cgi?id=484377

Bug ID: 484377
   Summary: At Login neochat fails to connect because kwallet
starts later
Classification: Applications
   Product: NeoChat
   Version: 23.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: anase...@linux.it
CC: c...@carlschwan.eu
  Target Milestone: ---

When i login to my home with kde the kwallet password is asked, but that
happens later than NeoChat starts, so NeoChat remains in the attempting to
connect screen forever.
Unfortunately there is no way to go on from that but exiting NeoChat and
entering again.

Maybe an option to disconnect/connect again could help as a workaround.

STEPS TO REPRODUCE
1. Enable kwallet
2. Save neochat accounts
3. reboot
4. login

SOFTWARE/OS VERSIONS
 Mageia Linux 9
 Kde plasma version: 5.237.10
 KDE Frameworks Version:5.114.0 
 Qt Version: 5.15.17

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 484377] At Login neochat fails to connect because kwallet starts later

[Angelo Naselli]

https://bugs.kde.org/show_bug.cgi?id=484377

Angelo Naselli  changed:

   What|Removed |Added

   Severity|normal  |major

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 443758] New: Akregator crashes by clicking on a link

[Pier Angelo]

https://bugs.kde.org/show_bug.cgi?id=443758

Bug ID: 443758
   Summary: Akregator crashes by clicking on a link
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: pier.angelo.favar...@gmail.com
  Target Milestone: ---

Application: akregator (5.14.2 (20.04.2))

Qt Version: 5.12.7
Frameworks Version: 5.76.0
Operating System: Linux 5.3.18-59.27-default x86_64
Windowing system: X11
Distribution: openSUSE Leap 15.3

-- Information about the crash:
- What I was doing when the application crashed:

Every time I try to click on a link in a news, akregator crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[KCrash Handler]
#4  0x7f3aac285c08 in vtable for content::RenderFrameHostImpl () from
/usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f3aa9b3d90c in content::WebContentsImpl::CreateNewWindow () at
../../3rdparty/chromium/content/browser/web_contents/web_contents_impl.cc:3758
#6  0x7f3aa99bf521 in
content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr,
base::OnceCallback)>) () at
../../3rdparty/chromium/content/browser/renderer_host/render_frame_host_impl.cc:5041
#7  0x7f3aa5c54c11 in
content::mojom::FrameHostStubDispatch::AcceptWithResponder () at
gen/content/common/frame.mojom.cc:7074
#8  0x7f3aa999789a in
content::mojom::FrameHostStub
>::AcceptWithResponder () at gen/content/common/frame.mojom.h:1026
#9  0x7f3aa78eb785 in mojo::InterfaceEndpointClient::HandleValidatedMessage
() at
../../3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:528
#10 0x7f3aa78ec255 in mojo::MessageDispatcher::Accept () at
../../3rdparty/chromium/mojo/public/cpp/bindings/lib/message_dispatcher.cc:46
#11 0x7f3aa79347ff in AcceptSyncMessage () at
../../3rdparty/chromium/ipc/ipc_mojo_bootstrap.cc:982
#12 0x7f3aa72080a3 in base::OnceCallback::Run() && () at
../../3rdparty/chromium/base/callback.h:100
#13 base::TaskAnnotator::RunTask () at
./../../3rdparty/chromium/base/task/common/task_annotator.cc:163
#14 0x7f3aa721c05c in
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl
() at
./../../3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:332
#15 0x7f3aa721c7d2 in
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork
() at
./../../3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:252
#16 0x7f3aa4fa2bc7 in
QtWebEngineCore::MessagePumpForUIQt::handleScheduledWork (this=0x5648152ac030)
at
/usr/src/debug/libqt5-qtwebengine-5.15.3-bp153.2.2.1.x86_64/src/core/browser_main_parts_qt.cpp:206
#17
QtWebEngineCore::MessagePumpForUIQt::MessagePumpForUIQt()::{lambda()#1}::operator()()
const (__closure=) at
/usr/src/debug/libqt5-qtwebengine-5.15.3-bp153.2.2.1.x86_64/src/core/browser_main_parts_qt.cpp:119
#18 std::_Function_handler::_M_invoke(std::_Any_data
const&) (__functor=...) at /usr/include/c++/7/bits/std_function.h:316
#19 0x7f3aae638a1b in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#20 0x7f3aaf48df9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#21 0x7f3aaf4955b0 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#22 0x7f3aae6083a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#23 0x7f3aae60af67 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#24 0x7f3aae665e13 in ?? () from /usr/lib64/libQt5Core.so.5
#25 0x7f3a9da82694 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#26 0x7f3a9da82a30 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x7f3a9da82abc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#28 0x7f3aae66542f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#29 0x7f3aae6065fa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#30 0x7f3aae60f800 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#31 0x56481352dbbb in main ()
[Inferior 1 (process 3024) detached]

Possible duplicates by query: bug 443669, bug 443586, bug 443435, bug 443430,
bug 443320.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[kgraphviewer] [Bug 477036] New: Graphs are shown with tamil fonts

[Angelo Puglisi]

https://bugs.kde.org/show_bug.cgi?id=477036

Bug ID: 477036
   Summary: Graphs are shown with tamil fonts
Classification: Applications
   Product: kgraphviewer
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kle...@gmail.com
  Reporter: angelopuglis...@msn.com
  Target Milestone: ---

Created attachment 163179
  --> https://bugs.kde.org/attachment.cgi?id=163179&action=edit
kgraphviewer screenshot

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Whenever I open a dot file, it's rendered with tamil fonts, and I get this in
the console output:
```
org.kde.kgraphviewer.lib: Unknown DOT font ' "" '. returning Qt default.
```
If I edit the dot file and add e.g.:
```
node [fontname="notomono"];
edge [fontname="notomono"];
```
then I can properly see it.

This is particularly annoying when working with massif-visualizer, which
generates the callgraph on the fly.
STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kgraphviewer] [Bug 477036] Graphs are shown with tamil fonts

[Angelo Puglisi]

https://bugs.kde.org/show_bug.cgi?id=477036

--- Comment #1 from Angelo Puglisi  ---
It works properly with:
```
diff --git a/src/part/dot2qtconsts.cpp b/src/part/dot2qtconsts.cpp
index c600f70..91d7515 100644
--- a/src/part/dot2qtconsts.cpp
+++ b/src/part/dot2qtconsts.cpp
@@ -24,6 +24,7 @@

 #include 
 #include 
+#include 

 const Dot2QtConsts Dot2QtConsts::m_componentData;

@@ -841,6 +842,9 @@ Dot2QtConsts::Dot2QtConsts()
 i++;
 }

+// Add a default font too
+m_psFonts[""] = QApplication::font();
+
 uint j = 0;
 while (color_lib[j].name) {
 // () << "Adding color " << color_lib[j].name;
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 464068] New: Bluetooth audio randomly cuts out for 2-10 seconds.

[Angelo Campos]

https://bugs.kde.org/show_bug.cgi?id=464068

Bug ID: 464068
   Summary: Bluetooth audio randomly cuts out for 2-10 seconds.
Classification: Plasma
   Product: Bluedevil
   Version: 5.26.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: noobi...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
Bluetooth on 2 different audio devices cuts in and out randomly when idle using
just youtube or spotify.
It doesn't disconnect it just doesn't play audio then when it plays audio again
it has leftover audio from before it cut out for a millisecond. I tried all the
audio codecs available on both devices with the latest Archlinux kernel and an
LTS kernel.


STEPS TO REPRODUCE
1. Turn on the system.
2. Connect with bluetooth.
3. Play audio. 

OBSERVED RESULT
Connects and registers devices fine but the audio randomly cuts out.

EXPECTED RESULT
Connect and register fine and play audio without cutting in and out.

SOFTWARE/OS VERSIONS
Operating System: XeroLinux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.8
Kernel Version: 6.1.4-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i3-10100F CPU @ 3.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2
Manufacturer: ASUS

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 464068] Bluetooth audio randomly cuts out for 2-10 seconds.

[Angelo Campos]

https://bugs.kde.org/show_bug.cgi?id=464068

--- Comment #3 from Angelo Campos  ---
(In reply to Nicolas Fella from comment #2)
> You can try reporting this to bluez or PulseAudio/PipeWire, but from a
> Plasma perspective there's nothing we can do for you

The reason I thought it was KDE related was because I have another install with
my same disto but using gnome and the bluetooth doesn't have the issue but it
also using pipewire and the same drivers for bluetooth.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 408976] New: Crash typing

[Angelo Rota]

https://bugs.kde.org/show_bug.cgi?id=408976

Bug ID: 408976
   Summary: Crash typing
   Product: kdevelop
   Version: 5.1.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: angelo.r...@projectandconsulting.it
  Target Milestone: ---

Application: kdevelop (5.1.2)

Qt Version: 5.9.4
Frameworks Version: 5.45.0
Operating System: Linux 4.12.14-lp150.12.64-default x86_64
Distribution (Platform): openSUSE RPMs

-- Information about the crash:
- What I was doing when the application crashed:
crashed immediately after the insertion of a static prototype c function

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbacf2cf980 (LWP 3448))]

Thread 13 (Thread 0x7fba4f7fe700 (LWP 3783)):
#0  0x7fbacbfc20bb in poll () at /lib64/libc.so.6
#1  0x7fbac37a9129 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbac37a923c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbacc8f1c1b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbacc89a09a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbacc6c94da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbaca1e88ff in  () at /usr/lib64/libKDevPlatformLanguage.so.10
#7  0x7fbacc6ce0ce in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbac5acc569 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbacbfcc85f in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fba69a6e700 (LWP 3577)):
#0  0x7fbacbfc20bb in poll () at /lib64/libc.so.6
#1  0x7fbac37a9129 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbac37a923c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbacc8f1c1b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbacc89a09a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbacc6c94da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbacc6ce0ce in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fbac5acc569 in start_thread () at /lib64/libpthread.so.0
#8  0x7fbacbfcc85f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fba6b7fe700 (LWP 3519)):
#0  0x7fbac5ad28ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbacc6cf3eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fbac0e02b45 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fbac0e06b98 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fbac0e01cfd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fbac0e04adb in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fbacc6ce0ce in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fbac5acc569 in start_thread () at /lib64/libpthread.so.0
#8  0x7fbacbfcc85f in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fba6bfff700 (LWP 3518)):
[KCrash Handler]
#6  0x7fba61ce0210 in  ()
#7  0x7fbaca0f82ca in
KDevelop::IndexedDeclaration::IndexedDeclaration(KDevelop::Declaration const*)
() at /usr/lib64/libKDevPlatformLanguage.so.10
#8  0x7fba4d7a367d in
Python::DeclarationBuilder::visitGlobal(Python::GlobalAst*) () at
/usr/lib64/libkdevpythonduchain.so
#9  0x7fba4d7a0e78 in Python::DeclarationBuilder::visitNode(Python::Ast*)
() at /usr/lib64/libkdevpythonduchain.so
#10 0x7fba4d79b198 in
Python::ContextBuilder::visitFunctionBody(Python::FunctionDefinitionAst*) () at
/usr/lib64/libkdevpythonduchain.so
#11 0x7fba4d7ad395 in
Python::DeclarationBuilder::visitFunctionDefinition(Python::FunctionDefinitionAst*)
() at /usr/lib64/libkdevpythonduchain.so
#12 0x7fba4d7a0e78 in Python::DeclarationBuilder::visitNode(Python::Ast*)
() at /usr/lib64/libkdevpythonduchain.so
#13 0x7fba7ccfef9c in
Python::AstDefaultVisitor::visitCode(Python::CodeAst*) () at
/usr/lib64/libkdevpythonparser.so
#14 0x7fba4d79d3b0 in Python::ContextBuilder::visitCode(Python::CodeAst*)
() at /usr/lib64/libkdevpythonduchain.so
#15 0x7fba4d7a19da in
Python::DeclarationBuilder::visitCode(Python::CodeAst*) () at
/usr/lib64/libkdevpythonduchain.so
#16 0x7fba4d7a0e78 in Python::DeclarationBuilder::visitNode(Python::Ast*)
() at /usr/lib64/libkdevpythonduchain.so
#17 0x7fba4d7b21b5 in  () at /usr/lib64/libkdevpythonduchain.so
#18 0x7fba4d7990fb in Python::ContextBuilder::build(KDevelop::IndexedString
const&, Python::Ast*, KDevelop::ReferencedTopDUContext) () at
/usr/lib64/libkdevpythonduchain.so
#19 0x7fba4d7a15cb in

[Falkon] [Bug 408945] Some pages fail loading

[Emanuel Angelo]

https://bugs.kde.org/show_bug.cgi?id=408945

Emanuel Angelo  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
   Platform|Other   |Archlinux Packages
 Ever confirmed|0   |1
 CC||emanuel.ang...@gmail.com

--- Comment #1 from Emanuel Angelo  ---
It happens with a few other websites, like https://duckduckgo.com/

It is quite frustrating, since DuckDuckGo is the default search engine in
Falkon.

I couldn't find, so far, a pattern for the websites that fail to load. One
thing that I noticed, however, is that the page seems to load almost entirely
before it throws an error.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-gdrive] [Bug 412620] New: impossible connecting gdrive using dolphin

[Angelo Naselli]

https://bugs.kde.org/show_bug.cgi?id=412620

Bug ID: 412620
   Summary: impossible connecting gdrive using dolphin
   Product: kio-gdrive
   Version: 1.2.6
  Platform: Mageia RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: anase...@linux.it
  Target Milestone: ---

This bug happened after upgrading to mageia 7 (version used in mageia 6 worked
well).
Before upgrading i had 3 working connection to gdrive (3 different accounts of
course). After upgrading they disappeared and i am not able to add them back.

Steps to try
1. Open "dolphin gdrive:/"
2. Create a google account
3. No popup login windows appear and wait forever (no errors and no results)

See https://bugs.mageia.org/show_bug.cgi?id=25441 for additional information

-- 
You are receiving this mail because:
You are watching all bug changes.

[KAccounts] [Bug 412620] impossible connecting gdrive using dolphin

[Angelo Naselli]

https://bugs.kde.org/show_bug.cgi?id=412620

--- Comment #2 from Angelo Naselli  ---
What should i check? i seem i can't give any username and password... what i
get as soon as i click on create is here
https://bugs.mageia.org/attachment.cgi?id=11280
and that remains so forever...

-- 
You are receiving this mail because:
You are watching all bug changes.

[KAccounts] [Bug 412620] impossible connecting gdrive using dolphin

[Angelo Naselli]

https://bugs.kde.org/show_bug.cgi?id=412620

--- Comment #3 from Angelo Naselli  ---
ok following is what i get from journalctl:

ott 06 15:13:42 localhost kcmshell5[7204]: Starting new account dialog for
"google"
ott 06 15:13:42 localhost kcmshell5[7204]: "google"
ott 06 15:13:42 localhost kcmshell5[7204]: Looking for plugin ""
ott 06 15:13:42 localhost dbus-daemon[2656]: [session uid= pid=2656]
Activating service name='com.google.code.AccountsSSO.SingleSignOn' requested by
':1.129' (uid= pid=7204 comm="/usr/bin/kcmshell5 kcm_kaccounts")
ott 06 15:13:42 localhost kcmshell5[7204]: Starting auth session with "oauth2"
ott 06 15:13:42 localhost dbus-daemon[2656]: [session uid= pid=2656]
Activated service 'com.google.code.AccountsSSO.SingleSignOn' failed: Failed to
execute program com.google.code.AccountsSSO.SingleSignOn: No such file or
directory
ott 06 15:13:42 localhost kcmshell5[7204]:
QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute
program com.google.code.AccountsSSO.SingleSignOn: No such file or directory")
ott 06 15:13:52 localhost kwin_x11[2740]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 29439, resource id: 119537680, major code: 18
(ChangeProperty), minor code: 0
ott 06 15:13:52 localhost kdeinit5[7199]: kf5.kio.gdrive: No new account
created.
ott 06 15:13:52 localhost kdeinit5[7199]: kf5.kio.gdrive: Going to stat()
QUrl("gdrive:/")
ott 06 15:13:52 localhost kdeinit5[7199]: kf5.kio.gdrive: Going to stat()
QUrl("gdrive:/")
ott 06 15:13:52 localhost kdeinit5[7199]: kf5.kio.gdrive: Going to stat()
QUrl("gdrive:/")
ott 06 15:13:52 localhost kdeinit5[7199]: kf5.kio.gdrive: Fetching content of
QUrl("gdrive:/")

-- 
You are receiving this mail because:
You are watching all bug changes.

[KAccounts] [Bug 412620] impossible connecting gdrive using dolphin

[Angelo Naselli]

https://bugs.kde.org/show_bug.cgi?id=412620

--- Comment #4 from Angelo Naselli  ---
hmm please confirm i need to add signond dependency, i installed it and seems
to ask user and password again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 405427] New: KWin crashes after waking from suspension

[Emanuel Angelo]

https://bugs.kde.org/show_bug.cgi?id=405427

Bug ID: 405427
   Summary: KWin crashes after waking from suspension
   Product: kwin
   Version: 5.13.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: emanuel.ang...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.13.5)

Qt Version: 5.11.1
Frameworks Version: 5.50.0
Operating System: Linux 4.18.0-16-generic x86_64
Distribution: Ubuntu 18.10

-- Information about the crash:
- What I was doing when the application crashed:
I woke up my laptop from suspension by opening the lid.

- Unusual behavior I noticed:
After having the laptop suspended for several hours, when I wake it up it
usually presents an error message. Sometimes it messes up the desktop's icons'
titles and/or the windows' titlebar.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f332a081840 (LWP 10383))]

Thread 5 (Thread 0x7f3307fff700 (LWP 10574)):
#0  0x7f3331e4d2eb in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f3332c2afb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f3331e4d2eb in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f3332c2af68, cond=0x7f3332c2af90) at pthread_cond_wait.c:502
#2  0x7f3331e4d2eb in __pthread_cond_wait (cond=0x7f3332c2af90,
mutex=0x7f3332c2af68) at pthread_cond_wait.c:655
#3  0x7f3332b33e2a in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f3332b33e49 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f3331e47164 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f3334678def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f3322c42700 (LWP 10485)):
#0  0x7f333466c7d6 in __GI_ppoll (fds=0x7f3318000d28, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f20d141 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f20e5b9 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1be16b in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f00d0b6 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f33316781f5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f016c87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3331e47164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f3334678def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f3323fff700 (LWP 10408)):
#0  0x7f333466c7d6 in __GI_ppoll (fds=0x7f331c00b878, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f20d141 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f20e5b9 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1be16b in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f00d0b6 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f333115c545 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6  0x7f016c87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3331e47164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f3334678def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f33294ca700 (LWP 10403)):
#0  0x7f333466c6d9 in __GI___poll (fds=0x7f33294c9c78, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3334171917 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f333417353a in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f33299ac159 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f016c87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3331e47164 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f3334678def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f332a081840 (LWP 10383)):
[KCrash Handler]
#6  0x7f3332da9b0b in KWin::WindowQuadList::makeInterleavedArrays(unsigned
int, KWin::GLVertex2D*, QMatrix4x4 const&) const () at
/usr/lib/x86_64-linux-gnu/libkwineffects.so.11
#7  0x7f3320fdcf42 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#8  0x7f3320fe58b9 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#9  0x7f3320fe59e7 in  () at
/usr/lib/x86_64-linux-gnu/qt5/p

[kdevelop] [Bug 386720] Ubuntu 17.10 becomes very slow / unresponsive / freezes / hangs when opening a small C++ project that uses Boost

[Angelo Puglisi]

https://bugs.kde.org/show_bug.cgi?id=386720

Angelo Puglisi  changed:

   What|Removed |Added

 CC||angelopuglis...@msn.com

--- Comment #1 from Angelo Puglisi  ---
Created attachment 109737
  --> https://bugs.kde.org/attachment.cgi?id=109737&action=edit
gdb stacktrace

I've got an unusually high CPU usage, kdevelop 5.2.1.

I got two threads at 100%, background parser stuck at 0%:
>  PID USER  PR  NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 
>    
> 5823 angelo20   0 2817224 1,019g 347332 R 99,9  6,5  10:59.67 
> /usr/bin/kdevelop     
>  
> 5822 angelo20   0 2817224 1,019g 347332 R 99,9  6,5  12:04.31 
> /usr/bin/kdevelop

It seems something related to libclang, as you can see in attached stacktrace

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 386720] Ubuntu 17.10 becomes very slow / unresponsive / freezes / hangs when opening a small C++ project that uses Boost

[Angelo Puglisi]

https://bugs.kde.org/show_bug.cgi?id=386720

--- Comment #2 from Angelo Puglisi  ---
Created attachment 109738
  --> https://bugs.kde.org/attachment.cgi?id=109738&action=edit
stacktrace with libclang symbols

Attached another stacktrace, now with libclang debugging symbols. I hope it
helps.

>  PID USER  PR  NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
>11426 angelo20   0 2743056 998024 343924 R 99,7  6,1   4:58.01 kdevelop
>11427 angelo20   0 2743056 998024 343924 R 99,7  6,1   4:41.15 kdevelop

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 386720] Ubuntu 17.10 becomes very slow / unresponsive / freezes / hangs when opening a small C++ project that uses Boost

[Angelo Puglisi]

https://bugs.kde.org/show_bug.cgi?id=386720

--- Comment #4 from Angelo Puglisi  ---
(In reply to Milian Wolff from comment #3)
> Can you check what file is triggering this? To do that, enable the language
> debug output and start KDevelop form the command line:
> 
> $ nano ~/config/QtProject/qtlogging.ini
> [Rules]
> kdevplatform.language.debug=true
> $ kdevelop -s ... |& grep -i parse
> 
> So what files are being parsed at the end? How many problems do they have?
> Are the files really large?

I see a few of those:
> kdevplatform.language: creating parse-job  new count of active 
> parse-jobs: 
but I can't see anything suggesting that there are any problems.
I have those lines only for the files I have opened.

Then I have a couple of:
> kdevplatform.language: Aborting cleanup because language plugin is still 
> parsing: "clang"
and nothing more...


I have a kde neon user edition, kdevelop is 4:5.2.1-0neon+16.04+xenial+build38
and libclang1-5.0 1:5.0-3~16.04.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 386720] Ubuntu 17.10 becomes very slow / unresponsive / freezes / hangs when opening a small C++ project that uses Boost

[Angelo Puglisi]

https://bugs.kde.org/show_bug.cgi?id=386720

--- Comment #6 from Angelo Puglisi  ---
(In reply to Milian Wolff from comment #5)
> Is the first kind of output repeating, even while you think kdevelop is
> frozen? Then it's not frozen and actually does useful work. You simply need
> to wait. It should take roughly (hopefully a bit less) as long to parse the
> project in KDevelop as it would take to compile it.
> 
> It would only be a bug if you'd see this output stopping at some files and
> not going anywhere, while CPU usage is high.
> 
> The last kind of output is OK, it's internal debug output and expected. You
> can ignore it.

My kdevelop is not frozen, it's still working but the parser is stuck at 0% and
I have the parser thread at 100% all the time (I mean my whole working day).
Except from the last line I have no other output.


I tried to reproduce the issue with a simpler project, including some boost
headers I use, but I have only a cpu peak for a couple of seconds and then it
stops.
I'll try to figure out something to be helpful

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 487662] New: Plasma crashed after logon

[Marcos Angelo Molizane]

https://bugs.kde.org/show_bug.cgi?id=487662

Bug ID: 487662
   Summary: Plasma crashed after logon
Classification: Plasma
   Product: plasmashell
   Version: 6.0.5
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: mam...@hotmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.5)

Qt Version: 6.7.1
Frameworks Version: 6.2.0
Operating System: Linux 6.9.2-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.5 [CoredumpBackend]

-- Information about the crash:
When plasma was loading, the crash report was opened with the details about the
issue in plasmashell, I didn't see anything different on loading.

Only the konsole and dolphin applications were loaded (from the last closed
session).

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x7a0a32cea343 in QQuickPane::qt_static_metacall (_o=0x583901942570,
_c=, _id=2, _a=0x7fff406d3e60) at
/usr/src/debug/qt6-declarative/qtdeclarative/src/quicktemplates/qquickpane_p.h:67
#6  0x7a0a32cea3f2 in QQuickPane::qt_metacall
(this=this@entry=0x583901942570, _c=_c@entry=QMetaObject::ReadProperty, _id=2,
_a=_a@entry=0x7fff406d3e60) at
/usr/src/debug/qt6-declarative/build/src/quicktemplates/QuickTemplates2_autogen/include/moc_qquickpane_p.cpp:220
#7  0x7a0a32ced35e in QQuickPage::qt_metacall (this=0x583901942570,
_c=QMetaObject::ReadProperty, _id=, _a=0x7fff406d3e60) at
/usr/src/debug/qt6-declarative/build/src/quicktemplates/QuickTemplates2_autogen/include/moc_qquickpage_p.cpp:270
#8  0x7a0a3aae1fcb in QQmlObjectCreator::setupBindings
(this=0x7fff406d44e0, mode=...) at
/usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlobjectcreator.cpp:783
#9  0x7a0a3aae6b28 in QQmlObjectCreator::populateInstance
(this=this@entry=0x7fff406d44e0, index=-1, index@entry=0, instance=0x0,
instance@entry=0x583901942570, bindingTarget=,
bindingTarget@entry=0x583901942570, valueTypeProperty=,
valueTypeProperty@entry=0x0, binding=binding@entry=0x0) at
/usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlobjectcreator.cpp:1781


Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 487662] Plasma crashed after logon

[Marcos Angelo Molizane]

https://bugs.kde.org/show_bug.cgi?id=487662

--- Comment #1 from Marcos Angelo Molizane  ---
Created attachment 169899
  --> https://bugs.kde.org/attachment.cgi?id=169899&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 487662] Plasma crashed after logon

[Marcos Angelo Molizane]

https://bugs.kde.org/show_bug.cgi?id=487662

--- Comment #3 from Marcos Angelo Molizane  ---
(In reply to David Edmundson from comment #2)
> The crash is deep in our upstream libraries. Have you seen this crash since?

It only happened once until now.
I rebooted 4 times after the crash and it did not happen again

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 485299] New: Black screen on startup

[Marcos Angelo Molizane]

https://bugs.kde.org/show_bug.cgi?id=485299

Bug ID: 485299
   Summary: Black screen on startup
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: mam...@hotmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.3)

Qt Version: 6.6.3
Frameworks Version: 6.0.0
Operating System: Linux 6.8.4-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.3 [CoredumpBackend]

-- Information about the crash:
On system start-up, the windows from the last session have been opened, but the
desktop environment has no (wallpapers, desktop icons, or taskbar).

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 1462]
[New LWP 1489]
[New LWP 1487]
[New LWP 1657]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7e5e07aab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7e5e032361c0 (LWP 1462))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7e5e032361c0 (LWP 1462))]

Thread 4 (Thread 0x7e5e00e006c0 (LWP 1657)):
#0  0x7e5e07b190bf in poll () at /usr/lib/libc.so.6
#1  0x7e5e06e3b306 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x7e5e06ddb712 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7e5e08373cd4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x7e5e081446ee in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x7e5e08221bbf in QThread::run() () at /usr/lib/libQt6Core.so.6
#6  0x7e5e082a15d3 in ??? () at /usr/lib/libQt6Core.so.6
#7  0x7e5e07aa955a in ??? () at /usr/lib/libc.so.6
#8  0x7e5e07b26a3c in ??? () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7e5e02c006c0 (LWP 1487)):
#0  0x7e5e07b190bf in poll () at /usr/lib/libc.so.6
#1  0x7e5e06e3b306 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x7e5e06ddb712 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7e5e08373cd4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x7e5e081446ee in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x7e5e08221abf in QThread::exec() () at /usr/lib/libQt6Core.so.6
#6  0x7e5e08f769df in ??? () at /usr/lib/libQt6DBus.so.6
#7  0x7e5e082a15d3 in ??? () at /usr/lib/libQt6Core.so.6
#8  0x7e5e07aa955a in ??? () at /usr/lib/libc.so.6
#9  0x7e5e07b26a3c in ??? () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7e5e022006c0 (LWP 1489)):
#0  0x7e5e07b190bf in poll () at /usr/lib/libc.so.6
#1  0x7e5e0a8ec20b in ??? () at /usr/lib/libxcb.so.1
#2  0x7e5e0a8edf3d in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7e5e031def2e in ??? () at
/usr/lib/qt6/plugins/platforms/../../../libQt6XcbQpa.so.6
#4  0x7e5e082a15d3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7e5e07aa955a in ??? () at /usr/lib/libc.so.6
#6  0x7e5e07b26a3c in ??? () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7e5e032361c0 (LWP 1462)):
[KCrash Handler]
#4  0x7e5e09789ad0 in QQuickItem::setWidth(double) () at
/usr/lib/libQt6Quick.so.6
#5  0x7e5e097a416f in ??? () at /usr/lib/libQt6Quick.so.6
#6  0x7e5e0818ef3c in
QPropertyBindingPrivate::evaluateRecursive(QVarLengthArray&, QBindingStatus*) () at /usr/lib/libQt6Core.so.6
#7  0x7e5e0818f22f in
QtPrivate::QPropertyBindingData::setBinding(QUntypedPropertyBinding const&,
QUntypedPropertyData*, void (*)(QUntypedPropertyData*), bool (*)(QMetaType,
QUntypedPropertyData*, QtPrivate::QPropertyBindingFunction)) () at
/usr/lib/libQt6Core.so.6
#8  0x7e5e0979c6ff in ??? () at /usr/lib/libQt6Quick.so.6
#9  0x7e5e092d3d12 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at
/usr/lib/libQt6Qml.so.6
#10 0x7e5e0925795d in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () at /usr/lib/libQt6Qml.so.6
#11 0x7e5e09258815 in QQmlComponentPrivate::completeCreate() () at
/usr/lib/libQt6Qml.so.6
#12 0x7e5df9350244 in ??? () at
/usr/lib/qt6/qml/org/kde/plasma/private/containmentlayoutmanager/libcontainmentlayoutmanagerplugin.so
#13 0x7e5df93531f3 in ??? () at
/usr/lib/qt6/qml/org/kde/plasma/private/containmentlayoutmanager/libcontai

[plasmashell] [Bug 485299] Black screen on startup

[Marcos Angelo Molizane]

https://bugs.kde.org/show_bug.cgi?id=485299

--- Comment #2 from Marcos Angelo Molizane  ---
Hello Nate!
Thanks for your reply!
After I sent the report, the plasmashell entered an infinite loop, and I forced
my computer to turn off after the 20th crash report window was opened.
I checked all the 20 backtraces and all the contents look the same, without the
information in the same places.

I attached the backtrace sent in this report, but I believe it is not useful
either.

Is there something more that I can do to improve the backtrace?

  Size on Disk: 4.7M
   Message: Process 1462 (plasmashell) of user 1000 dumped core.

Stack trace of thread 1462:
#0  0x7e5e07aab32c n/a (libc.so.6 + 0x8d32c)
#1  0x7e5e07a5a6c8 raise (libc.so.6 + 0x3c6c8)
#2  0x7e5e0a8d843f _ZN6KCrash19defaultCrashHandlerEi
(libKF6Crash.so.6 + 0x643f)
#3  0x7e5e07a5a770 n/a (libc.so.6 + 0x3c770)
#4  0x7e5e09789ad0 _ZN10QQuickItem8setWidthEd
(libQt6Quick.so.6 + 0x189ad0)
#5  0x7e5e097a416f n/a (libQt6Quick.so.6 + 0x1a416f)
#6  0x7e5e0818ef3c
_ZN23QPropertyBindingPrivate17evaluateRecursiveER15QVarLengthArrayI19QBindingObserverPtrLx256EEP14QBindingStatus
(libQt6Core.so.6 + 0x18ef3c)
#7  0x7e5e0818f22f
_ZN9QtPrivate20QPropertyBindingData10setBindingERK23QUntypedPropertyBindingP20QUntypedPropertyDataPFvS5_EPFb9QMetaTypeS5_NS_24QPropertyBindingFunctionEE
(libQt6Core.so.6 + 0x18f22f)
#8  0x7e5e0979c6ff n/a (libQt6Quick.so.6 + 0x19c6ff)
#9  0x7e5e092d3d12
_ZN17QQmlObjectCreator8finalizeER26QQmlInstantiationInterrupt (libQt6Qml.so.6 +
0x2d3d12)
#10 0x7e5e0925795d
_ZN20QQmlComponentPrivate8completeEP17QQmlEnginePrivatePNS_17ConstructionStateE
(libQt6Qml.so.6 + 0x25795d)
#11 0x7e5e09258815
_ZN20QQmlComponentPrivate14completeCreateEv (libQt6Qml.so.6 + 0x258815)
#12 0x7e5df9350244 n/a
(libcontainmentlayoutmanagerplugin.so + 0x10244)
#13 0x7e5df93531f3 n/a
(libcontainmentlayoutmanagerplugin.so + 0x131f3)
#14 0x7e5e092d4106
_ZN17QQmlObjectCreator8finalizeER26QQmlInstantiationInterrupt (libQt6Qml.so.6 +
0x2d4106)
#15 0x7e5e0925795d
_ZN20QQmlComponentPrivate8completeEP17QQmlEnginePrivatePNS_17ConstructionStateE
(libQt6Qml.so.6 + 0x25795d)
#16 0x7e5e09258815
_ZN20QQmlComponentPrivate14completeCreateEv (libQt6Qml.so.6 + 0x258815)
#17 0x7e5e0ac1537e
_ZN11PlasmaQuick15SharedQmlEngine25createObjectFromComponentEP13QQmlComponentP11QQmlContextRK5QHashI7QString8QVariantE
(libPlasmaQuick.so.6 + 0x4a37e)
#18 0x7e5e0abf62a4 n/a (libPlasmaQuick.so.6 + 0x2b2a4)
#19 0x7e5e0abf6b68
_ZN11PlasmaQuick15AppletQuickItem28setPreloadFullRepresentationEb
(libPlasmaQuick.so.6 + 0x2bb68)
#20 0x7e5e09230138 n/a (libQt6Qml.so.6 + 0x230138)
#21 0x7e5e092d4a6c
_ZN17QQmlObjectCreator16setPropertyValueEPK16QQmlPropertyDataPKN3QV412CompiledData7BindingE
(libQt6Qml.so.6 + 0x2d4a6c)
#22 0x7e5e092d7513
_ZN17QQmlObjectCreator18setPropertyBindingEPK16QQmlPropertyDataPKN3QV412CompiledData7BindingE
(libQt6Qml.so.6 + 0x2d7513)
#23 0x7e5e092da5be
_ZN17QQmlObjectCreator13setupBindingsE6QFlagsINS_11BindingModeEE
(libQt6Qml.so.6 + 0x2da5be)
#24 0x7e5e092e23bb
_ZN17QQmlObjectCreator16populateInstanceEiP7QObjectS1_PK16QQmlPropertyDataPKN3QV412CompiledData7BindingE
(libQt6Qml.so.6 + 0x2e23bb)
#25 0x7e5e092d63ee
_ZN17QQmlObjectCreator14createInstanceEiP7QObjectb (libQt6Qml.so.6 + 0x2d63ee)
#26 0x7e5e092e3c24 n/a (libQt6Qml.so.6 + 0x2e3c24)
#27 0x7e5e0925b0b8
_ZN20QQmlComponentPrivate11beginCreateE14QQmlRefPointerI15QQmlContextDataE
(libQt6Qml.so.6 + 0x25b0b8)
#28 0x7e5e0925b2fd
_ZN13QQmlComponent11beginCreateEP11QQmlContext (libQt6Qml.so.6 + 0x25b2fd)
#29 0x7e5e0ac14acd
_ZN11PlasmaQuick15SharedQmlEngine9setSourceERK4QUrl (libPlasmaQuick.so.6 +
0x49acd)
#30 0x7e5e0abf9ce6
_ZN11PlasmaQuick15AppletQuickItem13itemForAppletEPN6Plasma6AppletE
(libPlasmaQuick.so.6 + 0x2ece6)
#31 0x7e5e0ac0f8cc n/a (libPlasmaQuick.so.6 + 0x448cc)
#32 0x5cc6e8cdc6e3 n/a (plasmashell + 0x656e3)
#33 0x5cc6e8cd6758 n/a (plasmashell + 0x5f758)
#34 0x7e5e08191599 n/a (libQt6Core.so.6 + 0x191599)
#35 0x7e5e0a6c5616
_ZN11KActivities8Consumer20serviceStatusChangedENS0_13ServiceStatusE
(libPlasmaActivities.so.6 + 0xd616)
#36 0x7e5e08191599 n/a (libQt6Core.so.6 + 0x191599)
#37 0x7e5e0a6d3191 n/a (libPlasmaActivities.so.6 + 0x1b191)
#38 0x7e5e0a6d6742 n

[plasmashell] [Bug 431304] New: Plasma Crash after login

[Felipe Angelo Sgarbi]

https://bugs.kde.org/show_bug.cgi?id=431304

Bug ID: 431304
   Summary: Plasma Crash after login
   Product: plasmashell
   Version: 5.20.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: akatsukil...@yahoo.co.jp
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.20.4)

Qt Version: 5.15.2
Frameworks Version: 5.75.0
Operating System: Linux 5.9.16-200.fc33.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (Workstation Edition)

-- Information about the crash:
- What I was doing when the application crashed:
Had just logged in my computer. Plasma loaded, screen sudden went black and
returned to normal. When it returned i had the bug report notification on
status bar.

- Unusual behavior I noticed:
Despite the sudden black screen, none. Was the first time that had happened.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  0x7f688c5b99d5 in raise () from /lib64/libc.so.6
#5  0x7f688c5a28a4 in abort () from /lib64/libc.so.6
#6  0x7f688c5a2789 in __assert_fail_base.cold () from /lib64/libc.so.6
#7  0x7f688c5b2026 in __assert_fail () from /lib64/libc.so.6
#8  0x7f68651e3da7 in nouveau_pushbuf_data () from
/lib64/libdrm_nouveau.so.2
#9  0x7f68651e3d07 in nouveau_pushbuf_data () from
/lib64/libdrm_nouveau.so.2
#10 0x7f68651e3e2f in pushbuf_submit () from /lib64/libdrm_nouveau.so.2
#11 0x7f68651e4247 in pushbuf_flush.isra () from /lib64/libdrm_nouveau.so.2
#12 0x7f68651e4faa in pushbuf_validate () from /lib64/libdrm_nouveau.so.2
#13 0x7f686aed3395 in nvc0_state_validate () from
/usr/lib64/dri/nouveau_dri.so
#14 0x7f686aed348b in nvc0_state_validate_3d () from
/usr/lib64/dri/nouveau_dri.so
#15 0x7f686ae1e798 in nvc0_clear () from /usr/lib64/dri/nouveau_dri.so
#16 0x7f686a676f88 in st_Clear () from /usr/lib64/dri/nouveau_dri.so
#17 0x7f688e5731aa in QSGBatchRenderer::Renderer::renderBatches() () from
/lib64/libQt5Quick.so.5
#18 0x7f688e573902 in QSGBatchRenderer::Renderer::render() () from
/lib64/libQt5Quick.so.5
#19 0x7f688e55e034 in QSGRenderer::renderScene(QSGBindable const&) () from
/lib64/libQt5Quick.so.5
#20 0x7f688e55e503 in QSGRenderer::renderScene(unsigned int) () from
/lib64/libQt5Quick.so.5
#21 0x7f688e5b2665 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from
/lib64/libQt5Quick.so.5
#22 0x7f688e612e29 in QQuickWindowPrivate::renderSceneGraph(QSize const&,
QSize const&) () from /lib64/libQt5Quick.so.5
#23 0x7f688e5a0fe5 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
() from /lib64/libQt5Quick.so.5
#24 0x7f688e61bf48 in QQuickWindow::event(QEvent*) () from
/lib64/libQt5Quick.so.5
#25 0x7f688d81aec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#26 0x7f688cbb2bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#27 0x7f688cfdefa4 in QPlatformWindow::windowEvent(QEvent*) () from
/lib64/libQt5Gui.so.5
#28 0x7f688d821aaa in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#29 0x7f688cbb2bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#30 0x7f688cbfea03 in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5
#31 0x7f688cbff344 in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#32 0x7f688b0fe96f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#33 0x7f688b150758 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#34 0x7f688b0fbd43 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#35 0x7f688cbff6f3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#36 0x7f688cbb157b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#37 0x7f688cbb91b4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#38 0x557ed77597ca in main ()
[Inferior 1 (process 1768) detached]

Possible duplicates by query: bug 422433, bug 414938, bug 405226, bug 396459,
bug 388308.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 371757] New: kmail crashed on startup

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371757

Bug ID: 371757
   Summary: kmail crashed on startup
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.8.4-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I just started the app. The second time, it worked without error.

The crash does not seem to be reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f70c1624940 (LWP 9301))]

Thread 34 (Thread 0x7f6f5bfff700 (LWP 9369)):
#0  0x7f70b42ea10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f70aa1f46c9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f70aa1f4ce9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f70aa1f4ea0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f70aa1f1b27 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f70b42e4454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f70be45239f in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f6fe25b2700 (LWP 9363)):
#0  0x7f70b42ea10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f70a469b834 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f70a469b879 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f70b42e4454 in start_thread () at /lib64/libpthread.so.0
#4  0x7f70be45239f in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f6fe2db3700 (LWP 9361)):
#0  0x7f70be44968d in poll () at /lib64/libc.so.6
#1  0x7f70b2526876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f70b252698c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f70bef7f79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f70bef291ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f70bed578b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f70bed5c558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f70b42e4454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f70be45239f in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f6ff0931700 (LWP 9353)):
#0  0x7f70b2525d02 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f70b252679b in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f70b252698c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f70bef7f79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f70bef291ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f70bed578b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f70bed5c558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f70b42e4454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f70be45239f in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7f6ff47ba700 (LWP 9351)):
#0  0x7f70be42255d in nanosleep () at /lib64/libc.so.6
#1  0x7f70be44b434 in usleep () at /lib64/libc.so.6
#2  0x7f7014b15092 in  () at /usr/lib64/libeToken.so
#3  0x7f7014b154ef in  () at /usr/lib64/libeToken.so
#4  0x7f70b42e4454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f70be45239f in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f6ff4fbb700 (LWP 9349)):
#0  0x7f70be42255d in nanosleep () at /lib64/libc.so.6
#1  0x7f70be44b434 in usleep () at /lib64/libc.so.6
#2  0x7f7014ac5539 in  () at /usr/lib64/libeToken.so
#3  0x7f7014ac562a in  () at /usr/lib64/libeToken.so
#4  0x7f70b42e4454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f70be45239f in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f70157fa700 (LWP 9342)):
#0  0x7f70b42ea10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f70aa1f46c9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f70aa1f4ce9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f70aa1f4ea0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f70aa1f1b27 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f70b42e4454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f70be45239f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f7015ffb700 (LWP 9341)):
#0  0x7f7099a62b90 in pa_fdsem_before_poll () at
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#1  0x7f7099a7a847 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7f70a142965c in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0
#3  0x7f70a14

[kdeplasma-addons] [Bug 371829] New: mediaframe reading files even after all plasmoids where removed

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371829

Bug ID: 371829
   Summary: mediaframe reading files even after all plasmoids
where removed
   Product: kdeplasma-addons
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Hello,

I'm using plasma5-addons-5.8.2-1.1.x86_64 from OpenSUSE Tumbleweed.

I noticed that my plasma was eating CPU and with strace -e "read,open" -p
$(pidof plasmashell), I checked that it was frequently opening and reading the
media I used in the mediaframe. The problem is that it keeps doing that even
after the plasmoid was removed. As I added/removed the plasmoid a bunch of
times, plasma was openning and reading the same media files a bunch of times
per second!

This is the frequency of each syscall during a few seconds monitoring:

3 mmap
3 munmap
4 access
5 write
16 lstat
23 ioctl
35 statfs
70 getdents
90 writev
270 fcntl
305 close
306 open
577 fstat
804 lseek
2825 stat
5107 read
16926 recvmsg
17230 poll
33774 futex

read and open are almost exclusively generated by mediaframe (and probably
others).

As a workaround, I moved the files, which might generate a read error and
somehow stopped the loop process. My cpu usage, then, reduced from 160% to 40%.

BTW, it would be nice to have mediaframe on bugzilla components list

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 371830] New: mediaframe: leave residual config after removed, reuse it on readd

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371830

Bug ID: 371830
   Summary: mediaframe: leave residual config after removed, reuse
it on readd
   Product: kdeplasma-addons
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Hello,

I'm using plasma5-addons-5.8.2-1.1.x86_64 from OpenSUSE Tumbleweed.

When removed, mediaframe can leave some configs behind. If readded, those
configs are reused (this is not how plasma works :-). If another plasmoid is
added, I get this strange result:

[Containments][10][Applets][104]
immutability=1
plugin=org.kde.plasma.notes

[Containments][10][Applets][104][Configuration][General]
noteId=9c6c8f5a-9788-4392-805f-b581af13f1

[Containments][10][Applets][104][Configuration][Paths]
pathList={"path":"http://www.ciram.epagri.sc.gov.br/images/radar/ultima_RADAR.png"\\,"type":"file"},{"path":"http://www.ciram.epagri.sc.gov.br/images/radar/anima_RADAR.gif"\\,"type":"file"}

Applet 104 was a removed mediaframe and not it is a notes. However,
[Configuration][Paths] from mediaframe is still there.
There might be some cleanup missing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 371832] New: mediaframe: next/previous buttons are not usable during image transaction

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371832

Bug ID: 371832
   Summary: mediaframe: next/previous buttons are not usable
during image transaction
   Product: kdeplasma-addons
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Hello,

I'm using plasma5-addons-5.8.2-1.1.x86_64 from OpenSUSE Tumbleweed.

If someone tries to go to the next media in mediaframe quickly pressing the
next/previous buttons, it opens the image in an external program as if I
clicked on the image. The problem seems that during the image translation, the
button is not functional (I can see the button fade in when it will work).
Maybe the buttons are just under the image during the transition.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 371833] New: mediaframe: random order still considers current image

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371833

Bug ID: 371833
   Summary: mediaframe: random order still considers current image
   Product: kdeplasma-addons
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Hello,

I'm using plasma5-addons-5.8.2-1.1.x86_64 from OpenSUSE Tumbleweed.

When random order is defined on mediaframe, it still can randomly selects the
current image. When the list of images are very small as 2, there is a chance
of 50% of next/prev button or transition doing nothing. Probably what a user
would expect is that next/prev image would be any but the current one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 371832] mediaframe: next/previous buttons are not usable during image transition

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371832

Luiz Angelo De Luca  changed:

   What|Removed |Added

Summary|mediaframe: next/previous   |mediaframe: next/previous
   |buttons are not usable  |buttons are not usable
   |during image transaction|during image transition

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 371834] New: mediaframe: fails to use some remote images

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371834

Bug ID: 371834
   Summary: mediaframe: fails to use some remote images
   Product: kdeplasma-addons
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Hello,

Using this config on plasmawindowed:

pathList={"path":"https://media.giphy.com/media/AsnwZm3ttHnFu/giphy.gif"\\,"type":"file"},{"path":"https://upload.wikimedia.org/wikipedia/commons/thumb/4/41/Dore-munchausen-illustration.jpg/100px-Dore-munchausen-illustration.jpg"\\,"type":"file"}

Bart is shown when applet is opened. Afterwards, it is gone.

This is the log I got:

Adding "https://media.giphy.com/media/AsnwZm3ttHnFu/giphy.gif"; as remote file
Can't watch remote file "https://media.giphy.com/media/AsnwZm3ttHnFu/giphy.gif";
for changes
Adding
"https://upload.wikimedia.org/wikipedia/commons/thumb/4/41/Dore-munchausen-illustration.jpg/100px-Dore-munchausen-illustration.jpg";
as remote file
"https://media.giphy.com/media/AsnwZm3ttHnFu/giphy.gif"; doesn't exist locally,
trying remote.
Saving download to "/tmp/85c4b8cb41a134953327dccce74c3712_giphy.gif"
Saved to "/tmp/85c4b8cb41a134953327dccce74c3712_giphy.gif"
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediaframe/contents/ui/main.qml:179:13:
QML Image: Cannot open: file:///tmp/85c4b8cb41a134953327dccce74c3712_giphy.gif
Can't watch remote file "/tmp/85c4b8cb41a134953327dccce74c3712_giphy.gif" for
changes
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediaframe/contents/ui/main.qml:195:13:
QML Image: Cannot open: file:///tmp/85c4b8cb41a134953327dccce74c3712_giphy.gif
Resetting next count from 2 due to queue size 1
"https://upload.wikimedia.org/wikipedia/commons/thumb/4/41/Dore-munchausen-illustration.jpg/100px-Dore-munchausen-illustration.jpg";
is cached as
"/tmp/bed0fd620241aa9d40f2b99fe2736ace_100px-Dore-munchausen-illustration.jpg"

The file is really gone from /tmp/85c4b8cb41a134953327dccce74c3712_giphy.gif.
It seems that it could not save the cache file, but it believed that it did.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 371834] mediaframe: fails to use some remote images

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=371834

--- Comment #1 from Luiz Angelo De Luca  ---
BTW, with https://git.reviewboard.kde.org/r/129227/, the same image can
generate a segfault. This might give some hint about the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 372196] New: kate crash when opening files on system mounted cifs share (not kio)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=372196

Bug ID: 372196
   Summary: kate crash when opening files on system mounted cifs
share (not kio)
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Application: kate (16.08.2)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

I just tried to open a shell script on a mounted shared. Kate simply crashed.
I did not try to use smb:// kio.
The same file opens nicely if copied to local FS

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb2ab641040 (LWP 22912))]

Thread 38 (Thread 0x7fb220ff9700 (LWP 31834)):
#0  0x7fb2a25d110f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb2a661540b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1164b80) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x109aac0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fb282e5607b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x1171d90, th=) at
/usr/src/debug/threadweaver-5.27.0/src/weaver.cpp:594
#4  0x7fb282e56e60 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x1171d90,
th=, th@entry=0x7fb204003190,
threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at
/usr/src/debug/threadweaver-5.27.0/src/weaver.cpp:554
#5  0x7fb282e5b018 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x109cfe0, th=0x7fb204003190, wasBusy=) at
/usr/src/debug/threadweaver-5.27.0/src/workinghardstate.cpp:66
#6  0x7fb282e55fdd in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fb204003190, wasBusy=) at
/usr/src/debug/threadweaver-5.27.0/src/weaver.cpp:568
#7  0x7fb282e58ea9 in ThreadWeaver::Thread::run (this=0x7fb204003190) at
/usr/src/debug/threadweaver-5.27.0/src/thread.cpp:103
#8  0x7fb2a6614558 in QThreadPrivate::start (arg=0x7fb204003190) at
thread/qthread_unix.cpp:344
#9  0x7fb2a25cb454 in start_thread () from /lib64/libpthread.so.0
#10 0x7fb2a5c1d39f in clone () from /lib64/libc.so.6

Thread 37 (Thread 0x7fb2217fa700 (LWP 31833)):
#0  0x7fb2a25d110f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb2a661540b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1164b80) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x109aac0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fb282e5607b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x1171d90, th=) at
/usr/src/debug/threadweaver-5.27.0/src/weaver.cpp:594
#4  0x7fb282e56e60 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x1171d90,
th=, th@entry=0x7fb210002f90,
threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at
/usr/src/debug/threadweaver-5.27.0/src/weaver.cpp:554
#5  0x7fb282e5b018 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x109cfe0, th=0x7fb210002f90, wasBusy=) at
/usr/src/debug/threadweaver-5.27.0/src/workinghardstate.cpp:66
#6  0x7fb282e55fdd in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fb210002f90, wasBusy=) at
/usr/src/debug/threadweaver-5.27.0/src/weaver.cpp:568
#7  0x7fb282e58ea9 in ThreadWeaver::Thread::run (this=0x7fb210002f90) at
/usr/src/debug/threadweaver-5.27.0/src/thread.cpp:103
#8  0x7fb2a6614558 in QThreadPrivate::start (arg=0x7fb210002f90) at
thread/qthread_unix.cpp:344
#9  0x7fb2a25cb454 in start_thread () from /lib64/libpthread.so.0
#10 0x7fb2a5c1d39f in clone () from /lib64/libc.so.6

Thread 36 (Thread 0x7fb221ffb700 (LWP 31832)):
#0  0x7fb2a25d110f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb2a661540b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1164b80) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x109aac0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fb282e5607b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x1171d90, th=) at
/usr/src/debug/threadweaver-5.27.0/src/weaver.cpp:594
#4  0x7fb282e56e60 in
ThreadWeaver::Weaver::takeFir

[kate] [Bug 372196] kate crash when opening files on system mounted cifs share (not kio)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=372196

--- Comment #5 from Luiz Angelo De Luca  ---
OK, I'll join the github discuss

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 228210] KWin crashed when dragging Maximized Window to top of second Screen (to maximize it there with smaller screen-size)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=228210

Luiz Angelo De Luca  changed:

   What|Removed |Added

 CC||luizl...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 459804] New: Mouse cursor is hidden windows when crossing the screen over a window on both screens

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=459804

Bug ID: 459804
   Summary: Mouse cursor is hidden windows when crossing the
screen over a window on both screens
Classification: Plasma
   Product: kwin
   Version: 5.25.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

SUMMARY

If I put any non-Qt/Kde window crossing two screens and move the mouse over it,
the cursor is hidden when it crosses the screen border until it reaches that
window border. It does not reappears if I simply move back to the old screen.
The same does not happen with Qt apps. Mouse even like click, does still work
(but it does not make the mouse cursor back).

1. configure side-by-side screen
2. open xterm
3. put the xterm screen over the border between the two screens
4. move the mouse cursor over the xterm window and across the screen border

OBSERVED RESULT

5. mouse cursor is hidden.

EXPECTED RESULT

5. mouse cursor should be still there as usual.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed 20220917
KDE Plasma Version:  5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 459804] Mouse cursor is hidden windows when crossing the screen over a window on both screens

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=459804

Luiz Angelo De Luca  changed:

   What|Removed |Added

   Platform|Other   |OpenSUSE

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 459804] Mouse cursor is hidden windows when crossing the screen over a window on both screens

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=459804

--- Comment #2 from Luiz Angelo De Luca  ---
Created attachment 152509
  --> https://bugs.kde.org/attachment.cgi?id=152509&action=edit
Photo of a hidden cursor

I activated the "Follow mouse effect" to show that the mouse cursor was there
and externally took a picture. I tried to record the screen or that a
screenshot but the mouse was there.

My multiscreen is not a simple side-by-side. The left monitor is rotated, with
extra border over and under the right monitor. There is no screen overlap.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 459804] Mouse cursor is hidden windows when crossing the screen over a window on both screens

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=459804

--- Comment #4 from Luiz Angelo De Luca  ---
(In reply to Vlad Zahorodnii from comment #3)
> Can you post the output of `qdbus org.kde.KWin /KWin supportInformation`?

https://invent.kde.org/-/snippets/2363

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 459804] Mouse cursor is hidden windows when crossing the screen over a window on both screens

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=459804

--- Comment #6 from Luiz Angelo De Luca  ---
(In reply to Vlad Zahorodnii from comment #5)
> Hmm, I see nothing "weird" about your setup. A shot in the dark:
> 
> - can you run kwin with KWIN_DRM_SW_ROTATIONS_ONLY=1 environment variable
> set? e.g. you could put it in /etc/environment and reboot the computer
> 
> - if the issue is still reproducible, can you try setting
> KWIN_FORCE_SW_CURSOR=1 too?

With KWIN_DRM_SW_ROTATIONS_ONLY=1, the issue is still there
With KWIN_FORCE_SW_CURSOR=1, it worked as expected. 

I tested the KWIN_FORCE_SW_CURSOR keeping KWIN_DRM_SW_ROTATIONS_ONLY set. Is it
worth it to test it without KWIN_DRM_SW_ROTATIONS_ONLY?

The software cursor now draws a darker region over the konsole black (with a
little bit transparent) background for a second while moving when konsole when
the window under it is mostly white. I don't know how software cursors works
today but in the old times, we used to copy the region where the cursor would
appear, draw, before drawing the next cursor position, erase it pasting the
copied region. It looks like kwin copied konsole region (or asked konsole to do
it) without considering the transparency effect, just like the spectacle
ignores that same effect while taking a screen shot.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 445953] New: plasma notes cannot apply the same format as the next line when triple clicked

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=445953

Bug ID: 445953
   Summary: plasma notes cannot apply the same format as the next
line when triple clicked
   Product: plasmashell
   Version: 5.23.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: luizl...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

STEPS TO REPRODUCE
1. add a plasma applet note
2. type two lines
3. select the second line with triple click
4. click the bold button (the line is now bold)
5. select the first line with triple click, apply any formatting like bold

OBSERVED RESULT
6. click the bold button (the line is NOT bold) 

When I triple clicked the first line, the cursor was actually at the beginning
of the second line and the bold button was shown as applied. It looks like it
is misplacing the cursor when I do triple clicks.

The issue is not with bold but with any formatting. It does not happen if the
applied format is different nor when it is removing a format.

EXPECTED RESULT
6. click the bold button (the line should be bold) 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.23.3 OpenSUSE Tumbleweed

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 402370] Multi monitor config lost while returning from standby

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=402370

Luiz Angelo De Luca  changed:

   What|Removed |Added

 CC||luizl...@gmail.com

--- Comment #3 from Luiz Angelo De Luca  ---
This bug is still with us in 5.24.5, at least with wayland.

I have two side-by-side monitors, with the left one rotated and the right one
primary.

When I return from standby, the left screen reduces the resolution, isolating
both screens. I cannot move mouse between them anymore as their borders do not
touch anymore.

It also happens if I simply power it off and on again. From kscreen, I can see
it detected much less resolution options, with the greater one being 1024x768
(much less than the supported 1920x1080). If I turn it off/on again, it
correctly detects the resolution. However, as the last time it reduced the
resolution, it will stick with that lower resolution until I manually fix it.

The desktop background/plasmoids are also inconsistent. I normally use notes
but it is rare to ever return to the same "desktop". Each boot, it looks like
it create a new desktop config and forget everything I did with it. And,
sometimes, the background just becomes a plain black.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 453673] New: Make it possible to recover lost notes

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=453673

Bug ID: 453673
   Summary: Make it possible to recover lost notes
   Product: kdeplasma-addons
   Version: 5.24.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: notes
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

When plasma lost track of an desktop and reset all applets, all notes are gone.
It would be nice if we could list all existing notes (xml files are still
there) and let the user re-add them.

STEPS TO REPRODUCE
1. plug a monitor
2. create a note on that monitor
3. unplug the monitor

OBSERVED RESULT
The note is gone forever until you get that exactly same monitor back.

EXPECTED RESULT
It should be possible to recover lost notes. Maybe a simple note manager inside
its settings or a simple pop-up that asks if the user wishes to reuse an old
note or create a new one (with possibly a way to delete old notes).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.24.5 on OpenSUSE Tumbleweed

ADDITIONAL INFORMATION
It would be nice to merge notes solutions in KDE into a single consistent app.
We have knotes (standalone or inside kontact, but standalone does not start if
kontact is open) and plasma-addon notes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 445175] New: Maximized screen does not use the full screen, kscreen kept the right screen 1px over the left one

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=445175

Bug ID: 445175
   Summary: Maximized screen does not use the full screen, kscreen
kept the right screen 1px over the left one
   Product: KScreen
   Version: 5.23.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Created attachment 143347
  --> https://bugs.kde.org/attachment.cgi?id=143347&action=edit
screenshot

SUMMARY

I have two monitor, one is rotated and scaled down (95%). When I maximize an
app on that screen, it is using the bottom limit from the right monitor. I'll
attach a screenshot. I'm using wayland.

Zooming in the border, I could see that the right painel is about 1px over the
left screen.
The panel was expanded using the painel config ("maximize the painel")

My kscreen conf:

[
{
"enabled": true,
"id": "47da3181b6cbbae6d1472241e6f8",
"metadata": {
"fullname": "xrandr-Hewlett Packard-HP L190hb-BRG11407Q8",
"name": "Hewlett Packard HP L190hb/BRG11407Q8"
},
"mode": {
"refresh": 59.887001037597656,
"size": {
"height": 900,
"width": 1440
}
},
"overscan": 50,
"pos": {
"x": 0,
"y": 0
},
"primary": false,
"rgbrange": 0,
"rotation": 2,
"scale": 0.9492,
"vrrpolicy": 0
},
{
"enabled": true,
"id": "9c25045418948794054c3d2d64ad8519",
"metadata": {
"fullname": "xrandr-2470W-E8562IA000190",
"name": "AOC 2470W/E8562IA00019"
},
"mode": {
"refresh": 60,
"size": {
"height": 1080,
"width": 1920
}
},
"overscan": 0,
"pos": {
"x": 947,
"y": 218
},
"primary": true,
"rgbrange": 0,
"rotation": 1,
"scale": 1,
"vrrpolicy": 0
}
]

It might be a rounding error (because of the scale)

Linux/KDE Plasma: Linux OpenSUSE Tumbleweed 20211106.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 445175] Maximized screen does not use the full screen, kscreen kept the right screen 1px over the left one

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=445175

--- Comment #1 from Luiz Angelo De Luca  ---
Created attachment 143348
  --> https://bugs.kde.org/attachment.cgi?id=143348&action=edit
kscreen-console bug

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 443412] New: Spectacle crashes if I add a text annotation

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=443412

Bug ID: 443412
   Summary: Spectacle crashes if I add a text annotation
   Product: Spectacle
   Version: 21.08.1
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: luizl...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

Application: spectacle (21.08.1)

Qt Version: 5.15.2
Frameworks Version: 5.86.0
Operating System: Linux 5.14.6-1-default x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.5
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

I created a snapshot and tried to add a text to it. The crash happens as soon
as I type the first char.
Other annotations seems to be working as expected.

The crash can be reproduced every time.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x7fc8c3a01e09 in XCloseDisplay (dpy=0x0) at
/usr/src/debug/libX11-1.7.2-1.2.x86_64/src/ClDisplay.c:51
#5  0x7fc8c63e10fc in
kImageAnnotator::CapsLockStatusChecker::isCapsLockEnabled () at
/usr/src/debug/kImageAnnotator-0.5.2-1.1.x86_64/src/annotations/items/text/CapsLockStatusChecker.cpp:47
#6  kImageAnnotator::KeyInputHelper::getTextWithCorrectCase
(this=0x55936aee8f88, event=0x7ffc9a83af70) at
/usr/src/debug/kImageAnnotator-0.5.2-1.1.x86_64/src/annotations/items/text/KeyInputHelper.cpp:88
#7  kImageAnnotator::KeyInputHelper::handleKeyPress (this=0x55936aee8f88,
event=0x7ffc9a83af70) at
/usr/src/debug/kImageAnnotator-0.5.2-1.1.x86_64/src/annotations/items/text/KeyInputHelper.cpp:81
#8  0x7fc8c63e13d1 in non-virtual thunk to
kImageAnnotator::AnnotationText::keyPressEvent(QKeyEvent*) () at
/usr/src/debug/kImageAnnotator-0.5.2-1.1.x86_64/build/kImageAnnotator_autogen/AJBCAZNY4V/moc_AnnotationTextHandler.cpp:143
#9  0x7fc8c564fee1 in QGraphicsItem::sceneEvent (this=0x55936aee8ed0,
event=0x7ffc9a83af70) at graphicsview/qgraphicsitem.cpp:6960
#10 0x7fc8c5672e96 in QGraphicsScene::keyPressEvent (this=,
keyEvent=0x7ffc9a83af70) at graphicsview/qgraphicsscene.cpp:4000
#11 0x7fc8c56851d3 in QGraphicsScene::event (this=0x55936af648b0,
event=0x7ffc9a83af70) at graphicsview/qgraphicsscene.cpp:3410
#12 0x7fc8c533ea7f in QApplicationPrivate::notify_helper (this=, receiver=0x55936af648b0, e=0x7ffc9a83af70) at
kernel/qapplication.cpp:3632
#13 0x7fc8c478d9ca in QCoreApplication::notifyInternal2
(receiver=0x55936af648b0, event=0x7ffc9a83af70) at
kernel/qcoreapplication.cpp:1064
#14 0x7fc8c56a46c8 in QGraphicsView::keyPressEvent (this=0x55936aeaa990,
event=0x7ffc9a83af70) at graphicsview/qgraphicsview.cpp:3206
#15 0x7fc8c53815f8 in QWidget::event (this=this@entry=0x55936aeaa990,
event=event@entry=0x7ffc9a83af70) at kernel/qwidget.cpp:8679
#16 0x7fc8c542cf1e in QFrame::event (this=0x55936aeaa990, e=0x7ffc9a83af70)
at widgets/qframe.cpp:550
#17 0x7fc8c533ea7f in QApplicationPrivate::notify_helper
(this=this@entry=0x55936a866a90, receiver=receiver@entry=0x55936aeaa990,
e=e@entry=0x7ffc9a83af70) at kernel/qapplication.cpp:3632
#18 0x7fc8c53466be in QApplication::notify (this=,
receiver=0x55936aeaa990, e=0x7ffc9a83af70) at kernel/qapplication.cpp:2994
#19 0x7fc8c478d9ca in QCoreApplication::notifyInternal2
(receiver=0x55936aeaa990, event=0x7ffc9a83af70) at
kernel/qcoreapplication.cpp:1064
#20 0x7fc8c539ccaf in QWidgetWindow::event (this=0x55936add3e30,
event=0x7ffc9a83af70) at kernel/qwidgetwindow.cpp:293
#21 0x7fc8c533ea7f in QApplicationPrivate::notify_helper (this=, receiver=0x55936add3e30, e=0x7ffc9a83af70) at
kernel/qapplication.cpp:3632
#22 0x7fc8c478d9ca in QCoreApplication::notifyInternal2
(receiver=0x55936add3e30, event=0x7ffc9a83af70) at
kernel/qcoreapplication.cpp:1064
#23 0x7fc8c4be67a2 in QGuiApplicationPrivate::processKeyEvent
(e=0x55936af8fc60) at kernel/qguiapplication.cpp:2414
#24 0x7fc8c4bc079c in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at kernel/qwindowsysteminterface.cpp:1169
#25 0x7fc8c1d33a00 in userEventSourceDispatch (source=) at
qeventdispatcher_glib.cpp:74
#26 0x7fc8c236ad5f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#27 0x7fc8c236b0e8 in ?? () from /lib64/libglib-2.0.so.0
#28 0x7fc8c236b19f in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#29 0x7fc8c47e4ea4 in QEventDispatcherGlib::processEvents
(this=0x55936a904560, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#30 0x7fc8c478c3cb in QEventLoop::exec (this=this@entry=0x7ffc9a83b200,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#31 0x7fc8c47946b0 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#32 0x7fc8

[plasmashell] [Bug 441237] New: pinned trayicon pannel is over popup menu

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=441237

Bug ID: 441237
   Summary: pinned trayicon pannel is over popup menu
   Product: plasmashell
   Version: 5.22.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: 1.0

Created attachment 140872
  --> https://bugs.kde.org/attachment.cgi?id=140872&action=edit
See the bottom right popup menu under the panel

SUMMARY

After I pinned a popup panel, right click menu is unusable as the panel is over
it. I'm using wayland and didn't test x11.


STEPS TO REPRODUCE
1. Open a popup panel (bluetooth, knetworkmanager) and pin it
2. Right click on other tray icons

OBSERVED RESULT

Most of cases, it shows the popup menu under the popup panel. For java app, it
is shown over (Xwayland)

EXPECTED RESULT

Popup menu should be over in z-order.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=422426

Luiz Angelo De Luca  changed:

   What|Removed |Added

 CC||luizl...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=424754

Luiz Angelo De Luca  changed:

   What|Removed |Added

 CC||luizl...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 432260] Spectacle fails to create rectangular and active window screenshots on Wayland with multiple screens

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=432260

--- Comment #30 from Luiz Angelo De Luca  ---
(In reply to Andrés B.S. from comment #26)
> Not sure what the connection between this and the issue is, but I found out
> that the bug can be worked-around by launching spectacle as:
> QT_QPA_PLATFORM=wayland spectacle
> 
> On Wayland, it seems to prefer xcb. Rectangular selection was working on the
> XOrg session.
> 
> What I found out too, is that Spectacle itself would be part of the
> screenshot when doing rectangular selection, it would be sometimes caught in
> the middle of the animation (IIRC the effect is called "Scale").
> 
> Also, just a reminder that we currently have two Wayland sessions for
> openSUSE:
> "Full Wayland" forces QT_QPA_PLATFORM=GDK_BACKEND=wayland, while the
> "Wayland" session doesn't touch QT_QPA_PLATFORM. This issue does not happen
> on the Full Wayland for the reason mentioned above.

If someone wants to use the workaround but keep it working in X11 as well, I
suggest:

  QT_QPA_PLATFORM="wayland;xcb" spectacle

Or as an argument:

 spectacle -platform 'wayland;xcb'

The argument should be suitable for .desktop files. However, changing
org.kde.spectacle.desktop gets kwin angry:

 spectacle[16738]: Error calling KWin DBus interface:
"org.kde.kwin.Screenshot.Error.NoAuthorized" "The process is not authorized to
take a screenshot"

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420522] KDE apps started on session restore cannot type accented chars like 'á'

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=420522

Luiz Angelo De Luca  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #7 from Luiz Angelo De Luca  ---
Just removing wait for info

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-disks] [Bug 429331] New: smart properties and test results should be visible and notify the user

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=429331

Bug ID: 429331
   Summary: smart properties and test results should be visible
and notify the user
   Product: plasma-disks
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: luizl...@gmail.com
CC: sit...@kde.org
  Target Milestone: ---

SUMMARY

I have a failing disk and give plasma-disks a try. However, according to
plasma-disks, my device was as good as a new HDD. The "SMART overall-health
self-assessment test result" should not be blindly trusted.

I'll paste my smartctl output showing many warning problems like:

1) failed tests. They might not be a final sentence but the user should be
notified
2) repeated failed tests on the same sector: This indicates a even worse
scenario than 1)
3) Reported_Uncorrect increasing
4) Multiple repeating UNC

# smartctl -a /dev/sdb
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.1-2-default] (SUSE RPM)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-1ER166
Serial Number:Z501MAQ5
LU WWN Device Id: 5 000c50 07bd700c6
Firmware Version: CC26
User Capacity:3.000.592.982.016 bytes [3,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate:7200 rpm
Form Factor:  3.5 inches
Device is:In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Wed Nov 18 23:21:10 2020 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status:  (   0) The previous self-test routine
completed
without error or no self-test has ever 
been run.
Total time to complete Offline 
data collection:(   89) seconds.
Offline data collection
capabilities:(0x73) SMART execute Offline immediate.
Auto Offline data collection on/off
support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:(0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:(0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine 
recommended polling time:(   1) minutes.
Extended self-test routine
recommended polling time:( 321) minutes.
Conveyance self-test routine
recommended polling time:(   2) minutes.
SCT capabilities:  (0x1085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED 
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000f   119   099   006Pre-fail  Always  
-   220595456
  3 Spin_Up_Time0x0003   095   094   000Pre-fail  Always  
-   0
  4 Start_Stop_Count0x0032   100   100   020Old_age   Always  
-   471
  5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail  Always  
-   8
  7 Seek_Error_Rate 0x000f   070   047   030Pre-fail  Always  
-   387418648400
  9 Power_On_Hours  0x0032   069   069   000Old_age   Always  
-   27196
 10 Spin_Retry_Count0x0013   100   100   097Pre-fail  Always  
-   0
 12 Power_Cycle_Count   0x0032   100   100   020Old_age   Always  
-   402
183 Runtime_Bad_Block   0x0032   099   099   000Old_age   Always  
-   1
184 End-to-End_Error0x0032   100   100   099Old_age   Always  
-   0
187 Reported_Uncorrect  0x0032   011   011   000Old_age   Always  
-   89
188 Command_Timeout   

[plasma-disks] [Bug 429331] smart properties and test results should be visible and notify the user

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=429331

--- Comment #2 from Luiz Angelo De Luca  ---
Created attachment 133453
  --> https://bugs.kde.org/attachment.cgi?id=133453&action=edit
smart.json

I wouldn't say it's a firmware problem as some of those errors might be
transient. However, the same way smartd reported to logs as errors (in red),
kde should notify the user:

Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel
changed from 58 to 59
Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed
from 42 to 41
Device: /dev/sdc [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate
changed from 117 to 120
Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed
from 41 to 40
Device: /dev/sdb [SAT], 1640 Currently unreadable (pending) sectors
Device: /dev/sdb [SAT], 1640 Offline uncorrectable sectors

These last two are in red.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-disks] [Bug 429331] smart properties and test results should be visible and notify the user

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=429331

--- Comment #4 from Luiz Angelo De Luca  ---
(In reply to Harald Sitter from comment #3)
> KDE is a community. I'm sure we'll not report anything ;)
> Plasma will, but unfortunately the userbase of Plasma is mch too varied
> to report that kind of data.

I'm still from the times where kde was a thing, not a community... Old habits
die hard. 


> The problem with reporting the lines you mention is that 99% of people won't
> know what they mean or what to do about them which is why we break the
> entire affair down to a binary state of either everything is grand or
> everything is not. Which has the disadvantage that potentially failing disks
> slip under the radar if the overall status says ok even when it isn't.

HDD dying process is a little more subtle than "run, I'm gonna explode!". A
read error with a msg like "it might be a one time error like a power outage.
However, if this error keeps reoccurring, it indicates that part of your data
in your HDD is not readable anymore". This is something a user might
understand. It could show previous tests or error messages to let the user
decide if a new HDD is needed.

> At the same time replicating what smartd already does and tracking report
> trends to discern problems seems a bit useless given, well, smartd already
> does just that ^^

It generates the error log. However, that error will never reach a gui-only
user. That's what I'm suggesting: exposing "Hey, a read error happened!" to gui
users. If smarttools guys does not have a good heuristic, it is not plasma-disk
that will implement one. But plasma-disk could expose and "translate" some
errors and let the user decide.

> We could maybe have a tiny hint icon somewhere in kinfocenter that there
> were problems in the report data so the user can look at it and/or choose to
> err on the side of caution and replace the disk.

If all last self-tests finished with an error, it should be something to report
with a big red flashing icon. Not something subtle inside kinfocenter.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-disks] [Bug 429331] smart properties and test results should be visible and notify the user

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=429331

--- Comment #7 from Luiz Angelo De Luca  ---
(In reply to Harald Sitter from comment #6)
> Whoops. Hit save too soon. You could have smartd send notifications to
> journal and then pick them out via trivial scripting.

If the user can script that, plasma-disk is just an additional feature. I was
thinking about those users that does not know how to do that (and does not even
know S.M.A.R.T. exists. If plasma has a tool that reads smart data, it would
not make sense to have a new tool to do just the same, but better. 

A repeated error at the same position would tell the user that if there is info
info stored there, it is gone as CRC is not matching. Is it a HW failure? Maybe
not. It could be generated by a power outage, and external interference
scrambling bits, firmware bug... who knows? As an advanced user, I would look
for badblocks, fsck the filesystem or ever recreate the FS. It would be nice if
the read error message could identify the affected filepath, offer to run check
tools (fsck, badblocks, ), suggest a backup... plasma-disks is a nice
feature for a cli user but it will be the only monitor tool for non-cli plasma
users.

In my case, I zero-filled the disk and now it is working as usual. However, I
don't trust that HDD anymore to store anything important. My filesystem got
irrecoverably corrupted and I did a backup and recreated the FS.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 473015] New: Google chat call does not stop ringing when kde plasma integration is enabled

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=473015

Bug ID: 473015
   Summary: Google chat call does not stop ringing when kde plasma
integration is enabled
Classification: Plasma
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Chrome
  Assignee: k...@privat.broulik.de
  Reporter: luizl...@gmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Enable plasma integration in a google-chrome
2. open chat.google.com
3. call any contact

OBSERVED RESULT
4. No matter what happens (hang up, answer, cancel), the ringing sound keeps
going forever

EXPECTED RESULT
4. The ringing should stop

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed 20230801
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Google chrome 115.0.5790.110

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 477226] New: Crash no plasma ao clicar abri menu de aplicações

[Angelo Queiroz de Souza]

https://bugs.kde.org/show_bug.cgi?id=477226

Bug ID: 477226
   Summary: Crash no plasma ao clicar abri menu de aplicações
Classification: Plasma
   Product: kwin
   Version: 5.27.9
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: angel...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.27.9)

Qt Version: 5.15.11
Frameworks Version: 5.112.0
Operating System: Linux 6.6.1-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.9 [CoredumpBackend]

-- Information about the crash:
Ao clicar no menu de aplicações e tentar selecionar um aplicativo para abrir, o
plasma fechou instantaneamente e ficou somente o cursor do mouse visível e
funcionando com uma tela preta de fundo, depois ele retornou com a tela de
mensagem para enviar o relatório de erro, após 1 minuto de falha. Durante esse
momento estavam ocorrendo as atualizações do sistema.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Bus error

   PID: 1864 (kwin_x11)
   UID: 1000 (promidia)
   GID: 1000 (promidia)
Signal: 7 (BUS)
 Timestamp: Sun 2023-11-19 08:23:15 -03 (1min 15s ago)
  Command Line: /usr/bin/kwin_x11 --replace
Executable: /usr/bin/kwin_x11
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service
  Unit: user@1000.service
 User Unit: plasma-kwin_x11.service
 Slice: user-1000.slice
 Owner UID: 1000 (promidia)
   Boot ID: 4c2af0390bec4e74b723c1e39970ff61
Machine ID: 91fef3f8139d498d8aefa2e38577085c
  Hostname: localhost.localdomain
   Storage:
/var/lib/systemd/coredump/core.kwin_x11.1000.4c2af0390bec4e74b723c1e39970ff61.1864.170039299500.zst
(present)
  Size on Disk: 6.2M
   Message: Process 1864 (kwin_x11) of user 1000 dumped core.

Stack trace of thread 1864:
#0  0x7f6f46e972a8 pthread_sigmask@GLIBC_2.2.5 (libc.so.6 +
0x972a8)
#1  0x7f6f46e3f3ad sigprocmask (libc.so.6 + 0x3f3ad)
#2  0x7f6f4a2248db _ZN6KCrash15setCrashHandlerEPFviE
(libKF5Crash.so.5 + 0x58db)
#3  0x7f6f4a226d93 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x7d93)
#4  0x7f6f46e3f190 __restore_rt (libc.so.6 + 0x3f190)
#5  0x7f6f46eac5f8 __memmove_sse2_unaligned_erms (libc.so.6
+ 0xac5f8)
#6  0x7f6f4805702b
_ZN16KSharedDataCache6insertERK7QStringRK10QByteArray (libKF5CoreAddons.so.5 +
0x3702b)
#7  0x7f6f4a2d3309 n/a (libKF5Plasma.so.5 + 0x77309)
#8  0x7f6f48525442 n/a (libQt5Core.so.5 + 0x325442)
#9  0x7f6f4852921a _ZN6QTimer7timeoutENS_14QPrivateSignalE
(libQt5Core.so.5 + 0x32921a)
#10 0x7f6f48518e5b _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5 + 0x318e5b)
#11 0x7f6f477a519e
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x1a519e)
#12 0x7f6f484ed198
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2ed198)
#13 0x7f6f485454c9 _ZN14QTimerInfoList14activateTimersEv
(libQt5Core.so.5 + 0x3454c9)
#14 0x7f6f48545dac n/a (libQt5Core.so.5 + 0x345dac)
#15 0x7f6f45b13f30 n/a (libglib-2.0.so.0 + 0x5bf30)
#16 0x7f6f45b15b58 n/a (libglib-2.0.so.0 + 0x5db58)
#17 0x7f6f45b1620c g_main_context_iteration
(libglib-2.0.so.0 + 0x5e20c)
#18 0x7f6f485460d6
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x3460d6)
#19 0x7f6f484ebc2b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2ebc2b)
#20 0x7f6f484f40c0 _ZN16QCoreApplication4execEv
(libQt5Core.so.5 + 0x2f40c0)
#21 0x5642683244dd n/a (kwin_x11 + 0x464dd)
#22 0x7f6f46e281b0 __libc_start_call_main (libc.so.6 +
0x281b0)
#23 0x7f6f46e28279 __libc_start_main@@GLIBC_2.34 (libc.so.6
+ 0x28279)
#24 0x5642683259a5 n/a (kwin_x11 + 0x479a5)

Stack trace of thread 1882:
#0  0x7f6f46f09d7f __poll (libc.so.6 + 0x109d7f)
#1  0x7f6f45b15aff n/a (libglib-2.0.so.0 + 0x5daff)
#2  0x7f6f45b1620c g_main_context_iteration
(libglib-2.0.so.0 + 0x5e20c)
#3  0x7f6f485460ee
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x3460ee)
#4  0x7f6f484ebc2b
_ZN10QEventLoop4execE6QFlagsINS_17Pro

[konsole] [Bug 463126] Many bells with sound notification slows terminal

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=463126

--- Comment #3 from Luiz Angelo De Luca  ---
(In reply to Kurt Hindenburg from comment #2)
> Currently Konsole sends a notification every 500ms.   Perhaps that needs
> increased at the minimum.

That does not seem to be what I experience. I almost hear a constant noise
(about 700 bpm or less than 0.01s), even getting faster (about 1500 bpm) when I
open the Audio panel in traybar. The main issue is not the noise but the fact
that it hangs the main thread. It should not freeze the GUI because there are a
large queue of notifications. It should simply discard them (maybe with a
follow-up notification saying it missed some notifications like kernel does).

I still don't know why it bells (a lot) when I paste a large file. It is just
text, with more data. Maybe the large paste warning dialog is related?

As a workaround, you can speed up things enabling the "Do not disturb" mode
from notification panel in the tray icon (you may need to do it twice). Muting
the app is not enough.

-- 
You are receiving this mail because:
You are watching all bug changes.

[libkgapi] [Bug 474281] New: kgapi gets token expired and retries indefinitely

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=474281

Bug ID: 474281
   Summary: kgapi gets token expired and retries indefinitely
Classification: Frameworks and Libraries
   Product: libkgapi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: dvra...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

SUMMARY

I noticed that my HDD was emitting a sound in at a specific rate (4/s).
Checking logs, I noticed:

...
set 07 23:15:44 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access
token has expired or is invalid.
set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access
token has expired or is invalid.
set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access
token has expired or is invalid.
set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access
token has expired or is invalid.
set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access
token has expired or is invalid.
set 07 23:15:46 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access
token has expired or is invalid.
...

Besides being annoying, this type of HDD exercise might not help extend its
lifetime.

After I get Gmail authenticated, it is too easy to get this error. I don't
believe google actually expired the token as it might happen even in less than
a day. I have already reconfigured the google account dozens of times.


STEPS TO REPRODUCE
1. Configure google account
2. Use for a couple of days
3. Check logs

OBSERVED RESULT

4. Endless sequence of the same error message

EXPECTED RESULT

4. If it is really an expired token, it should desist and ask the user for a
new token. However, it might be a different type of error. I don't see google
token expire as fast as this.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I'm only using packages from official ubuntu repo.

-- 
You are receiving this mail because:
You are watching all bug changes.

[libkgapi] [Bug 474281] kgapi gets token expired and retries indefinitely

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=474281

--- Comment #1 from Luiz Angelo De Luca  ---
The PID 13483 is:

/lib/x86_64-linux-gnu/libexec/kf5/kioslave5
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so gdrive 
local:/run/user/1000/dolphinKfTdSY.4.kioworker.socket

It didn't stop even after I removed the account. If it helps, after I removed
the account, this is the strace I got from that process (it repeates these
lines):

write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\2\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd9f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\2\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
fcntl(36, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=124, l_len=1}) =
0
fcntl(36, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=124, l_len=1}) =
0
newfstatat(AT_FDCWD, "/home/luizluca/.local/share/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/plasma/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/plasma/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/gnome/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/gnome/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/local/share/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/local/share/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/accounts/services/.service", 0x7fff8e8fd360,
0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/var/lib/snapd/desktop/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/var/lib/snapd/desktop/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, -1) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\1\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fb998d60910, FUTEX_WAKE_PRIVATE, 1) = 1
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fff8e8fd000, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\3\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x558d84659f30, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\3\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fff8e8fcfe0, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fff8e8fcfe0, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, eve

[konsole] [Bug 463126] New: Many bells with sound notification slows terminal

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=463126

Bug ID: 463126
   Summary: Many bells with sound notification slows terminal
Classification: Applications
   Product: konsole
   Version: 22.12.0
  Platform: OpenSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

If you paste a large file into the terminal or cat a binary file, it generates
lots of bells. If that bells is configured to play a sound, it will slow
dramatically the process.

STEPS TO REPRODUCE
1. configure bell to play a sound
2. cat a large binary file

OBSERVED RESULT
3. it will play a long noise, merging many consecutive notifications. Terminal
takes much longer to display the content 

EXPECTED RESULT
3. Notification should be handled async or it should be limited to a small
number of occurrences per second. It should not affect terminal printing.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: opensuse tumbleweed
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7 (compilado com 5.15.7)

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 459804] Mouse cursor is hidden windows when crossing the screen over a window on both screens

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=459804

Luiz Angelo De Luca  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #8 from Luiz Angelo De Luca  ---
Cleared needsinfo

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=411729

Luiz Angelo De Luca  changed:

   What|Removed |Added

 CC||luizl...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 431625] New: Windows frozen and forgot with wayland

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=431625

Bug ID: 431625
   Summary: Windows frozen and forgot with wayland
   Product: kwin
   Version: 5.20.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

While switching windows, including minimizing/maximizing using decoration bar
and plasma panel, sometimes a window freezes. The app seems to be running but
without accepting inputs nor updating its contents. It returns to normal if I
minimize it restore it back.

It happened with multiple apps (telegram, chrome, firefox, konsole)

It looks like kwin is forgetting that a window exists. I can see, sometimes,
apps in alt+tab that does not exists in plasma panel

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 431625] Windows frozen and forgot with wayland

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=431625

--- Comment #1 from Luiz Angelo De Luca  ---
Created attachment 134876
  --> https://bugs.kde.org/attachment.cgi?id=134876&action=edit
Panel with 2 konsoles while alt+tab was three. The one gone is blank

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420522] KDE apps started on session restore cannot type accented chars like 'á'

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=420522

--- Comment #3 from Luiz Angelo De Luca  ---
Created attachment 130100
  --> https://bugs.kde.org/attachment.cgi?id=130100&action=edit
env from konsole where accents do not work

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420522] KDE apps started on session restore cannot type accented chars like 'á'

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=420522

--- Comment #5 from Luiz Angelo De Luca  ---
Created attachment 130101
  --> https://bugs.kde.org/attachment.cgi?id=130101&action=edit
env from konsole where accents do work

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420522] KDE apps started on session restore cannot type accented chars like 'á'

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=420522

--- Comment #4 from Luiz Angelo De Luca  ---
(In reply to David Edmundson from comment #1)
> That's surprising.
> 
> 
> Can you give full steps to reproduce

I don't know how to reproduce it. I'm upgrading my ubuntu installation for some
years and I installed kubuntu packages (while still using ubuntu gdm). 

> Also could you include output of 
> 
> cat /proc/`pidof konsole`/environ | tr '\0' '\n'
> 
> 
> for a working and broken konsole.


~ $ diff -u konsole.err konsole.ok | grep -v '^ '
--- konsole.err 2020-07-13 22:16:30.544985468 -0300
+++ konsole.ok  2020-07-13 22:16:41.496413493 -0300
@@ -3,16 +3,15 @@
+DESKTOP_STARTUP_ID=zipper;1594689313;826606;50572_TIME32863387
-GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/luizluca/.gtkrc-2.0:/home/luizluca/.config/gtkrc-2.0
-GTK_RC_FILES=/etc/gtk/gtkrc:/home/luizluca/.gtkrc:/home/luizluca/.config/gtkrc
@@ -55,7 +54,7 @@
-XAUTHORITY=/tmp/xauth-1000-_1
+XAUTHORITY=/run/user/1000/gdm/Xauthority

I'll attach the files.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 424342] New: Konsole crash while changing tab (shift + left arrow)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=424342

Bug ID: 424342
   Summary: Konsole crash while changing tab (shift + left arrow)
   Product: konsole
   Version: 19.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Application: konsole (19.12.3)

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.4.0-40-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

I just just browsing between tabs using shift + left arrow.
I was not doing anything special.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f68370f6080 (LWP 3066))]

Thread 4 (Thread 0x7f682384c700 (LWP 3667)):
#0  __GI___libc_read (nbytes=10, buf=0x7f682384bbde, fd=96) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=96, buf=0x7f682384bbde, nbytes=10) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f683769c955 in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#3  0x7f683955b416 in pa_mainloop_prepare () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f683955beb4 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f683955bf70 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f683956a11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f68376cb57c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#8  0x7f6839fb1609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f683ca3e103 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f6834b49700 (LWP 3068)):
#0  __GI___libc_read (nbytes=16, buf=0x7f6834b48b60, fd=7) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=7, buf=buf@entry=0x7f6834b48b60,
nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f683979589f in read (__nbytes=16, __buf=0x7f6834b48b60,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#3  g_wakeup_acknowledge (wakeup=0x7f6830001bc0) at ../../../glib/gwakeup.c:210
#4  0x7f683974ccfe in g_main_context_check
(context=context@entry=0x7f6828000c30, max_priority=2147483647,
fds=fds@entry=0x7f6828012080, n_fds=n_fds@entry=1) at
../../../glib/gmain.c:3825
#5  0x7f683974d152 in g_main_context_iterate
(context=context@entry=0x7f6828000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044
#6  0x7f683974d2e3 in g_main_context_iteration (context=0x7f6828000c30,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#7  0x7f683b235583 in QEventDispatcherGlib::processEvents
(this=0x7f6828000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#8  0x7f683b1dc4db in QEventLoop::exec (this=this@entry=0x7f6834b48d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#9  0x7f683b014785 in QThread::exec (this=this@entry=0x7f683a7b3d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#10 0x7f683a730efa in QDBusConnectionManager::run (this=0x7f683a7b3d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#11 0x7f683b0159d2 in QThreadPrivate::start (arg=0x7f683a7b3d80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
#12 0x7f6839fb1609 in start_thread (arg=) at
pthread_create.c:477
#13 0x7f683ca3e103 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f6836240700 (LWP 3067)):
#0  0x7f683ca3196f in __GI___poll (fds=fds@entry=0x7f683623fca8,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f6839fe5c1a in poll (__timeout=-1, __nfds=1, __fds=0x7f683623fca8)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x55d5ab7c3ed0, cond=cond@entry=0x55d5ab7c3f10,
vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:480
#3  0x7f6839fe790a in xcb_wait_for_event (c=c@entry=0x55d5ab7c3ed0) at
../../src/xcb_in.c:697
#4  0x7f6836a33298 in QXcbEventQueue::run (this=0x55d5ab7b3200) at
qxcbeventqueue.cpp:228
#5  0x7f683b0159d2 in QThreadPrivate::start (arg=0x55d5ab7b3200) at
thread/qthread_unix.cpp:361
#6  0x7f6839fb1609 in start_thread (arg=) at
pthread_create.c:477
#7  0x7f683ca3e103 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f68370f6080 (LWP 3066

[konsole] [Bug 424342] Konsole crash while changing tab (shift + left arrow)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=424342

--- Comment #2 from Luiz Angelo De Luca  ---
This is what current (k)ubuntu 20.04 offers me. But I'll install
ppa:kubuntu-ppa/backports.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 424342] Konsole crash while changing tab (shift + left arrow)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=424342

--- Comment #3 from Luiz Angelo De Luca  ---
konsole 20.04 is not available even for ppa:kubuntu-ci/unstable, nor in a
snapcraft form.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 420522] KDE apps started on session restore cannot type accented chars like 'á'

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=420522

--- Comment #9 from Luiz Angelo De Luca  ---
(In reply to Nate Graham from comment #8)
> Not quite the same as Bug 411729, but seems related.

I'm affected by both on different systems. That one in OpenSUSE Tumbleweed
(wayland only) and this one only in Ubuntu.

It's difficult to isolate this problem as it only happens with software
launched by session restore. If I launch a new one, even from inside a konsole
that is manifesting the problem, the new process work as expected.

In the case of Ubuntu, QT_IM_MODULE is defined as ibus, even for those
problematic processes. I gave another try to debug it:

I noticed that there is no ibus-daemon running. The moment I launch it, konsole
starts to type accent chars correctly. If I kill ibus-daemon afterwards, it
stops to type anything. It looks like it started in a "basic input fallback
mode" when it failed to use ibus. After KDE is up, KDE might offer another
option for input, which new konsole processes take and it works as expected. It
is just a guess.

Now, as I know it is related to ibus, I grepped my .config and found:

.config/systemsettingsrc:
...
[Open-with settings]
CompletionMode=5
History=ibus-daemon --xim --replace --panel=/usr/lib/ibus/ibus-ui-gtk3
...

.config/autostart/ibus-daemon.desktop:
...
Exec=ibus-daemon --xim --replace --panel=/usr/lib/ibus/ibus-ui-gtk3
...

If I manually run that line after ibus-daemon was manually started, konsole
returns to the broken state. The "--panel=/usr/lib/ibus/ibus-ui-gtk3" is the
one generating the issue.

That autostart file is old, from 2017, probably from the time I used unity or
gnome3. I disabled that autostart and now it works as expected.

What is broken? QT? Ibus? Someone that added that autostart and left it there?

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 445175] With 95% scale, maximized screen does not use the full screen, kscreen kept the right screen 1px over the left one

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=445175

Luiz Angelo De Luca  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REOPENED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #3 from Luiz Angelo De Luca  ---
It works as expected with 5.26

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 445175] With 95% scale, maximized screen does not use the full screen, kscreen kept the right screen 1px over the left one

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=445175

--- Comment #4 from Luiz Angelo De Luca  ---
It works as expected with 5.26

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 445175] With 95% scale, maximized screen does not use the full screen, kscreen kept the right screen 1px over the left one

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=445175

Luiz Angelo De Luca  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 462182] New: HTTP access retries immediately and indefinitely when received proxy authentication required (407)

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=462182

Bug ID: 462182
   Summary: HTTP access retries immediately and indefinitely when
received proxy authentication required (407)
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: luizl...@gmail.com
  Target Milestone: ---

Some KDE apps/services like geolocation (location.services.mozilla.org) and
discovery does not deal with HTTP Code 407 correctly. They simply retries on
and on the same connection immediately after it gets 407. The frequency is so
high that it generates dozens of gigabytes of logs. It should, at least, wait a
couple of seconds. 

In my site, the proxy authentication uses kerberos, but NTLM and basic are
still valid options. The issue is that the moment the failed sw runs, it might
not be a valid TGT. Normally you can stop the "DoS attack" signing out/in KDE.

It happens with different KDE apps and maybe it is a QT bug (I also saw that
behavior with OpenSUSE welcome app).

STEPS TO REPRODUCE
1. Configure a proxy that requires authentication
2. Configure KDE to use it (without offering the credentials)
3. Use some affected apps.

OBSERVED RESULT
 4. a wave of failed authentications

EXPECTED RESULT
4. some failed authentications but with a much lower frequency

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed 20221120
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 433547] New: Spectacle fails to capture rectangle on wayland

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=433547

Bug ID: 433547
   Summary: Spectacle fails to capture rectangle on wayland
   Product: Spectacle
   Version: 20.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: luizl...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

Just open Spectacle and do a new screenshot using rectangular region. (window
and full screen does work). Spectacle failed and asked me to open this bug
report

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

It was supposed to be fixed (Bug 377157)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 433547] Spectacle fails to capture rectangle on wayland

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=433547

--- Comment #1 from Luiz Angelo De Luca  ---
When I run from konsole, I get:

$ spectacle --region
Error calling KWin DBus interface:
"org.kde.kwin.Screenshot.Error.ScreenMissing" "Screen not found"
QPixmap::scaled: Pixmap is a null pixmap

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 432260] Spectacle fails to create rectangular and active window screenshots on Wayland

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=432260

--- Comment #15 from Luiz Angelo De Luca  ---
If it helps, here is my screen info:

$ kscreen-doctor -o
Output: 33 XWAYLAND0 enabled connected  Unknown Modes: 34:1920x1080@60*!
Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 

I get the same error msg when I launch from a terminal.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 432260] Spectacle fails to create rectangular and active window screenshots on Wayland

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=432260

--- Comment #17 from Luiz Angelo De Luca  ---
Is it possible that it happens only with opensuse tumbleweed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=411729

--- Comment #30 from Luiz Angelo De Luca  ---
(In reply to Nate Graham from comment #29)
> So this is 100% an upstream issue? Nothing reasonable that we can do on our
> side?

Most affected software will run in KDE. It should be in KDE interest to do
something, specially when there is the increasing focus on wayland. From the
user perspective, KDE is the one asking to use a broken setup, no matter who
wrote the code.

If there is some form of workaround and KDE is also responsible to setup the
user environment, KDE should do it instead of expecting (thousands of) users or
(dozens of) distributions to do it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 228361] Cannot add icons with space character in path

[Luiz Angelo De Luca]

https://bugs.kde.org/show_bug.cgi?id=228361

Luiz Angelo De Luca  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #12 from Luiz Angelo De Luca  ---
It seems to be working with 5.14

-- 
You are receiving this mail because:
You are watching all bug changes.