Re: Dell Latitude E7470 Install: Selected boot device failed

[Michael B Allen]

On Thu, Oct 13, 2016 at 10:08 PM, Michael B Allen  wrote:
> I'm trying to boot the latest Fedora Live iso on a brand new Dell and
> I'm getting:
>
>   Selected boot device failed
>
> What is the trick to getting this to boot?
>
> I just dd'd the iso on the USB drive.

Nevermind. I was able to boot from USB. There was something wrong with
the USB drive. I was using a 128GB USB 3.0 drive. I tried a lowly 8GB
drive and it worked.

No doubt I'll be back with other questions though ...

Thanks for listening.

Mike
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Dell Latitude E7470 Install: Selected boot device failed

[Michael B Allen]

I'm trying to boot the latest Fedora Live iso on a brand new Dell and
I'm getting:

  Selected boot device failed

What is the trick to getting this to boot?

I just dd'd the iso on the USB drive. Do I need to make it bootable or
some such?

I updated the BIOS to the latest. I verfied everything works as it
should under Windows. I tried playing with the BIOS settings but stuff
is mostly disabled already. I tried booting in both Legacy and UEFI
modes.

Any help would be greatly appreciated. I'm nursing a 5 year old
Toshiba with CentOS 6 and it's time to upgrade. I've been using Linux
as my primary machine since late 90's but it has been so long since I
last installed on a newish laptop I have no idea what the issues are
anymore.

Help!

Mike
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: issue with pycam

[stan]

On Thu, 13 Oct 2016 12:08:06 -0700
Howard Howell  wrote:

> > > radeon: Failed to deallocate virtual address for buffer:
> > > radeon:size  : 4096 bytes
> > > radeon:va: 0x884000
> > > Segmentation fault (core dumped)  

> Ok, I tried the previous kernel, and had no luck.  

Then, it is likely not a kernel issue.  Was the error the same?

> I just remembered that I attempted to delete a package from my system
> and it started to erase things, but I stopped it.  This may have done
> the damage.  This was a real screw-up on my part, and so I don't think
> a bugzilla is the correct action.

Did you try re-installing the package(s) that you think caused the
problem?
dnf reinstall [package]
There should be a record of them in the dnf logs (/var/log/dnf*.log)
That would put everything back the way it was before the delete (minus
any configuration customization).

> However if the Kernel is the location, is the radeon package in a
> separate file?  If it is, what could I reinstall to recover that
> driver?

The radeon driver is built into all stock Fedora kernels, so it is
always there.  And a reboot always loads it fresh, so unless it was
damaged on the disk in both kernels, it is probably not the problem.
Is it possible you have a failing hard disk?  You should be seeing
warning messages if it is.

Is it possible that the video card itself is flaky?  Is anything else
failing occasionally?  Is it really dusty?

You could try a reinstall of pycam, in case it has been damaged.  It
hasn't changed in ages, so there is no newer version to worry about.
Is there any configuration that might have been accidentally changed?

Are there any errors showing up in the logs when you try the pycam
command and it fails? You can try  dmesg  or  journalctl -r  which shows
log messages in reverse time order.

Obviously, something changed, it's just figuring out what it is.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Filesystem for backup system

[Gordon Messmer]

On 10/12/2016 03:57 PM, c...@zip.com.au wrote:

Except it the wildest scenarios, XFS fsks at mount, almost immediately.


Is that different from fsck.ext4 replaying the journal?


Go and cat (yes, cat) the fsck.xfs command.


OK.  I'm not sure what you think I'll learn by doing so.  fsck.xfs 
exists because Linux's "fsck" supports multiple filesystems and Irix's 
did not.  On Irix, fsck was exclusively for EFS.  XFS used xfs_check and 
xfs_repair.  When XFS was ported to Linux, the tools were not renamed; 
instead fsck.xfs was put in place to direct users to the correct tool 
when they ran "fsck -t xfs".


None of that makes XFS immune to corruption, nor reduce the time or the 
memory required to fix an XFS filesystem if it's damaged.


"Never" is indeed not _literally_ true, but it is effectively true, 
far far far far more than is so with ext4. Ext4 really needs fsck 
after an unclean unmount, and it is not cheap for large filesystems.


With journaling and write barriers in place, I don't know any reason 
that ext4 would be any more affected by a power loss than XFS would be, 
and having had to perform recoveries on both, I don't find one to be 
significantly better than the other.


Thus, my advice remains that users should test both because they do 
differ in performance in different workloads.  If one will be faster 
under normal operation, 99.95% of the time, and require slightly more 
down time to recover in the other .05% of the time, then selecting the 
option which is superior 99.95% of the time is a perfectly rational 
thing to do.


That's especially true of backup systems where down time does not carry 
the same impact as down time in a production system does.


The two are like night and day in the recovery scenario (== xfs pretty 
much never needs manual recovery, and recover is very fast).


That seems subjective.  I've personally had to recover more XFS 
filesystems than I have ext4 filesystems, and I use ext4 filesystems 
more often.  My subjective experience is quite different than yours.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Forward and Backward Steppers missing in Thunderbird and Possibly Firefox

[Stephen Morris]

On 11/10/16 22:23, Ahmad Samir wrote:

On 10 October 2016 at 22:47, Stephen Morris  wrote:

On 11/10/16 03:37, Ahmad Samir wrote:

On 9 October 2016 at 23:03, Stephen Morris 
wrote:

Hi,

  I'm using Thunderbird 52.0a1 and I have an issue with the forward
and
backward steppers (top and bottom arrows on scrollbars) missing. In
another
thread Tom Horsley provided a gtk-3 css script that needed to be placed
in
~/.config/gtk-3.0/gtk.css. This script rectified the missing arrows issue
when I was using KDE, but now that I am trying Gnome this script does not
appear to work, what needs to be done to get the script to work under
Gnome?


regards,

Steve


In ~/.config/gtk-3.0/gtk.css, replace:
.scrollbar {

with:
scrollbar {

that seems to work for me.

Thanks Ahmad, your suggestion works under both Gnome and KDE, which now
raises the question of why does the original format of .scrollbar { only
work under KDE and not Gnome.


It could be that you're using different GTK3 themes under KDE and
GNOME respectively. Check the output of these commands while running
GNOME:
$ grep gtk-theme ~/.config/gtk-3.0/settings.ini
$ gsettings get org.gnome.desktop.interface gtk-theme
Thanks Ahmad, I am using different themes under KDE and Gnome. In KDE 
I'm using Breeze and under Gnome I'm using the default of Adwaita.


regards,
Steve



___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

[389-users] Re: SIEM Audit Data

[Paul Robert Marino]

user authentication errors are usually recorded on the client end.

On Thu, Oct 13, 2016 at 4:47 PM, Jason Nielsen  wrote:
> Im looking for ways to pull a number of audit events from 389. Such as:
>
> -User authentication success and failures.
> -Group additions, removals and changes.
> -User additions, removals and possibly changes.
>
> Details in each of these would include items such as:
>
> username
> groupname
> attribute changed
> timestamp of event
> action
>
> Sending these out via syslog formatted messages is the preferred route.
>
> I have not been able to find anything definitive in how to do this. Debug
> logs seem to lack much of this or contain far too much information making
> the prohibitive to use. They are also formatted in such a way making it
> extremely difficult to process in any practical way. For example, you would
> probably need a full LDIF interpreter to reformat them on the fly. I assume
> I either have not dug far enough or simply digging in the wrong direction.
>
> Is anyone out there doing something similar and pulling the above data into
> a SIEM? If so would you be willing to share your experience on the topic or
> point me in the right direction?
>
> Thanks!
>
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] SIEM Audit Data

[Jason Nielsen]

Im looking for ways to pull a number of audit events from 389. Such as:

-User authentication success and failures.
-Group additions, removals and changes.
-User additions, removals and possibly changes.

Details in each of these would include items such as:

username
groupname
attribute changed
timestamp of event
action

Sending these out via syslog formatted messages is the preferred route.

I have not been able to find anything definitive in how to do this. Debug
logs seem to lack much of this or contain far too much information making
the prohibitive to use. They are also formatted in such a way making it
extremely difficult to process in any practical way. For example, you would
probably need a full LDIF interpreter to reformat them on the fly. I assume
I either have not dug far enough or simply digging in the wrong direction.

Is anyone out there doing something similar and pulling the above data into
a SIEM? If so would you be willing to share your experience on the topic or
point me in the right direction?

Thanks!
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

Re: issue with pycam

[Howard Howell]

On Sun, 2016-10-02 at 10:23 -0700, stan wrote:
> On Sun, 02 Oct 2016 09:34:52 -0700
> Howard Howell  wrote:
> 
> > 
> > Hi, everyone,
> > I use Pycam with my milling machine.  The process I follow is:
> >  design with OpenSCAD, export as DXF or STL format.
> >  Open with PYCAM and adjust settings for feedrate, speed, bit
> > size and so forth as required for the project and material.  Load
> > the
> > DXF or STL file and run one of the tool paths.
> > 
> > This has worked for years with no issues.  Today, though,
> > Pycam fails.  No errors when the window closes suddenly withour
> > finishing the job.  So I started Pycam from the terminal windows
> > and
> > here are the error messages:
> > 
> > Psyco is not available (performance will probably suffer slightly)
> > Enabled 8 parallel local processes
> > Font directory: /usr/share/pycam/fonts
> > Loading task settings file: /home/lesh/CNC/PYCAM/plywood.conf
> > Imported STL model: 839 vertices, 0 edges, 1444 triangles
> > No previous undo state available - request ignored
> > Imported STL model: 518 vertices, 0 edges, 800 triangles
> 
> I think these are just informational.  I find this about psyco.
> 
> 12 March 2012
> 
> Psyco is unmaintained and dead. Please look at PyPy for the
> state-of-the-art in JIT compilers for Python.
> 
> [snip]
> > 
> > radeon: Failed to deallocate virtual address for buffer:
> > radeon:size  : 4096 bytes
> > radeon:va: 0x884000
> > Segmentation fault (core dumped)
> 
> This seems to be your problem.  Since radeon is a kernel module, it
> is
> possible that it is a kernel issue.  What happens if you boot a
> previous kernel?  
> 
> If a previous kernel works, you should open a ticket against the
> kernel
> at https://bugzilla.redhat.com/ describing your problem with the
> radeon
> driver.
> 
> If it doesn't, then something else has changed.  That will take
> further
> sleuthing to find.

Ok, I tried the previous kernel, and had no luck.  

I just remembered that I attempted to delete a package from my system
and it started to erase things, but I stopped it.  This may have done
the damage.  

It had also erased the Repetier host package that I used to generate
the Gcodes for my K8200 printer.  I reinstalled Repetier host and that
works, but pycam still does not.  Nothing else seems to be affected.

However if the Kernel is the location, is the radeon package in a
separate file?  If it is, what could I reinstall to recover that
driver?

Regards,
Les H
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: issue with pycam

[Howard Howell]

On Sun, 2016-10-02 at 10:23 -0700, stan wrote:
> On Sun, 02 Oct 2016 09:34:52 -0700
> Howard Howell  wrote:
> 
> > 
> > Hi, everyone,
> > I use Pycam with my milling machine.  The process I follow is:
> >  design with OpenSCAD, export as DXF or STL format.
> >  Open with PYCAM and adjust settings for feedrate, speed, bit
> > size and so forth as required for the project and material.  Load
> > the
> > DXF or STL file and run one of the tool paths.
> > 
> > This has worked for years with no issues.  Today, though,
> > Pycam fails.  No errors when the window closes suddenly withour
> > finishing the job.  So I started Pycam from the terminal windows
> > and
> > here are the error messages:
> > 
> > Psyco is not available (performance will probably suffer slightly)
> > Enabled 8 parallel local processes
> > Font directory: /usr/share/pycam/fonts
> > Loading task settings file: /home/lesh/CNC/PYCAM/plywood.conf
> > Imported STL model: 839 vertices, 0 edges, 1444 triangles
> > No previous undo state available - request ignored
> > Imported STL model: 518 vertices, 0 edges, 800 triangles
> 
> I think these are just informational.  I find this about psyco.
> 
> 12 March 2012
> 
> Psyco is unmaintained and dead. Please look at PyPy for the
> state-of-the-art in JIT compilers for Python.
> 
> [snip]
> > 
> > radeon: Failed to deallocate virtual address for buffer:
> > radeon:size  : 4096 bytes
> > radeon:va: 0x884000
> > Segmentation fault (core dumped)
> 
> This seems to be your problem.  Since radeon is a kernel module, it
> is
> possible that it is a kernel issue.  What happens if you boot a
> previous kernel?  
> 
> If a previous kernel works, you should open a ticket against the
> kernel
> at https://bugzilla.redhat.com/ describing your problem with the
> radeon
> driver.
> 
> If it doesn't, then something else has changed.  That will take
> further
> sleuthing to find.

Ok, I tried the previous kernel, and had no luck.  

I just remembered that I attempted to delete a package from my system
and it started to erase things, but I stopped it.  This may have done
the damage.  This was a real screw-up on my part, and so I don't think
a bugzilla is the correct action.

It had also erased the Repetier host package that I used to generate
the Gcodes for my K8200 printer.  I reinstalled Repetier host and that
works, but pycam still does not.  Nothing else seems to be affected.

However if the Kernel is the location, is the radeon package in a
separate file?  If it is, what could I reinstall to recover that
driver?

Regards,
Les H
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Patrick O'Callaghan]

On Thu, 2016-10-13 at 10:36 +0100, Gary Stainburn wrote:
> On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote:
> > Unfortunately, I cannot convert this into a usable solution in the KDE menu
> > Editor
> 
> I've been totally unable to get this working properly within KDE Menu Editor.

This might be better discussed on the Fedora KDE List.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote:
> Unfortunately, I cannot convert this into a usable solution in the KDE menu
> Editor

I've been totally unable to get this working properly within KDE Menu Editor.

Instead I've had to modify my root BASH script to cope.  Not pretty, but here 
it is in case anyone else wants it.

#!/bin/bash

user=root
kons=''
ssh=`which ssh`
while [[ "$1" =~ ^-.* ]]; do
  if [ "$1" == "-u" ]; then
user=$2
shift
shift
  fi
  if [ "$1" == '-k' ]; then
kons='y'
shift
  fi
# echo remainder $*
done

if [ "$1" == "" ]; then
  host=127.0.0.1
else
  host=`shift`
fi

if [ -z "$kons" ]; then
  $ssh -Y -C -l $user $host $*
else
  konsole -e "$ssh -Y -C -l $user $host $*"
fi
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

On Thursday 13 October 2016 09:48:31 Gary Stainburn wrote:
> On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote:
> > That looks similar to this upstream bug:
> > https://bugs.kde.org/show_bug.cgi?id=366793
>
> Interestingly, I now have two problems.
>
> This is indeed the problem on the PC I initially experienced the problem
> on.
>
> As suggested in the bug report, changing
>
> konsole -c root ollie
>
> to
>
> konsole -e bash root ollie
>
> fixed the problem.
>
Unfortunately, I cannot convert this into a usable solution in the KDE menu 
Editor
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote:
> That looks similar to this upstream bug:
> https://bugs.kde.org/show_bug.cgi?id=366793

Interestingly, I now have two problems.

This is indeed the problem on the PC I initially experienced the problem on.

As suggested in the bug report, changing 

konsole -c root ollie

to

konsole -e bash root ollie

fixed the problem.

However, I now have a similar but different problem on the laptop I used on 
Tuesday. Hay Ho
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

RE: Filesystem for backup system

[J.Witvliet]

-Original Message-
From: c...@zip.com.au [mailto:c...@zip.com.au]
Sent: donderdag 13 oktober 2016 0:58
To: Community support for Fedora users
Subject: Re: Filesystem for backup system

On 12Oct2016 09:40, Mike Wright  wrote:
>On 10/12/2016 08:53 AM, Heinz Diehl wrote:
>>On 10.10.2016, Gordon Messmer wrote:
>>
>>>Ext4 is probably a better option for a filesystem with a large number
>>>of small files.  XFS continues to be slower for metadata operations.
>>
>>It was, some years ago. This is no longer the case.
>
>Given those, would you go so far as to recommend xfs in lieu of ext4
>for general usage?

Yes.

Cameron Simpson 
___
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an 
email to users-le...@lists.fedoraproject.org

How about btrfs, (at least the stable parts of it :-)


Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet 
de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u 
verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat 
aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband 
houdt met risico's verbonden aan het elektronisch verzenden van berichten.

This message may contain information that is not intended for you. If you are 
not the addressee or if this message was sent to you by mistake, you are 
requested to inform the sender and delete the message. The State accepts no 
liability for damage of any kind resulting from the risks inherent in the 
electronic transmission of messages.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org