Re: SSH_AUTH_SOCK behavior is completely insane

[Eric Griffith]

This is not just Fedora specific behavior. I ran into this a few days ago on a 
Mac after adding a bunch of keys to my agent (one per AWS region). Even if you 
specify a key with “-i” it will still go for the agent, resulting in an Auth 
failure. Not sure if specifying a key in the config will over ride it though, I 
didn’t try that. 

The fact that SSH prioritizes the agent over a manually specified key 
definitely smells like an upstream bug though. That’s not just counter 
intuitive that’s a blatant disregard of an explicit command specified by the 
user. 

Cheers!
Eric

> On Nov 22, 2017, at 19:33, Todd Zullinger  wrote:
> 
> Tom Horsley wrote:
>>> On Thu, 23 Nov 2017 00:06:11 +0100 cen wrote:
>>> 
>>> Anyone doing linux admin or dev work has more than 5 keys in their .ssh 
>>> directory, rendering the agent completely USELESS PIECE OF SHIT PROGRAM.
>> 
>> Why? I do lots of linux admin work and I only have two keys. 
> 
> I use a different key for each organization I'm working for/with.  I have a 
> personal key, one for Fedora packaging, one for github, another for 
> bitbucket, and several for different companies where I perform admin work.
> 
> You can certainly use one or two keys for all of that, but I don't think it's 
> the best practice to do so.  Not everyone feels the same, but it's far from 
> unusual to have quite a few keys.
> 
> -- 
> Todd
> ~~
> If people are good only because they fear punishment, and hope for
> reward, then we are a sorry lot indeed.
>   -- Albert Einstein
> 
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: gnome-shell favourites integration on fedora 25

[Eric Griffith]

Last time this came up, it was because the running LibreOffice binary name 
doesn't match the application name that was added to the dock. I think a fix 
has to come from LibreOffice's / LO's packager. 

Cheers!
Eric

> On Dec 26, 2016, at 16:11, Anca Tibor Attila  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hi,
> 
> has anybody got the same problem? I added the LibreOffice-Writer icon to
> gnome-shell favourites, but if I start the Writer it generates a new
> icon looking like some icon for gnome-terminal. I already had this
> problem a couple of years ago, as gnome-shell was still young.
> 
> Is this now a wayland issue? Otherwise, f25 is great, thanks!
> - -- 
> 
> Tibor
> 
> I use OpenSource!
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQEcBAEBCAAGBQJYYYd6AAoJEFPx1OiomcqwvPkH/jto00OTrAZgcimSEgofy2+y
> QRQmK0LCKDnqGZ2OPwtuBtgyqZi1Uqt5sRmjTNgB0z8DgNjurHnd531iX7ZLrzBJ
> 5LTAiT/81KUbAO9u164F+MMqvikA1keBD0uOZv0q3GQuUch7HViZWl9EZ929ilqi
> wlfZkblPc3yCuF2YdtaR5RsRE46HREPpt1gkWdvz6XKRmpGW76lYU8bEtY9MIwXi
> q3TFeJr+kQjAveZpDWNlqoq5kmVn98+iri2isCIUeb//c1YGwt5CMaE2oODpjLGm
> TDDoJSWNldVYfX6ZsAKS1yvqh7PPjPrp5TLvWHOu0FGjCYMZfbGrC2NllsC4KjE=
> =XtVT
> -END PGP SIGNATURE-
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: disk monopolized?

[Eric Griffith]

On a related note, did the kernel devs ever fix the bug where high I/O
would make the system basically unusable? This sounds a lot like that, but
I thought stuff like blk-mq were supposed to fix it.

On Sun, Dec 11, 2016 at 1:13 PM, jd1008  wrote:

>
>
> On 12/11/2016 06:08 AM, Tom Horsley wrote:
>
>> Last night I was "optimizing" a qcow2 virtual image
>> (after zero filling the free space), running (as root):
>>
>> qemu-img convert -f qcow2 -O qcow2 old.img new.img
>>
>> The copying and scanning for zero blocks pretty
>> much took over the disk. Anything else I tried to run
>> which needed access to something on that disk would
>> hang for minutes at a time before getting through.
>>
>> Is that normal behavior? I thought folks were supposed
>> to take turns and play nice together :-).
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>
> So "qcow2 old.img" is on the file system you want other apps to access,
> and so is  "new.img" ? this sounds like "as if" qemu-img wants to make sure
> that the two images, old and new, will not be modified during the
> conversion
> process. Since you ARE running as root, you have the privs to run the
> conversion
> at a very high priority that, for most of the time, it is picked first off
> the run queue
> and placed on cpu, and "might" even be inhibiting access to the filesystem
> hosting
> the 2 images during the conversion.
>
> Now this is all conjecture on my part as I have never used it.
>
> Other issues might be
> 1. The drive is a very slow drive
>  and/or
> 2. You do not have sufficient ram for buffering large amounts of data
> and/or
> 3. You do not have multiple cores for other threads to run on different
> cores.
>
> One of the ways to really debug this is to scan the source code of
> qemu-img to
> see what priority it tries to give itself, what read/write/ioctl
> operations it is performing
> and look up the man pages on those operations to see if they are being
> performed
> in a manner that the process (in the kernel) spins idly while waiting for
> the operation
> to finish, and also scan the kernel to see if the huge FS spinlock is held
> during the entire
> conversion operation.
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Firewall methods for fedora25

[Eric Griffith]

I don't use fail2ban, so I can't vouch that these instructions work. That
being said, a quick google search of "firewalld fail2ban" led me to the
very first search result of:
https://fedoraproject.org/wiki/Fail2ban_with_FirewallD


Do those instructions work?

On Fri, Nov 25, 2016 at 8:31 PM, Alex  wrote:

> Hi,
>
> I'm most familiar and comfortable with iptables, and use shorewall on
> my firewalls. With fedora23, it appears the default has shifted to
> firewalld. This has created a problem for me ever since, particularly
> with trying to build a reasonable firewall on my mail servers, as well
> as interacting with fail2ban.
>
> We typically offer submission, simap/spop, smtp, http/https, ssh, and
> domain services on our Internet servers. We also need snmp and nrpe
> for monitoring.
>
> Does anyone have a set of reasonable firewalld rules and understand
> how it interacts with fail2ban that they could share? firewalld
> doesn't even include all these services by default, so it's necessary
> to do it one port at a time...
>
> firewalld just doesn't seem to be appropriate for anything more than a
> desktop. I'd appreciate any ideas on how you build a firewall for
> fedora servers, particularly as it relates to interoperating with
> fail2ban and standard Internet services.
>
> Thanks,
> Alex
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Redshift and Dropbox not quite working after F24-F25 upgrade

[Eric Griffith]

Not sure about Dropbox, but RedShift is a known issue. Redshift's model doesn't 
work under Wayland, the default session in F25. The same idea as RedShift has 
been / is working on being integrated into upstream Gnome and will work its way 
down to users in a future update. It still works under X, however.

You can go back to using X by logging out, and hitting the gear next to the 
"login" button. From there, hit "Gnome on Xorg" and login. 

Cheers!
Eric

> On Nov 25, 2016, at 12:39, Matthew Saltzman  wrote:
> 
> I have two GNOME workstations upgraded from F24 to F25. Before the
> upgrade, Dropbox and Redshift were accessible from the little slide-out 
> task bar at the lower left of the screen. Now, on one I see Dropbox but
> not Redshift and on the other, I don't have the slide-out drawer at
> all. According to GNOME Tweak-Tool, both apps are listed on the startup
> panel.
> 
> So far, everything else seems to have gone smoothly.
> 
> How to debug?  TIA.
> -- 
> Matthew Saltzman
> Clemson University Math Sciences
> mjs AT clemson DOT edu
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Taking a screenshot in GNOME desktop during a pulldown menu is open. How to?

[Eric Griffith]

Not sure about a GUI screenshot program, but you can call gnome-screenshot from 
terminal and it has a flag to wait X number of seconds. This would let call it, 
open the menu, and just wait the second or two after the menu opens for the 
screenshot to happen.

Cheers!
Eric

> On Oct 23, 2016, at 06:35, fred roller  wrote:
> 
> fyi, should be able set timer using screen shot program in accessories or 
> some such. This would allow you to set "stage".
> 
> Fred Roller
> 
> 
>> On Oct 23, 2016 5:32 AM, "Patrick O'Callaghan"  wrote:
>> On Sun, 2016-10-23 at 11:20 +0200, Joachim Backes wrote:
>> > Hi all,
>> > having a problem: I need to take a screenshot on the gnome desktop (no
>> > wayland!)with alt+print or shift+print keys, during some pulldown menu
>> > of some window is opened,  but nothing happens. How can I achive this?
>> > The pulldown menu should be included in the screenshot. The screenshot
>> > is performed flawlessly if the pulldown menu is closed.
>> >
>> > It seems that this is a X11 problem.
>> >
>> > All comments are welcome.
>> >
>> > Kind regards
>> >
>> > Joachim Backes
>> 
>> Your signature says you have F25. If so, then you're on the wrong list.
>> Unreleased systems should be discussed on the Fedora Test list.
>> 
>> poc
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: New(er) kernel RPMs?

[Eric Griffith]

You can always just setup the RawhideNoDebug repo, check the wiki.

Cheers!
Eric

> On Oct 17, 2016, at 22:10, Frederic Muller  wrote:
> 
>> On 10/18/2016 08:56 AM, Michael B Allen wrote:
>> I just got a Dell Latitude E7470. Mostly works with the latest Fedora live.
>> 
>> However, attaching an external monitor to the HDMI port hangs the
>> machine. I've been using Linux as my primary machine long enough to
>> know that it smells very much like a driver issue and that the only
>> way I'm going to get it to work is to try a newer kernel. So ...
>> 
>> Are there any vaguely official RPMs for new(er) kernels?
>> 
>> If not, what is the path-of-least-resistance for building a new(er)
>> kernel? I can google as well as anybody but if there's a definitive
>> way, I would appreciate any pointers.
>> 
>> Mike
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> 
> 
> Hi!
> 
> I've had a similar problem since Kernel 4.6.7 where any external screen
> would not be detected. It now only occurs only with my TV. In those
> instances where I want to use the TV I use Kernel 4.5.5. I filled a bug
> which hasn't gotten much attention here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1378686
> 
> Oh... and I have an Intel HD Graphics 5500.
> 
> If that helps.
> 
> Fred
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Google Chrome always asking me to enter the password to unlock my login keyring

[Eric Griffith]

Do you have autologin enabled? KDE or Gnome?

On Sep 9, 2016 09:48, "Paul Smith"  wrote:

> Dear All,
>
> Whenever I start Google Chrome, pops up a box asking me to enter the
> password to unlock my login keyring.
>
> Does somebody know how to get rid of this annoying box pop up?
>
> Thanks in advance,
>
> Paul
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Upgrade, what to do -

[Eric Griffith]

On Jul 5, 2016 12:45, "Rick Stevens"  wrote:
>
> On 07/03/2016 09:46 AM, Bob Goodwin wrote:
> > On 07/03/16 10:41, Ed Greshko wrote:
> >>
> >> On 07/03/16 21:53, Bob Goodwin wrote:
> >>> I ran "# dnf system-upgrade download --refresh --releasever=24
> >>> --allowerasing" earlier
> >>> this morning and got the following error message:
> >>>
> >>>   snip  ..
> >>>installing package nss-softokn-freebl-3.24.0-1.0.fc24.i686 needs
> >>> 1503MB on the /
> >>> filesystem
> >>>installing package glibc-2.23.1-8.fc24.i686 needs 1517MB on the /
> >>> filesystem
> >>>installing package compat-libvpx1-1.3.0-4.fc24.i686 needs 1511MB
> >>> on the / filesystem
> >>>
> >>> Error Summary
> >>> -
> >>> Disk Requirements:
> >>> At least 1598MB more space needed on the / filesystem.
> >>>
> >>> Obliviously / is near full.
> >>>
> >>> [root@Box10 bobg]# df -h
> >>> Filesystem  Size  Used Avail Use% Mounted on
> >>> devtmpfs3.7G 0  3.7G   0% /dev
> >>> tmpfs   3.7G  768K  3.7G   1% /dev/shm
> >>> tmpfs   3.7G  1.3M  3.7G   1% /run
> >>> tmpfs   3.7G 0  3.7G   0% /sys/fs/cgroup
> >>> /dev/sda350G   48G 0 100% /
> >>> tmpfs   3.7G  208K  3.7G   1% /tmp
> >>> /dev/sdc1   230G  6.6G  211G   4% /home2
> >>> /dev/sda2   173G  135G   30G  83% /home
> >>> /dev/sda1   477M  166M  282M  38% /boot
> >>> 192.168.1.8:/home   818G  574G  203G  74% /mnt/DATA1
> >>> //192.168.1.48/myshare  686G  217G  435G  34% /mnt/box48
> >>> tmpfs   748M   12K  748M   1% /run/user/1000
> >>>
> >>> Where can I look to delete a few files, will anything in root help or
> >>> do I have to be
> >>> more specific? Better yet, how to fix this? It looks like I could
> >>> take some space from
> >>> "home", home2 is another hard drive with some backup files on it.
> >>>
> >> Well, your / file system is pretty full.  You should investigate what
> >> is taking up the
> >> space.  /var/log and /var/cache are places to investigate.
> >>
> >> Just as a point of reference.  2 of my most heavily used and system
> >> with excessive
> >> installs show:
> >>
> >> Filesystem   Size  Used Avail Use% Mounted on
> >> /dev/mapper/fedora-root   50G   17G   34G  33% /
> >>
> >> and
> >>
> >> FilesystemSize  Used Avail Use% Mounted on
> >> /dev/sda2  48G   20G   27G  43% /
> >>
> >>
> >>
> > +
> >
> > It looks like the problem was the VM's. I will have to put them
> > somewhere else. / must have been the default?
>
> If you are using libvirt and qemu, then typically VM disk images end up
> in /var/lib/libvirt/images, but you can stick them wherever you want
> when you create them or move them and change the XML files in
> /etc/libvirt/qemu.

Symlinking works fine too, though I had to do a restorecon on
/var/lib/libvirt/images after making the link.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: GDM fails to load mesa-dri-drivers

[Eric Griffith]

On Jun 22, 2016 13:05, "Samuel Sieb" <sam...@sieb.net> wrote:
>
> On 06/22/2016 09:31 AM, Eric Griffith wrote:
>>
>> ldd /usr/lib64/xorg/modules/extensions/libglx.so
>>
>> libGL.so.1 => /usr/lib64/libglvnd/libGL.so.1 (0x7f5d15e9e000)
>> libGLX.so.0 => /usr/lib64/libglvnd/libGLX.so.0 (0x7f5d15172000)
>> libGLdispatch.so.0 => /usr/lib64/libglvnd/libGLdispatch.so.0
>> (0x7f5d14949000)
>>
> It's picking up the wrong libraries.
> Try "rpm -qf /usr/lib64/libglvnd/libGL.so.1" to see if anything owns it.
If yes, then remove the owning package, otherwise just remove the
directory.  Then check in /etc/ld.so.conf.d for any reference to the
/usr/lib64/libglvnd directory.  Remove the referencing file, then run
ldconfig.  You should be ok after that.

That fixed it. Libglvnd was the problem package (third party repo),
unfortunately now I need to untangle the mess of dependencies because
trying to remove libglvnd wants to rip out things like Totem and parts of
gstreamer. But that I can figure out on my own.

>
>> and dnf history
>>
>> 56 | remove nvidia-*  | 2016-06-21 22:40 | Erase
>> |1
>
>
> You had the nvidia proprietary drivers installed?  That would explain the
breakage.
>

Not quite. A package pulled in the nvidia-cuda-libs, but I was able to
remove only nvidia-cuda-libs without it pulling anything else, so I'm
chalking that up to a packaging bug.

Thanks for the assistance, Samuel. Much appreciated.

> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: GDM fails to load mesa-dri-drivers

[Eric Griffith]

On Wed, Jun 22, 2016 at 1:43 AM, Samuel Sieb <sam...@sieb.net> wrote:

> On 06/21/2016 10:01 PM, Eric Griffith wrote:
>
>> I was using my system earlier tonight, trying to get a couple games
>> working in wine. Everything was fine.. until I ran PlayOnLinux. It
>> errored out with saying it couldn't find any OpenGL drivers for my
>> laptop (Intel Broadwell). Thought it was odd, but nothing was freaking
>> out, so I didn't think anything of it. Saw some updates come up,
>> updated, rebooted, and everything went to hell.
>>
>> Doesn't PlayOnLinux install various bits and change settings?
>
> AIGLX error dlopen (path to i915_dri.so, and swrast) undefined symbol
>> _glapi_get_dispatch_table_size & _glapi_set_dispatch
>>
>> Can you copy and paste the exact error message?
>
> Other than going back and undoing a few days worth of dnf operations one
>> by one and seeing which one actually broke things, does anyone have any
>> ideas? I can't imagine that this something specific to my system because
>> that kind of error makes me think that something broke API/ABI
>>
>> What is the output of the following commands:
> ldd /usr/lib64/dri/i915_dri.so
>

linux-vdso.so.1 (0x7ffe5d9fd000)
libdrm_intel.so.1 => /lib64/libdrm_intel.so.1 (0x7feb0a25d000)
libdrm_nouveau.so.2 => /lib64/libdrm_nouveau.so.2 (0x7feb0a054000)
libdrm_radeon.so.1 => /lib64/libdrm_radeon.so.1 (0x7feb09e48000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x7feb09c21000)
libdrm.so.2 => /lib64/libdrm.so.2 (0x7feb09a12000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x7feb097e5000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7feb095c9000)
libdl.so.2 => /lib64/libdl.so.2 (0x7feb093c5000)
libm.so.6 => /lib64/libm.so.6 (0x7feb090ba000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7feb08ea3000)
libc.so.6 => /lib64/libc.so.6 (0x7feb08ae1000)
/lib64/ld-linux-x86-64.so.2 (0x55c8ad141000)
libpciaccess.so.0 => /usr/lib64/libpciaccess.so.0 (0x7feb088d6000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x7feb08663000)



> ldd /usr/lib64/dri/swrast_dri.so
>

linux-vdso.so.1 (0x7ffc18df8000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x7f5795f8f000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f5795d73000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f5795b6e000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x7f5795942000)
libdrm_intel.so.1 => /lib64/libdrm_intel.so.1 (0x7f5795721000)
libdrm_nouveau.so.2 => /lib64/libdrm_nouveau.so.2 (0x7f5795518000)
libdrm_radeon.so.1 => /lib64/libdrm_radeon.so.1 (0x7f579530c000)
libdrm_amdgpu.so.1 => /lib64/libdrm_amdgpu.so.1 (0x7f5795104000)
libdrm.so.2 => /lib64/libdrm.so.2 (0x7f5794ef4000)
libelf.so.1 => /lib64/libelf.so.1 (0x7f5794cdc000)
libLLVM-3.8.so => /lib64/libLLVM-3.8.so (0x7f5792668000)
libm.so.6 => /lib64/libm.so.6 (0x7f579235d000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f5792146000)
libc.so.6 => /lib64/libc.so.6 (0x7f5791d84000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x7f5791b1)
/lib64/ld-linux-x86-64.so.2 (0x55727c487000)
libpciaccess.so.0 => /usr/lib64/libpciaccess.so.0 (0x7f5791906000)
libz.so.1 => /lib64/libz.so.1 (0x7f57916ef000)
libffi.so.6 => /lib64/../lib64/libffi.so.6 (0x7f57914e7000)
librt.so.1 => /lib64/../lib64/librt.so.1 (0x7f57912df000)



> ldd /usr/lib64/xorg/modules/extensions/libglx.so
>

linux-vdso.so.1 (0x7ffd476f9000)
libGL.so.1 => /usr/lib64/libglvnd/libGL.so.1 (0x7f5d15e9e000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f5d15c9a000)
libaudit.so.1 => /lib64/libaudit.so.1 (0x7f5d15a71000)
libm.so.6 => /lib64/libm.so.6 (0x7f5d15767000)
libc.so.6 => /lib64/libc.so.6 (0x7f5d153a5000)
libGLX.so.0 => /usr/lib64/libglvnd/libGLX.so.0 (0x7f5d15172000)
libX11.so.6 => /lib64/libX11.so.6 (0x7f5d14e32000)
libXext.so.6 => /lib64/libXext.so.6 (0x7f5d14c2)
libGLdispatch.so.0 => /usr/lib64/libglvnd/libGLdispatch.so.0
(0x7f5d14949000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f5d1472d000)
/lib64/ld-linux-x86-64.so.2 (0x55adcdb2b000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x7f5d1450a000)
libXau.so.6 => /lib64/libXau.so.6 (0x7f5d14306000)

and dnf history

60 | remove flatpak-libs  | 2016-06-22 12:18 | Erase  |
12
59 | history undo 47  | 2016-06-22 02:14 | Erase  |
14
58 | distro-sync --nogpgcheck | 2016-06-21 23:20 | Update |
2
57 | reinstall mesa-libGL | 2016-06-21 23:14 | Reinstall  |
2
56 | remove nvidia-*

Re: GDM fails to load mesa-dri-drivers

[Eric Griffith]

On Jun 22, 2016 01:45, "Samuel Sieb" <sam...@sieb.net> wrote:
>
> On 06/21/2016 10:01 PM, Eric Griffith wrote:
>>
>> I was using my system earlier tonight, trying to get a couple games
>> working in wine. Everything was fine.. until I ran PlayOnLinux. It
>> errored out with saying it couldn't find any OpenGL drivers for my
>> laptop (Intel Broadwell). Thought it was odd, but nothing was freaking
>> out, so I didn't think anything of it. Saw some updates come up,
>> updated, rebooted, and everything went to hell.
>>
> Doesn't PlayOnLinux install various bits and change settings?
>

PlayOnLinux installs...

Cabextract, gstreamer, iconutils, libXaw, p7zip, wxGTK3, wzBase3, wxPython,
and xterm. None of which shouts "Let's break mesa!" to me. Not sure on what
settings it might change.

Just to test, I undid the PlayOnLinux install, and gdm still crashes on
boot.

>
>> AIGLX error dlopen (path to i915_dri.so, and swrast) undefined symbol
>> _glapi_get_dispatch_table_size & _glapi_set_dispatch
>>
> Can you copy and paste the exact error message?

Copy paste is hard until I can SSH in tomorrow.

/usr/libexec/gdm-x-session AIGLX error: dlopen of
/usr/lib64/dri/i915_dri.so failed (/usr/lib64/dri/i915_dri.so: undefined
symbol: _glapi_get_dispatch_table_size)

swrast is the same folder, but the undefined symbol is:  _glapi_set_dispatch

>
>> Other than going back and undoing a few days worth of dnf operations one
>> by one and seeing which one actually broke things, does anyone have any
>> ideas? I can't imagine that this something specific to my system because
>> that kind of error makes me think that something broke API/ABI
>>
> What is the output of the following commands:
> rpm -q mesa-dri-drivers

32 and 64 bit, version 11.2.2.-2.20160614.fc24

> ldd /usr/lib64/dri/i915_dri.so
> ldd /usr/lib64/dri/swrast_dri.so
> ldd /usr/lib64/xorg/modules/extensions/libglx.so

Will respond with ldd when I can SSH in.
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

GDM fails to load mesa-dri-drivers

[Eric Griffith]

Hey guys and gals. I'm at my wit's end on this one...

I was using my system earlier tonight, trying to get a couple games working
in wine. Everything was fine.. until I ran PlayOnLinux. It errored out with
saying it couldn't find any OpenGL drivers for my laptop (Intel Broadwell).
Thought it was odd, but nothing was freaking out, so I didn't think
anything of it. Saw some updates come up, updated, rebooted, and everything
went to hell.

Now whenever I try to boot, GDM errors out

AIGLX error dlopen (path to i915_dri.so, and swrast) undefined symbol
_glapi_get_dispatch_table_size & _glapi_set_dispatch

Other than going back and undoing a few days worth of dnf operations one by
one and seeing which one actually broke things, does anyone have any ideas?
I can't imagine that this something specific to my system because that kind
of error makes me think that something broke API/ABI
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Suspend Issues or Soft Kernel Locks and no wireless; which is worse?

[Eric Griffith]

On Wed, Aug 10, 2011 at 10:00 AM, Greg Woods wo...@ucar.edu wrote:
 On Tue, 2011-08-09 at 23:24 -0400, Eric Griffith wrote:
  KDE Power Management is set that if
 I close my laptop lid, it should go into sleep mode. When I close the
 lid, I give it a few seconds to enter sleep, and then I open it back
 up. I'm met with a black screen

 Just to make sure we check the obvious and the stupid first: I also
 thought suspend was not working on my laptop, but I now find that if I
 press CTRL-ALT-F1 to switch to the main console after opening the lid,
 the password prompt screen appears, at which point I can type my
 password and the desktop appears.

 --Greg



Yeah that doesn't work haha, I tried it before. Kernel / X is totally
unresponsive to any keyboard / mouse events except for the power
button, which goes straight to the mobo anyway lol. The guys on the
KDE mailing list seemed to think it might be a kernel module for one
of my devices but we we couldn't even figure out where to start since
it could be any one of them, and suspend.log seems to think
everything's fine
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Suspend Issues or Soft Kernel Locks and no wireless; which is worse?

[Eric Griffith]

Alright so basically...suspend's not working right; bomb of information below

Laptop Model: ASUS N73JQ-X2
Kernel: 2.6.40-4.fc15.i686
Desktop Enviro: KDE 4.6.5

The last time Suspend worked with no issues was Linux Mint 10 which
had, I think, kernel 2.6.35 (with ubuntu mods).

Alright, here's what's happening: KDE Power Management is set that if
I close my laptop lid, it should go into sleep mode. When I close the
lid, I give it a few seconds to enter sleep, and then I open it back
up. I'm met with a black screen, with a blinking cursor in the top
left. Fedora (15) is non-responsive to keyboard and mouse events
(SysRQ is enabled and doesn't work, so thats out the window), only
solution is to power it down and power it back up.  Little googling
around and I'm met with a post by an owner of an ASUS N71, one
generation back. With a custom sleep script for ehci-hcd that worked
for them. Figure I'll give it a shot. Throw the script into
/etc/pm/sleep.d/, give it the necessary permissions. Reboot to make
sure it loads it, and then try sleep again.

It works!

...kinda.

Closed the lid, gave it a few seconds. Opened the lid back up, black
screen, and moved the mouse, my desktop appears a second later. I see
that knetworkmanager says I have no network; no problem, sleep always
kills the network interface before bringing it back up. Wait a second
wireless to come backits not coming back. Mouse over
knetworkmanager in the systray: ethernet + wireless = 'unmanaged.'
*blink blink* Bug report pops up! Not for knetworkmanager... CPU #0 is
having soft kernel locks, and a lot of them. More and more bug reports
kept coming in, non stop until I powered down the laptop. Looking at
Fedora's automatic bug reporting, it says CPU#0 locked up for
23seconds, followed by the name of the custom sleep script I just
added. I'm pasting the sleep script below, if anyone is familiar with
suspend / sleep and can look it over, maybe give me a few hints on
what to do

Below is the backtrace for the kernel lockups, I do have more
information related to the lockup, but since Fedora keeps a bug report
inside 20+ different files each detailing 1 and only 1 thing, I'm not
sure which is relevant and which isn't.  Also below is the script, and
pm-suspend.log

Backtrace first:


BUG: soft lockup - CPU#0 stuck for 23s! [20_custom-ehci_:3920]
Modules linked in: ebtable_nat ebtables ipt_MASQUERADE iptable_nat
nf_nat xt_CHECKSUM iptable_mangle bridge sunrpc 8021q garp stp llc
cpufreq_ondemand acpi_cpufreq mperf ip6t_REJECT nf_conntrack_ipv6
nf_defrag_ipv6 ip6table_filter ip6_tables rfcomm nf_conntrack_ipv4
nf_defrag_ipv4 xt_state nf_conntrack bnep btusb snd_hda_codec_hdmi
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq
snd_seq_device snd_pcm snd_timer snd soundcore arc4 ath9k mac80211
ath9k_common ath9k_hw ath cfg80211 bluetooth snd_page_alloc
asus_laptop sparse_keymap rfkill virtio_net kvm_intel kvm fglrx(P)
iTCO_wdt xhci_hcd iTCO_vendor_support microcode i7core_edac uvcvideo
edac_core videodev joydev atl1c media serio_raw uas usb_storage video
radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded:
scsi_wait_scan]
Modules linked in: ebtable_nat ebtables ipt_MASQUERADE iptable_nat
nf_nat xt_CHECKSUM iptable_mangle bridge sunrpc 8021q garp stp llc
cpufreq_ondemand acpi_cpufreq mperf ip6t_REJECT nf_conntrack_ipv6
nf_defrag_ipv6 ip6table_filter ip6_tables rfcomm nf_conntrack_ipv4
nf_defrag_ipv4 xt_state nf_conntrack bnep btusb snd_hda_codec_hdmi
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq
snd_seq_device snd_pcm snd_timer snd soundcore arc4 ath9k mac80211
ath9k_common ath9k_hw ath cfg80211 bluetooth snd_page_alloc
asus_laptop sparse_keymap rfkill virtio_net kvm_intel kvm fglrx(P)
iTCO_wdt xhci_hcd iTCO_vendor_support microcode i7core_edac uvcvideo
edac_core videodev joydev atl1c media serio_raw uas usb_storage video
radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded:
scsi_wait_scan]
Pid: 3920, comm: 20_custom-ehci_ Tainted: P
2.6.40-4.fc15.i686 #1 ASUSTeK Computer Inc. N71Jq/N71Jq
EIP: 0060:[c0604a29] EFLAGS: 0203 CPU: 0
EIP is at dma_pte_free_pagetable+0xcf/0x1a0
EAX: 300f EBX: 0004 ECX: 0800 EDX: 0005
ESI: 2810 EDI: f3ada428 EBP: efe49e68 ESP: efe49e38
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process 20_custom-ehci_ (pid: 3920, ti=f400e000 task=f2853280 task.ti=efe48000)
Stack:
 efe49e58 0800 0004 07ff f389c100  f3ada000 
 0004 0024 f389c100 f401f060 efe49e94 c0604fd9  
 f389c10c 0292  f401f000 f389c100 0006 f401f060 efe49ea8
Call Trace:
 [c0604fd9] domain_exit+0xc5/0x18c
 [c0605d79] device_notifier+0x58/0x5f
 [c081748f] notifier_call_chain+0x2b/0x4d
 [c045813e] __blocking_notifier_call_chain+0x40/0x52
 [c045816f] blocking_notifier_call_chain+0x1f/0x21
 [c067fda2] __device_release_driver+0x98/0x9c
 [c067fdc3] device_release_driver+0x1d/0x28
 [c067f2cb]