[kwin] [Bug 462996] Windows do not stay on the virtual desktop they are on

2022-12-28 Thread Fabian Niepelt
https://bugs.kde.org/show_bug.cgi?id=462996

Fabian Niepelt  changed:

   What|Removed |Added

 CC||bugs...@takios.de

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

[konversation] [Bug 381066] Konversation crashes with a segmentation fault

2020-12-02 Thread Fabian Niepelt
https://bugs.kde.org/show_bug.cgi?id=381066

Fabian Niepelt  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #14 from Fabian Niepelt  ---
This is not happening to me anymore so I'm marking it as resolved.

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

[kdeconnect] [Bug 429400] New: Virtual Keyboard: Typing "<" results in ">"

2020-11-20 Thread Fabian Niepelt
https://bugs.kde.org/show_bug.cgi?id=429400

Bug ID: 429400
   Summary: Virtual Keyboard: Typing "<" results in ">"
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: bugs...@takios.de
  Target Milestone: ---

SUMMARY

Hello,

when using the virtual keyboard on my Android to write something on my PC
(KDE), typing a "<" results in a ">". 

STEPS TO REPRODUCE

1. Use kdeconnect-kde and connect with Android kdeconnect
2. Focus any textarea on desktop (e.g. Kate)
3. Open the "Ferneingabe" (I think original name is Remote Control?) function
in the kdeconnect app.
4. Open the virtual keyboard using top right button. Gboard opens.
5. Press "?123"
6. Press "=/<"
7. Press "<"

OBSERVED RESULT

A ">" appears in the active textarea.

EXPECTED RESULT

A "<" appears in the active textarea.

SOFTWARE/OS VERSIONS
Windows: Not tested
macOS: Not tested
Linux/KDE Plasma: Yes
(available in About System)
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION

Android Version: 10
Android Keyboard used: Gboard
KDEConnect App Version: 1.15.1

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

[konversation] [Bug 381066] Konversation crashes with a segmentation fault

2017-06-15 Thread Fabian Niepelt
https://bugs.kde.org/show_bug.cgi?id=381066

--- Comment #9 from Fabian Niepelt <bugs...@takios.de> ---
Crashes even with LANG=C. I also tried setting my shortcuts to Defaults, but
that didn't solve the probleme either.

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

[konversation] [Bug 381066] Konversation crashes with a segmentation fault

2017-06-15 Thread Fabian Niepelt
https://bugs.kde.org/show_bug.cgi?id=381066

--- Comment #8 from Fabian Niepelt <bugs...@takios.de> ---
I don't have a ~/.local/share/kxmlgui5/konversation/konversationui.rc , so I'll
try launching Konversation with LANG=C and report back.

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

[konversation] [Bug 381066] New: Konversation crashes with a segmentation fault

2017-06-10 Thread Fabian Niepelt
https://bugs.kde.org/show_bug.cgi?id=381066

Bug ID: 381066
   Summary: Konversation crashes with a segmentation fault
   Product: konversation
   Version: 1.7.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: bugs...@takios.de
  Target Milestone: ---

Application: konversation (1.7.2)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Started Konversation. Automatically connected to snoonet and freenode. Joined 2
rooms on snoonet and 3 rooms on freenode. Did not send a message, only read.

I have no specific action that triggers the crash, it can happen while writing
or not doing anything with the application at.

I reported the bug at my distribution's bugtracker
(https://bugzilla.opensuse.org/show_bug.cgi?id=1041130) and was advised to
report this behaviour upstream.

The crash can be reproduced every time.

-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7d77251100 (LWP 13620))]

Thread 10 (Thread 0x7f7d3fae0700 (LWP 13632)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcafe0500) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d3fae0700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 9 (Thread 0x7f7d402e1700 (LWP 13631)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcb01cc80) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d402e1700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7f7d40ae2700 (LWP 13630)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcb08bd20) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d40ae2700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 7 (Thread 0x7f7d412e3700 (LWP 13629)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcafe0500) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d412e3700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f7d41ce9700 (LWP 13628)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0,