Solicitud de Información

2016-10-11 Thread Gerencia Comercial
Estimados Srs. Quisieramos entrar en contacto con la persona encarga de compras de servicios de Transporte de Carga de su organización, nos gustaría ofrecerles nuestros servicios, por lo que agradecemos cualquier información que nos pueda facilitar de contacto de la misma. Puede ver nuestra

Bug#797999: We are now more than one year later and this critical bug is not fixed

2016-10-11 Thread Dominique Dumont
On Monday, 10 October 2016 11:59:59 CEST eric2.vale...@orange.com wrote: > First of all, the bug is not critical because it only affects a very > > > specific setup for a particular video driver. > > A docked station using a nvidia driver is not that uncommon I guess... For the record, this

Re: Skrooge package

2016-10-11 Thread Sandro Knauß
Hey, > Stéphane could also work with debian-qt-kde team to help packaging skrooge > for Debian/unstable as soon as he creates a new release. Once the new > package is in Debian/unstable, it should migrate to Ubuntu in a matter of > weeks. > > May be Stéphane's PPA would not be needed then..

Re: Skrooge package

2016-10-11 Thread Dominique Dumont
On Monday, 10 October 2016 23:30:39 CEST Pino Toscano wrote: > Because, I'm on Kubuntu (Sorry for that!), I made a ppa > > > (https://launchpad.net/~s-mankowski/+archive/ubuntu/ppa-kf5) to provide > > the last version of Skrooge as soon as possible. > > Ubuntu PPAs are useless for Debian. While

Bug#840405: kontact: does not start

2016-10-11 Thread Thorsten Glaser
Package: kontact Version: 4:16.04.3-1 Severity: important Kontact does not start. It outputs the following to .xsession-errors while that: -cutting here may damage your screen surface- QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-tglase' QDBusObjectPath

Bug#587323: marked as done (kgpg: Key server communication disabled)

2016-10-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Oct 2016 21:03:57 +0200 with message-id <10710700.O9o76ZdvQC@adrien-portable2> and subject line kgpg: Key server communication disabled has caused the Debian Bug report #587323, regarding kgpg: Key server communication disabled to be marked as done. This means that you

Bug#649756: marked as done (kgpg: tray icon missing)

2016-10-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Oct 2016 21:03:57 +0200 with message-id <10710700.O9o76ZdvQC@adrien-portable2> and subject line kgpg: Key server communication disabled has caused the Debian Bug report #649756, regarding kgpg: tray icon missing to be marked as done. This means that you claim that the

Bug#750467: marked as done (kgpg: KGpg always lists the fingerprint of the subkey even when clicking on the main key)

2016-10-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Oct 2016 21:03:57 +0200 with message-id <10710700.O9o76ZdvQC@adrien-portable2> and subject line kgpg: Key server communication disabled has caused the Debian Bug report #750467, regarding kgpg: KGpg always lists the fingerprint of the subkey even when clicking on the

Bug#595558: marked as done (kgpg editor does not support non-Latin characters)

2016-10-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Oct 2016 21:03:57 +0200 with message-id <10710700.O9o76ZdvQC@adrien-portable2> and subject line kgpg: Key server communication disabled has caused the Debian Bug report #595558, regarding kgpg editor does not support non-Latin characters to be marked as done. This means

Bug#611554: marked as done (Ark no longer allows to "Open with" a suitable application)

2016-10-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Oct 2016 21:16:15 +0200 with message-id <231d2dad-9357-8421-ad4f-b740e5c29...@adrieng.fr> and subject line Ark no longer allows to "Open with" a suitable application has caused the Debian Bug report #611554, regarding Ark no longer allows to "Open with" a suitable

Bug#840478: ksmserver: autostart service "/usr/bin/conky" finished with exit code 0

2016-10-11 Thread allan grossman
Package: kde-baseapps-bin Version: 4:16.08.0-1 Severity: important * What led up to the situation? Upgraded Debian Unstable today. * What exactly did you do (or not do) that was effective (or ineffective)? Rebooted machine and started KDE as normal. conky refused to start and