[opensuse-kde] Tumbleweed 20160909 & kmail (from oss)
Since 16.08 enter TW I'm getting more an more trouble with kmail. (Mostly linked I guess to the new qwebview engine) Today after upgrading the whole TW to its last state I've seen kmail unable to display correctly messages in its window see http://susepaste.org/31174158 My screen is setup to use 168dpi on the external monitor, In systemsettings the fonts are forced to 168dpi and the display scale factor is setup to 1.4 As the display is completely borked, I'm not able to clic on link etc. It seems that 16.08.1 is coming, has anybody news about changes related to that ? Strangely two days ago, before the new gcc6 and libc it was working, could it be related ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data domenica 11 settembre 2016 15:51:08 CEST, Bruno Friedmann ha scritto:
Since 16.08 enter TW I'm getting more an more trouble with kmail. (Mostly linked I guess to the new qwebview engine)
There are some issues with QWebEngine in Qt 5.6, some are better handled in 5.7 (but not without regressions...), but the idea is to wait for Leap 42.2 to be out before updating Qt to 5.7.
to display correctly messages in its window see http://susepaste.org/31174158
What happens if you try to change header theme? -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B
On lundi, 12 septembre 2016 07.34:34 h CEST Luca Beltrame wrote:
In data domenica 11 settembre 2016 15:51:08 CEST, Bruno Friedmann ha scritto:
Since 16.08 enter TW I'm getting more an more trouble with kmail. (Mostly linked I guess to the new qwebview engine)
Thanks for the news Luca,
There are some issues with QWebEngine in Qt 5.6, some are better handled in 5.7 (but not without regressions...), but the idea is to wait for Leap 42.2 to be out before updating Qt to 5.7.
Wouah ... does that mean we will keep a broken kmail during that time (end of november ?) That sound harsh for those who would like to continue to use it. I mean not being able to read correctly the content, not being able to click on link inside message, plus pain in ass for printing is really really annoying. I would have love to stick to pure oss (and kextra for TW) to have a clear vision of what we offer in terms of end user experience. But then it seems I will have to move again to another repository, certainly unstable to qt57? Crossing my fingers about getting something else broken ;-) ? Don't take this as personal or offensive, I'm just a bit worried about getting such damageable changes coming from upstream when they are not ready to use. This added to akonadi messages log_akonadicore: Creating/updating items from the akonadi database failed: "Unknown error." log_akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting" Make PIM stack less and less attractive unfortunately.
to display correctly messages in its window see http://susepaste.org/31174158
What happens if you try to change header theme?
Nothing the header and disposal change, but not the unusable view box. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data lunedì 12 settembre 2016 09:46:01 CEST, Bruno Friedmann ha scritto:
I mean not being able to read correctly the content, not being able to click on link inside message, plus pain in ass for printing is really really annoying.
Printing is partially fixed in Qt 5.7, but there's no print preview support until 5.8 (KMail works around it by opening it in the browser). Yes, Qt dropped the ball *hard* when adding QWebEngine.
log_akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting"
This indicates an inconsistency between your local items and what the server says: although this should occur much less than before, there are some corner cases where it occurs. It doesn't say where unfortunately. The debug string has changed in 16.12 to show where (which account and folder) this occurs. The only solution to this is to clear the cache of the offending folder (I hope it's not your INBOX). -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B
On lundi, 12 septembre 2016 09.56:27 h CEST Luca Beltrame wrote:
In data lunedì 12 settembre 2016 09:46:01 CEST, Bruno Friedmann ha scritto:
I mean not being able to read correctly the content, not being able to click on link inside message, plus pain in ass for printing is really really annoying.
Printing is partially fixed in Qt 5.7, but there's no print preview support until 5.8 (KMail works around it by opening it in the browser). Yes, Qt dropped the ball *hard* when adding QWebEngine.
Pfuu, ok will offer moral support and beer to Laurent when I will be in Toulouse for CDL in November.
log_akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting"
This indicates an inconsistency between your local items and what the server says: although this should occur much less than before, there are some corner cases where it occurs. It doesn't say where unfortunately. The debug string has changed in 16.12 to show where (which account and folder) this occurs.
Let see what I can activate debug log for akonadi.
The only solution to this is to clear the cache of the offending folder (I hope it's not your INBOX). I've no file local cache, everything is stored in db. But this start to happen when xapian move to 3.0. At that time I simply destroy the local/share/akonadi/search_db folder and let akonadi rebuild it.
I never see the akonadi crash like other have that move back to xapian2. Doesn't Akonadictl fsck and vacuum should cleanup the structure of cache and db alone ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Montag, 12. September 2016 09:46:01 CEST Bruno Friedmann wrote:
That sound harsh for those who would like to continue to use it. I mean not being able to read correctly the content, not being able to click on link inside message, plus pain in ass for printing is really really annoying.
Is QtWebEngine still optional for KMail? QtWebKit is being developed again, you know… http://qtwebkit.blogspot.com/2016/08/qtwebkit-im-back.html -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data lunedì 12 settembre 2016 16:17:24 CEST, Markus Slopianka ha scritto:
Is QtWebEngine still optional for KMail? QtWebKit is being developed again, you know? http://qtwebkit.blogspot.com/2016/08/qtwebkit-im-back.html
No, it's a hard dependency from 16.08. Qwebkit is still used in a couple of places, but it's being removed from there. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B
On lundi, 12 septembre 2016 16.22:36 h CEST Luca Beltrame wrote:
In data lunedì 12 settembre 2016 16:17:24 CEST, Markus Slopianka ha scritto:
Is QtWebEngine still optional for KMail? QtWebKit is being developed again, you know? http://qtwebkit.blogspot.com/2016/08/qtwebkit-im-back.html
No, it's a hard dependency from 16.08. Qwebkit is still used in a couple of places, but it's being removed from there.
My main concern, is that first message is almost unreadable, and all link inside the display is not working due to misplaced element. so I can't anymore show html message (disabled by default here), nor copy and paste the part I'm interested without using edit message print to browser is not displaying the html part (sometimes needed for having a nice invoice printed) and when it's text I have to correct the encoding of the preview (initially iso-8859-1) when message is utf-8 plain/text. I'm now waiting 16.08.1, a take a big stock of calm down pills :-) I'm just confused, when I was in May using Unstable and qtwebengine was coming apart the print part, I've not seen those kind of troubles. And I just dicover that html mode ritch text is now on .... -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On mardi, 13 septembre 2016 11.01:42 h CEST Bruno Friedmann wrote:
On lundi, 12 septembre 2016 16.22:36 h CEST Luca Beltrame wrote:
In data lunedì 12 settembre 2016 16:17:24 CEST, Markus Slopianka ha scritto:
Is QtWebEngine still optional for KMail? QtWebKit is being developed again, you know? http://qtwebkit.blogspot.com/2016/08/qtwebkit-im-back.html
No, it's a hard dependency from 16.08. Qwebkit is still used in a couple of places, but it's being removed from there.
My main concern, is that first message is almost unreadable, and all link inside the display is not working due to misplaced element.
so I can't anymore show html message (disabled by default here), nor copy and paste the part I'm interested without using edit message
print to browser is not displaying the html part (sometimes needed for having a nice invoice printed) and when it's text I have to correct the encoding of the preview (initially iso-8859-1) when message is utf-8 plain/text.
I'm now waiting 16.08.1, a take a big stock of calm down pills :-) I'm just confused, when I was in May using Unstable and qtwebengine was coming apart the print part, I've not seen those kind of troubles.
And I just dicover that html mode ritch text is now on ....
I just create a bug report from kmail2 https://bugs.kde.org/show_bug.cgi?id=368843 seems the fix is quite light (but I'm not a C++ dev :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am 15.09.2016 um 13:56 schrieb Bruno Friedmann:
On mardi, 13 septembre 2016 11.01:42 h CEST Bruno Friedmann wrote:
On lundi, 12 septembre 2016 16.22:36 h CEST Luca Beltrame wrote:
Is QtWebEngine still optional for KMail? QtWebKit is being developed again, you know? http://qtwebkit.blogspot.com/2016/08/qtwebkit-im-back.html No, it's a hard dependency from 16.08. Qwebkit is still used in a couple of
In data lunedì 12 settembre 2016 16:17:24 CEST, Markus Slopianka ha scritto: places, but it's being removed from there. My main concern, is that first message is almost unreadable, and all link inside the display is not working due to misplaced element.
so I can't anymore show html message (disabled by default here), nor copy and paste the part I'm interested without using edit message
print to browser is not displaying the html part (sometimes needed for having a nice invoice printed) and when it's text I have to correct the encoding of the preview (initially iso-8859-1) when message is utf-8 plain/text.
I'm now waiting 16.08.1, a take a big stock of calm down pills :-) I'm just confused, when I was in May using Unstable and qtwebengine was coming apart the print part, I've not seen those kind of troubles.
And I just dicover that html mode ritch text is now on .... I just create a bug report from kmail2 https://bugs.kde.org/show_bug.cgi?id=368843
seems the fix is quite light (but I'm not a C++ dev :-) This may work. But has the potential to to break some other high dpi workarounds made on other places.
But I am bitten by this problem, too. So I will make a test in the evening. Herbert -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 15. September 2016, 13:56:13 schrieb Bruno Friedmann:
seems the fix is quite light (but I'm not a C++ dev :-)
It's probably not as straight-forward as you may think though, because kmail actually does enable HiDPI scaling already (i.e. call QCoreApplication::setAttribute(Qt::EnableHighDPIScaling) ). See the kmail 16.08.0 sources, main.cpp line#116: https://quickgit.kde.org/?p=kdepim.git&a=blob&h=083a763214152e96b808fda3e4c0087011ee2a19&hb=69c5ac205e405f2304ba9abe08427feec4624a37&f=kmail%2Fsrc%2Fmain.cpp The problem may be that it does so *after* creating the application while the docs say "This attribute must be set before Q(Gui)Application is constructed". I don't have a HiDPI screen to test it though. Care to try a patched kmail5 package? http://download.opensuse.org/repositories/home:/wolfi323:/test/openSUSE_Tumb... Btw, if this is indeed the problem, it affects every single KDEPIM application. Have a look at the patch, it consists of over 300 lines: https://build.opensuse.org/package/view_file/home:wolfi323:test/kdepim/fix-h... So much for "seems the fix is quite light"... ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On jeudi, 15 septembre 2016 17.14:22 h CEST Wolfgang Bauer wrote:
Am Donnerstag, 15. September 2016, 13:56:13 schrieb Bruno Friedmann:
seems the fix is quite light (but I'm not a C++ dev :-)
It's probably not as straight-forward as you may think though, because kmail actually does enable HiDPI scaling already (i.e. call QCoreApplication::setAttribute(Qt::EnableHighDPIScaling) ).
See the kmail 16.08.0 sources, main.cpp line#116: https://quickgit.kde.org/?p=kdepim.git&a=blob&h=083a763214152e96b808fda3e4c0 087011ee2a19&hb=69c5ac205e405f2304ba9abe08427feec4624a37&f=kmail%2Fsrc%2Fmai n.cpp
The problem may be that it does so *after* creating the application while the docs say "This attribute must be set before Q(Gui)Application is constructed".
I don't have a HiDPI screen to test it though. Care to try a patched kmail5 package? http://download.opensuse.org/repositories/home:/wolfi323:/test/openSUSE_Tumb leweed/
Would like soo much :-) but I encounter a missing package 6 Problems: Problem: nothing provides libkdepim = 16.08.1 needed by kaddressbook5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kalarm5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kmail5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by knotes5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kontact5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by korganizer5-16.08.1-88.1.x86_64 also tw has still only have the 16.08.0 :-( (Damn queue )
Btw, if this is indeed the problem, it affects every single KDEPIM application. Have a look at the patch, it consists of over 300 lines: https://build.opensuse.org/package/view_file/home:wolfi323:test/kdepim/fix-h idpi-scaling.patch?expand=1
So much for "seems the fix is quite light"... ;-)
You're a lucky guy, I'm not doing C++ :-)
Kind Regards, Wolfgang
Eager to have the missing libkdepim to test it. ps: I put montel in CC just in case. How and I just found another victim of qtwebengine gwenview seems to suffer the case type of bug :-( But we will keep that one for the rainy week-end :-))) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 15. September 2016, 21:32:35 schrieb Bruno Friedmann:
Would like soo much :-) but I encounter a missing package 6 Problems: Problem: nothing provides libkdepim = 16.08.1 needed by kaddressbook5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kalarm5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kmail5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by knotes5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kontact5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by korganizer5-16.08.1-88.1.x86_64
also tw has still only have the 16.08.0 :-( (Damn queue )
Yeah, 16.08.1 has been accepted to Factory yesterday, but a new Tumbleweed snapshot that contains it has not been released yet. Unfortunately, I cannot easily build a 16.08.0 version with that patch either for the same reasons. You have two options I suppose: - wait for 16.08.1 to enter Tumbleweed (should be in the next snapshot) - install the 16.08.1 packages from KDE:Applications
How and I just found another victim of qtwebengine gwenview seems to suffer the case type of bug :-( But we will keep that one for the rainy week-end :-)))
Hm, I was not aware that gwenview uses QtWebEngine at all. But yes, it may have a similar bug... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On jeudi, 15 septembre 2016 21.40:15 h CEST Wolfgang Bauer wrote:
Am Donnerstag, 15. September 2016, 21:32:35 schrieb Bruno Friedmann:
Would like soo much :-) but I encounter a missing package 6 Problems: Problem: nothing provides libkdepim = 16.08.1 needed by kaddressbook5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kalarm5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kmail5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by knotes5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by kontact5-16.08.1-88.1.x86_64 Problem: nothing provides libkdepim = 16.08.1 needed by korganizer5-16.08.1-88.1.x86_64
also tw has still only have the 16.08.0 :-( (Damn queue )
Yeah, 16.08.1 has been accepted to Factory yesterday, but a new Tumbleweed snapshot that contains it has not been released yet.
Unfortunately, I cannot easily build a 16.08.0 version with that patch either for the same reasons.
Don't worry, I will survive a day more, and wait the 16.08.1 Once its available I test and report back.
You have two options I suppose: - wait for 16.08.1 to enter Tumbleweed (should be in the next snapshot) - install the 16.08.1 packages from KDE:Applications
How and I just found another victim of qtwebengine gwenview seems to suffer the case type of bug :-( But we will keep that one for the rainy week-end :-)))
Hm, I was not aware that gwenview uses QtWebEngine at all. But yes, it may have a similar bug...
Oh yeah baby :-) https://drive.google.com/open?id=0B7QKxkCRy_GxUGwwRzl5aTNGaDg with fit activated ...
Kind Regards, Wolfgang
-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 15. September 2016, 21:40:15 schrieb Wolfgang Bauer:
Unfortunately, I cannot easily build a 16.08.0 version with that patch either for the same reasons.
You have two options I suppose: - wait for 16.08.1 to enter Tumbleweed (should be in the next snapshot) - install the 16.08.1 packages from KDE:Applications
I removed the strict-versioned requirement to libkdepim from my testing packages now and they have been rebuilt, so you may try again. I cannot guarantee that they work at all though with 16.08.0, as they are still being built against the 16.08.1 libraries. If they don't work, you may try these, they are still built against an older Tumbleweed snapshot with 16.08.0: http://download.opensuse.org/repositories/home:/wolfi323:/test/openSUSE_Fact... (but then, they are built against KDE Frameworks 5.26.0 from KDE:Frameworks5, which isn't in Tumbleweed either yet AFAICS)
Hm, I was not aware that gwenview uses QtWebEngine at all. But yes, it may have a similar bug...
I had a look, and gwenview apparently doesn't set Qt::EnableHighDPIScaling at all. You probably should file a bug report upstream (if there isn't one already), feel free to CC me. I may try to fix it myself too, but I don't think I will do that (and provide a testing package) before tomorrow... ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On jeudi, 15 septembre 2016 22.36:50 h CEST Wolfgang Bauer wrote:
Am Donnerstag, 15. September 2016, 21:40:15 schrieb Wolfgang Bauer:
Unfortunately, I cannot easily build a 16.08.0 version with that patch either for the same reasons.
You have two options I suppose: - wait for 16.08.1 to enter Tumbleweed (should be in the next snapshot) - install the 16.08.1 packages from KDE:Applications
I removed the strict-versioned requirement to libkdepim from my testing packages now and they have been rebuilt, so you may try again. I cannot guarantee that they work at all though with 16.08.0, as they are still being built against the 16.08.1 libraries.
If they don't work, you may try these, they are still built against an older Tumbleweed snapshot with 16.08.0: http://download.opensuse.org/repositories/home:/wolfi323:/test/openSUSE_Fact ory/ (but then, they are built against KDE Frameworks 5.26.0 from KDE:Frameworks5, which isn't in Tumbleweed either yet AFAICS)
I've tried them this morning but still not fixes visible. I guess I have to wait the whole update of TW.
Hm, I was not aware that gwenview uses QtWebEngine at all. But yes, it may have a similar bug...
I had a look, and gwenview apparently doesn't set Qt::EnableHighDPIScaling at all. You probably should file a bug report upstream (if there isn't one already), feel free to CC me. I may try to fix it myself too, but I don't think I will do that (and provide a testing package) before tomorrow... ;-)
Kind Regards, Wolfgang yep I will find time this friday evening or saturday to report the bug.
About trying hidpi on standard hardware I wonder if starting xorg with the - dpi 144 couldn't allow non owner to detect the problem ? Once I got the update I retry and report here. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On vendredi, 16 septembre 2016 08.59:50 h CEST Bruno Friedmann wrote:
On jeudi, 15 septembre 2016 22.36:50 h CEST Wolfgang Bauer wrote:
Am Donnerstag, 15. September 2016, 21:40:15 schrieb Wolfgang Bauer:
Unfortunately, I cannot easily build a 16.08.0 version with that patch either for the same reasons.
You have two options I suppose: - wait for 16.08.1 to enter Tumbleweed (should be in the next snapshot) - install the 16.08.1 packages from KDE:Applications
I removed the strict-versioned requirement to libkdepim from my testing packages now and they have been rebuilt, so you may try again. I cannot guarantee that they work at all though with 16.08.0, as they are still being built against the 16.08.1 libraries.
If they don't work, you may try these, they are still built against an older Tumbleweed snapshot with 16.08.0: http://download.opensuse.org/repositories/home:/wolfi323:/test/openSUSE_Fa ct ory/ (but then, they are built against KDE Frameworks 5.26.0 from KDE:Frameworks5, which isn't in Tumbleweed either yet AFAICS)
I've tried them this morning but still not fixes visible. I guess I have to wait the whole update of TW.
Hm, I was not aware that gwenview uses QtWebEngine at all. But yes, it may have a similar bug...
I had a look, and gwenview apparently doesn't set Qt::EnableHighDPIScaling at all. You probably should file a bug report upstream (if there isn't one already), feel free to CC me. I may try to fix it myself too, but I don't think I will do that (and provide a testing package) before tomorrow... ;-)
Kind Regards, Wolfgang
yep I will find time this friday evening or saturday to report the bug.
About trying hidpi on standard hardware I wonder if starting xorg with the - dpi 144 couldn't allow non owner to detect the problem ?
Once I got the update I retry and report here.
New TW snapshot all 16.08.1 components activated, plus yours but unfortunately I didn't have the expected result. see https://drive.google.com/open?id=0B7QKxkCRy_GxSmcxZmkzNnVFZXc I'm so sorry. Anything I can activate in kdedebug to get a trace of what's happening ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Freitag, 16. September 2016, 08:59:50 schrieb Bruno Friedmann:
About trying hidpi on standard hardware I wonder if starting xorg with the - dpi 144 couldn't allow non owner to detect the problem ?
Well, yes, that would work, but it will scale everything and make the system rather unusable. An acceptable way is using "xrandr --dpi 144" (or whatever value), that only affects newly started applications. I tried this and can see that the message view will not get scaled for HTML messages, but I don't see those empty spaces at all (might be because the window is much too small anyway for the larger fonts). Am Samstag, 17. September 2016, 11:09:04 schrieb Bruno Friedmann:
New TW snapshot all 16.08.1 components activated, plus yours but unfortunately I didn't have the expected result.
Well, as I wrote it's probably not that straight-forward...
see https://drive.google.com/open?id=0B7QKxkCRy_GxSmcxZmkzNnVFZXc
Hm, doesn't look that bad as I would have thought. ;-) But, have you tried to use the Zoom option in the "View" menu already? That should at least be an acceptable workaround.
I'm so sorry. Anything I can activate in kdedebug to get a trace of what's happening ?
No idea. But I don't think the existing debugging output will help in this case. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On samedi, 17 septembre 2016 18.20:36 h CEST Wolfgang Bauer wrote:
Am Freitag, 16. September 2016, 08:59:50 schrieb Bruno Friedmann:
About trying hidpi on standard hardware I wonder if starting xorg with the - dpi 144 couldn't allow non owner to detect the problem ?
Well, yes, that would work, but it will scale everything and make the system rather unusable. An acceptable way is using "xrandr --dpi 144" (or whatever value), that only affects newly started applications.
I tried this and can see that the message view will not get scaled for HTML messages, but I don't see those empty spaces at all (might be because the window is much too small anyway for the larger fonts).
Am Samstag, 17. September 2016, 11:09:04 schrieb Bruno Friedmann:
New TW snapshot all 16.08.1 components activated, plus yours but unfortunately I didn't have the expected result.
Well, as I wrote it's probably not that straight-forward...
see https://drive.google.com/open?id=0B7QKxkCRy_GxSmcxZmkzNnVFZXc
Hm, doesn't look that bad as I would have thought. ;-)
But, have you tried to use the Zoom option in the "View" menu already? That should at least be an acceptable workaround.
I'm so sorry. Anything I can activate in kdedebug to get a trace of what's happening ?
No idea. But I don't think the existing debugging output will help in this case.
Kind Regards, Wolfgang
I found the reason of the space around the way it's shown here. It's the scaling factor, My screen widget etc work great with a factor scale of 1.4 (Which was determined last fosdem by David Edmundson). This can explain the difference. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (5)
-
Bruno Friedmann -
Herbert Graeber -
Luca Beltrame -
Markus Slopianka -
Wolfgang Bauer