On 23/07/18 19:16, Alan Grimes wrote:
Also, I'm version frozen on my linux kernel at 4.15.14... Is it getting
time to jump to 4.16? I'm much too shy to go to 4.17 at the moment...
You can use 4.14, which a long-term kernel and will be getting updates
for years to come.
No complaints
On Fri, 20 Jul 2018 09:04:26 -0400, Philip Webb wrote:
> However, I've just escaped fr another beast, ie Linux Mint 19 :
> DON'T try to install it alongside Gentoo !!
>
> This beast leads you along to a point where you've told it where to
> install -- a partition on my HDD (sdb5) -- ,
> you
On Monday, 23 July 2018 21:19:30 BST Alan Grimes wrote:
> I had made a error when reporting my problem launching steam, I had a
> stalled steam launch that was causing the other launch to simply abort,
> steam does stall on load.
>
> I deleted my entire crufty old steam directory and am trying to
On 07/21/18 11:10, J�rg Schaible wrote:
> Hi,
>
> is someone aware of the existence of an ebuild for Java 11 e.g. somewhere in
> the overlays? Or has someone
> already crafted one and is willing to share it?
>
> Cheers,
> J�rg
>
My response is::
I had made a error when reporting my problem launching steam, I had a
stalled steam launch that was causing the other launch to simply abort,
steam does stall on load.
I deleted my entire crufty old steam directory and am trying to run this
virgin...
#
atg@tortoise ~ $
You are completely right - plasma does expect OpenGL to do what is expected
from the specs. I don't think GNOME pushes the limits as far. And I would
use GNOME if it suited my needs - which I'm quite sure my last mail made
abundantly clear that it doesn't.
Still, can't really blame plasma.
Thanks for taking the time to reply, Dr Valdés.
Unfortunately, I would like to game now and then, and I wholeheartedly
believe that the GNOME developers uncovered a spectacular cache of drugs
just before abandoning the perfectly functional, fast GNOME 2 for whatever
they call a desktop now.
On Mon, Jul 23, 2018 at 9:18 PM Davyd McColl wrote:
>
> Definitely Nouveau. I tried (really hard) to stick to proper open-source
> all the way. But the culprit became abundantly clear when I switched to
> proprietary and never again had a lockup. Ever.
>
> And there are plenty of other users on
On Mon, Jul 23, 2018 at 8:37 PM Davyd McColl wrote:
>
> Dr Valdés, I'd really like to know more. Are you using a compositor; what
desktop environment?
I use GNOME 3.24.2, with gnome-shell (which uses a compositor). Also, I
run Wayland, not "classic" X.
>
If I had had the positive
Definitely Nouveau. I tried (really hard) to stick to proper open-source
all the way. But the culprit became abundantly clear when I switched to
proprietary and never again had a lockup. Ever.
And there are plenty of other users on the interwebs with the same sad story.
-d
On July 23, 2018
On Mon, Jul 23, 2018 at 9:47 AM, Andrey F. wrote:
> My experience is the same. Things are super fast with Nouveau, but the
> random system-wide lock ups were unbearable. I'm a KDE plasma user as well.
> My last experience was about 6 months ago.
>
> I wonder if there is anything we can do to help
Em seg, 23 de jul de 2018 às 11:47, Andrey F. escreveu:
> My experience is the same. Things are super fast with Nouveau, but the
> random system-wide lock ups were unbearable. I'm a KDE plasma user as well.
> My last experience was about 6 months ago.
>
> I wonder if there is anything we can do
Dr Valdés, I'd really like to know more. Are you using a compositor; what
desktop environment? If I had had the positive experience you speak of, I
would adopt Nouveau in a heartbeat. Nvidia has clearly shown their lack of
interest in the Linux community by shunning higher console resolutions,
Or, if you've gone the whole hog (like me), right-click an ISO in dolphin,
choose "properties" and on the general pane, click "file type options".
Here you can add / remove handlers and prioritize which one you would like
by default. IIRC, this deals with mime types, so won't just affect
Okay, very good suggestions, still broken, that bootstrap.tar.gz must be
broken too. =\
atg@tortoise ~ $ steam --reset
Installing bootstrap /home/atg/.local/share/Steam/bootstrap.tar.xz
Reset complete!
[### edit ###]
atg@tortoise ~ $ steam
which: no gnome-terminal in
On Monday, 23 July 2018 16:58:41 BST Wols Lists wrote:
> While I appreciate it's a damn sight more powerful than Windoze's
> braindead file extension system, it feels to me like mimetypes are a
> rogue chainsaw sometimes ...
>
> How do I find out what mimetypes are associated with an application?
On Mon, Jul 23, 2018 at 12:17 PM Philip Webb wrote:
[...]
> (1) What are people's experiences with Nouveau ?
> -- does it work easily with various kernels ?
Usually without any intervention from my part.
> -- does it manage graphics stably & reliably ?
Much more than with the NVidia
Steam places the games in a directory called
Library. It is in the settings (no idea where is the default on Linux).
You can go there and either copy the whole folder out, or just rename it to
ensure it will not delete it and once you have reinstalled, just move the
directory back, or tell steam
Perhaps just back up ~/.local/share/Steam/steamapps and reset steam, then
close steam and copy back your steamapps?
I've done this on Windows before, for similar reasons. Haven't needed to
with steam on Linux - and it just updated about 1/2 an hour ago.
-d
On July 23, 2018 18:17:45 Alan
2018-07-23 18:58 GMT+03:00 Wols Lists :
> How do I find out what mimetypes are associated with an application?
>
> I would just inspect the .desktop files
We use Gentoo here so you know which package installed your application.
for kate it's... kate ;)
$ qlist kate | grep desktop
KDE is still very very broken.
Steam is almost 1/100th as bad as filezilla at pushing out stupid
updates to their beta client, which is pretty awful, whereas filezilla
is unbelievable...
Anyway, their client now doesn't load:
##
atg@tortoise ~ $ steam
which: no gnome-terminal in
Wol:
...
> How do I find out what mimetypes are associated with an application?
> Going the other way is a simple "System Settings" options, except that
> (a) I don't have a clue what half these mimetypes are, and (b) I don't
> fancy going through ALL of them one by one looking for the program in
While I appreciate it's a damn sight more powerful than Windoze's
braindead file extension system, it feels to me like mimetypes are a
rogue chainsaw sometimes ...
How do I find out what mimetypes are associated with an application?
Going the other way is a simple "System Settings" options,
My experience is the same. Things are super fast with Nouveau, but the
random system-wide lock ups were unbearable. I'm a KDE plasma user as well.
My last experience was about 6 months ago.
I wonder if there is anything we can do to help solve the lockup issues in
the long run with Nouveau.
On
On 23.07.2018 08:56, Kai Peter wrote:
> package.provided have to be configured at each host by hand wich is a
> big effort if you have a lot of boxes.
I call that nonsense. How is that an effort, especially if the proposed
alternative is installing a do-nothing ebuild on "a lot of boxes"?
"He
For what it's worth, my experience with Nouveau has been dismal.
I use KDE plasma, which runs everything via accelerated graphics and I
would encounter system-wide lockups within 2 hours, often much closer to
within 10 minutes.
Nouveau has better terminal support though, supporting the higher
Just for fun:
Open /usr/bin/emerge in a text editor and read the first 10 lines.
Then run
grep python-exec /usr/bin/*
It basically is the same what qtchooser does: Forward a python script to
the appropriate python version.
2018-07-23 13:20 GMT+03:00 Franz Fellner :
> IMO the problem is that
IMO the problem is that qtchooser acts as one point to select ALL
components for the default Qt, be it qt4 or qt5 (and possibly qt6 in 2020),
without checking if the tool really exists.
It just forwards the call to an execuatble with the same name inside the
qt-installation's bin dir.
Among my efforts to get scanning working again with Gentoo,
I've encountered another problem in a different area.
Recently, I sent a message to this list re Nvidia-drivers
-- that 396.24-r1 wouldn't start with my 4.14.52 kernel,
so I started using 390.67 -- & I've now discovered that there's a
On Monday, 23 July 2018 10:09:38 BST Franz Fellner wrote:
> Yeah, stupid qtchooser ;)
>
> qtconfig got dropped, use x11-misc/qt5ct instead.
Thanks Franz, qtconfig used to be installed by default with Qt. I wonder why
x11-misc/qt5ct isn't treated the same, especially as qtconfig is left on the
On Monday, 23 July 2018 10:01:18 BST Peter Humphrey wrote:
> On Monday, 23 July 2018 09:19:05 BST Mick wrote:
> > When I run /usr/bin/qtconfig it complains about a missing
> > '/usr/lib64/qt5/bin/ qtconfig':
> >
> > $ /usr/bin/qtconfig
> > qtconfig: could not exec '/usr/lib64/qt5/bin/qtconfig':
Yeah, stupid qtchooser ;)
qtconfig got dropped, use x11-misc/qt5ct instead.
2018-07-23 12:02 GMT+03:00 Dale :
> Mick wrote:
> > When I run /usr/bin/qtconfig it complains about a missing
> '/usr/lib64/qt5/bin/
> > qtconfig':
> >
> > $ /usr/bin/qtconfig
> > qtconfig: could not exec
Mick wrote:
> When I run /usr/bin/qtconfig it complains about a missing '/usr/lib64/qt5/bin/
> qtconfig':
>
> $ /usr/bin/qtconfig
> qtconfig: could not exec '/usr/lib64/qt5/bin/qtconfig': No such file or
> directory
>
> $ locate qtconfig
> /usr/bin/qtconfig
>
>
> Which package is responsible for
On Monday, 23 July 2018 09:19:05 BST Mick wrote:
> When I run /usr/bin/qtconfig it complains about a missing
> '/usr/lib64/qt5/bin/ qtconfig':
>
> $ /usr/bin/qtconfig
> qtconfig: could not exec '/usr/lib64/qt5/bin/qtconfig': No such file or
> directory
>
> $ locate qtconfig
> /usr/bin/qtconfig
>
When I run /usr/bin/qtconfig it complains about a missing '/usr/lib64/qt5/bin/
qtconfig':
$ /usr/bin/qtconfig
qtconfig: could not exec '/usr/lib64/qt5/bin/qtconfig': No such file or
directory
$ locate qtconfig
/usr/bin/qtconfig
Which package is responsible for it and how can I get it back?
On 2018-07-22 12:24, Ralph Seichter wrote:
On 22.07.2018 09:27, Kai Peter wrote:
A bit more easier is to create an 'empty' virtual ebuild which at
least does nothing but tells portage the dependency is fulfilled.
Not a good choice, IMO. Portage has its own mechanism for that:
36 matches
Mail list logo
