The Linux Questions Thread: a bunch of pitfalls, but technically it's possible

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Linux Questions Thread: a bunch of pitfalls, but technically it's possible

«‹›1025 »

xzzy: Mar 5, 2009

apropos man posted:

What do people use for benchmarking under Linux?

mprime (which is the linux version of prime95) for the cpu, badblocks for the disks. iozone is technically "better" for benchmarking disks because it produces actual statistics that you can make lovely graphs with, but badblocks is installed by default and we mostly use it for burnin. But you can get i/o rates out of it.

mprime with the -t option will make your processor sweat big time.

# ? Sep 30, 2016 21:00

Adbot: ADBOT LOVES YOU

# ? Apr 24, 2024 19:26

hifi: Jul 25, 2012

Toalpaz posted:

Hey there, sorry I didn't attach pictures or try other photo capturing techniques. I was really tired and passing out in my bed at that point!
So here's what my problem looks like using the gnome screenshot thing.

So this image up above shows the program's display not working. As you can see the visible box in the window's resolution is quite large too.

This is me showing uh, the fix I was directed to by the Arch wiki and I believe essentially what Bourricot asked me to do. So thanks a lot but I think I tried that, editing each comment away one by one until I've tried all the options once. (Leaving the rest commented of course.)

This is just an image of my Gnome on the preferences about thing to prove that I am running gnome 3, which I believe is the gtk3 option in the picture above. To speak to the people talking about my themes. I am using the default Adaita for everything! Except for the shell theme, I'm using no shell theme. As you can see I'm using Wayland. I use GDM I believe, when Arch starts up I'm taken to a graphical user selection screen and log onto the desktop from there. As for graphical driver, just uh, a basic one that does intel built in graphics, arch comes with the vesa drivers, and I just installed xf86-video-intel as a result of the question.

Hey thanks for all the comments, sorry I'm using Arch and making GBS threads up the thread with my problems. Calligra Word still technically works, and I have a desktop and windows. So I'm not totally out of options or desperate or anything. Calligra word just can't really open docx compatibility files however. I'd just like Linux to work and I think of it as a puzzle trying to figure out whats happening and investigating online and stuff. However I'm at a bit of a dead end this time. Thanks for taking the time to read this!

Just looking at your first screenshot maybe it's a hidpi issue

# ? Sep 30, 2016 21:27

apropos man: Sep 5, 2016; You get a hundred and forty one thousand years and you're out in eight!

xzzy posted:

mprime (which is the linux version of prime95) for the cpu, badblocks for the disks. iozone is technically "better" for benchmarking disks because it produces actual statistics that you can make lovely graphs with, but badblocks is installed by default and we mostly use it for burnin. But you can get i/o rates out of it.

mprime with the -t option will make your processor sweat big time.

Thanks. I ran mpime on my 3770k and I started sweating before the CPU. IOzone is the thing I'm looking for, if only the results were easier to read. Currently back to phoronix and running the filesystem io tests.

EDIT: I reckon something like the above will be able to give me a good impression of disk io when I fit the new board. I'll do some tweaking of options in the morning to generate a few different set of results with the old hardware.

apropos man fucked around with this message at 21:49 on Sep 30, 2016

# ? Sep 30, 2016 21:40

xzzy: Mar 5, 2009

mprime is so good at cooking processors we have to throttle our systems during burnin or we start flipping breakers.

One could reasonably argue that we should have bought enough power to allow the systems to actually run at full tilt, but we've discovered it's not really necessary. In production the systems almost never get past 80% of their theoretical max (due to i/o waits) so we spec for that instead.

# ? Sep 30, 2016 22:08

evol262: Nov 30, 2010; #!/usr/bin/perl

hifi posted:

Just looking at your first screenshot maybe it's a hidpi issue

It definitely looks like hidpi (which wayland is somewhat better at, but it looks like libreoffice is confused).

Can you try setting the DPI manually?

Keito posted:

Everyone in these threads furiously masturbate to CentOS and openSUSE and will jump in to throw a jab towards Arch at any opportunity. LibreOffice just Works For Me� to be honest, maybe start off with using a non-poo poo desktop environment like Xfce if you gotta have one.

We throw poo poo at Arch because the QA is nonexistent. It "just works" for me, too (if I wanted to use it), but "let's throw some totally untested upstream bullshit at users and hope they can troubleshoot issues they should never have in the first place" is not a great way to learn Linux. If experienced users want to use whatever distro, awesome. They won't post here. Furiously masterbating about SUSE, Fedora, CentOS, and other QA'd distros is because they work for people.

Toppest kek at blaming the DE for this issue, though.

# ? Oct 1, 2016 01:05

Docjowles: Apr 9, 2009

IAmKale posted:

What might be a good thread to ask OpenLDAP questions? It's kinda Linux-related so I figured I'd start here

This is probably the best thread, so fire away.

ewe2 posted:

Anyone got a recommendation for a web interface to a linux-based router that I want to run headless? It's a debian box, apache/nginx either one is fine. I'd like to manage the usual things, networking, dns, postfix etc.

What exactly do you want to do with this? I was going to suggest VyOS but you kinda lost me with postfix. What is your router doing sending mail.

If you just want a GUI to All The Things, you could do worse than Webmin

# ? Oct 1, 2016 01:21

Odette: Mar 19, 2011

Keito posted:

Everyone in these threads furiously masturbate to CentOS and openSUSE and will jump in to throw a jab towards Arch at any opportunity. LibreOffice just Works For Me� to be honest, maybe start off with using a non-poo poo desktop environment like Xfce if you gotta have one.

Eh. I use Arch and I don't mind it. I just hate how elitist & openly hostile the community is.

# ? Oct 1, 2016 01:42

ewe2: Jul 1, 2009

Docjowles posted:

What exactly do you want to do with this? I was going to suggest VyOS but you kinda lost me with postfix. What is your router doing sending mail.

If you just want a GUI to All The Things, you could do worse than Webmin

Not using postfix on the router, but I wanted the support for another box which does. I went with webmin anyway, I just wanted to canvass other options.

# ? Oct 1, 2016 02:50

Toalpaz: Mar 20, 2012; Peace through overwhelming determination

Bourricot posted:

I don't think LibreOffice is compatible with Wayland yet. Do you still have those issues if you use Gnome with an Xorg session ?

Hey Bourricot! You're really on point with your help!

So long story shorter; when I first installed arch I couldn't use the tap to click function on my touch pad. This led to me frantically searching for fixes half assedly reading through various guides and pages on the wikis. I installed a bad systemd.conf.whatever file in /etc/X11 which may have been loving with something. It appeared on my error list when running startx. However I also had permission errors trying to run startx first while I was already on the Gnome with Wayland session! So I had to add a file in /etc/X11 > Xwrapper.config.txt > with the text as :"allowed_users=anybody". I have no idea whether I deleted this file by accident or from the start have only been using Gnome with Wayland or what have you.

When you mentioned it wasn't compatible with Wayland, you set me off on that long journey. Now I've cleaned up my directories of that useless poo poo (that I shitted up my computer with) that was probably breaking Xorg. Thanks! Sorry it was such a simple mistake, laughable in hindsight.

# ? Oct 1, 2016 04:47

Tad Naff: Jul 8, 2004; _{I told you you'd be sorry buying an emoticon, but no, you were hung over. Well look at you now. It's not catching on at all!}

So, I have a couple of VMs on a university-hosted VMware whatsit. I am refreshing a "repository" by moving it into the VMware, which has gone well for itself (Ubuntu 14.04, I forgot to say). The thing is, we've built a lot of things that depend on the files in the repository and these things generally access those files via NFS.

So I reconfigured a test instance of one of these dependent apps to use the new repository machine and everything looked good, which I was expecting since now they're not even on separate VLANs. However! after a bit of use the client's NFS mount hangs. It comes back eventually, but it's very sporadic and I don't see anything telling in the logs. I am about done Googling and now I lay my problem down here. I can supply whatever diagnostics, but before I do that I'm hoping someone knows about the dumb thing I haven't found yet that will make it work.

# ? Oct 1, 2016 04:52

Tigren: Oct 3, 2003

Toalpaz posted:

Hey Bourricot! You're really on point with your help!

So long story shorter; when I first installed arch I couldn't use the tap to click function on my touch pad. This led to me frantically searching for fixes half assedly reading through various guides and pages on the wikis. I installed a bad systemd.conf.whatever file in /etc/X11 which may have been loving with something. It appeared on my error list when running startx. However I also had permission errors trying to run startx first while I was already on the Gnome with Wayland session! So I had to add a file in /etc/X11 > Xwrapper.config.txt > with the text as :"allowed_users=anybody". I have no idea whether I deleted this file by accident or from the start have only been using Gnome with Wayland or what have you.

When you mentioned it wasn't compatible with Wayland, you set me off on that long journey. Now I've cleaned up my directories of that useless poo poo (that I shitted up my computer with) that was probably breaking Xorg. Thanks! Sorry it was such a simple mistake, laughable in hindsight.

This is what Linux on the desktop was 5-10 years ago. It doesn't have to be this way.

# ? Oct 1, 2016 04:57

Toalpaz: Mar 20, 2012; Peace through overwhelming determination

Tigren posted:

This is what Linux on the desktop was 5-10 years ago. It doesn't have to be this way.

This time it's probably my fault, I dunno if I can keep this up if stuff like this keep happening.

# ? Oct 1, 2016 05:04

Buttcoin purse: Apr 24, 2014

Toalpaz posted:

sorry I'm using Arch and making GBS threads up the thread with my problems.

You never need to apologize for posting comedy on the comedy forums.

Sorry for laughing at you though. This is also educational, and not just in a "reasons not to use Arch" way - I never realized "doesn't work well with Wayland yet" was a thing as I got sick of being on the bleeding edge. I expect all the problems with it will be ironed out by the time Red Hat unleashes it on us CentOS users :flashfap:

# ? Oct 1, 2016 05:23

evol262: Nov 30, 2010; #!/usr/bin/perl

Buttcoin purse posted:

You never need to apologize for posting comedy on the comedy forums.

Sorry for laughing at you though. This is also educational, and not just in a "reasons not to use Arch" way - I never realized "doesn't work well with Wayland yet" was a thing as I got sick of being on the bleeding edge. I expect all the problems with it will be ironed out by the time Red Hat unleashes it on us CentOS users

8, maybe. Last I checked, it's still not the default in Fedora. But maybe it is on Intel

The Merlotdown posted:

So, I have a couple of VMs on a university-hosted VMware whatsit. I am refreshing a "repository" by moving it into the VMware, which has gone well for itself (Ubuntu 14.04, I forgot to say). The thing is, we've built a lot of things that depend on the files in the repository and these things generally access those files via NFS.

So I reconfigured a test instance of one of these dependent apps to use the new repository machine and everything looked good, which I was expecting since now they're not even on separate VLANs. However! after a bit of use the client's NFS mount hangs. It comes back eventually, but it's very sporadic and I don't see anything telling in the logs. I am about done Googling and now I lay my problem down here. I can supply whatever diagnostics, but before I do that I'm hoping someone knows about the dumb thing I haven't found yet that will make it work.

Are the clients also virtualized? Hard mount or soft mount?

# ? Oct 1, 2016 05:57

Tad Naff: Jul 8, 2004; _{I told you you'd be sorry buying an emoticon, but no, you were hung over. Well look at you now. It's not catching on at all!}

evol262 posted:

Are the clients also virtualized? Hard mount or soft mount?

Yep, it's all virtual. I've tried both hard and soft.

# ? Oct 1, 2016 06:06

IAmKale: Jun 7, 2007; やらないか; Fun Shoe

Docjowles posted:

This is probably the best thread, so fire away.

So I spun up this OpenLDAP Docker container to play around with LDAP authentication, and I was able to get it up and running with no issue. I created a mock OU and user and assigned a password to the user:

The issue I'm having is that, while I'm able to BIND no problem as uid=kale, performing a SRCH to retrieve my account information fails:

code:

ldap_1  | 57ee0c57 conn=1041 op=1 SRCH base="ou=users,dc=example,dc=org" scope=2 deref=3 filter="(&(objectClass=inetOrgPerson)(uid=kale))"
ldap_1  | 57ee0c57 conn=1041 op=1 SRCH attr=objectclass
ldap_1  | 57ee0c57 conn=1041 op=1 SEARCH RESULT tag=101 err=32 nentries=0 text=

The exact same SRCH while BINDd as cn=admin is able to pull up the account just fine:

code:

ldap_1  | 57ee0c65 conn=1032 op=17 SRCH base="ou=users,dc=example,dc=org" scope=2 deref=3 filter="(&(objectClass=inetOrgPerson)(uid=kale))"
ldap_1  | 57ee0c65 conn=1032 op=17 SRCH attr=objectclass
ldap_1  | 57ee0c65 conn=1032 op=17 SEARCH RESULT tag=101 err=0 nentries=1 text=

It's almost like there's an extra step I need to take to enable users to SRCH for their own LDAP entry. Is there some fundamental "permission" I need to enable before objects can SRCH themselves?

# ? Oct 1, 2016 06:57

kujeger: Feb 19, 2004; OH YES HA HA

wayland is default on fedora 25 (alpha). It works mostly okay, with some annoying issues and problems (at least from my experience). Not sure if they are gnome's implementation or wayland itself though.
Personally I would probably not recommend it as a default yet, but I see the point of giving it more exposure.

I should probably make some bugreports..

# ? Oct 1, 2016 09:57

kujeger: Feb 19, 2004; OH YES HA HA

IAmKale posted:

So I spun up this OpenLDAP Docker container to play around with LDAP authentication, and I was able to get it up and running with no issue. I created a mock OU and user and assigned a password to the user:

The issue I'm having is that, while I'm able to BIND no problem as uid=kale, performing a SRCH to retrieve my account information fails:
code:
ldap_1  | 57ee0c57 conn=1041 op=1 SRCH base="ou=users,dc=example,dc=org" scope=2 deref=3 filter="(&(objectClass=inetOrgPerson)(uid=kale))"
ldap_1  | 57ee0c57 conn=1041 op=1 SRCH attr=objectclass
ldap_1  | 57ee0c57 conn=1041 op=1 SEARCH RESULT tag=101 err=32 nentries=0 text=
The exact same SRCH while BINDd as cn=admin is able to pull up the account just fine:
code:
ldap_1  | 57ee0c65 conn=1032 op=17 SRCH base="ou=users,dc=example,dc=org" scope=2 deref=3 filter="(&(objectClass=inetOrgPerson)(uid=kale))"
ldap_1  | 57ee0c65 conn=1032 op=17 SRCH attr=objectclass
ldap_1  | 57ee0c65 conn=1032 op=17 SEARCH RESULT tag=101 err=0 nentries=1 text=
It's almost like there's an extra step I need to take to enable users to SRCH for their own LDAP entry. Is there some fundamental "permission" I need to enable before objects can SRCH themselves?

There are Access Control systems that dictate stuff like this. A common one is one that gives users the right to read their own object.

# ? Oct 1, 2016 10:01

Odette: Mar 19, 2011

kujeger posted:

wayland is default on fedora 25 (alpha). It works mostly okay, with some annoying issues and problems (at least from my experience). Not sure if they are gnome's implementation or wayland itself though.
Personally I would probably not recommend it as a default yet, but I see the point of giving it more exposure.

I should probably make some bugreports..

NVIDIA's hosed Wayland's uptake with their EGL streams vs. GBM.

# ? Oct 1, 2016 10:06

kujeger: Feb 19, 2004; OH YES HA HA

Odette posted:

NVIDIA's hosed Wayland's uptake with their EGL streams vs. GBM.

apparently there were fruitful discussions about creating a third alternative at the last XDC so uuuuh the future might be better???

# ? Oct 1, 2016 10:13

Double Punctuation: Dec 30, 2009; Ships were made for sinking;
Whiskey made for drinking;
If we were made of cellophane
We'd all get stinking drunk much faster!

kujeger posted:

apparently there were fruitful discussions about creating a third alternative at the last XDC so uuuuh the future might be better???

The future five years from now. From what I understand, NVIDIA's drivers are essentially a wrapper around the Windows driver, and the Linux team can't touch the actual driver code. On the other hand, GBM is practically Linux-only, but it's what everyone else uses because it's simple.

# ? Oct 2, 2016 02:09

apropos man: Sep 5, 2016; You get a hundred and forty one thousand years and you're out in eight!

So if you use Nvidia Linux drivers the system is essentially performing an extra hop in communicating with the graphics? Linux to Windows then Windows to machine?

I didn't phrase that very eloquently, but if so, uuurgh.

# ? Oct 2, 2016 10:16

apropos man: Sep 5, 2016; You get a hundred and forty one thousand years and you're out in eight!

Last night I was messing around with luks/dm-crypt on a laptop.

This morning, when I was more awake, I notice that

code:

sudo cryptsetup luksDump /dev/<whatever>

doesn't ask for a password before dumping the header. :what:

I thought the header contained sensitive information. Surely luksDump should ask for a keyslot passphrase before dumping the header, like it does with adding or deleting a passphrase? :-/

# ? Oct 2, 2016 11:00

evol262: Nov 30, 2010; #!/usr/bin/perl

apropos man posted:

So if you use Nvidia Linux drivers the system is essentially performing an extra hop in communicating with the graphics? Linux to Windows then Windows to machine?

I didn't phrase that very eloquently, but if so, uuurgh.

No, and this wouldn't be possible.

However, nvidia ships a "binary blob" as well as their own opengl libraries. Nobody can document how the driver works (or I've never spoken to anybody who does), but oblique comments from people who do know and can't comment due to NDA basically infer that the core parts of the driver (hardware initialization, shaders, etc) are identical on FreeBSD, Linux, and Windows, and that the driver is just a shim to interface with the host kernel.

This is probably ok, but it means that nvidia takes forever to support new features on Linux, and that there may be some dead code paths we can't see. It'd not de novo development

# ? Oct 2, 2016 16:09

telcoM: Mar 21, 2009; Fallen Rib

apropos man posted:

code:
sudo cryptsetup luksDump /dev/<whatever>
doesn't ask for a password before dumping the header.

I thought the header contained sensitive information. Surely luksDump should ask for a keyslot passphrase before dumping the header, like it does with adding or deleting a passphrase? :-/

The sensitive bit would be the device master key. Unless you specify the "--dump-master-key" option, the master key will be omitted from the dump... and if you do specify that option, it will ask for a passphrase.

When you use "cryptsetup luksDump" without the --dump-master-key option, the information you get is only what anyone could get by hex dumping the LUKS header block from the disk and decoding it manually. Basically, all of that is information you'll legitimately need to verify the passphrase and start using the disk.

If you count any of the following as sensitive information:
* the fact that the partition is encrypted using LUKS
* the number of active keyslots
* the encryption algorithm used
* the number of iterations you'll need to run the passphrase decryption algorithm for to decrypt the master key, and the salt you need for the decryption

...then you're basically trying to hide the fact that the encrypted volume exists, and that's not something LUKS is designed to do. For that, you would need something similar to TrueCrypt and its hidden-device functionality.

# ? Oct 2, 2016 18:44

telcoM: Mar 21, 2009; Fallen Rib

jaxercracks posted:

Now that you have me looking in /lib/modules I see I have a lot of extra stuff there as well:
code:
ls /lib/modules
3.13.0-27-generic  3.13.0-33-generic  3.13.0-37-generic  4.2.0-22-generic
3.13.0-29-generic  3.13.0-34-generic  3.13.0-39-generic  4.4.0-38-generic
3.13.0-30-generic  3.13.0-35-generic  3.16.0-24-generic  4.4.0-39-generic
3.13.0-32-generic  3.13.0-36-generic  3.16.0-25-generic
I assume I can rm the unneeded directories here as well just so everything is neat?

Looks like I forgot to follow up on this. Yes, feel free to blow the unneeded ones away.

If you are using something that compiles extra modules for your kernels without using the DKMS framework, like VirtualBox 5.1, that might be the reason why these get left over: the dpkg packaging system only removes files that it originally put in, and then runs a "rmdir" operation on the respective directories. If there are any extra files in those directories, rmdir will fail and those non-package files and directories will be left as they were.

You could make a script that cleans up the extra non-DKMS modules for a particular kernel, and put the script in /etc/kernel/prerm.d to handle those automatically.
Any script you put in there will be called as:

code:

/etc/kernel/prerm.d/<your script name> <"uname -r" version string of the kernel to be removed>

# ? Oct 2, 2016 18:56

apropos man: Sep 5, 2016; You get a hundred and forty one thousand years and you're out in eight!

telcoM posted:

The sensitive bit would be the device master key. Unless you specify the "--dump-master-key" option, the master key will be omitted from the dump... and if you do specify that option, it will ask for a passphrase.

When you use "cryptsetup luksDump" without the --dump-master-key option, the information you get is only what anyone could get by hex dumping the LUKS header block from the disk and decoding it manually. Basically, all of that is information you'll legitimately need to verify the passphrase and start using the disk.

If you count any of the following as sensitive information:
* the fact that the partition is encrypted using LUKS
* the number of active keyslots
* the encryption algorithm used
* the number of iterations you'll need to run the passphrase decryption algorithm for to decrypt the master key, and the salt you need for the decryption

...then you're basically trying to hide the fact that the encrypted volume exists, and that's not something LUKS is designed to do. For that, you would need something similar to TrueCrypt and its hidden-device functionality.

Ah, yes. Cheers. It would seem that I had assumed that the output of luksDump contained the disk encryption key. From the sample here:

I'd thought that the blocks of hex were the key, but doing a dump again with '--dump-master-key' gives the real key. My lack of attention.

I started playing around with it after reading about the secondary Nuke key built into Kali Linux. It seems like a really cool function to have, but I'm not personally interested in using Kali as a daily driver as I'm not interested in pen testing.

I wonder if the Nuke function's been built into Ubuntu or if there's a general patch that can be applied to any Linux distro?

Edit: Actually. Reading about potential Nuke scenarios (i.e. Handing over a nuke passphrase to someone at border control) just opens up a whole can of worms. Silly idea. I was just being nerdy

apropos man fucked around with this message at 20:32 on Oct 2, 2016

# ? Oct 2, 2016 19:24

Odette: Mar 19, 2011

evol262 posted:

No, and this wouldn't be possible.

However, nvidia ships a "binary blob" as well as their own opengl libraries. Nobody can document how the driver works (or I've never spoken to anybody who does), but oblique comments from people who do know and can't comment due to NDA basically infer that the core parts of the driver (hardware initialization, shaders, etc) are identical on FreeBSD, Linux, and Windows, and that the driver is just a shim to interface with the host kernel.

This is probably ok, but it means that nvidia takes forever to support new features on Linux, and that there may be some dead code paths we can't see. It'd not de novo development

My next GPU is definitely not going to be NVIDIA after all the bullshit I've had to put up with in Linux.

# ? Oct 3, 2016 07:36

apropos man: Sep 5, 2016; You get a hundred and forty one thousand years and you're out in eight!

I bought an Nvidia only a couple of months ago. To go in a machine that boots Linux 90% and Windows the rest of the time. I thought they'd ironed out their drivers since the famous Torvalds "gently caress you Nvidia" rant.

# ? Oct 3, 2016 10:20

evol262: Nov 30, 2010; #!/usr/bin/perl

For all of the complaints, fglrx is/was a nightmare. It's great that AMD opened everything, and that they're now contributing to AMDGPU, but nvidia has been a safe buy for years if you wanted it to work (well) on Linux.

# ? Oct 3, 2016 15:14

telcoM: Mar 21, 2009; Fallen Rib

apropos man posted:

I wonder if the Nuke function's been built into Ubuntu or if there's a general patch that can be applied to any Linux distro?

Edit: Actually. Reading about potential Nuke scenarios (i.e. Handing over a nuke passphrase to someone at border control) just opens up a whole can of worms. Silly idea. I was just being nerdy

From what I can see here, it is just a patch to the cryptsetup utility. The patch looks like it is written for cryptsetup version 1.6.1, so if your distribution uses a different version, you might have to modify it somewhat.

And yes, giving the nuke passphrase at border control sounds like "this person is now classified as suspicious and will receive intensive security checks from this point onwards", if it causes the system to obviously fail.

# ? Oct 3, 2016 16:35

apropos man: Sep 5, 2016; You get a hundred and forty one thousand years and you're out in eight!

telcoM posted:

From what I can see here, it is just a patch to the cryptsetup utility. The patch looks like it is written for cryptsetup version 1.6.1, so if your distribution uses a different version, you might have to modify it somewhat.

And yes, giving the nuke passphrase at border control sounds like "this person is now classified as suspicious and will receive intensive security checks from this point onwards", if it causes the system to obviously fail.

I think I'll have a play with the patch in KVM (when I can reset KVM networking back to stock config and actually bridge my wireless connection to the VM!).

# ? Oct 3, 2016 16:54

CaptainSarcastic: Jul 6, 2013

apropos man posted:

I bought an Nvidia only a couple of months ago. To go in a machine that boots Linux 90% and Windows the rest of the time. I thought they'd ironed out their drivers since the famous Torvalds "gently caress you Nvidia" rant.

It's been a bad year for Nvidia drivers in general, at least as far as I can tell. I have run dual-boots with Nvidia cards for years now and this has been the worst year that I can remember, both on Windows and Linux.

# ? Oct 4, 2016 02:35

wargames: Mar 16, 2008; official yospos cat censor

I will say AMD drivers have been not terrible me this year.

# ? Oct 4, 2016 03:45

The XKCD Larper: Mar 1, 2009; by Lowtax

Posted this in YOSPOS originally, would appreciate any help, thanks.

quote:

The XKCD Larper posted:
Gnome Software does not work on my computer
The XKCD Larper posted:
I get an error box with this in it whenever I attempt to install programs from Gnome Software:
code:
Detailed errors from the package manager follow:

Failed to obtain authentication.
I'm using i3 and an otherwise stock Fedora 24 Desktop install.
Any help to get this fixed would be appreciated, every time something is in Gnome Software I have to just not get it and do it through the terminal

# ? Oct 6, 2016 00:24

evol262: Nov 30, 2010; #!/usr/bin/perl

Does PackageKit work?

# ? Oct 6, 2016 04:07

The XKCD Larper: Mar 1, 2009; by Lowtax

I'm a complete retard when it comes to Linux's underpinnings. If you have a suggestion for something to try, I'm going to need an example command.

# ? Oct 6, 2016 13:30

evol262: Nov 30, 2010; #!/usr/bin/perl

Try "pkcon install foo"

# ? Oct 6, 2016 13:57

hooah: Feb 6, 2006; WTF?

I'm learning a new environment at work that uses GNU bash 3.2.25(1) on RHEL. Occasionally, I'll hit some key that makes bash go into a weird mode where typing isn't normal. It's maybe vi-like, but I can't say for sure. Does anyone know what I'm doing to trigger this mode and what I can do to get out of it? Ideally I'd like to disable that key command, but that probably isn't possible due to permissions.

# ? Oct 6, 2016 18:19

Adbot: ADBOT LOVES YOU

# ? Apr 24, 2024 19:26

evol262: Nov 30, 2010; #!/usr/bin/perl

Without knowing what key combination you hit or how it behaves, this question is unanswerable.

I don't think you accidentally typed "set -o vi", so...

# ? Oct 6, 2016 19:30

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Linux Questions Thread: a bunch of pitfalls, but technically it's possible

«‹›1025 »