[okular] [Bug 455650] Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 --- Comment #15 from MichaelOF --- @andreas.naum...@kdemail.net: THANKS for helping! @aa...@kde.org: Didn't want to confuse you :) Colorized/marked screenshots added. Regarding flatpal question: Both Andreas and I used the same flatpak version. But as shown in screenshot https://bugs.kde.org/attachment.cgi?id=149979, flatpak's Okular doesn't even work on my machine. I guess maybe because of Wayland, no idea, as no error msg. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455650] Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 MichaelOF changed: What|Removed |Added Attachment #149976|0 |1 is obsolete|| Attachment #149977|0 |1 is obsolete|| Attachment #149978|0 |1 is obsolete|| --- Comment #14 from MichaelOF --- Created attachment 150096 --> https://bugs.kde.org/attachment.cgi?id=150096&action=edit Screenshots as requested, commented inline -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455650] Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 --- Comment #10 from MichaelOF --- Created attachment 149979 --> https://bugs.kde.org/attachment.cgi?id=149979&action=edit Okular via flatpak Tried with flatpak. No base PDF doc anymore visible, only form data left. Maybe because of Wayland? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455650] Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 --- Comment #9 from MichaelOF --- (In reply to Albert Astals Cid from comment #5) > You're probably using some mega old poppler $ zypper se -iv poppler Repository-Daten werden geladen... Installierte Pakete werden gelesen... S | Name | Type | Version | Arch | Repository --++---+--++- i | libpoppler-cpp0| Paket | 0.79.0-3.5.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 name: libpoppler-cpp0 i | libpoppler-glib8 | Paket | 0.79.0-3.5.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 name: libpoppler-glib8 i | libpoppler-glib8-32bit | Paket | 0.79.0-3.5.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 name: libpoppler-glib8-32bit i | libpoppler-qt5-1 | Paket | 0.79.0-3.5.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 name: libpoppler-qt5-1 i | libpoppler89 | Paket | 0.79.0-3.5.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 name: libpoppler89 i | libpoppler89-32bit | Paket | 0.79.0-3.5.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 name: libpoppler89-32bit i | poppler-data | Paket | 0.4.9-bp153.1.14 | noarch | openSUSE OSS name: poppler-data i | poppler-tools | Paket | 0.79.0-3.5.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 name: poppler-tools Will try flatpak version next -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455650] Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 --- Comment #8 from MichaelOF --- Created attachment 149978 --> https://bugs.kde.org/attachment.cgi?id=149978&action=edit SourcePdfFWithFormData_CUPS-PDF-Printed_from_Xreader_GARBAGED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455650] Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 --- Comment #7 from MichaelOF --- Created attachment 149977 --> https://bugs.kde.org/attachment.cgi?id=149977&action=edit SourcePdfFWithFormData_CUPS-PDF-Printed_from_Okular_GARBAGED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455650] Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 --- Comment #6 from MichaelOF --- Created attachment 149976 --> https://bugs.kde.org/attachment.cgi?id=149976&action=edit SourcePdfFWithFormData -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455650] New: Garbage Printing for PDF with form data
https://bugs.kde.org/show_bug.cgi?id=455650 Bug ID: 455650 Summary: Garbage Printing for PDF with form data Product: okular Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: michae...@rocketmail.com Target Milestone: --- Okular 20.04.2 (current OpenSUSE leap 15.3 rpm version) STEPS TO REPRODUCE 1. Have a PDF with form data entered and saved 2. print this PDF with form date OBSERVED RESULT - pdf is shown in Okular correctly, with form data or without - base pdf, without form data, is printed fine - form data on top garbaged (form fields are printed stacked, unreadable = wrong positions) - printed from Okular to 2 different printers (old HP Laserjet 2200d, new Xerox WorkCentre), both different print drivers: same garbaged output - printed from same Linux/KDE Plasma box via CHROMIUM's internal PDF viewer: prints FINE - printed same PDF with same data on same HP and Xerox printers, but with Adobe Reader on WIN10 laptop: prints FINE. --> IMHO bug in Okular EXPECTED RESULT should print correctly, WYSIWYG ;) SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.3 (available in About System) KDE Plasma Version: Plasma 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION This is the downloadable form: https://www.energienetze-offenbach.de/fileadmin/user_upload_eno/Dokumente/Service/220302_ENO_Ladeinfastruktur_02.03.2022.pdf In chapter 3 there are several rows like this: "Davon Ladepunkte: , je kW Gesamtleistung: kW", these "numvalues" form data are garbaged when printed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433188] Some desktop icons disappear on mouse hover, and only reappear on next hover
https://bugs.kde.org/show_bug.cgi?id=433188 --- Comment #12 from MichaelOF --- FYI I've been the reporter of the duplicate bug 433528 (comment 3). It's a Zotac zbox nano with an Intel Celeron N2930, not an i5 as from the reporter of this bug. KDE-InfoCenter says about OpenGL "Atom Processor Z36xxx/Z37xxx Series Graphics&Display", kernel module i915. Renderer Mesa DRI Intel(R) Bay Trail, 3.0 Mesa 19.3.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433188] Some desktop icons disappear on mouse hover, and only reappear on next hover
https://bugs.kde.org/show_bug.cgi?id=433188 --- Comment #10 from MichaelOF --- Tried a reboot. getting a system tray/bar info icon "software renderer is used" (Maybe?) good news. icons are staying STABLE with this setting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433188] Some desktop icons disappear on mouse hover, and only reappear on next hover
https://bugs.kde.org/show_bug.cgi?id=433188 --- Comment #9 from MichaelOF --- Never used kcmshell5 before, so unsure: - adviced "kcmshell5 qtquick settings" runs into error "module qtquick not found" - "kcmshell5 --list" shows "qtquicksettings" as allowed option, tried instead. - maybe not relevant: 'Couldn't load plugin "kcms/kcm_qtquicksettings" : "The shared library was not found." -- falling back to old-style loading from desktop file' - Got "Plasma Renderer - System Settings Module". - Set "Rendering Backend" to "Software" --> No change, error still happens, icons dissappear. Will try a reboot also, if maybe needed to aplly "rendering backend" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433188] Some desktop icons disappear on mouse hover, and only reappear on next hover
https://bugs.kde.org/show_bug.cgi?id=433188 --- Comment #7 from MichaelOF --- Wow! Found a "workaround": As long as anything is running in a plasmoid, which has to be "pinned" (to stay open), e.g. "software updates" checking for updates, all desktop icons stay stable. As soon as e.g. updates check is finished, or plasmoid unpinned, icons are disappearing again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433188] Some desktop icons disappear on mouse hover, and only reappear on next hover
https://bugs.kde.org/show_bug.cgi?id=433188 --- Comment #6 from MichaelOF --- (In reply to Marco Martin from comment #4) > it's a thing that screams graphics driver bug is the graphics driver used different for Wayland or "normal X"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433188] Some desktop icons disappear on mouse hover, and only reappear on next hover
https://bugs.kde.org/show_bug.cgi?id=433188 --- Comment #5 from MichaelOF --- FYI happens only when in "normal" Plasma mode. Stable in "Plasma (Wayland)" and "Plasma (Full Wayland)". Unfortunately the Wayland modes itself are freezing very frequently :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433528] New: Desktop icons are "disappearing" when mouse over
https://bugs.kde.org/show_bug.cgi?id=433528 Bug ID: 433528 Summary: Desktop icons are "disappearing" when mouse over Product: plasmashell Version: 5.18.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: michae...@rocketmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY - worked FINE in OpenSuse Leap 15.1 / Plasma 5.12.8, so newly introduced in Leap 15.2 / Plasma 5.18.6 STEPS TO REPRODUCE 1. Move mouse over icons, they "dissappear" 2. move mouse somewhere else, they appear again. 3. click on invisible/disappeared icon, it will re-appear. 4. click 2nd time to execute/open OBSERVED RESULT Thought at first that there are no rules, maybe a graphics card issue (Intel HD graphics). BUT depends on file type: - .desktop, .sh mostly disappear. not all, no further "rule" known. - .pdf and all LibreOffice files stay stable Thought that maybe access rights are triggering issue: no, tried. Also e.g. .png files are mostly dissappearing, so not only executable files. EXPECTED RESULT icons should stable and visible SOFTWARE/OS VERSIONS Linux/KDE Plasma: openuSUSE Leap 15.2 / Plasma 5.18.6 KDE Plasma Version: Plasma 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION openSUSE bug also exists: https://bugzilla.opensuse.org/show_bug.cgi?id=1175797 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428928] New: Android App: Clipboard not synced for Android 10
https://bugs.kde.org/show_bug.cgi?id=428928 Bug ID: 428928 Summary: Android App: Clipboard not synced for Android 10 Product: kdeconnect Version: unspecified Platform: Other OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: michae...@rocketmail.com Target Milestone: --- SUMMARY I have 2 Android devices, old Android 6 and new Android 10. Same KDE Connect App on both, 1.15.1 F-Droid version. Connected to same KDE connect on my OpenSuse Leap 15.2 box, KDE Plasma 5.18.5, OpenSuse pkg 20.04.2-lp152.2.3.1 - NO issue with old Android 6 device, clipboard is synced bidirectional - clipboard is NOT synced between Android 10 and Linux. Not sure if this might be related to some changes that seems to be made to clipboard in general, on Android 10 (or maybe earlier, don't know). Several clipboard related apps have issues on Android 10, like in my case "Clip Stack" clipboard history mgmt (https://f-droid.org/en/packages/com.catchingnow.tinyclipboardmanager/), stopped working on 10. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425557] Plasma freezes when Compositor set to use OpenGL, both 2.1 or 3.0. No freeze with Xrender
https://bugs.kde.org/show_bug.cgi?id=425557 --- Comment #2 from MichaelOF --- yes, that's my "rescue path" to systemctl isolate multi-user.target and systemctl isolate graphical.target to get my machine back to a working state, avoiding hard reboots. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425557] New: Plasma freezes when Compositor set to use OpenGL, both 2.1 or 3.0. No freeze with Xrender
https://bugs.kde.org/show_bug.cgi?id=425557 Bug ID: 425557 Summary: Plasma freezes when Compositor set to use OpenGL, both 2.1 or 3.0. No freeze with Xrender Product: kwin Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: michae...@rocketmail.com Target Milestone: --- Created attachment 131017 --> https://bugs.kde.org/attachment.cgi?id=131017&action=edit KDE Info Center OpenGL When Compositor set to set to use OpenGL, both 2.1 or 3.0, GUI "freezes" after a while. Especially when working with Firefox. Freeze means mouse moves are still possible, but no clicks etc. possible/accepted anymore. No window changes, like refreshed graphs etc. No / never any freezes with Xrender. STEPS TO REPRODUCE 1. open plasma settings, all settings, display and monitor, Compositor 2. set output module to OpenGL, 2.1 or 3.0. 3. work some time, 1-15 minutes. OBSERVED RESULT Freeze, as described. EXPECTED RESULT NO freeze :-) SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.2 (available in About System) KDE Plasma Version: Plasma 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION Hardware is ZBOX nano CI320 with an Intel Celeron N2930 and Intel HD Graphics. KDE Info Center OpenGL Info appended as screenshot -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 395284] Clipboard entries added by xclip are not accessible by ctrl-v
https://bugs.kde.org/show_bug.cgi?id=395284 MichaelOF changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from MichaelOF --- Asked today also again in #kde. Got a hint from user JanKusanagi: xclip has an option "-selection", and with parameter "clipboard" (in my case "xlip -r -selection clipboard" EVERYTHING works like a charme. So not a bug, not even an issue with kclipboard, solely xclip. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 395284] Clipboard entries added by xclip are not accessible by ctrl-v
https://bugs.kde.org/show_bug.cgi?id=395284 --- Comment #2 from MichaelOF --- Opened this small but painful bug months ago, unfortunately not a single comment. Is kclipboard abandoned? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396004] Duplex settings are ignored for HP Laserjet PCL based printer driver
https://bugs.kde.org/show_bug.cgi?id=396004 --- Comment #1 from MichaelOF --- Issue can be closed. Happens only with (old) driver "HP LaserJet 2200 Series, hpcups 3.15.2", seems to be kept when upgrading from older OpenSuse versions. OpenSuse 15.0 now has "HP LaserJet 2200 pcl3, hpcups 3.17.9" available, WORKS FINE with this driver, also from Okular :-) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396004] New: Duplex settings are ignored for HP Laserjet PCL based printer driver
https://bugs.kde.org/show_bug.cgi?id=396004 Bug ID: 396004 Summary: Duplex settings are ignored for HP Laserjet PCL based printer driver Product: okular Version: 1.3.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: michae...@rocketmail.com Target Milestone: --- When using Okular 1.3.3 on OpenSuse 15.0 with the Postscript driver, printing takes unbelievable long (20+ min/page sometimes, sometimes never stops spooling) but mostly works. If printer produces any output, duplex-ing with Okular works fine. When using Okular 1.3.3 on OpenSuse 15.0 with the PCL based driver, printing itself goes pretty fast, but DUPLEX settings are ignored when using Okular. Same printer driver is doing duplex-jobs fine when e.g. using xreader instead of Okular. Or any other software like editors, LibreOffice, Firefox etc., so I'm convinced that this must be an Okular bug. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 395284] Clipboard entries added by xclip are not accessible by ctrl-v
https://bugs.kde.org/show_bug.cgi?id=395284 --- Comment #1 from MichaelOF --- Got a hint in #kde that it might work with klipper's setting "sync clipboard and selection" set to true. True, works when set. But I don't like this "selection" setting, as it "destroys" my clipboard everytime, when just "selecting" something, unusable setting for me. So IMHO this is still a bug, hopefully worth fixing. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 395284] New: Clipboard entries added by xclip are not accessible by ctrl-v
https://bugs.kde.org/show_bug.cgi?id=395284 Bug ID: 395284 Summary: Clipboard entries added by xclip are not accessible by ctrl-v Product: klipper Version: 5.12.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: michae...@rocketmail.com Target Milestone: --- Plasma 5.12.5 on OpenSuse 15.0 When I copy an entry via xclip on bash to X clipboard, e.g. echo abc | xclip -r "abc" is shown as latest entry in clipboard plasmoid, as expected. But whyever, this entry is NOT accessible by ctrl-v, as usual for clipboard entries. If older "manually" added (ctrl-c) entries in clipboard history exists, the latest entry of these is pasted, instead. 100% reproducible. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 394814] New: ssh-add in sourced .profile leads to immediate logout, after entering the passphrase, after login to Plasma
https://bugs.kde.org/show_bug.cgi?id=394814 Bug ID: 394814 Summary: ssh-add in sourced .profile leads to immediate logout, after entering the passphrase, after login to Plasma Product: ksmserver Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: michae...@rocketmail.com Target Milestone: --- - not sure if this is the right kde "product" - not sure if my issue may be related to https://bugs.kde.org/show_bug.cgi?id=81067, esp. the later posts For years now I have a ~/.profile with a last line: . ~/bin/start_ssh-agent and ~/bin/start_ssh-agent containing just 2 line: eval `ssh-agent -s` ssh-add Worked fine for years now, asking me to enter the passphrase for my ssh keys, once, when logging into plasma, and never again for all my konsole sessions. Exactly what I want, cool! BUT since the last OpenSuse update, which updates KDE/Plasma to 5.12.5, I still am asked for the passphrase, but after entering the (correct) passphrase, I'm immediately getting logged out. Of course NOT what I want. Anything relevant differences between 5.8.7 (last working) and 5.12.5? -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding for column "address" (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 MichaelOF changed: What|Removed |Added Summary|DAV-Groupware resource for |DAV-Groupware resource for |OwnCloud uses incorrect |OwnCloud uses incorrect |encoding (not UTF-8)|encoding for column ||"address" (not UTF-8) -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 --- Comment #10 from MichaelOF --- last remark for now: tested with another field, "notice" (Shown as "Anmerkung" in German kaddressbook): Everything FINE, umlauts shown correctly in kaddressbook for "notice", after changing on Android. Maybe this bug might be isolated to field "address"? -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 --- Comment #9 from MichaelOF --- not sure if this is of any help, but if I try kaddressbook's "print preview" functionality, the "corrupted" address is shown correctly "again" -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 --- Comment #7 from MichaelOF --- Hi Allen, just "dug" a little bit more inside and found out that this bug is somewhat "weird". Steps I tried: 1. created a contact directly in OwnCloud, as OC is single source of truth for all my contacts. 2. waited until kaddressbook got this new contact imported (manual sync / F5 somehow does not work for me, so set interval to "every 2 minutes"). Intermediate RESULT: Umlauts in kaddressbook are correct (Screenhot: https://bugs.kde.org/attachment.cgi?id=107548) 3. Synched this new contact via DAVdroid. Umlauts are correct on Android. 4. Changed in AOSP's (native Android) calendar app. Changed in "address" old value "Mühlheim, Hauptstraße" to "Mählheim, Hauptstraße 5" 5. Synched back to OwnCloud via DAVdroid. RESULT: - ALL Umlauts are correct on OwnCloud, as to be seen in Firefox (52.3.0, OpenSuse 42.3) - ALL Umlauts are correct in e.g. iPad, Thunderbird's addressbook (52.3.0, with SOGo connector) - NAME is correct in kaddressbook, although containing umlauts - ADDRESS is NOT shown correctly in kaddressbook. (Screenshot: https://bugs.kde.org/attachment.cgi?id=107550) FYI I've also appended OwnCloud's database content, table OC_CARDS, column CARDDATA, datatype BLOB, as "binary attachements" here. Step 1, kaddressbook CORRECT: https://bugs.kde.org/attachment.cgi?id=107549 Step 5, kaddressbook INCORRECT: https://bugs.kde.org/attachment.cgi?id=107551 I've tested these BLOB-content-file with my programmer's Editor jEdit, both are UTF-8 and MS WIN CR+LF, all umlauts are correct in both file. Tested additionaly with kdiff3, which also shows both files, set to UTF-8, correct -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 --- Comment #5 from MichaelOF --- Created attachment 107551 --> https://bugs.kde.org/attachment.cgi?id=107551&action=edit BLOB content from OwnCloud (OC_CARDS.CARDDATA), exported from phpMyAdmin with Firefox 52.3.0 (Umlauts INCORRECT in kaddressbook) -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 --- Comment #4 from MichaelOF --- Created attachment 107550 --> https://bugs.kde.org/attachment.cgi?id=107550&action=edit Screenshot from kaddressbook: Imported Contact, changed in Android: Umlauts correct in Name, INCORRECT in Address -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 --- Comment #3 from MichaelOF --- Created attachment 107549 --> https://bugs.kde.org/attachment.cgi?id=107549&action=edit BLOB content from OwnCloud (OC_CARDS.CARDDATA), exported from phpMyAdmin with Firefox 52.3.0 (Umlauts CORRECT in kaddressbook) -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 --- Comment #2 from MichaelOF --- Created attachment 107548 --> https://bugs.kde.org/attachment.cgi?id=107548&action=edit Screenshot from kaddressbook: Imported Contact, created in Owncloud: Umlauts CORRECT -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] New: DAV-Groupware resource for owncloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 Bug ID: 383934 Summary: DAV-Groupware resource for owncloud uses incorrect encoding (not UTF-8) Product: kaddressbook Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: michae...@rocketmail.com CC: to...@kde.org Target Milestone: --- Using kAddressBook with a DAV-Groupware resource to sync with cardDAV contacts store in my OwnCloud instance, on my private VPS. Both VPS and kAddressBook "client" are OpenSuse 42.3, Plasma 5.8.7. EVERYTHING set to UTF-8, including Apache, MariaDB/MySQL etc., both on VPS and local KDE client. Wrong encoding, non-UTF-8, in kaddressbook. E.g. German Umlaut "ü" is shown as "ü" No issue when syncing with - Android Contacts (using DAVdroid) - iPad Contacts(even with bloody old iOS) - Thunderbird AddressBook (with Inverse SOGo connector) -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 MichaelOF changed: What|Removed |Added Summary|DAV-Groupware resource for |DAV-Groupware resource for |owncloud uses incorrect |OwnCloud uses incorrect |encoding (not UTF-8)|encoding (not UTF-8) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364441] New: Option "Symbols/Sort by/Not sorted" does not work for Desktop folder
https://bugs.kde.org/show_bug.cgi?id=364441 Bug ID: 364441 Summary: Option "Symbols/Sort by/Not sorted" does not work for Desktop folder Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Dashboard Assignee: notm...@gmail.com Reporter: michae...@rocketmail.com CC: bhus...@gmail.com When sort option is set to "no sort" / unsorted for the Desktop folder widget (not sure if "widget" is the correct translation from German "Miniprogramm") , which shows the content of ~/Desktop or ~/Schreibtisch in German, it's not possible to rearrange icons in the Desktop folder. New icons are placed at the end, so at least for adding something "not sorted" is true. Reproducible: Always Steps to Reproduce: 1. Set Desktop folder widget's symbols sort option to "not sorted" 2. drag and (try to) drop a symbol to a different position Actual Results: nothing happens after dropping, folder stays unchanged Expected Results: Symbol should be placed on the "drop" location Maybe a misunderstanding of to-be-expected functionality, please advice if "works as designed". Change Severity to "wishlist" in that case :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364440] New: no focus to/ no mouse click possible on desktop after ctrl-F12
https://bugs.kde.org/show_bug.cgi?id=364440 Bug ID: 364440 Summary: no focus to/ no mouse click possible on desktop after ctrl-F12 Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Dashboard Assignee: notm...@gmail.com Reporter: michae...@rocketmail.com CC: bhus...@gmail.com Pretty Often after clicking ctrl+F12 to see the Desktop with the intention to click on an icon in the "Desktop" folder (~/Desktop, or ~/Schreibtisch in German) the mouse doesn't get the "focus" for the desktop. Normal behaviour: - click on desktop background / wallpaper: Desktop stays open - "hovering" over any icons in the Desktop folder will show a frame for the icon under the mouse pointer. "Buggy" behaviour: "hovering" over any icons in the Desktop folder will NOT show a frame for the icon under the mouse pointer. - click on an icon in Desktop folder just restores the original open windows. - open/run action for icon will not be performed - click on an icon Reproducible: Sometimes Steps to Reproduce: up to now I'm not able to see the "trigger" for the buggy behavior, so unfortunately currently not reproducible Trying ctrl-F12 and click twice or three times will usually lead to a "working" ctrl-F12 again (for a while :-)) So not a critical bug. -- You are receiving this mail because: You are watching all bug changes.
