[xdg-desktop-portal-kde] [Bug 473624] New: Crash on saving file existension assiciation from telegram app

2023-08-22 Thread VitalyOrbitSoft
https://bugs.kde.org/show_bug.cgi?id=473624

Bug ID: 473624
   Summary: Crash on saving file existension assiciation from
telegram app
Classification: Plasma
   Product: xdg-desktop-portal-kde
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: vitaly.khatlamadzhiyan+...@orbitsoft.com
CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org
  Target Milestone: ---

Application: xdg-desktop-portal-kde (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-11-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Tried twice:
1. click on a file from telegram chant to download.
2. get a dialog to select an app from that file
3. mark checkbox to assocoate current files type with selected app (tried with
.txt and .docx file)
4. get errors, but file extension is asssiciated successful

The crash can be reproduced every time.

-- Backtrace:
Application: ÐоÑÑал (xdg-desktop-portal-kde), signal: Aborted

   PID: 333648 (xdg-desktop-por)
   UID: 1000 (local)
   GID: 1001 (local)
Signal: 6 (ABRT)
 Timestamp: Tue 2023-08-22 10:34:50 MSK (39s ago)
  Command Line: /usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde
Executable: /usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-xdg-desktop-portal-kde.service
  Unit: user@1000.service
 User Unit: plasma-xdg-desktop-portal-kde.service
 Slice: user-1000.slice
 Owner UID: 1000 (local)
   Boot ID: 505f5a041e764f339767c4b711973b7a
Machine ID: fca7e90857a049ca85760b7f77a36afa
  Hostname: vitaly
   Storage:
/var/lib/systemd/coredump/core.xdg-desktop-por.1000.505f5a041e764f339767c4b711973b7a.333648.169268969000.zst
(present)
  Size on Disk: 6.1M
   Message: Process 333648 (xdg-desktop-por) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64
Stack trace of thread 333649:
#0  0x7fe2a62a9d3c n/a (libc.so.6 + 0x8ad3c)
#1  0x7fe2a625af32 raise (libc.so.6 + 0x3bf32)
#2  0x7fe2a788db46 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b46)
#3  0x7fe2a625afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7fe2a62a9d3c n/a (libc.so.6 + 0x8ad3c)
#5  0x7fe2a625af32 raise (libc.so.6 + 0x3bf32)
#6  0x7fe2a625afd0 n/a (libc.so.6 + 0x3bfd0)
#7  0x7fe2a631b03f __poll (libc.so.6 + 0xfc03f)
#8  0x7fe2a57f0d12 n/a (libxcb.so.1 + 0xcd12)
#9  0x7fe2a57f307a xcb_wait_for_event (libxcb.so.1 +
0xf07a)
#10 0x7fe2a16faf00 n/a (libQt5XcbQpa.so.5 + 0x6cf00)
#11 0x7fe2a64cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#12 0x7fe2a62a8044 n/a (libc.so.6 + 0x89044)
#13 0x7fe2a63285fc n/a (libc.so.6 + 0x1095fc)

Stack trace of thread 333650:
#0  0x7fe2a49d43b8 g_main_context_check (libglib-2.0.so.0 +
0x543b8)
#1  0x7fe2a49d4958 n/a (libglib-2.0.so.0 + 0x54958)
#2  0x7fe2a49d4acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#3  0x7fe2a6709836
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x309836)
#4  0x7fe2a66b017b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2b017b)
#5  0x7fe2a64cab87 _ZN7QThread4execEv (libQt5Core.so.5 +
0xcab87)
#6  0x7fe2a7f86487 n/a (libQt5DBus.so.5 + 0x17487)
#7  0x7fe2a64cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#8  0x7fe2a62a8044 n/a (libc.so.6 + 0x89044)
#9  0x7fe2a63285fc n/a (libc.so.6 + 0x1095fc)

Stack trace of thread 333694:
#0  0x7fe2a4a292b4 g_mutex_unlock (libglib-2.0.so.0 +
0xa92b4)
#1  0x7fe2a49d3ed0 g_main_context_prepare (libglib-2.0.so.0
+ 0x53ed0)
#2  0x7fe2a49d48e3 n/a (libglib-2.0.so.0 + 0x548e3)
#3  0x7fe2a49d4acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#4  0x7fe2a670984e
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x30984e)
#5  0x7fe2a66b017b
_ZN10QEventLoop4execE6QFl

[xdg-desktop-portal-kde] [Bug 473624] Crash on saving file existension assiciation from telegram app

2023-08-22 Thread VitalyOrbitSoft
https://bugs.kde.org/show_bug.cgi?id=473624

--- Comment #1 from VitalyOrbitSoft  
---
One more try with .xlsx file.
Repeated again.

Doesn't matter what the file type.

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

[plasmashell] [Bug 395099] New: Plasma falls when search on start menu

2018-06-07 Thread VitalyOrbitSoft
https://bugs.kde.org/show_bug.cgi?id=395099

Bug ID: 395099
   Summary: Plasma falls when search on start menu
   Product: plasmashell
   Version: 5.12.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vitaly.khatlamadzhiyan+...@orbitsoft.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.5)

Qt Version: 5.9.4
Frameworks Version: 5.46.0
Operating System: Linux 4.16.13-200.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

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

- Unusual behavior I noticed:

Just call menu (Alt+F1) and type.
But do it quick.

For example, I offen launch google chrome from start menu.
For it I type "chome", but sometimes after "ch" Plasma falls.
If I wait a little after the start menu shown, no falls.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f881d243940 (LWP 2031))]

Thread 16 (Thread 0x7f8717fff700 (LWP 7458)):
#0  0x7f8813cee82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88157ec53b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f8752005725 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f8752009778 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f87520048dd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f87520097d2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f87520048dd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7f87520076bb in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7f88157ebde2 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f8813ce850b in start_thread () at /lib64/libpthread.so.0
#10 0x7f8814b9d16f in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f872cb27700 (LWP 7457)):
#0  0x7f8813cee82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88157ec53b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f8752005725 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f8752009778 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f87520048dd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f87520076bb in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f88157ebde2 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f8813ce850b in start_thread () at /lib64/libpthread.so.0
#8  0x7f8814b9d16f in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f872d328700 (LWP 7456)):
#0  0x7f8813cee82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88157ec53b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f8752005725 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f8752009778 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f87520048dd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f87520097d2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f87520048dd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7f87520076bb in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7f88157ebde2 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f8813ce850b in start_thread () at /lib64/libpthread.so.0
#10 0x7f8814b9d16f in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f872db29700 (LWP 7455)):
#0  0x7f8813cee82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88157ec53b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f8752005725 in
ThreadWeaver::Weav

[plasmashell] [Bug 501634] New: doesn't changed connected/disconnected state

2025-03-17 Thread VitalyOrbitSoft
https://bugs.kde.org/show_bug.cgi?id=501634

Bug ID: 501634
   Summary: doesn't changed connected/disconnected state
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Bluetooth widget
  Assignee: plasma-b...@kde.org
  Reporter: vitaly.khatlamadzhiyan+...@orbitsoft.com
  Target Milestone: 1.0

The bluetooth system tray icon doesn't changed its state after connecting to
devices. However, devices are connected.
But I'm not sure it's related to the Plasma DE. It works fine with 6.1.0-27
core.
That issue appears with new core versions.

Only,  if I remove (not just disconnect) and add devices again, the system tray
icon changed to the "connected" state.


STEPS TO REPRODUCE
1. Use any cores after 6.1.0-27
2. Just turn a bluetooth devices on, connected before.

OBSERVED RESULT
The tray icon changed to the "connected" state.


EXPECTED RESULT
The tray icon changed to the "connected" state.


SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-32-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics
Memory: 30.8 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Rombica
Product Name: myBook Zenith

ADDITIONAL INFORMATION

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