Bug#760472: korganizer: Korganizer crashes when adding "traditional KDE calendar" fails to find any plugins
Kevin Krammer wrote: > It would still be a good idea to try the real/current calendar resource > instead of the compatibility mechanism, since the latter will go away at some > point. Sorry, I am not quite sure which kind of calendar resource you mean here. When I try to add a new calendar, I get to choose between - Birthdays from my address book - but I don't use KDE's address book (nor mail) - DAV groupware resource - but I don't use any groupware - Google calendar and tasks - but I don't want to tell google everything I do - ICal calendar file - That is what I use now. - ICal calendar folder - sounds like an overkill for a single calendar - KAlarm calendar file - I can point that to my calendar (over fish://), but nothing happens, no new calendar appears. - KAlarm calendar folder - overkill - Kolab groupware server - never heard of, have not installed on my server - Open-Xchange groupware server - same here. All I want to do is to have my own calendar on my server, so I can open it locally on my home workstation, and remotely from work, preferably over ssh. And I want a read-only access to our company calendar, which is exported from google as a ical file. I prefer not to log in to google to access that, want to keep private life and work life separate. As far as I can see, ical over fish (or sftp) fits my needs best. I would be sad to see that go away at some point. Or have I misunderstood something? Regards Heikki -- Heikki Levantoheikki at indexdata dot dk "In Murphy We Turst" -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140909064244.ga10...@indexdata.dk
Bug#760752: marked as done ([okular] [Okular] Title bar shows "Please insert PrerenderUnicode{??} into preamble]" when there is an umlaut in the PDF's title)
Your message dated Tue, 9 Sep 2014 09:18:40 +1000
with message-id <201409090918.40744.stu...@debian.org>
and subject line Re: Bug#760751: [okular] Okular shows "[Please insert
PrerenderUnicode{??} into preamble]" in the title bar, when the title of the
document contains an umlaut
has caused the Debian Bug report #760751,
regarding [okular] [Okular] Title bar shows "Please insert PrerenderUnicode{??}
into preamble]" when there is an umlaut in the PDF's title
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
760751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: okular
Version: 4:4.14.0-2
Severity: normal
--- Please enter the report below this line. ---
--- System information. ---
Architecture: i386
Kernel: Linux 3.14-2-686-pae
Debian Release: jessie/sid
500 unstabledownload.jitsi.org
500 trusty ppa.launchpad.net
500 testing www.deb-multimedia.org
500 testing security.debian.org
500 testing ftp.de.debian.org
500 stable dl.google.com
500 sid-pgdgapt.postgresql.org
500 sid linux.dropbox.com
--- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Hi Thomas,
> > The producer of this pdf (pdfeTeX-1.21a by the looks of it) needs to be
> > configured to correctly handle non-ASCII characters in the PDF metadata.
> > If you had the latex source available, you'd be able to fix this by
>
> I am afraid not ... :(
>
> > regenerating the PDF... The solution is to either tell pdflatex that the
> > input file is encoded in UTF-8 (for example \usepackage[utf8]{inputenc})
> > or to help pdflatex understand how to deal with this character (add
> > \PrerenderUnicode{ü} to the preamble.)
>
> O.K. I will try to ask someone from bib, if it is possible to fix this.
> Thanks again for your answer and have a nice evening
> Thomas.
This can be also fixed using pdf editing software to change the Title and
Keywords metadata. In Debian, pdfmod can edit the metadata.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7--- End Message ---
Bug#760750: marked as done ([okular] Okular shows "[Please insert PrerenderUnicode{??} into preamble]", when the title of the PDF contains an umlaut)
Your message dated Tue, 9 Sep 2014 09:18:40 +1000
with message-id <201409090918.40744.stu...@debian.org>
and subject line Re: Bug#760751: [okular] Okular shows "[Please insert
PrerenderUnicode{??} into preamble]" in the title bar, when the title of the
document contains an umlaut
has caused the Debian Bug report #760751,
regarding [okular] Okular shows "[Please insert PrerenderUnicode{??} into
preamble]", when the title of the PDF contains an umlaut
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
760751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: okular
Version: 4:4.14.0-2
Severity: normal
--- Please enter the report below this line. ---
--- System information. ---
Architecture: i386
Kernel: Linux 3.14-2-686-pae
Debian Release: jessie/sid
500 unstabledownload.jitsi.org
500 trusty ppa.launchpad.net
500 testing www.deb-multimedia.org
500 testing security.debian.org
500 testing ftp.de.debian.org
500 stable dl.google.com
500 sid-pgdgapt.postgresql.org
500 sid linux.dropbox.com
--- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Hi Thomas,
> > The producer of this pdf (pdfeTeX-1.21a by the looks of it) needs to be
> > configured to correctly handle non-ASCII characters in the PDF metadata.
> > If you had the latex source available, you'd be able to fix this by
>
> I am afraid not ... :(
>
> > regenerating the PDF... The solution is to either tell pdflatex that the
> > input file is encoded in UTF-8 (for example \usepackage[utf8]{inputenc})
> > or to help pdflatex understand how to deal with this character (add
> > \PrerenderUnicode{ü} to the preamble.)
>
> O.K. I will try to ask someone from bib, if it is possible to fix this.
> Thanks again for your answer and have a nice evening
> Thomas.
This can be also fixed using pdf editing software to change the Title and
Keywords metadata. In Debian, pdfmod can edit the metadata.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7--- End Message ---
Bug#760753: marked as done ([okular] Okular shows "[Please insert PrerenderUnicode{??} into preamble]" in title bar, when there is an umaut in the PDF's title)
Your message dated Tue, 9 Sep 2014 09:18:40 +1000
with message-id <201409090918.40744.stu...@debian.org>
and subject line Re: Bug#760751: [okular] Okular shows "[Please insert
PrerenderUnicode{??} into preamble]" in the title bar, when the title of the
document contains an umlaut
has caused the Debian Bug report #760751,
regarding [okular] Okular shows "[Please insert PrerenderUnicode{??} into
preamble]" in title bar, when there is an umaut in the PDF's title
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
760751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: okular
Version: 4:4.14.0-2
Severity: normal
--- Please enter the report below this line. ---
--- System information. ---
Architecture: i386
Kernel: Linux 3.14-2-686-pae
Debian Release: jessie/sid
500 unstabledownload.jitsi.org
500 trusty ppa.launchpad.net
500 testing www.deb-multimedia.org
500 testing security.debian.org
500 testing ftp.de.debian.org
500 stable dl.google.com
500 sid-pgdgapt.postgresql.org
500 sid linux.dropbox.com
--- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Hi Thomas,
> > The producer of this pdf (pdfeTeX-1.21a by the looks of it) needs to be
> > configured to correctly handle non-ASCII characters in the PDF metadata.
> > If you had the latex source available, you'd be able to fix this by
>
> I am afraid not ... :(
>
> > regenerating the PDF... The solution is to either tell pdflatex that the
> > input file is encoded in UTF-8 (for example \usepackage[utf8]{inputenc})
> > or to help pdflatex understand how to deal with this character (add
> > \PrerenderUnicode{ü} to the preamble.)
>
> O.K. I will try to ask someone from bib, if it is possible to fix this.
> Thanks again for your answer and have a nice evening
> Thomas.
This can be also fixed using pdf editing software to change the Title and
Keywords metadata. In Debian, pdfmod can edit the metadata.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7--- End Message ---
Bug#760751: marked as done ([okular] Okular shows "[Please insert PrerenderUnicode{??} into preamble]" in the title bar, when the title of the document contains an umlaut)
Your message dated Tue, 9 Sep 2014 09:18:40 +1000
with message-id <201409090918.40744.stu...@debian.org>
and subject line Re: Bug#760751: [okular] Okular shows "[Please insert
PrerenderUnicode{??} into preamble]" in the title bar, when the title of the
document contains an umlaut
has caused the Debian Bug report #760751,
regarding [okular] Okular shows "[Please insert PrerenderUnicode{??} into
preamble]" in the title bar, when the title of the document contains an umlaut
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
760751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: okular
Version: 4:4.14.0-2
Severity: normal
--- Please enter the report below this line. ---
--- System information. ---
Architecture: i386
Kernel: Linux 3.14-2-686-pae
Debian Release: jessie/sid
500 unstabledownload.jitsi.org
500 trusty ppa.launchpad.net
500 testing www.deb-multimedia.org
500 testing security.debian.org
500 testing ftp.de.debian.org
500 stable dl.google.com
500 sid-pgdgapt.postgresql.org
500 sid linux.dropbox.com
--- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Hi Thomas,
> > The producer of this pdf (pdfeTeX-1.21a by the looks of it) needs to be
> > configured to correctly handle non-ASCII characters in the PDF metadata.
> > If you had the latex source available, you'd be able to fix this by
>
> I am afraid not ... :(
>
> > regenerating the PDF... The solution is to either tell pdflatex that the
> > input file is encoded in UTF-8 (for example \usepackage[utf8]{inputenc})
> > or to help pdflatex understand how to deal with this character (add
> > \PrerenderUnicode{ü} to the preamble.)
>
> O.K. I will try to ask someone from bib, if it is possible to fix this.
> Thanks again for your answer and have a nice evening
> Thomas.
This can be also fixed using pdf editing software to change the Title and
Keywords metadata. In Debian, pdfmod can edit the metadata.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7--- End Message ---
Bug#760751: [okular] Okular shows "[Please insert PrerenderUnicode{??} into preamble]" in the title bar, when the title of the document contains an umlaut
Hello Stuart, *,
On Mon, Sep 08, 2014 at 04:12:04PM +1000, Stuart Prescott wrote:
> > But now to my problem. If I open an PDF file, which has an German umlaut
> > in its title, Okular will replace the umlaut with "Please insert
> > PrerenderUnicode{??} into preamble]" (e.g. if its title would be
> > "Einführung" it will become "Einf[Please insert PrerenderUnicode{??} into
> > preamble]hrung") ... :
> >
> > Steps to reproduce:
> >
> > 1. Download https://www.bg.bib.de/portale/dab/pdf/einf_dab.pdf
> > 2. Open it in Okular
> > 3. Look at the title bar
> >
> > You will see "Einf[Please insert PrerenderUnicode{ü} into preamble]hrung
> > in das Fach Datenbanken" instead of "Einführung in das Fach Datenbanken"
> > ... :(
> >
> > You could also use "File - Properties" (I hope, this is the right
> > translation. In German it is "Datei - Eigenschaften" ... ;) ), where you
> > could see its title with this "Please insert..." annotation.
>
> This is a problem with the specific PDF that you have linked to and not with
> okular. What you see in the title bar there is quite literally what is set
> as the title for that PDF in the document metadata:
>
> $ pdfinfo einf_dab.pdf
> [...]
> Keywords: Datenbanken, Einf[Please insert PrerenderUnicode{ü} into
> preamble]hrung, Motivation
thank you for your information :)
> The producer of this pdf (pdfeTeX-1.21a by the looks of it) needs to be
> configured to correctly handle non-ASCII characters in the PDF metadata. If
> you had the latex source available, you'd be able to fix this by
I am afraid not ... :(
> regenerating the PDF... The solution is to either tell pdflatex that the
> input file is encoded in UTF-8 (for example \usepackage[utf8]{inputenc}) or
> to help pdflatex understand how to deal with this character (add
> \PrerenderUnicode{ü} to the preamble.)
O.K. I will try to ask someone from bib, if it is possible to fix this.
Thanks again for your answer and have a nice evening
Thomas.
--
Operator, please trace this call and tell me where I am.
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140908154838.ga10...@neo.matrix.org
Processed: merging 760750 760752 760753 760751
Processing commands for cont...@bugs.debian.org:
> merge 760750 760752 760753 760751
Bug #760750 [okular] [okular] Okular shows "[Please insert PrerenderUnicode{??}
into preamble]", when the title of the PDF contains an umlaut
Bug #760751 [okular] [okular] Okular shows "[Please insert PrerenderUnicode{??}
into preamble]" in the title bar, when the title of the document contains an
umlaut
Bug #760752 [okular] [okular] [Okular] Title bar shows "Please insert
PrerenderUnicode{??} into preamble]" when there is an umlaut in the PDF's title
Bug #760753 [okular] [okular] Okular shows "[Please insert PrerenderUnicode{??}
into preamble]" in title bar, when there is an umaut in the PDF's title
Merged 760750 760751 760752 760753
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
760750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760750
760751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760751
760752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760752
760753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/handler.s.c.141018052632495.transcr...@bugs.debian.org
Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr<_GError>(_GError*)'
On 07/09/14 22:22, Steven Chamberlain wrote: > I wonder if there's some significance that it was templated for > <_GError> whereas I think that should be a typedef to GError (without > underscore)? My test build finished - the change I tried didn't help - but looking for _GError (with underscore) it seemed it was specific to GStreamer: > $ grep _GError . -R > Binary file > ./WebKitBuild/Release/Source/WebCore/obj/release/MediaPlayerPrivateGStreamer.o > matches > Binary file > ./WebKitBuild/Release/Source/WebCore/obj/release/GStreamerUtilities.o matches > Binary file > ./WebKitBuild/Release/Source/WebCore/obj/release/WebKitWebSourceGStreamer.o > matches Then I found this related upstream commit mentioned in the 2.3.3 changelog: > 242013-12-17 Alex Christensen > 25 > 26[Win] Fixed linker error with GStreamer. > 27https://bugs.webkit.org/show_bug.cgi?id=124861 > 28 > 29Reviewed by Martin Robinson. > 30 > 31* wtf/gobject/GOwnPtr.cpp: > 32(WTF::GError): > 33* wtf/gobject/GOwnPtr.h: > 34Added WTF_EXPORT_PRIVATE to freeOwnedGPtr declaration > and definition. I'm trying another test build now with this change applied: http://trac.webkit.org/changeset/160716 Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Processed: affects
Processing commands for cont...@bugs.debian.org: > affects 760663 + amarok systemsettings Bug #760663 [phonon-backend-gstreamer] phonon-backend-gstreamer: Prevents Amarok from starting Added indication that 760663 affects amarok and systemsettings > thanks Stopping processing here. Please contact me if you need assistance. -- 760663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141017269011018.transcr...@bugs.debian.org
Bug#760663: phonon-backend-gstreamer: Prevents Amarok from starting
I can confirm this problem. My temporary workaround was to install phonon-backend-vlc start `kcmshell4 phonon`, go through backend and switch it to vlc (move it as top entry). Trying it through systemsettings -> Multimedia didn't work because it froze with a similar problem as amarok. Removing gstreamer1.0 doesn't seem to be possible for me because I would have to remove essentially my whole system -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1410172002.53991.yahoomail...@web133204.mail.ir2.yahoo.com
Re: Bug#760822: kde-config-cron: should depends on cron-daemon
On Monday 08 September 2014 01:46 PM, Alexandre Detiste wrote: Please depends on "cron-daemon | cron" instead of just cron. This way, users can use a alternative cron implementation. I looked into this some time back when I was exploring systemd-cron, which provides cron-daemon. In my opinion, having this hard dependency is good. Otherwise either systemd-cron should stop claiming that it can Provide cron-daemon. Because it does not support all cron features. -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3270eb-9ph@news.researchut.com
Bug#760822: kde-config-cron: should depends on cron-daemon
Package: kde-config-cron Version: 4:4.14.0-1 Severity: normal Dear Maintainer, Please depends on "cron-daemon | cron" instead of just cron. This way, users can use a alternative cron implementation. Here is the policy statement regarding the cron-daemon virtual package: https://www.debian.org/doc/debian-policy/ch-binary.html#s-virtual_pkg and here is the annexed list: https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt Bine à vous, Alexandre Detiste -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-trunk-amd64 (SMP w/6 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kde-config-cron depends on: ii libc62.19-10 ii libkdecore5 4:4.14.0-1 ii libkdeui54:4.14.0-1 ii libkio5 4:4.14.0-1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-1 ii libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-1 ii libstdc++6 4.9.1-12 ii systemd-cron [cron] 1.3.0-1 kde-config-cron recommends no packages. Versions of packages kde-config-cron suggests: ii khelpcenter4 4:4.14.0-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140908081632.8068.62859.reportbug@antec
