[okular] [Bug 348171] Scaling problem during printing
https://bugs.kde.org/show_bug.cgi?id=348171 Ferry changed: What|Removed |Added CC||ft...@telfort.nl --- Comment #2 from Ferry --- This is a regression in Okular 0.25.0 (using KDE platform 4.14.22) in Kubuntu Yakkety Yak. Okular prints A4 pages in A5 size (so shrinks the page), this does not happen with other applications (Documentviewer printing the same pdf, Libreoffice printing other documents). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363788] Fit to page printing does incorrect scaling and unwanted offsetting
https://bugs.kde.org/show_bug.cgi?id=363788 Ferry changed: What|Removed |Added CC||ft...@telfort.nl --- Comment #11 from Ferry --- This is regressing in Okular 0.25.0 (using KDE platform 4.14.22) in Kubuntu Yakkety Yak (16.10). Okular prints A4 pages in A5 size (so unnecessarily shrinks the page) on a A4 printer, this does not happen with other applications (Documentviewer printing the same pdf, Libreoffice printing other documents). This happens when printing to our cups printer server (Kubuntu Xenial) which prints to the HP laser (2 different tried both with network connection and PS support). When printing directly to the network printer the downscaling does not happen. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467299] New: Screenlocker becomes active on wakeup
https://bugs.kde.org/show_bug.cgi?id=467299 Bug ID: 467299 Summary: Screenlocker becomes active on wakeup Classification: Plasma Product: kscreenlocker Version: 5.25.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ferry.t...@elsinga.info Target Milestone: --- SUMMARY *** When closing the lid of my laptop it sleeps as it should. However, when opening the lid the laptop wakes, and shows the desktop for a few seconds. Then the screenlocker kicks in, hides the desktop and asks for a password. This only happens with Wayland, not with X11. *** This is with Kubuntu Kinetic (22.10) libkscreenlocker5.25.5-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 455805] At start of digikam: "Your locale has changed since this album was last opened."
https://bugs.kde.org/show_bug.cgi?id=455805 Ferry <06f13.41...@mailbox.org> changed: What|Removed |Added CC||06f13.41...@mailbox.org --- Comment #4 from Ferry <06f13.41...@mailbox.org> --- (In reply to Maik Qualmann from comment #2) > The mentioned change of reading the current database encoding is actually > not included in digiKam-7.7.0. > However, a long-standing Qt bug that always returned "System" as the current > text encoding under Windows has been fixed by Qt. Now the actually used code > page is returned. Hence the message. > This means that the message will appear again in digiKam-8.0.0. > However, this message is purely informative and has no further influence in > digiKam and can simply be confirmed with ok. > > Maik Unfortunately, I have to disagree. This effect acts as a blockade when using GPX data to subsequently add geodata to the images. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 455805] At start of digikam: "Your locale has changed since this album was last opened."
https://bugs.kde.org/show_bug.cgi?id=455805 --- Comment #6 from Ferry <06f13.41...@mailbox.org> --- (In reply to Maik Qualmann from comment #5) > No, this change does not affect adding GPX data either. Can you describe > your problem when adding GPX data? > There is a change due to bug reports that the decimal separator (dot or > comma) for GPS coordinates should match the locale. > > Maik Thanks Maik. Here comes the overall picture. My configuration: Windows: 10 Pro / 21H2 / Build 19044.1806 / Region Germany / Format German / Date Time: ISO 8601: -MM-DD hh:mm:ss Digikam: 7.7.0 since 2022-07-08 (until version 7.6 the insertion of GPX data worked) GPX data: Garmin Oregon 600, alternatively 'GPS Logging App'@Android12 When installing digikam 7.7.0 I got a hint about changed code page: 'Old locale: System, new locale: windows-1252' (attachment, page 1). I did not understand what is meant by this and what to do. My Windows is installed as usual. When trying to add coordinates to photos using GPX data, the message came up "Correlation failed - No image could be correlated - please make sure time zone and time difference settings are correct." My understanding is that everything is set correctly in Windows. However, if digikam is meant, I don't know where to look. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 455805] At start of digikam: "Your locale has changed since this album was last opened."
https://bugs.kde.org/show_bug.cgi?id=455805 --- Comment #7 from Ferry <06f13.41...@mailbox.org> --- I did not find the bug, but my digikam 7.7.0 works again regarding geodata entry in photos from GMX files. No further action is required. Sorry for my false report. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 429121] New: No context menu when drag and drop file / directory from Dolfin
https://bugs.kde.org/show_bug.cgi?id=429121 Bug ID: 429121 Summary: No context menu when drag and drop file / directory from Dolfin Product: konsole Version: 20.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ferry.t...@elsinga.info Target Milestone: --- SUMMARY Context menu does not appear STEPS TO REPRODUCE 1. Drag folder from Dolfin into Konsole 2. 3. OBSERVED RESULT path is dropped as text, no menu appears EXPECTED RESULT https://docs.kde.org/stable5/en/applications/konsole/drag-and-drop.html SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 20.08.02 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This has worked in the past, but hasn't for some time. Note that "disable the context menu to insert URLs as text by default, enable the corresponding options on the Mouse tab in the profile settings dialog." doesn't work. It's is always disabled. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 429121] No context menu when drag and drop file / directory from Dolfin
https://bugs.kde.org/show_bug.cgi?id=429121 --- Comment #3 from Ferry --- I see. Something is mixed up with the profiles. I used Settings->Manage Profile->default and "edit"->Mouse->Miscellaneous->uncheck default is the checked profile (and the only visible profile), but apparently not the current profile. When I now tried Setting->Edit current profile it appears an unvisible profile is the current, and when I modify the setting it works. Seems the behavior of profiles may be confusing, but working as intended. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 429121] No context menu when drag and drop file / directory from Dolfin
https://bugs.kde.org/show_bug.cgi?id=429121 Ferry changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429346] New: Rotating and cropping: Concentration of the cropping frame on the real image area.
https://bugs.kde.org/show_bug.cgi?id=429346 Bug ID: 429346 Summary: Rotating and cropping: Concentration of the cropping frame on the real image area. Product: digikam Version: 7.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Crop Assignee: digikam-bugs-n...@kde.org Reporter: 06f13.41...@mailbox.org Target Milestone: --- Created attachment 133455 --> https://bugs.kde.org/attachment.cgi?id=133455&action=edit Photo series to reproduce the above mentioned hint For reproduction see the attached photo series If a photo is not correctly oriented (# 1, twisted), the first step is to correct the orientation (# 2). The second step is cropping, which is typically set to "Current aspect ratio" for me. In order to get the largest possible area, I press "Largest possible area", but the cropping frame expands to the frame size (# 3). Only a small part of the frame format can be used, which I then have to adjust manually (# 4). EXPECTED RESULT: Shouldn't the automatic adjustment of the cropping frame be limited to the usable image format (# 4)? Windows 10 PRO, Version 20H2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429346] Rotating and cropping: Concentration of the cropping frame on the real image area.
https://bugs.kde.org/show_bug.cgi?id=429346 --- Comment #2 from Ferry <06f13.41...@mailbox.org> --- Thanks Maik, the rotation tool is much more powerful than I expected. My problem is now solved. Am 2020-11-19 um 19:27 schrieb Maik Qualmann: > https://bugs.kde.org/show_bug.cgi?id=429346 > > Maik Qualmann changed: > > What|Removed |Added > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann --- > The tool to crop the aspect ratio does not consider pixel content, this is not > an bug. The rotation tool can automatically cut to the largest area. Then with > the aspect ratio tool crop to the maximum area - done. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Ferry changed: What|Removed |Added CC||ferry.t...@elsinga.info --- Comment #25 from Ferry --- I have this since I just updated from Kubuntu 22.04 to 22.10. I have multiple machine all with Intel gfx but this is the only one with dual monitors. Not sure if it is related to dual monitors or if I missed updating some conf file during the update. I have been monitoring processes (htop) and logs (journalctl) on the console (crtl-alt F2), but nothing seems to be consuming lots of cpu or spitting sensible messages. Switching to console and back after I typed the password does make the screen onlock. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 386238] Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=386238 --- Comment #4 from Ferry --- Unfortunately (or fortunately?) I never had the issue again since removing the autosave file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422347] New: Program crash when clone repair
https://bugs.kde.org/show_bug.cgi?id=422347 Bug ID: 422347 Summary: Program crash when clone repair Product: digikam Version: 7.0.0 Platform: MS Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Plugin-Editor-Clone Assignee: digikam-bugs-n...@kde.org Reporter: 06f13.41...@mailbox.org Target Milestone: --- Program crash during clone repair 1. During the repair using clone, digikam crashes suddenly and completely. 2. After restarting digikam only, the sensitivity to the crash is significantly increased. 3. After restarting the computer, the probability of a crash is the same as before the first crash. The error pattern already occurred in version 6.4. Version 7.0 of digikam shows the same bug. System: Windows 10 Pro, version 2004, build 19041.264 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423004] New: Stringent up or down order for croping shapes
https://bugs.kde.org/show_bug.cgi?id=423004 Bug ID: 423004 Summary: Stringent up or down order for croping shapes Product: digikam Version: 7.0.0 Platform: MS Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Crop Assignee: digikam-bugs-n...@kde.org Reporter: 06f13.41...@mailbox.org Target Milestone: --- Created attachment 129376 --> https://bugs.kde.org/attachment.cgi?id=129376&action=edit Sample für up/down sorting SUMMARY: The sorting in 'Settings for cropping' appears somewhat disorganized because there is no logically increasing or decreasing order. A stringent sorting from 'square' to 'line shape' or vice versa would make the required selection easier, I think. See annex for an example STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 pro macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 7.0.0 Beta 3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422347] Program crash when clone repair
https://bugs.kde.org/show_bug.cgi?id=422347 --- Comment #2 from Ferry <06f13.41...@mailbox.org> --- The error (id = 422347) has not yet been completely corrected in 'Version 7.0.0 rc'. I apologize because I forgot to say that I am using a 'Logitech Anywhere MX' mouse, which allows me to move the object left / right by tilting the mouse wheel. This is necessary if the picture is enlarged to detect small errors. If the mouse wheel is tilted several times, the entire program still crashes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423004] Stringent up or down order for croping shapes
https://bugs.kde.org/show_bug.cgi?id=423004 --- Comment #3 from Ferry <06f13.41...@mailbox.org> --- Created attachment 129393 --> https://bugs.kde.org/attachment.cgi?id=129393&action=edit Falling or rising trend of formats instead of alternating landscape / portrait Ok, your second message came in. I only wants to explain by a graph, why I would prefer a stringent falling or rising sort sequence. It is not necessary to list the decimal fraction but it can be helpful for the decision of choosing a format. Please see also the attachment. Grenn side = my suggestion; red side = current situation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422347] Program crash when clone repair
https://bugs.kde.org/show_bug.cgi?id=422347 --- Comment #4 from Ferry <06f13.41...@mailbox.org> --- PROBLEM SOLVED On the contrary to my message (Comment # 2), I accidentally installed the wrong version. The digikam version '7.0.0 rc' works correctly with regard to the lateral image shift. Thank You! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 40892] extended ACL support for 2.2.* enabled servers
https://bugs.kde.org/show_bug.cgi?id=40892 --- Comment #2 from Ferry --- Unfortunately this is still not implemented in 17.12.3 (Kubuntu Bionic). I'll try to make the case for this functionality: on a shared file server (obviously sharing with Windows users), just giving the group read/write permissions is not always enough (for instance to change the owner of a file). The situation can be resolved using ACL's as that translates nicely to windows permissions. As ACL's can be made to inherit (on file/dir creation) all new files under a shared directory can have their correct ACL's set. Of course if a sub directory is created without setting ACL's (by moving from another place without ACL's) these wrong settings also inherit. So it would be very nice to be able to correctly view and set them from within Dolphin. Currently we work around this by mounting the server using smb4k so we don't need to use the kio slave. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368796] Problem with Exif-tags: ImageDescription and UserComment
https://bugs.kde.org/show_bug.cgi?id=368796 Ferry <06f13.41...@mailbox.org> changed: What|Removed |Added Version|5.8.0 |5.9.0 CC||06f13.41...@mailbox.org --- Comment #6 from Ferry <06f13.41...@mailbox.org> --- Capion input is not possible with digikam 5.9; I can tag only (German version 5.9). If I fill in caption by Picasa, it is shown in Exif-data with digikam as well. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368796] Problem with Exif-tags: ImageDescription and UserComment
https://bugs.kde.org/show_bug.cgi?id=368796 --- Comment #8 from Ferry <06f13.41...@mailbox.org> --- (In reply to hardy.public from comment #7) > (In reply to Ferry from comment #6) > > Capion input is not possible with digikam 5.9; I can tag only (German > > version 5.9). If I fill in caption by Picasa, it is shown in Exif-data with > > digikam as well. > > Strange, I see no problem in EN or DE Windows 64bit 5.9.0. Do you mean you > cannot type in the box after activating Caption? I can not find any posibility to enter captions, neither in the menues nor in the manual. In the container "Captions / Beschriftungen" I can only find stars, flags and color pads. There is no entry for captions as text. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368796] Problem with Exif-tags: ImageDescription and UserComment
https://bugs.kde.org/show_bug.cgi?id=368796 --- Comment #12 from Ferry <06f13.41...@mailbox.org> --- Created attachment 111876 --> https://bugs.kde.org/attachment.cgi?id=111876&action=edit US version -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368796] Problem with Exif-tags: ImageDescription and UserComment
https://bugs.kde.org/show_bug.cgi?id=368796 --- Comment #13 from Ferry <06f13.41...@mailbox.org> --- Created attachment 111877 --> https://bugs.kde.org/attachment.cgi?id=111877&action=edit DE version -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368796] Problem with Exif-tags: ImageDescription and UserComment
https://bugs.kde.org/show_bug.cgi?id=368796 --- Comment #14 from Ferry <06f13.41...@mailbox.org> --- (In reply to caulier.gilles from comment #9) > Really... Can you take a screenshot to see exactly where is the problem ? I found the problem: There are inproper namings in the German version. In the US version are used 'Labels' and 'Captions'. The German version uses in both cases 'Beschriftungen' which is confusing. I suggest to use the following wordings: US = 'Label'; DE = 'Markierung' or 'Kennzeichen' US = 'Captions'; DE = 'Bildunterschrift' -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 386238] New: Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=386238
Bug ID: 386238
Summary: Kmail crashes on start
Product: kmail2
Version: 5.5.3
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: ft...@telfort.nl
Target Milestone: ---
Kontact crashes on start, every time now. The problem is in Kmail probably
trying to recover a new e-mail that I was writing. The result is that I need to
turn to another e-mail program until I get this fixed.
Starting from the command line shows:
~$ kontact
[6381:6399:1027/095231.504292:ERROR:nss_util.cc(808)] After loading Root Certs,
loaded==false: NSS error code: -8018
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
sonnet.plugins.hspell: HSpellDict::HSpellDict: Init failed
sonnet.core: Missing trigrams for languages: QSet("es_HN", "fr_LU", "es_UY",
"en_GB", "fr_CA", "es_MX", "fr_BE", "es_VE", "es_CO", "de_AT", "en_AU",
"de_CH", "es_PE", "fr_CH", "es_GT", "es_PR", "sv_FI", "en_CA", "es_CL",
"es_CU", "es_DO", "es_SV", "es_CR", "de_LU", "nl_BE", "es_PY", "es_NI",
"es_EC", "fr_MC", "de_BE", "es_PA", "es_BO", "es_AR")
org.kde.pim.webengineviewer: It's not necessary to check database now
KXMLGUI file found at deprecated location
("/home/ferry/.local/share/kontact/kontactsummary_part.rc") -- please use
${KXMLGUI_INSTALL_DIR} to install this file instead.
org.kde.pim.webengineviewer: Database already initialized. It's a bug in code
if you call it twice.
"Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie
over het gebruikt van Akregator, kij...}."
"Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie
over het gebruikt van Akregator, kij...}."
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
[1:1:0100/00.807773:ERROR:broker_posix.cc(41)] Invalid node channel message
QSocketNotifier: Invalid socket 70 and type 'Read', disabling...
QSocketNotifier: Invalid socket 88 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kontact path = /usr/bin pid = 6381
KCrash: Arguments: /usr/bin/kontact
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1001/kdeinit5__0
[warn] epoll_wait: Ongeldige bestandsdescriptor
[warn] epoll_wait: Ongeldige bestandsdescriptor
.
(and this repeated 1000 times or so)
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: kontact 4:17.04.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 27 10:07:22 2017
InstallationDate: Installed on 2012-11-19 (1802 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
SourcePackage: kontact
UpgradeStatus: Upgraded to artful on 2017-10-25 (2 days ago)
Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f933d4bcb80 (LWP 22139))]
Thread 23 (Thread 0x7f92a4ff9700 (LWP 22194)):
#0 0x7f93300e9072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5567f6747c1c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5567f6747bc8,
cond=0x5567f6747bf0) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x5567f6747bf0, mutex=0x5567f6747bc8) at
pthread_cond_wait.c:655
#3 0x7f9325021e75 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4 0x7f9325022357 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5 0x7f93250230f1 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6 0x7f932501f7bb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7 0x7f93300e27fc in start_thread (arg=0x7f92a4ff9700) at
pthread_create.c:465
#8 0x7f933a5c3b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 22 (Thread 0x7f92a57fa700 (LWP 22193)):
#0 __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1 0x7f933a5d3f34 in ___fprintf_chk (fp=0x7f933a88b870
<_IO_stdfile_2_lock>, f
[kmail2] [Bug 386238] Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=386238
--- Comment #1 from Ferry ---
I just upgraded to kubuntu backport ppa:
~$ kmail -v
kmail2 5.5.3
Still kontact (and kmail) crash on each start. I think it tries to recover an
e-mail and then crashes again and again. How do I stop this?
Starting from command line now shows:
~$ kontact
[3491:3510:1031/170506.962118:ERROR:nss_util.cc(808)] After loading Root Certs,
loaded==false: NSS error code: -8018
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
sonnet.plugins.hspell: HSpellDict::HSpellDict: Init failed
sonnet.core: Missing trigrams for languages: QSet("es_VE", "es_AR", "fr_LU",
"es_BO", "es_PY", "en_AU", "es_CL", "es_NI", "fr_MC", "es_PE", "nl_BE",
"es_CO", "de_BE", "fr_CA", "fr_CH", "es_CU", "de_CH", "es_CR", "es_PR",
"fr_BE", "en_CA", "es_UY", "es_PA", "es_EC", "de_AT", "sv_FI", "es_GT",
"de_LU", "es_DO", "es_HN", "es_MX", "es_SV", "en_GB")
org.kde.pim.webengineviewer: It's not necessary to check database now
KXMLGUI file found at deprecated location
("/home/ferry/.local/share/kontact/kontactsummary_part.rc") -- please use
${KXMLGUI_INSTALL_DIR} to install this file instead.
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.webengineviewer: Database already initialized. It's a bug in code
if you call it twice.
"Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie
over het gebruikt van Akregator, kij...}."
"Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie
over het gebruikt van Akregator, kij...}."
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
[1:1:0100/00.525574:ERROR:broker_posix.cc(41)] Invalid node channel message
QSocketNotifier: Invalid socket 71 and type 'Read', disabling...
QSocketNotifier: Invalid socket 89 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kontact path = /usr/bin pid = 3491
KCrash: Arguments: /usr/bin/kontact
Segmentatiefout (geheugendump gemaakt)
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 386238] Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=386238 Ferry changed: What|Removed |Added CC||ft...@telfort.nl -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 386238] Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=386238 --- Comment #2 from Ferry --- OK I managed to work around this in the following way: - I went into ~ferry/.local/share/kmail2/autosave - removed the file there Started kmail, problem gone. May I suggest that if kmail is repeatedly trying to recover an open e-mail that it should give up on that and clear the autosave folder? Unfortunately I really deleted the file, so we can't use it here now to reproduce the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384891] Keyboard input barely works
https://bugs.kde.org/show_bug.cgi?id=384891 Ferry changed: What|Removed |Added CC||ft...@telfort.nl --- Comment #5 from Ferry --- There certain is a problem somewhere. But it's difficult to report a bug with the keyboard not working :-) In my case, after working well for a while the keyboard stops working normally in all KDE applications, with the same symptoms as reported under #1. Non-kde applications work fine (chromium yes, libo yes, kate no, kickoff no). Replugging the keyboard (usb) also does not help. I didn't find how to get ibus restarted and removing it wants to remove a lot of other packages so I didn't want to go there. I am on Kubuntu 17.10, upgraded to Kubuntu backports but that had no effect. I did manage to get the keyboard working again by going to systemsettings, systemd and rerun keyboard-setup.service (this reruns the one-shot /lib/console-setup/keyboard-setup.sh) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377505] New: Let Kate automatically reload
https://bugs.kde.org/show_bug.cgi?id=377505 Bug ID: 377505 Summary: Let Kate automatically reload Product: kate Version: 16.04 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: ft...@telfort.nl Target Milestone: --- When viewing a view that is continuously being modified by an external program (i.e. when viewing logs) Kate keeps asking if you want to reload the file. Now, either you want it to automatically reload or you don't. I wish ... that I could select to automatically reload the file (as long as it hasn't been modified by Kate itself) without any further questions. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Ferry changed: What|Removed |Added CC||k...@kn0x.org --- Comment #4 from Ferry --- *** Bug 444108 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Ferry changed: What|Removed |Added CC||ferry.t...@elsinga.info --- Comment #3 from Ferry --- I confirm this issue also affects Kontact 5.24.5 (23.08.5) With Frameworks 5.115.0, Qt 5.15.13 as found in Kubuntu 24.04 (LTS). For us this makes the wayland session impossible to use, as we routinely manually archive our e-mails to a local imap server with 1000's of (sub)folders. This scrolling of the folders list happens in about 50% of the attempts, no clue how to influence this. The only workaround we found is not use drag/drop but cut/paste. But ctrl-alt-x, ctrl-shift-v is so inconvenient we prefer to just fall back to X. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 444108] kmail dragging mail to sidebar starts scrolling fast in wayland sessions
https://bugs.kde.org/show_bug.cgi?id=444108 Ferry changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ferry.t...@elsinga.info --- Comment #3 from Ferry --- *** This bug has been marked as a duplicate of bug 440874 *** -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 448985] New: In Digital Clock 3.0 - Custom date format shows incorrect month - M01 instead of Jan
https://bugs.kde.org/show_bug.cgi?id=448985 Bug ID: 448985 Summary: In Digital Clock 3.0 - Custom date format shows incorrect month - M01 instead of Jan Product: Active Window Control Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: bmfe...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** I've set a custom format in the widget - ' dd-MMM'. It should show 'Sat 22-Jan' but shows 'Sat 22-M01' instead. *** STEPS TO REPRODUCE 1. Add a widget 2. Configure date format ' dd-MMM' 3. Apply and observe the date shown OBSERVED RESULT See summary EXPECTED RESULT See summary SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.23.5-1.1 (available in About System) KDE Plasma Version: 5.23.5-1.1 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448985] In Digital Clock 3.0 - Custom date format shows incorrect month - M01 instead of Jan
https://bugs.kde.org/show_bug.cgi?id=448985 --- Comment #3 from Bruce Ferry --- Created attachment 145810 --> https://bugs.kde.org/attachment.cgi?id=145810&action=edit Screenshot showing the config and what I see Should have attached this before. I'm in the eastern US time zone if that matters. I do remember that this used to work correctly but I'm not sure when it changed. I don't normally have the widget installed but I see exactly the same thing on the task bar clock. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448985] In Digital Clock 3.0 - Custom date format shows incorrect month - M01 instead of Jan
https://bugs.kde.org/show_bug.cgi?id=448985 Bruce Ferry changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #8 from Bruce Ferry --- Problem solved. Locale showed 'LC_TIME="lv_US.UTF-8"'. Changing it to LC_TIME="en_US.UTF-8" resolved it. I have no idea how this might have gotten changed. Thanks to all who pitched in their two cents -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 326803] Kontact keep downloading message bodies
https://bugs.kde.org/show_bug.cgi?id=326803 --- Comment #2 from Ferry --- Can be closed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344319] Suspend desktop effects for fullscreen windows does not work in Plasma5 (Intel Haswell)
https://bugs.kde.org/show_bug.cgi?id=344319 Ferry changed: What|Removed |Added CC||ft...@telfort.nl --- Comment #25 from Ferry --- To my best recollection, this did work in kde4 on intel. And despite #22, there is a use case where it is important: I'm using a NUC DE3815 with Atom E3815 as HTPC. Even though it is 1.5GHz single core, it will play back video in 1080p when the player is bare bones, so MPV works fine, but VLC tries much tricks in the CPU. But only when using vaapi for decode and opengl for rendering. And of course by eliminating other unnecessary load as MPV even when offloading to the GPU loads the CPU over 60%. With desktop effects disabled VLC will play 720p. So , why use this weak NUC for this task? It consumes ~5W, so it can stay always on at little cost. It doesn't make sense to need to implement a rule for each app that runs in full screen to disable compositing. Or can there be one rule that this for all full screen apps? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Ferry changed: What|Removed |Added CC||ft...@telfort.nl --- Comment #33 from Ferry --- I have the same problem as Gene in comment #24: After updating Kubuntu Backports today (to KDE 5.5.3) I have: - my normal screen on the left - black screen on the right - cannot right click on the right screen - I was able to move a task bar to the right screen, coming from the left - I always had the task bar only show the applications on it's own screen, this doesn't seem to work any more. I looks like the applications don't know on which screen they are. Turning off this filter on both the left and right task bar shows all applications on both bars. - on the right screen I cannot add any other widgets (cannot right click, also there is not the little icon on the top left, also can not create on the left screen and then move to the right as it blocks at the screen edge) This is a regression of course. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #34 from Ferry --- I tried the script above and with kscreen2 disabled. That didn't work well as I have 2 1920x1200 monitors and both monitors showed the same thing, except vertically displayed on one. After I enabled kscreen2 (without logging in/out) magically all problems mentioned in #33 disappeared. Only one new thing: - click on the start icon (launcher) on the right monitor, the window unfolds on the left screen. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 353987] Incomplete CardDav sync with ownCloud
https://bugs.kde.org/show_bug.cgi?id=353987 --- Comment #5 from Ferry --- In my case updating owncloud to a bit higher point release solved the issue. -- You are receiving this mail because: You are watching all bug changes.
