Dear maintainers,
Below is the output you required (in French).
I hope I am not just making you lose time because of a bad config
Regards,
python3-numpy:
Installé : 1:1.16.2-1
Candidat : 1:1.16.2-1
Table de version :
*** 1:1.16.2-1 500
500 http://ftp.fr.debian.org/debian sid/
My bad,
Just ignore please,
(It is just that I can not update python-tornado yet in sid but I will
wait)
Regards,
2018-03-23 12:40 GMT+01:00 Laurent Debian :
> Dear all,
>
> It seems to me that I suffer the same bug in jupyter notebook
> on a system that does not have python
Dear all,
It seems to me that I suffer the same bug in jupyter notebook
on a system that does not have python-tornado : I use a sagemath install :
in particular python-ipykernel python-ipywidgets python-jupyter-client
python-nbconvert pythonpython-sagetex python-zmq sagemath sagemath-jupyter
saget
Dear maintainer,
As suspected doing
System Settings → Display and Monitor → Display Configuration → Scale
Display =1
in KDE
Restores back a neat system
Sorry for the noise,
Regards,
Laurent
HI,
2017-03-10 4:50 GMT+01:00 Ben Hutchings :
> Control: tag -1 moreinfo
>
> On Thu, 2017-03-09 at 23:09 +0100, laurent B wrote:
> > Package: src:linux
> > Version: 4.9.13-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > After last upgrade.
> > I Lost any support whatsoever of the wireles
Hi,
I am a bit doubtful,
Regarding the first issue :
- the same issue happened both in my laptop without any kind of dual screen
("mac book pro retina 2013" using intel i915 ) and my desktop HP with dual
screen (DVI VGA ) using nouveau...
-the symptoms seem different : sddm start into the K icon
A simple workaround is to erase the file
"kileuirc"
and at next start kile goes back to a normal behavior.
Maybe it was just a "sid" update that broke it.
I am not sure if it should actually be considered as a kile bug,...
cheers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.d
This has been fixed (kile-10n-2.1.3-2).
Package: phoronix-test-suite
Version: 4.4.0-1
Severity: important
Tags: upstream
Dear Maintainer,
What led up to the situation?
Try to run benchmark after switching to discrete gpu on hybrid graphics system
What exactly did you do (or not do) that was effective (or
ineffective)?
Try to la
Package: powertop
Version: 2.0-0.2
Severity: important
Dear Maintainer,
What led up to the situation? Launch powertop on battery on a(my) laptop
What was the outcome of this action? It instanly crashed with the following
message :
> terminate called after throwing an instance of 'std::ios_base
Package: powertop
Version: 2.0-0.2
Severity: important
Dear Maintainer,
What led up to the situation? Launch powertop on battery on a(my) laptop
What was the outcome of this action? It instanly crashed with the following
message :
> terminate called after throwing an instance of 'std::ios_base
Hi,
I've been able to reproduce this bug.
It doesn't happen when using nfs4, it does with nfsvers=2 or
nfsvers=3.
I can reproduce it with:
ii linux-image-3.2.0-2-amd64 3.2.15-1
ii libmount1 2.20.1-4
ii mount 2.20.1-4
ii nfs-commo
12 matches
Mail list logo