[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library

2024-05-27 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=420280

Mateus Honorato  changed:

   What|Removed |Added

 CC||mateush.honor...@gmail.com

--- Comment #105 from Mateus Honorato  ---
I'm still dealing with this bug on Arch Linux, even tho the signon-ui package
version is quite new, 0.17+20231016-2.1. When running systemsettings from the
terminal and trying to login to my account, I get this errors on the terminal:

file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView:
Binding loop detected for property "calculatedImplicitHeight"
file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding:
Binding loop detected for property "value"
"google"
Looking for plugin ""
Starting auth session with "oauth2"
Info:
Id: 3
caption: "google"
owner: ""
userName: ""
qt.dbus.integration: Could not disconnect
"com.google.code.AccountsSSO.SingleSignOn.Identity" to "destroyed(QObject*)" :
Pointers are not supported: QObject*
Error:
 "Access grant not present"

I'm using Wayland and nvidia drivers. I was able to login once in the Xorg
session, but it doesn't always work, and even when I get to login successfully,
the google drive integration in Dolphin randomly stops working when accessing
folders.

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

[kde] [Bug 439916] New: Latte crashes whenever there is a widget reloading

2021-07-15 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=439916

Bug ID: 439916
   Summary: Latte crashes whenever there is a widget reloading
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mateush.honor...@gmail.com
  Target Milestone: ---

Application: latte-dock (0.9.12)

Qt Version: 5.15.3
Frameworks Version: 5.84.0
Operating System: Linux 5.8.0-59-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.3
Distribution: KDE neon User Edition 5.22

-- Information about the crash:
- What I was doing when the application crashed:
I was connecting with a bluetooth device from the system tray added on a Latte
panel, and the entire Latte application crashed.

- Unusual behavior I noticed:
This also happens while interacing with some other widgets sometimes, whenever
something is loading.

- Additional Information:
I have the plasma-systray-latte-tweaks added, but I've already tried to remove
it and the problem persists.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault

[New LWP 4034]
[New LWP 4036]
[New LWP 4037]
[New LWP 4038]
[New LWP 4039]
[New LWP 4040]
[New LWP 4047]
[New LWP 5071]
[New LWP 5072]
[New LWP 5074]
[New LWP 5075]
[New LWP 5076]
[New LWP 5078]
[New LWP 5095]
[New LWP 5118]
[New LWP 5119]
[New LWP 5122]
[New LWP 5167]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x5572938d5bf0) at ../sysdeps/nptl/futex-internal.h:183
[Current thread is 1 (Thread 0x7fb63c5f9980 (LWP 4033))]

Thread 19 (Thread 0x7fb5c976b700 (LWP 5167)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55728e0946d4) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55728e094680,
cond=0x55728e0946a8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55728e0946a8, mutex=0x55728e094680) at
pthread_cond_wait.c:647
#3  0x7fb6409d8f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb64283cb44 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fb64283cfb9 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fb6409d2dbc in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb63f87c609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb640504293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 18 (Thread 0x7fb5ca242700 (LWP 5122)):
#0  __GI___libc_read (nbytes=16, buf=0x7fb5ca241a10, fd=57) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=57, buf=0x7fb5ca241a10, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fb63ebc2b2f in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb63eb79ebe in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb63eb7a312 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb63eb7a4a3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb640c13fcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb640bb825b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb6409d1c22 in QThread::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fb6409d2dbc in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fb63f87c609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7fb640504293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7fb5eccba700 (LWP 5119)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55729b8473f0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55729b8473a0,
cond=0x55729b8473c8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55729b8473c8, mutex=0x55729b8473a0) at
pthread_cond_wait.c:647
#3  0x7fb6409d8f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb64283cb44 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fb64283cfb9 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fb6409d2dbc in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb63f87c609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb640504293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fb5ee702700 (LWP 5118)):
#0  __GI___libc_read (nbytes=16, buf=0x7fb5ee7019f0, fd=53) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=53, buf=0x7fb5ee7019f0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fb63ebc2b2f in  () at /l

[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)

2021-04-08 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=433664

--- Comment #2 from Mateus Honorato  ---
still present today. just found out this might have something to do with my
dual display setup. when the problem happens, if I go to the display settings,
disable and enable one of the displays, things come back to normal

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

[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)

2021-04-08 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=433664

Mateus Honorato  changed:

   What|Removed |Added

Version|5.21.1  |5.21.4

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

[kwin] [Bug 426412] Kwin laggy after pausing and un-pausing compositing

2021-03-02 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=426412

Mateus Honorato  changed:

   What|Removed |Added

 CC||mateush.honor...@gmail.com

--- Comment #2 from Mateus Honorato  ---
This also happens on intel graphics

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

[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)

2021-02-26 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=433664

--- Comment #1 from Mateus Honorato  ---
https://drive.google.com/file/d/1m9SAKBYt1kY5zhtoY9i8JMs2rXKigaGB/view?usp=sharing

video of the issue

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

[kwin] [Bug 433664] New: Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)

2021-02-26 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=433664

Bug ID: 433664
   Summary: Desktop becomes really slow after disabling and
enabling the kwin compositor again (After 5.21 Update)
   Product: kwin
   Version: 5.21.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mateush.honor...@gmail.com
  Target Milestone: ---

Created attachment 136197
  --> https://bugs.kde.org/attachment.cgi?id=136197&action=edit
output of 'qdbus org.kde.KWin /KWin supportInformation'

SUMMARY
After disabling and enabling the compositor, or restarting kwin with kwin_x11
--replace, the desktop becomes very slow, with like 1-2 fps, and becomes pretty
much unusable. The only solution is to logout and login again. This started
happening after the Plasma 5.21 update.

STEPS TO REPRODUCE
1. Restarting kwin or disabling and enabling the compositor in system settings

OBSERVED RESULT
Every window or plasmashell itself is stuttering, slow, just the mouse pointer
is moving fine with normal framerate, the windows become slow and everything
gets really slow.

EXPECTED RESULT
Normal behavior of the desktop.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.21.1
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Graphics platform: X11 (In the wayland session, everything seems fine)
Kernel Version: 5.4.0-66-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-3230M CPU @ 2.60GHz
Memory: 7,7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000

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

[lattedock] [Bug 430956] Latte Dock crashes on startup

2020-12-29 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=430956

--- Comment #1 from Mateus Honorato  ---
Also, I wasn't able to report the bug using kcrash dialog, because the product
is identified there as "latte-dock" but here the name is "lattedock", so it
says the project can't be found or I don't have permission to submit a bug.

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

[lattedock] [Bug 430956] New: Latte Dock crashes on startup

2020-12-29 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=430956

Bug ID: 430956
   Summary: Latte Dock crashes on startup
   Product: lattedock
   Version: 0.9.11
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: mateush.honor...@gmail.com
  Target Milestone: ---

Created attachment 134386
  --> https://bugs.kde.org/attachment.cgi?id=134386&action=edit
kcrash genereted info

Application: latte-dock (0.9.11)

Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.4.0-58-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.20

-- Information about the crash:
- What I was doing when the application crashed: Nothing, I was just starting
the system. Sometimes this is happening when plasma-session is starting. I have
Latte added to startup on Autostart Settings, and no panels added in
plasmashell itself.

- Unusual behavior I noticed: KDE Connect also crashes sometimes on startup.
Krunner and Dolphin is unable to search for files.

- Custom settings of the application: I have only 5 custom widgets added to a
panel with Latte: Window Title, Global Menu, System Tray (with Latte Tweaks),
Event Calendar and Window App Buttons.

The crash can be reproduced sometimes.

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

[lattedock] [Bug 409985] Promo video for Latte v0.9

2019-07-23 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=409985

Mateus Honorato  changed:

   What|Removed |Added

 CC||mateush.honor...@gmail.com
   Assignee|mvourla...@gmail.com|mateush.honor...@gmail.com

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

[plasmashell] [Bug 383098] Plasma crash on audio volume change

2017-08-06 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=383098

Mateus Honorato  changed:

   What|Removed |Added

 CC||mateush.honor...@gmail.com

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

[plasmashell] [Bug 383098] Plasma crash on audio volume change

2017-08-06 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=383098

--- Comment #2 from Mateus Honorato  ---
Created attachment 107115
  --> https://bugs.kde.org/attachment.cgi?id=107115&action=edit
New crash information added by DrKonqi

plasmashell (5.10.4) using Qt 5.9.1

- What I was doing when the application crashed:
just before i changed the audio output from internal speaker to HDMI

-- Backtrace (Reduced):
#6  QVector::count (this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:234
#7  QQmlPropertyCache::property (index=58, this=0x0) at
../../include/QtQml/5.9.1/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:711
#8  QQmlBinding::getPropertyData (this=this@entry=0x5c9a690,
propertyData=propertyData@entry=0x7ffc0eb32bc8,
valueTypeData=valueTypeData@entry=0x7ffc0eb32bd0) at qml/qqmlbinding.cpp:520
#9  0x7f6220cc9ac2 in GenericBinding<10>::write (this=0x5c9a690,
result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:246
#10 0x7f6220cca740 in QQmlNonbindingBinding::doUpdate (this=0x5c9a690,
watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:210

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

[plasmashell] [Bug 382770] New: plasmashell crashed when mouse scrolling to increase volume from panel widget

2017-07-26 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=382770

Bug ID: 382770
   Summary: plasmashell crashed when mouse scrolling to increase
volume from panel widget
   Product: plasmashell
   Version: 5.10.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mateush.honor...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.10.0-27-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed: i was with a bluetooth
headphone connected, a bluetooth mouse connected too. 

- Unusual behavior I noticed: plasmashell crashes frequently on my system.
also, sometimes, it feels very slow, even when I have noting running

- Custom settings of the application: I use a custom icon theme (papirus), and
also some custom widgets, like event calendar

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd7241348c0 (LWP 1862))]

Thread 19 (Thread 0x7f96135f6700 (LWP 21013)):
#0  0x7fd71347b24f in pa_pstream_unref () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#1  0x7fd71347b7a3 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7fd71347c01a in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#3  0x7fd7141f60b7 in pa_mainloop_dispatch () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fd7141f64bc in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fd7141f6560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7fd7142047a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7fd71348c078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#8  0x7fd71df276ba in start_thread (arg=0x7f96135f6700) at
pthread_create.c:333
#9  0x7fd71e98f3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fd63ccb3700 (LWP 21012)):
#0  0x7fd71a360a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fd71a31c4a6 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd71f2ab94b in QEventDispatcherGlib::processEvents
(this=0x7f961c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7fd71f2547ca in QEventLoop::exec (this=this@entry=0x7fd63ccb2ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#4  0x7fd71f07dcd4 in QThread::exec (this=this@entry=0x6aeb4f0) at
thread/qthread.cpp:515
#5  0x7fd72174bfa5 in QQmlThreadPrivate::run (this=0x6aeb4f0) at
qml/ftw/qqmlthread.cpp:147
#6  0x7fd71f082989 in QThreadPrivate::start (arg=0x6aeb4f0) at
thread/qthread_unix.cpp:368
#7  0x7fd71df276ba in start_thread (arg=0x7fd63ccb3700) at
pthread_create.c:333
#8  0x7fd71e98f3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fd63e0b4700 (LWP 21008)):
#0  0x7fd71e98370d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd71a31c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd71a31c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd71f2ab94b in QEventDispatcherGlib::processEvents
(this=0x7f96180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd71f2547ca in QEventLoop::exec (this=this@entry=0x7fd63e0b3ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fd71f07dcd4 in QThread::exec (this=this@entry=0x6a57640) at
thread/qthread.cpp:515
#6  0x7fd72174bfa5 in QQmlThreadPrivate::run (this=0x6a57640) at
qml/ftw/qqmlthread.cpp:147
#7  0x7fd71f082989 in QThreadPrivate::start (arg=0x6a57640) at
thread/qthread_unix.cpp:368
#8  0x7fd71df276ba in start_thread (arg=0x7fd63e0b4700) at
pthread_create.c:333
#9  0x7fd71e98f3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fd6457fa700 (LWP 8452)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fd71f0838eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x4d2a650) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x502d200,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fd660eef07f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fd660ef

[systemsettings] [Bug 376042] Systemsettings crash when pressing the back button

2017-02-06 Thread Mateus Honorato
https://bugs.kde.org/show_bug.cgi?id=376042

Mateus Honorato  changed:

   What|Removed |Added

 CC||mateush.honor...@gmail.com

--- Comment #2 from Mateus Honorato  ---
I'm having the same bug after update to KDE 5.9.0

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