See
https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/382//console
or just https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/382/
for more information.
See
https://jenkins.debian.net/job/chroot-installation_sid_install_kde-full/969//console
or just
https://jenkins.debian.net/job/chroot-installation_sid_install_kde-full/969/
for more information.
See
https://jenkins.debian.net/job/chroot-installation_sid_install_kde/1067//console
or just
https://jenkins.debian.net/job/chroot-installation_sid_install_kde/1067/ for
more information.
See
https://jenkins.debian.net/job/chroot-installation_sid_install_qt4/375//console
or just https://jenkins.debian.net/job/chroot-installation_sid_install_qt4/375/
for more information.
On December 15, 2015 01:32:49 PM Eric Valette wrote:
> On 12/15/2015 07:29 AM, Steve M. Robbins wrote:
> > Anyway, despite Eric V's advice to jump to digikam 5, I went ahead and did
> > a local rebuild of digikam 4.14 and it seems to run fine.
>
> What's the benefice of taking this path? Developpe
Package: dolphin
Version: 4:15.08.3-1
Severity: important
Tags: upstream
I'm sorry about opening a bug report with so little information
but this is a major issue with dolphin, at least on my setup so
it needs to be informed.
The program crashes constanly and I can't find steps to reproduce
it. T
Package: okular
Version: 4:15.08.3-1
When running from a screen(1) session that was created before logging out and
logging in again,
so various envvars are wrong, okular crashes and presents the bug-reporting
dialog instead of
presenting to the user the more informative "Session bus not found" t
7 matches
Mail list logo
