Am 28.07.2017 um 21:59 schrieb ch...@musicchris.de:
> Please give me some time to change to nvidia-driver, to see if it
> really makes the difference. Maybe on sunday I can get back to this
> odyssey...
Funny! I now tried with Cinnamon, MATE, nvidia and nouveau in all combinations,
and can't
On Wed, Aug 02, 2017 at 10:37:14AM +0100, Antonio Marcos López Alonso wrote:
>But it is amd64 indeed:
>
>uname -a
>
>Linux 4.11.0-1-amd64 #1 SMP Debian 4.11.6-1 (2017-06-19)
>x86_64 GNU/Linux
uname -a shows the kernel. You can run a amd64 kernel and a i386 userland, too.
>
Package: libreoffice
Version: 1:5.3.5~rc1-3
>Since reportbug-ng failed to report Architecture: I assumed amd64 given the
>kernel,
>but obviously not.
>This is clear case of why "I report a me, too to a random bug which might
>have appeared the same tim as mine but the symptoms are clearly
Hi,
On Fri, Jul 28, 2017 at 02:16:11PM +0200, ch...@musicchris.de wrote:
> > It was wrecked before already ;)
>
> That is, if you're not meaning to say that using nvidia-driver instead of
> nouveau is wrecking the system... :o)
I am meaning exactly that. :)
> >> Bottom line is, using Nouveau
Am 28.07.2017 um 14:03 schrieb Rene Engelhard:
> Hi,
>
> On Fri, Jul 28, 2017 at 01:39:34PM +0200, ch...@musicchris.de wrote:
>> Well, that wrecked my whole system!
>
> It was wrecked before already ;)
Actually, it ran very smooth for a long time! That is, if you're not meaning to
say that
Hi,
On Fri, Jul 28, 2017 at 01:39:34PM +0200, ch...@musicchris.de wrote:
> Well, that wrecked my whole system!
It was wrecked before already ;)
> Bottom line is, using Nouveau driver "repaired" LibreOffice! It works like a
> charm. Unfortunately I need the nvidia-driver...
No need to rush, I
On Fri, Jul 28, 2017 at 12:51:40PM +0100, Antonio Marcos López Alonso wrote:
> Package: libreoffice
> Version: 1:5.3.5~rc1-3
>
> Attaching "glxinfo" and backtrace, just in case. No NVIDIA involved.
Good, you didn't mention a X Error printed on the console. Anyways,
so it's NOT this bug since the
Package: libreoffice
Version: 1:5.3.5~rc1-3
Attaching "glxinfo" and backtrace, just in case. No NVIDIA involved.
Regards,
Antonio
--- System information. ---
Architecture:
Kernel: Linux 4.11.0-1-amd64
Debian Release: buster/sid
500 testing ftp.es.debian.org
500 stable
Am 27.07.2017 um 12:37 schrieb Rene Engelhard:
>
> See http://bugs.debian.org/868507. Giving the information requested there
> would actually be nice.
Let me get back to this a little later, because:
> Try without the binary nvidia drivers if you used them?
Well, that wrecked my whole system!
Package: libreoffice
Version: 1:5.3.5~rc1-3
>"Just"? To 5.3.4-4? That one was obsoleted sincd 6 days by 5.3.5 rc1. Which
>also
>is in testing since this morning. So how did you upgrade to 5.3.4-4 "just
>(now)"?
OK, my bad: I forgot "apt update" and upgraded to whatever was in local cache
On Thu, Jul 27, 2017 at 12:41:06PM +0100, Antonio Marcos López Alonso wrote:
> Package: libreoffice
> Version: 1:5.3.4-4
>
> Metooing here.
>
> Just updated LO and things started to go wrong: opening a document leads to a
"Just"? To 5.3.4-4? That one was obsoleted sincd 6 days by 5.3.5 rc1.
Package: libreoffice
Version: 1:5.3.4-4
Metooing here.
Just updated LO and things started to go wrong: opening a document leads to a
recovery warning dialog popping out which never ends. LO windows turned
unusable and B colored.
No gtk3, using KDE Plasma desktop and no NVIDIA drivers (Intel
tag 869874 + moreinfo
thanks
Hi,
On Thu, Jul 27, 2017 at 12:03:43PM +0200, chris_blues wrote:
> Severity: grave
>
> > Justification: renders
Package: libreoffice
Version: 1:5.3.5~rc1-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I did an update 3 days ago.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing unusual.
14 matches
Mail list logo
