There are 2 workarounds for this:
1. Convert printers.py to python3 yourself:
$ cd /usr/share/gcc-4.8/python/libstdcxx/v6/
$ 2to3 -w printers.py
2. Use this patch: http://gcc.gnu.org/ml/libstdc++/2013-10/msg00243.html
--
You received this bug notification because you are a member of Ubuntu
Bug
"nouveau is an open-source driver that is used as default, and it will
not appear in jockey, which only lists restricted/additional drivers"
I quite don't understand why should it be restricted to additional
drivers? If somebody installs restricted driver which causes problems
and makes it impossi
** Changed in: jockey (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728784
Title:
no nouveau driver in jockey list
To manage notifications about this bu
I'am happy to hear it, full of hope I tried your procedure, but it didn't work
for me..
I've already got used to pressing "stop" button every time and will wait until
problem will got solved by update / reinstall of system.
--
You received this bug notification because you are a member of Ubunt
I am happy that everything works fine on your system. As mentioned before -
I'am not TexStudio fan, neither Texmaker fan, i just use Texmaker (despite this
strange behaviour).
My desktop is not "strange" - it's just new gnome shell installed in normal
Ubuntu. As you can see on my previous video
#36: It's not me. I've never used texstudio because I find Texmaker a
better program.
#35: I understand, you are right, the problem in part comes from my system (but
I don't think it has anything in common with my CPU usage, which may be high on
the recording due to desktop recording). On other
"You have a serious problem with your system : the xorg process takes between
37% and 95% of cpu usage "
No, I don't, most of the time it stays at normal levels, below 10%. Probably
high CPU usage on the video was caused by frequent switching between windows.
"(and you're using now gnome shell ,
#31
- "the pdf process should stop himself in 1 or 2 seconds" - I agree!
- "the log file is not displayed automatically as it should be" - I agree!
- "everybody can see on your video (58 s) that the main.pdf file has exactly
the same date and time (11:55) than the source main.tex" - I agree
-
This bug report is not false, I don;t believe it is submitted with wrong
intentions, but maybe it;s not correct - the problem possibly is in some
specific system configuration not in TexMaker itself. Anyway: the problem
exists and it would be really great to hear at least some words of advise i
Why? What is so abnormal?
If you refer to opening result pdf in external browser - you are right, I could
open it in internal TexMaker viewer that's what I usually do, it's just that
this turning progress icon and 100% CPU load discouraged me from doing it with
TexMaker.
If you refer to using "c
Hmm, I have successfully used Texmaker for a long time and always
without problems. Why do you suggest that I can't use it correctly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175539
Title:
tex
What I can see is that this problem doesn't affect you.
Still it does affects me and at least 2 other people, which can be seen on this
video: http://youtu.be/Fy7HY-nQs2I
I would be grateful for any advice on solving this problem. I've already tried
to reinstall texmaker, both versions, from repo
I've already tried this procedure. It doesn't cause hanging on whole
Ubuntu, it even doesn't causes TexMaker to hang - it is still fully
functional except for that progress icon keeps turning and TexMaker uses
100% of one CPU core. This state persist, possibly forever, I killed
TexMaker process aft
One interesting fact to add: Few seconds after running pdflatex from within
TexMaker buttons "Run" and "View" become enabled again just as if compilation
has finished, but "busy status" still keeps turning around and CPU usage is
100% on one core. What is even more interesting: in the output fol
Unfortunately I have to confirm this bug: I have exactly the same
problem: After upgrade to Ubuntu 13.04, both TexMaker from Ubuntu repos
and 4.0.2 from project's website hang when trying to compile with
pdflatex which works fine on command line.
--
You received this bug notification because you
15 matches
Mail list logo