Re: Okular Trim Margin
On Fri, 15 Mar 2019 17:23:28 +0100 inkbottle wrote: Hello inkbottle, >Hence my question: is Margin Trimming working alright for you on the >above hello.pdf? Works here, using okular 1.3.2 (up to date testing) on 1680x1050 monitor. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Love is a temple, love is a shrine You Have Placed A Chill In My Heart - Eurythmics pgpg5_Zu0IUON.pgp Description: OpenPGP digital signature
Re: Okular Trim Margin
Hi, Am Freitag, 15. März 2019, 17:23:28 CET schrieb inkbottle: > If I download sample pdf http://www.xmlpdf.com/manualfiles/hello.pdf[1] , > open it in Okular and do View > Trim View > Trim Margin, well, nothing > happens. > > I am now using Okular 18.04 from experimental; I'm not ready to downgrade to > Okular 17.12 from testing, because that version has too many annoying bugs > (maybe mostly related to annotations, that I use a lot); anyway... > > Anyway, Trim Margin hasn't worked for me for at least 2 years, so it is not > something related to 18.04. > > Actually, I've been induced to think, that it was a property of the > documents I was opening... (like, all of them) > > But a few days ago, it came to my attention that if you do the same > manipulation with Qpdfview, with the document hello.pdf from above, the > margin trimming thing is working, no issues whatsoever. > > One possible explanation is that for 2 years or so, I've been consistently > missing a key package. > > Another, is that I'm the only one with a small screen nowadays, and > therefore the only one observing that Trimming Margin is not working. > > Hence my question: is Margin Trimming working alright for you on the above > hello.pdf? Works for me on Okular 1.3.2 (alias 17.12) from Debian/Buster. Have not tried 18.04, though. > Thanks, > Chris > > > > [1] http://www.xmlpdf.com/manualfiles/hello.pdf Cu, Chris --
Okular Trim Margin
If I download sample pdf http://www.xmlpdf.com/manualfiles/hello.pdf[1] , open it in Okular and do View > Trim View > Trim Margin, well, nothing happens. I am now using Okular 18.04 from experimental; I'm not ready to downgrade to Okular 17.12 from testing, because that version has too many annoying bugs (maybe mostly related to annotations, that I use a lot); anyway... Anyway, Trim Margin hasn't worked for me for at least 2 years, so it is not something related to 18.04. Actually, I've been induced to think, that it was a property of the documents I was opening... (like, all of them) But a few days ago, it came to my attention that if you do the same manipulation with Qpdfview, with the document hello.pdf from above, the margin trimming thing is working, no issues whatsoever. One possible explanation is that for 2 years or so, I've been consistently missing a key package. Another, is that I'm the only one with a small screen nowadays, and therefore the only one observing that Trimming Margin is not working. Hence my question: is Margin Trimming working alright for you on the above hello.pdf? Thanks, Chris [1] http://www.xmlpdf.com/manualfiles/hello.pdf
Re: Akonadi does not start Debian Buster
It is installed but i had stopped it before. ● apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2019-03-15 14:34:10 EET; 1h 3min ago Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Process: 20391 ExecStop=/bin/true (code=exited, status=0/SUCCESS) Main PID: 7874 (code=exited, status=0/SUCCESS) Mar 15 14:14:24 blackcat2 systemd[1]: Starting Load AppArmor profiles... Mar 15 14:14:24 blackcat2 apparmor.systemd[7874]: Restarting AppArmor Mar 15 14:14:24 blackcat2 apparmor.systemd[7874]: Reloading AppArmor profiles Mar 15 14:14:24 blackcat2 apparmor.systemd[7874]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.mysqld Mar 15 14:14:24 blackcat2 apparmor.systemd[7874]: Skipping profile in /etc/apparmor.d/disable: usr.bin.thunderbird Mar 15 14:14:24 blackcat2 systemd[1]: Started Load AppArmor profiles. Mar 15 14:34:10 blackcat2 systemd[1]: Stopping Load AppArmor profiles... Mar 15 14:34:10 blackcat2 systemd[1]: apparmor.service: Succeeded. Mar 15 14:34:10 blackcat2 systemd[1]: Stopped Load AppArmor profiles. On 3/15/19 3:33 PM, Reinhard Karcher wrote: Is apparmor runnig? I accidently installed apparmor and got the same messages. After removing apparmor the errors where gone. Reinhard
Re: Akonadi does not start Debian Buster
Is apparmor runnig? I accidently installed apparmor and got the same messages. After removing apparmor the errors where gone. Reinhard
Akonadi does not start Debian Buster
Hello everybody,
After upgrading to akonadi 18.08.3-4 akonadi does not start anymore
The log of akonadictl start
org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck"
org.kde.pim.akonadiserver: Using mysqld: "/usr/sbin/mysqld-akonadi"
org.kde.pim.akonadiserver: mysqld reports version 10.3.13 (MariaDB)
org.kde.pim.akonadiserver: Executing: "/usr/sbin/mysqld-akonadi"
"--defaults-file=/home/jim/.local/share/akonadi/mysql.conf
--datadir=/home/jim/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-jim.5qGLAh/mysql.socket
--pid-file=/tmp/akonadi-jim.5qGLAh/mysql.pid"
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during
initial connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld-akonadi"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/jim/.local/share/akonadi/mysql.conf",
"--datadir=/home/jim/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-jim.5qGLAh/mysql.socket",
"--pid-file=/tmp/akonadi-jim.5qGLAh/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "Could not open required defaults
file: /home/jim/.local/share/akonadi/mysql.conf\nFatal error in defaults
handling. Program aborted\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: terminating connection threads
org.kde.pim.akonadiserver: terminating service threads
org.kde.pim.akonadiserver: stopping db process
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/tmp/akonadi-jim.5qGLAh/mysql.socket' (2)'
Check that mysqld is running and that the socket:
'/tmp/akonadi-jim.5qGLAh/mysql.socket' exists!
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally..
Thank yoy
Dimitris
Re: KDEPIM 18.08.3 for Buster
Hi, Am Freitag, 15. März 2019, 12:02:42 CET schrieb Andy G Wood: > Hello, > > I have also been suffering from infrequent kmail crashes in recent weeks. > It is not related to filtering, nor is it specific to nouveau (I use the > NVIDIA proprietary display driver). I'm seeing the issue with both, nouveau and (legacy 390) nvidia blob. Currently running Kontact inside a VM instead, let's see what that does. > Not currently reproducible ... and yes I need to install debug syms in order > to provide more than a "me too". The impact may be wider than kmail > because I have also had one okular crash too. Regarding wider impact, the traces I've seen so far point towards QtWebEngine, so any app integrating this might be affected. > Andy. > > On Friday, 15 March 2019 09:55:10 GMT Christian Hilberg wrote: > > Hi there, > > > > Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald: > > > Sandro Knauß - 07.02.19, 00:33: > > > > Hey, > > > > > > > > as Debian is already in freeze, the version of KDEPIM that will > > > > shipped with the next stable is 18.08.3. That was uploaded same days > > > > ago. There is no time to package 18.12.X sorry for that. > > > > So please test this version in more depth and report issues. If you > > > > also manage to point to existing bugfixes like done in #921535 it is > > > > very likely we can ship a that bugfix also for Buster. > > > > > > The other issue I have since 18.08 packages is: > > > > > > Debian #921624: kmail: Crash during/after filtering inbox, probably > > > related to Qt WebEngine integration > > > https://bugs.debian.org/921624 > > > > > > Crash during/after filtering inbox, probably related to Qt WebEngine > > > integration > > > https://bugs.kde.org/404052 > > > > Filed another one (since 18.08): > > > > KMail (in Kontact) crashing upon start or shortly after > > https://bugs.kde.org/405491 > > > > It might be related (or even duplicate) to #404052, > > only that I do not need to have mails filtered for > > KMail to crash. Looks like a QtWebEngine thing. > > > > Just like Martin, I missed out on debug syms. Got them > > installed now and trying to get another backtrace. > > > > > I can add more backtraces to the upstream bug report. For some reason > > > DrKonqi shortened the second backtrace I had it generate after fully > > > upgrading to 18.08.3-1. > > > > > > At least this one produces a crash, instead of just stalling… for > > > whatever reason. > > > > > > Thanks, (Bye)², Christian --
Re: KDEPIM 18.08.3 for Buster
Hello, I have also been suffering from infrequent kmail crashes in recent weeks. It is not related to filtering, nor is it specific to nouveau (I use the NVIDIA proprietary display driver). Not currently reproducible ... and yes I need to install debug syms in order to provide more than a "me too". The impact may be wider than kmail because I have also had one okular crash too. Andy. On Friday, 15 March 2019 09:55:10 GMT Christian Hilberg wrote: > Hi there, > > Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald: > > Sandro Knauß - 07.02.19, 00:33: > > > Hey, > > > > > > as Debian is already in freeze, the version of KDEPIM that will > > > shipped with the next stable is 18.08.3. That was uploaded same days > > > ago. There is no time to package 18.12.X sorry for that. > > > So please test this version in more depth and report issues. If you > > > also manage to point to existing bugfixes like done in #921535 it is > > > very likely we can ship a that bugfix also for Buster. > > > > The other issue I have since 18.08 packages is: > > > > Debian #921624: kmail: Crash during/after filtering inbox, probably > > related to Qt WebEngine integration > > https://bugs.debian.org/921624 > > > > Crash during/after filtering inbox, probably related to Qt WebEngine > > integration > > https://bugs.kde.org/404052 > > Filed another one (since 18.08): > > KMail (in Kontact) crashing upon start or shortly after > https://bugs.kde.org/405491 > > It might be related (or even duplicate) to #404052, > only that I do not need to have mails filtered for > KMail to crash. Looks like a QtWebEngine thing. > > Just like Martin, I missed out on debug syms. Got them > installed now and trying to get another backtrace. > > > I can add more backtraces to the upstream bug report. For some reason > > DrKonqi shortened the second backtrace I had it generate after fully > > upgrading to 18.08.3-1. > > > > At least this one produces a crash, instead of just stalling… for > > whatever reason. > > > > Thanks, > (Bye)², > Christian
Re: KDEPIM 18.08.3 for Buster
Hi there, Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald: > Sandro Knauß - 07.02.19, 00:33: > > Hey, > > > > as Debian is already in freeze, the version of KDEPIM that will > > shipped with the next stable is 18.08.3. That was uploaded same days > > ago. There is no time to package 18.12.X sorry for that. > > So please test this version in more depth and report issues. If you > > also manage to point to existing bugfixes like done in #921535 it is > > very likely we can ship a that bugfix also for Buster. > > The other issue I have since 18.08 packages is: > > Debian #921624: kmail: Crash during/after filtering inbox, probably > related to Qt WebEngine integration > https://bugs.debian.org/921624 > > Crash during/after filtering inbox, probably related to Qt WebEngine > integration > https://bugs.kde.org/404052 Filed another one (since 18.08): KMail (in Kontact) crashing upon start or shortly after https://bugs.kde.org/405491 It might be related (or even duplicate) to #404052, only that I do not need to have mails filtered for KMail to crash. Looks like a QtWebEngine thing. Just like Martin, I missed out on debug syms. Got them installed now and trying to get another backtrace. > I can add more backtraces to the upstream bug report. For some reason > DrKonqi shortened the second backtrace I had it generate after fully > upgrading to 18.08.3-1. > > At least this one produces a crash, instead of just stalling… for > whatever reason. > > Thanks, (Bye)², Christian --
