[kontact] [Bug 405440] Kontact crash when click on configure kontact
https://bugs.kde.org/show_bug.cgi?id=405440 Francisco Gonzalez changed: What|Removed |Added CC||gzmor...@gmail.com --- Comment #1 from Francisco Gonzalez --- *** Bug 405426 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405426] kontact crash when trying configure
https://bugs.kde.org/show_bug.cgi?id=405426 Francisco Gonzalez changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Francisco Gonzalez --- *** This bug has been marked as a duplicate of bug 405440 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405426] kontact crash when trying configure
https://bugs.kde.org/show_bug.cgi?id=405426 Francisco Gonzalez changed: What|Removed |Added Summary|kontact crash |kontact crash when trying ||configure -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405426] New: kontact crash
https://bugs.kde.org/show_bug.cgi?id=405426 Bug ID: 405426 Summary: kontact crash Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gzmor...@gmail.com Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: Try to open kontact configuration - What I was expectiing To be able to change kontact configuration - What I get: kontact crash The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc4b0695bc0 (LWP 6103))] Thread 29 (Thread 0x7fc35d5bc700 (LWP 6175)): #0 0x7fc4a88c2ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc35d5bb710, expected=0, futex_word=0x7fc35d5bb8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fc4a88c2ed9 in __pthread_cond_wait_common (abstime=0x7fc35d5bb7b0, mutex=0x7fc35d5bb8a8, cond=0x7fc35d5bb8d0) at pthread_cond_wait.c:533 #2 0x7fc4a88c2ed9 in __pthread_cond_timedwait (cond=0x7fc35d5bb8d0, mutex=0x7fc35d5bb8a8, abstime=0x7fc35d5bb7b0) at pthread_cond_wait.c:667 #3 0x7fc49df22177 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc49df22ada in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc49df22bc2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc49dee0851 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc49dee3387 in base::internal::SchedulerWorker::RunWorker() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc49dee3974 in base::internal::SchedulerWorker::RunPooledWorker() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc49df24cd1 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fc4a88bc6db in start_thread (arg=0x7fc35d5bc700) at pthread_create.c:463 #11 0x7fc4acfc788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fc35e1dd700 (LWP 6171)): #0 0x7fc4acfb60b4 in __GI___libc_read (fd=106, buf=0x7fc35e1dc7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc4a6a34cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4a69f0027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4a69f04e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc4a69f064c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc4adb1515b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fc354000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fc4adab664a in QEventLoop::exec(QFlags) (this=this@entry=0x7fc35e1dc9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fc4ad8de41a in QThread::exec() (this=) at thread/qthread.cpp:531 #8 0x7fc4ad8dfbc2 in QThreadPrivate::start(void*) (arg=0x55f5b4425ff0) at thread/qthread_unix.cpp:361 #9 0x7fc4a88bc6db in start_thread (arg=0x7fc35e1dd700) at pthread_create.c:463 #10 0x7fc4acfc788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fc35f3ee700 (LWP 6168)): #0 0x7fc4acfbabb9 in __GI___poll (fds=0x7fc350004a10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc4a69f0539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4a69f064c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4adb1515b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fc35b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fc4adab664a in QEventLoop::exec(QFlags) (this=this@entry=0x7fc35f3ed9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc4ad8de41a in QThread::exec() (this=) at thread/qthread.cpp:531 #6 0x7fc4ad8dfbc2 in QThreadPrivate::start(void*) (arg=0x55f5b43eb4f0) at thread/qthread_unix.cpp:361 #7 0x7fc4a88bc6db in start_thread (arg=0x7fc35f3ee700) at pthread_create.c:463 #8 0x7fc4acfc788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7fc35fbef700 (LWP 6165)): #0 0x7fc4acfbabf9 in __GI___poll (fds=0x7fc358003ce0, nfds=1,
[kdeconnect] [Bug 402102] Unable to send files from smartphone to desktop
https://bugs.kde.org/show_bug.cgi?id=402102 Francisco Gonzalez changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Francisco Gonzalez --- Ok problem solved. Android was restoring settings from the auto-save feature. The settings were from an old phone. To solve the issue I have disabled the auto restore settings from auto-save. Removing the app, cache and data were not enough, as Android will recover the data from your account if the featue is enabled. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402102] Unable to send files from smartphone to desktop
https://bugs.kde.org/show_bug.cgi?id=402102
--- Comment #2 from Francisco Gonzalez ---
This is the datagram received on UDP channel before pairing:
kdeconnect.core: Datagram
{"id":1544834411076,"type":"kdeconnect.identity","body":{"deviceId":"c3bedee7133dbc3a","deviceName":"gzmorell@mia2","protocolVersion":7,"deviceType":"phone","incomingCapabilities":["kdeconnect.sms.request_conversations","kdeconnect.telephony.request_mute","kdeconnect.telephony.request","kdeconnect.mpris","kdeconnect.notification","kdeconnect.sms.request_conversation","kdeconnect.findmyphone.request","kdeconnect.ping","kdeconnect.systemvolume","kdeconnect.notification.reply","kdeconnect.share.request","kdeconnect.sftp.request","kdeconnect.notification.request","kdeconnect.mousepad.request","kdeconnect.contacts.request_vcards_by_uid","kdeconnect.sms.request","kdeconnect.runcommand","kdeconnect.battery.request","kdeconnect.clipboard","kdeconnect.contacts.request_all_uids_timestamps"],"outgoingCapabilities":["kdeconnect.sms.messages","kdeconnect.telephony","kdeconnect.notification","kdeconnect.contacts.response_uids_timestamps","kdeconnect.findmyphone.request","kdeconnect.ping","kdeconnect.mousepad.keyboardstate","kdeconnect.share.request","kdeconnect.contacts.response_vcards","kdeconnect.notification.request","kdeconnect.mousepad.echo","kdeconnect.mousepad.request","kdeconnect.sftp","kdeconnect.runcommand.request","kdeconnect.mpris.request","kdeconnect.systemvolume.request","kdeconnect.battery","kdeconnect.clipboard"],"tcpPort":1716}}
And this is the certificate of the smartphone:
"Certificate:\n
Data:\n
Version: 3 (0x2)\n
Serial Number: 1 (0x1)\n
Signature Algorithm: sha256WithRSAEncryption\n
Issuer: CN=ef03bd23be35246a, OU=KDE Connect, O=KDE\n
Validity\n
Not Before: Sep 11 10:30:35 2016 GMT\n
Not After : Sep 11 10:30:35 2026 GMT\n
Subject: CN=ef03bd23be35246a, OU=KDE Connect, O=KDE\n
Subject Public Key Info:\n
Public Key Algorithm: rsaEncryption\n
RSA Public-Key: (2048 bit)\n
Modulus:\n
00:98:68:eb:b7:f2:47:23:a6:43:1e:c8:a8:e9:5b:\n
64:89:95:0f:71:d3:6f:35:75:bd:bf:80:53:bd:12:\n
b0:1b:be:50:c4:a6:d7:ea:35:4a:19:c2:8d:16:a5:\n
6e:57:a3:7c:3a:92:b8:46:39:6e:4b:1c:d4:07:6c:\n
74:a2:a2:93:77:82:51:44:86:8c:be:f8:b2:f3:c3:\n
aa:ac:f4:50:a1:a0:67:54:31:7b:8a:b1:ec:97:0e:\n
68:e0:cc:29:6c:e6:1b:87:d8:4a:a6:d5:3d:78:75:\n
f7:ac:6c:66:8c:a0:75:1e:d1:29:68:c2:f4:c7:39:\n
47:9f:b9:f7:08:2a:ca:ec:96:27:91:80:78:64:d4:\n
82:b3:08:6a:ca:f4:52:95:ce:1b:da:96:20:82:58:\n
89:db:47:f3:4b:44:95:7d:75:1b:59:19:79:34:d7:\n
00:e4:29:1f:f6:27:65:c6:bf:2d:71:46:ed:7e:d2:\n
01:43:9c:52:cf:19:6d:90:c8:92:98:79:c3:d2:25:\n
88:da:41:db:8e:24:5f:12:8d:6f:8b:a7:e6:5d:65:\n
ce:7b:06:39:12:58:c8:c9:ef:7e:b3:f8:5d:15:bd:\n
72:97:ca:36:f0:17:1c:bd:14:be:a1:77:20:26:81:\n
da:3d:f9:d0:ec:6d:22:fa:e3:97:03:f5:5f:b9:03:\n
dd:1f\n
Exponent: 65537 (0x10001)\n
Signature Algorithm: sha256WithRSAEncryption\n
8a:2e:11:7d:1c:d1:1c:f0:56:c1:50:3c:56:71:47:33:6a:70:\n
f2:f8:49:54:d2:f2:8e:dd:0e:d0:ec:c4:ff:6a:b3:29:d8:7e:\n
f8:c1:6c:31:01:b1:ba:09:3c:f6:cb:bf:e3:8e:48:16:86:6c:\n
77:26:3e:7b:10:73:aa:25:50:a1:9c:5d:3b:32:b6:d5:c7:3a:\n
23:b8:52:46:c5:d3:52:5e:d9:58:85:af:e1:2e:7f:9e:18:32:\n
b4:c8:86:da:db:35:fd:bf:36:89:bc:21:d6:a3:81:ca:93:b1:\n
a1:47:43:81:d1:29:72:69:b8:e4:65:37:97:6c:a1:ba:c0:73:\n
23:2b:2d:78:41:6f:00:d7:50:b0:4c:6b:0a:22:d9:64:22:53:\n
69:ca:dc:57:20:68:4d:96:a1:5f:a1:92:1f:5a:92:16:a8:14:\n
48:62:17:40:75:ec:d4:3f:7e:0a:a1:ec:30:c1:2c:06:c8:9b:\n
d6:8b:fe:d0:cc:4d:dd:d7:ce:61:5f:b5:6e:71:61:b6:96:8f:\n
32:96:66:b1:11:30:31:17:b6:2e:07:9f:48:12:57:76:a1:9a:\n
3a:70:0a:d6:2a:2d:2c:fe:ca:64:a5:c4:64:ab:42:dd:d0:d1:\n
2e:0c:cb:a8:b3:47:30:b1:c3:40:a7:33:6f:11:11:54:9d:58:\n
eb:ca:3d:8b\n
The "deviceId":"c3bedee7133dbc3a"
The CN=ef03bd23be35246a
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 402102] Unable to send files from smartphone to desktop
https://bugs.kde.org/show_bug.cgi?id=402102 --- Comment #1 from Francisco Gonzalez --- The problem seems to be with the id of the phone. The id it sends is not the same as the CN (common name) of the SSL certificate that the smartphone sends. When kdeconnect tries to open a QSslSocket to download the file the connection fails with the error: "The host name did not match any of the valid hosts for this certificate", so the file can not be downloaded. I have tested other phones and de "id" and CN are the same. How is it possible to be different on this phone? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402102] New: Unable to send files from smartphone to desktop
https://bugs.kde.org/show_bug.cgi?id=402102 Bug ID: 402102 Summary: Unable to send files from smartphone to desktop Product: kdeconnect Version: 1.3.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: gzmor...@gmail.com Target Milestone: --- SUMMARY This only happens with one smartphone (XIAOMI A2) with Android One version 8.1.0 and kdeconnectd. It is not possible to send files from the smartphone to the desktop. The notification system also do not work due to the same problem (it tries to download the icon file and the job never finishes nor produce an error). The problem appears when running "filetranferjob.cpp" code: if (m_origin->bytesAvailable()) startTransfer(); connect(m_origin.data(), ::readyRead, this, ::startTransfer); bytesAvailabe are 0 and FileTransferJob::startTransfer is never called. With gsconnect both file transfer and indications works as expected. I have also tried Kde-Neon with the same result. I have also tried the git kdeconnect version on the desktop. STEPS TO REPRODUCE 1. In the androidsmartphone app press send file 2. Choose one file (do not matter the size or type). OBSERVED RESULT . After some time the smartphone report that the file could not be sent. The kde desktop shows the file downloading "forever". With gnome and gsconnect the file is transfered correctly. EXPECTED RESULT The file is already transfered. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Archlinux with kde desktop updated (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368758] New: Printing with grayscale option do not work
https://bugs.kde.org/show_bug.cgi?id=368758 Bug ID: 368758 Summary: Printing with grayscale option do not work Product: okular Version: 0.25.80 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: gzmor...@gmail.com Trying to print a color pdf document in grayscale produces a color printing. This happens when printing to a color printer and also printing to a file. Printing a png file in grayscale works as expected. Reproducible: Always Steps to Reproduce: 1. Open a pdf color file 2. Select "File -> Print -> Options -> Options -> (Color Mode) Grayscale" 3. Press "Print" Actual Results: The document is printed in color Expected Results: The document should be printed in grayscale Tested in Archlinux with version 0.26.0 Frameworks 5.25.0 Plasma 5.7.5 PDF Backend 0.6.5 KDE Development Platform 4.14.24 kdelibs 4.14.24 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 354204] Checkboxes in QtCreator Wizards are uncheckable
https://bugs.kde.org/show_bug.cgi?id=354204 --- Comment #5 from Francisco Gonzalez <gzmor...@gmail.com> --- Still present on Arch : qtcreator 4.1.0-1 plasma 5.7.4-2 qt 5.7.0-2 frameworkintegration 5.25.0-1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 367688] New: Audio Volume Settings of Notification Sounds reset to zero
https://bugs.kde.org/show_bug.cgi?id=367688 Bug ID: 367688 Summary: Audio Volume Settings of Notification Sounds reset to zero Product: systemsettings Version: 5.7.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_phonon Assignee: sit...@kde.org Reporter: gzmor...@gmail.com Trying to set notification sounds volume to a value different to 0 is not possible. The slider returns to 0 value. Reproducible: Always Steps to Reproduce: 1. Open system settings. 2. Open multimedia settings. 3. On "Applications" tab try to set the "Notifications Sounds" slider to a value different to zero" Actual Results: The value remains at 0. Expected Results: Able to set the volume to a value different than 0. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 354204] Checkboxes in QtCreator Wizards are uncheckable
https://bugs.kde.org/show_bug.cgi?id=354204 Francisco Gonzalez <gzmor...@gmail.com> changed: What|Removed |Added CC||gzmor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
