[kdeconnect] [Bug 424912] Last modified dates of received images are incorrect after sharing through the app

[Rüdiger Bente]

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

--- Comment #5 from Rüdiger Bente  ---
strange result:
when i use the file manager to send a picture from the mobile to the PC the
timestamp on the PC is valid and ok,
when i send the same picture using the send function of the gallery the
timestamp on the PC is 2446-05-11 00:38:55
both test are repeated a couple of times with the same results using KDEConnect
on the mobile, same network

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

[kdeconnect] [Bug 424912] Last modified dates of received images are incorrect after sharing through the app

[Rüdiger Bente]

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

--- Comment #4 from Rüdiger Bente  ---
i use only the send function for sharing pictures from the mobile to the PC
using the send function of the gallery.

Version KDEConnect on Android is 1.26.0, KDEConnect under Linux Mint (V21
Vanessa base: Ubuntu 22.04, Kernel 5.15) is on 21.12.3
The mobile is a Xiaomi Redmi 9, Android 12, MIUI 13.01 stable

Will test the other functions soon and report the results.

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

[kdeconnect] [Bug 424912] Last modified dates of received images are incorrect after sharing through the app

[Rüdiger Bente]

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

--- Comment #2 from Rüdiger Bente  ---
no reaction here, but for those with a similar problem
I use inotifywait for a temporary solution, running a script in bash nonstop:

#!/bin/bash

inotifywait -mrq -e move --format %w%f /home//Downloads | while read FILE
do
EXP=$(echo -n $FILE | tail -c 4)
if [ "$EXP" = ".jpg" ]; then
touch $FILE
fi
done

by the way, the timestamp for files created by this bug are always 2446-05-11
00:38:55 which is the unix timestamp 15032385535 which is hex 37FFF  or
binary 110111. Could be a buffer problem???

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

[kdeconnect] [Bug 424912] Last modified dates of received images are incorrect after sharing through the app

[Rüdiger Bente]

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

Rüdiger Bente  changed:

   What|Removed |Added

 CC||ruediger.be...@gmx.de

--- Comment #1 from Rüdiger Bente  ---
Same for me.
KDEConnect on Android Version 1.23.2and on Linux (Mint) 21.12.3-0ubuntu1

Because of this i run into severe problems with my Nextcloud installation,
because the files were automatically transferred  to the Nextcloud host and
that produces critical errors with the replication, when the modification time
is in the future

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

[kwin] [Bug 375400] KWIN crashes at start of second application

[Rüdiger Bente]

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

Rüdiger Bente <ruediger.be...@gmx.de> changed:

   What|Removed |Added

 CC||ruediger.be...@gmx.de

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

[kwin] [Bug 375400] New: KWIN crashes at start of second application

[Rüdiger Bente]

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

Bug ID: 375400
   Summary: KWIN crashes at start of second application
   Product: kwin
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ruediger.be...@gmx.de
  Target Milestone: ---

Created attachment 103582
  --> https://bugs.kde.org/attachment.cgi?id=103582=edit
kwin qdbus support information

After login, starting the second application, kwin crashes. Does no matter,
which are this application, most of the time is start first Firefox and after
that Thunderbird, but the problem occurs on other scenarios as well.
Got some debug information:
 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 0x7f6905958940 (LWP 1552))]

Thread 4 (Thread 0x7f684700 (LWP 1763)):
#0  0x7f69054439e3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6903c47e5f in qt_safe_select (nfds=15,
fdread=fdread@entry=0x7f68480df878, fdwrite=fdwrite@entry=0x7f68480dfb08,
fdexcept=fdexcept@entry=0x7f68480dfd98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f6903c4995e in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f68480dfd98, writefds=0x7f68480dfb08, readfds=0x7f68480df878,
nfds=, this=0x7f6848146070) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f68480df6e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f6903c49e8e in QEventDispatcherUNIX::processEvents
(this=0x7f6848146070, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f6903bf3b4a in QEventLoop::exec (this=this@entry=0x7f684fffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f6903a10834 in QThread::exec (this=this@entry=0x2c6d270) at
thread/qthread.cpp:503
#7  0x7f68fe5263c5 in QQmlThreadPrivate::run (this=0x2c6d270) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f6903a157be in QThreadPrivate::start (arg=0x2c6d270) at
thread/qthread_unix.cpp:331
#9  0x7f68ff3c96ba in start_thread (arg=0x7f684700) at
pthread_create.c:333
#10 0x7f690544d82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f68db7fe700 (LWP 1586)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6902b9dbd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f6902b9dc19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f68ff3c96ba in start_thread (arg=0x7f68db7fe700) at
pthread_create.c:333
#4  0x7f690544d82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f68e1515700 (LWP 1583)):
#0  0x7f6903a0dd5f in QBasicAtomicOps<8>::testAndSetRelaxed
(currentValue=, newValue=0x0, expectedValue=0x1,
_q_value=@0x290b638: 0x0) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259
#1  QGenericAtomicOps >::testAndSetRelease (currentValue=, newValue=0x0,
expectedValue=, _q_value=@0x290b638: 0x0) at
../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:175
#2  QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=,
this=this@entry=0x290b638) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:278
#3  QBasicMutex::fastTryUnlock (current=,
this=this@entry=0x290b638) at thread/qmutex.h:85
#4  QMutex::unlock (this=this@entry=0x290b638) at thread/qmutex.cpp:264
#5  0x7f6903c49d83 in QMutexLocker::unlock (this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:138
#6  QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:132
#7  QThreadData::canWaitLocked (this=) at
../../include/QtCore/5.5.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:240
#8  QEventDispatcherUNIX::processEvents (this=0x7f68d40008c0, flags=...) at
kernel/qeventdispatcher_unix.cpp:582
#9  0x7f6903bf3b4a in QEventLoop::exec (this=this@entry=0x7f68e1514c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#10 0x7f6903a10834 in QThread::exec (this=this@entry=0x28aa9d0) at
thread/qthread.cpp:503
#11 0x7f68fe5263c5 in QQmlThreadPrivate::run (this=0x28aa9d0) at
qml/ftw/qqmlthread.cpp:141
#12 0x7f6903a157be in QThreadPrivate::start (arg=0x28aa9d0) at
thread/qthread_unix.cpp:331
#13 0x7f68ff3c96ba in start_thread (arg=0x7f68e1515700) at
pthread_create.c:333
#14 0x7f690544d82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f6905958940 (LWP 1552)):
[KCrash Handler]
#6  QV4::Managed::d (this=0x0) at jsruntime/qv4managed_p.h:134
#7  

[konsole] [Bug 356541] New: add a configurable toolbar to Konsole

[Rüdiger Bente via KDE Bugzilla]

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

Bug ID: 356541
   Summary: add a configurable toolbar to Konsole
   Product: konsole
   Version: 15.08.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: ruediger.be...@gmx.de

Hello,

i would like to have a toolbar where i can store commands to execute.
For each command there must be a button placed on that toolbar.
for example:
+-+
|   +-+++  +--+
 |
|   |exit  ||  top  |  |  sudo vi| 
   |
|   +--+   ++  +---+   
|
+-+

All the commands must be configurable by a settings dialog and when i click on
that button the command must be placed to the commandline, with or without CR.

Thanks in advance.

Regards


Reproducible: Always

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

[konsole] [Bug 356541] add a configurable toolbar to Konsole

[Rüdiger Bente via KDE Bugzilla]

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

Rüdiger Bente <ruediger.be...@gmx.de> changed:

   What|Removed |Added

 CC||ruediger.be...@gmx.de

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