On 07/03/17 12:44, Amadeus W.M. wrote:
> I need a fix for my problem.
>
Oh, and I just restarted the nfs server and this was the journal recording
[root@f25f ~]# journalctl -b -0 | grep -i nfs | grep 14:52
Jul 03 14:52:05 f25f.greshko.com systemd[1]: Stopping NFS server and services...
Jul
On 07/03/17 12:44, Amadeus W.M. wrote:
> Yes, I know it should work, but I need a fix for my problem.
Oh, I'm sorry. When you said "I mean, really, nfs not working on a major
distribution?" I thought you were thinking it isn't working at all for anyone.
> I wonder if in my case it's some stale
Yes, I know it should work, but I need a fix for my problem.
I wonder if in my case it's some stale configuration from previous Fedora
versions, because I've been doing upgrades (as opposed to new installs)
for a long time. I imagine you installed F25 anew on the VM, right?
How do I even tell
On 07/02/2017 07:43 PM, William Mattison wrote:
On May 19, I started a thread called "ACPI errors (was: f24 boot fails; need
help)". The error messages that I reported there showed up during the boot process
as well as in the journalctl log. For a while in June, they showed up during the boot
That solved the more important part of the problem. The grub menu has an entry
for the correct, current kernel, and it boots the correct current kernel.
Thank-you, Sam.
On May 19, I started a thread called "ACPI errors (was: f24 boot fails; need
help)". The error messages that I reported the
Allegedly, on or about 01 July 2017, Samuel Sieb sent:
> The default policy is deny all, but let ssh in.
I didn't know that, it used to be thar you had to poke a hole through,
but I've not installed a recent version of Fedora.
> So all he needs to do is open the firewall config and uncheck the ss
On Sat, 2017-07-01 at 19:24 -0700, Joe Zeff wrote:
>
> Even better, use a LiveUSB to create a working Fedora system on a
> flash
> drive, create a set of ssh keys for it and when you're using a
> foreign
> system, boot from that drive so that you don't have to worry about
> having your key end
On 02/07/17 09:21, Ed Greshko wrote:
On 07/02/17 15:02, Mark wrote:
Is it just for me that VLC has stopped working with latest upgrade?
When I open a media file it will play the audio but not the video and
in the log there is
vlc.desktop[22216]: [7f5298001080] xcb vout display error: window
On 07/02/17 17:10, Mark wrote:
> On Sun, 2017-07-02 at 16:21 +0800, Ed Greshko wrote:
>> Running the same version as you on F25 with KDE as my desktop
>>
>> Just played files of these types
>>
>> Lion.2016.mp3.avi: RIFF (little-endian) data, AVI, 720 x 304, ~30
>> fps, video: XviD,
>> audio: MP
On Sun, 2017-07-02 at 16:21 +0800, Ed Greshko wrote:
> Running the same version as you on F25 with KDE as my desktop
>
> Just played files of these types
>
> Lion.2016.mp3.avi: RIFF (little-endian) data, AVI, 720 x 304, ~30
> fps, video: XviD,
> audio: MPEG-1 Layer 3 (stereo, 48000 Hz)
>
> B
On 02.07.2017, Mark wrote:
> Is it just for me that VLC has stopped working with latest upgrade?
Encountering the same behaviour..
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.o
On 07/02/17 15:02, Mark wrote:
> Is it just for me that VLC has stopped working with latest upgrade?
> When I open a media file it will play the audio but not the video and
> in the log there is
>
> vlc.desktop[22216]: [7f5298001080] xcb vout display error: window
> not available
>
> Totem doe
Is it just for me that VLC has stopped working with latest upgrade?
When I open a media file it will play the audio but not the video and
in the log there is
vlc.desktop[22216]: [7f5298001080] xcb vout display error: window
not available
Totem doesn't have any problem playing the same media
13 matches
Mail list logo
