Re: dnf aborting

[Tim]

Allegedly, on or about 30 March 2017, InvalidPath sent:
> Never a bad idea to take an air compressor to a laptop.. or desktop or
> any pc for that matter.

It can be if you're not careful, there are risks.

Air blasting out can generate damaging static electricity.
You can blast dust into the bearings of fans.
You can physically damage components with the force of the air (if it's
strong enough, and you get too close).

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

When it comes to electronics, I'm slightly biased.


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

[389-users] Re: [389-devel] Anyone still building 389 on HPUX?

[William Brown]

On Thu, 2017-03-16 at 15:16 -0400, Mark Reynolds wrote:

> Just curious if anyone is building 389 on HPUX?  There is very old code
> in our server that is specific to HPUX that we'd like to remove.  Most
> of it is probably not needed anymore(even on HPUX), but we want to check
> before we remove it.
> 

This is a follow up check regarding our support of 389 Directory Server
on HPUX.

We wish to remove support for this platform - if you are using Directory
Server in this configuration please contact us urgently as we will begin
removing this support very soon. 

-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Australia/Brisbane



signature.asc
Description: This is a digitally signed message part
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

F24 system shutdown during dnf cleanup

[Robert Moskowitz]

Today I was doing a dnf update and had a few things being updated and 
new kernel installed.


Right when it was past cleanup messages and you are waiting for the 
complete message, I lost power and for some reason the system did a 
shutdown.  Got that little active image Fedora shows during a shutdown.


The system restarted ok.  How do I find out what the state is?  What 
might still need to be done?  When I grep for 'kernel' in 
/var/log/dnf.log I get:


Mar 30 12:38:22 SUBDEBUG drpm: spawned 19063: /usr/bin/applydeltarpm -a 
x86_64 
/var/cache/dnf/updates-c4f1c95f64c2b794/packages/kernel-headers-4.9.13-101.fc24_4.9.17-100.fc24.x86_64.drpm 
/var/cache/dnf/updates-c4f1c95f64c2b794/packages/kernel-headers-4.9.17-100.fc24.x86_64.rpm



And the last install for kernel was:

Mar 30 12:38:03 DEBUG ---> Package kernel-modules.x86_64 4.9.9-100.fc24 
will be erased

 kernel  x86_64  4.9.17-100.fc24 updates80 k
 kernel-core x86_64  4.9.17-100.fc24 updates20 M
 kernel-debug-core   x86_64  4.9.17-100.fc24 updates21 M
 kernel-debug-modulesx86_64  4.9.17-100.fc24 updates23 M
 kernel-debug-modules-extra  x86_64  4.9.17-100.fc24 updates   2.3 M
 kernel-modules  x86_64  4.9.17-100.fc24 updates22 M
 kernel-headers  x86_64  4.9.17-100.fc24 updates   1.1 M
 kernel  x86_64  4.9.9-100.fc24 @updates0
 kernel-core x86_64  4.9.9-100.fc24 @updates   53 M
 kernel-debug-core   x86_64  4.9.9-100.fc24 @updates   55 M
 kernel-debug-modulesx86_64  4.9.9-100.fc24 @updates   22 M
 kernel-debug-modules-extra  x86_64  4.9.9-100.fc24 @updates  2.1 M
 kernel-modules  x86_64  4.9.9-100.fc24 @updates   22 M


How do I check this out?

thanks.

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

Re: System alive but can't access from the monitor

[Paolo Galtieri]

I booted off a prior kernel (4.9.14-200) and I don't see the problem. so 
the issue islikely to be related to the latest kernel.


Paolo

On 03/30/2017 12:35 AM, Ed Greshko wrote:

On 03/30/17 14:24, Paolo Galtieri wrote:

Folks,
   I have 2 F25 systems that have been updated today.  These 2 systems
share a monitor.  One system is attached via a kvm switch to the
monitor, the other system is attached via hdmi.  This morning and
twice this evening a problem has started to manifest itself.  This
configuration has been working fine for several years.  I will call
the systems A and B, system A is attached to the monitor via hdmi,
system B via VGA.  If I switch to system A for a while and then try to
switch back to system B the monitor instead of staying on VGA cycles
from VGA to DVI to HDMI and returns to system A.  I can ssh into
system B and everything looks fine, i.e. things that were running
under my user id are still running, e.g. chrome and firefox. I looked
at /var/log/messages and I see this:

Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0...
Mar 29 23:00:02 jackstraw systemd: Stopped target Default.
Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System.
Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets.
Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket.
Mar 29 23:00:02 jackstraw systemd: Stopped target Timers.
Mar 29 23:00:02 jackstraw systemd: Stopped target Paths.
Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown.
Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session...
Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588
(kill).

This was at the time I switched from system A to system B.  Each of
the other times I saw this problem I see the same set of messages in
the log file.  Can someone explain what they mean and could they be
the cause of the problem?

I see the same messages on the other system, but there they were part
of other messages related to rebooting the system.

The only way I can recover is reboot the system.

Here's my video card info:

01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce
8500 GT] (rev a1)

Any assistance is appreciated.

Since everything is still running as it was it sounds similar to
problems with monitors not coming back from sleep.

Couple of questions.

1.  Are you using the nouveau driver or the nVidia driver for your card?
2.  Are you running GNOME under Wayland or X11?

If you are using X11, and since you can ssh into  the system, what is
the output if you do...

ssh systemB
export DISPLAY=:0
xrandr

Using my system as an example, does doing something like this bring the
monitor back?

[egreshko@meimei ~]$ acer
Last login: Thu Mar 30 15:24:26 2017 from 192.168.1.18
[egreshko@acer ~]$ export DISPLAY=:0

[egreshko@acer ~]$ xrandr
Screen 0: minimum 8 x 8, current 1280 x 800, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 connected primary 1280x800+0+0 (normal left inverted right x axis
y axis) 331mm x 207mm
1280x800  59.91*+
HDMI-0 disconnected (normal left inverted right x axis y axis)

[egreshko@acer ~]$ xrandr --output LVDS-0 --off
[egreshko@acer ~]$ xrandr --output LVDS-0 --auto


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

Re: Not able to launch mediawriter

[Joe Zeff]

On 03/30/2017 06:34 AM, Martin Bříza wrote:

first, please don't run mediawriter as root.
Second, this is because it cannot find the Qt Quick Controls. These
should be included in the qt5-qtquickcontrols package, which is a
dependency of mediawriter. Did you modify your installation of one of
these packages?


The Fedora documentation says it needs to be run using sudo, which is 
the same as running it as root.

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

Re: Not able to launch mediawriter

[Lawrence E Graves]

On 03/30/2017 08:18 AM, Martin Bříza wrote:

rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative

Mine came back the same as yours did but still unable to launch mediawriter.

--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: dnf aborting

[Kevin Cummings]

On 03/30/17 10:24, InvalidPath wrote:
> 
> 
> On Thu, Mar 30, 2017 at 8:11 AM, stan  > wrote:
> 
> On Wed, 29 Mar 2017 18:01:29 -0400
> Kevin Cummings  > wrote:
> 
> > I had a different solution.  I went off site today (w/laptop) and
> > things worked well where I was.  When I got back home, I un-suspended
> > the laptop but forgot to plug it in.  After 2 hours, the battery
> > discharged. After plugging back in, when I tried to reboot
> > (kernel-4.9.13-101.fc24), it hung twice trying to start the gui.
> > When I rebooted with kernel-4.9.13-100.fc24, it came up, and the dnf
> > update succeeded!  Gee, now I have 4.9.17 kernel to try!  B^)
> 
> That makes it sound like the power supply has something to do with your
> problems.  Maybe it is overheating, or the voltages it provides are
> marginal?  Could there be a lot of dust buildup in the case?
> ___
> users mailing list -- users@lists.fedoraproject.org
> 
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> 
> 
> 
> Never a bad idea to take an air compressor to a laptop.. or desktop or
> any pc for that matter.

Yeah, it has been a while since I "popped the cover" on the laptop

-- 
Kevin J. Cummings
kjch...@verizon.net
cummi...@kjchome.homeip.net
cummi...@kjc386.framingham.ma.us
Registered Linux User #1232 (http://www.linuxcounter.net/)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: System alive but can't access from the monitor

[Paolo Galtieri]

I'm using the nouveau drivers and I'm running MATE under X11.

If I do

ssh systemB
export DISPLAY=:0
xrandr

I get no output, it just hangs, and the monitor does not wakeup.

Paolo

On 03/30/2017 12:35 AM, Ed Greshko wrote:

On 03/30/17 14:24, Paolo Galtieri wrote:

Folks,
   I have 2 F25 systems that have been updated today.  These 2 systems
share a monitor.  One system is attached via a kvm switch to the
monitor, the other system is attached via hdmi.  This morning and
twice this evening a problem has started to manifest itself.  This
configuration has been working fine for several years.  I will call
the systems A and B, system A is attached to the monitor via hdmi,
system B via VGA.  If I switch to system A for a while and then try to
switch back to system B the monitor instead of staying on VGA cycles
from VGA to DVI to HDMI and returns to system A.  I can ssh into
system B and everything looks fine, i.e. things that were running
under my user id are still running, e.g. chrome and firefox. I looked
at /var/log/messages and I see this:

Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0...
Mar 29 23:00:02 jackstraw systemd: Stopped target Default.
Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System.
Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets.
Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket.
Mar 29 23:00:02 jackstraw systemd: Stopped target Timers.
Mar 29 23:00:02 jackstraw systemd: Stopped target Paths.
Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown.
Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session...
Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588
(kill).

This was at the time I switched from system A to system B.  Each of
the other times I saw this problem I see the same set of messages in
the log file.  Can someone explain what they mean and could they be
the cause of the problem?

I see the same messages on the other system, but there they were part
of other messages related to rebooting the system.

The only way I can recover is reboot the system.

Here's my video card info:

01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce
8500 GT] (rev a1)

Any assistance is appreciated.

Since everything is still running as it was it sounds similar to
problems with monitors not coming back from sleep.

Couple of questions.

1.  Are you using the nouveau driver or the nVidia driver for your card?
2.  Are you running GNOME under Wayland or X11?

If you are using X11, and since you can ssh into  the system, what is
the output if you do...

ssh systemB
export DISPLAY=:0
xrandr

Using my system as an example, does doing something like this bring the
monitor back?

[egreshko@meimei ~]$ acer
Last login: Thu Mar 30 15:24:26 2017 from 192.168.1.18
[egreshko@acer ~]$ export DISPLAY=:0

[egreshko@acer ~]$ xrandr
Screen 0: minimum 8 x 8, current 1280 x 800, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 connected primary 1280x800+0+0 (normal left inverted right x axis
y axis) 331mm x 207mm
1280x800  59.91*+
HDMI-0 disconnected (normal left inverted right x axis y axis)

[egreshko@acer ~]$ xrandr --output LVDS-0 --off
[egreshko@acer ~]$ xrandr --output LVDS-0 --auto


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

Re: dnf aborting

[InvalidPath]

On Thu, Mar 30, 2017 at 8:11 AM, stan  wrote:

> On Wed, 29 Mar 2017 18:01:29 -0400
> Kevin Cummings  wrote:
>
> > I had a different solution.  I went off site today (w/laptop) and
> > things worked well where I was.  When I got back home, I un-suspended
> > the laptop but forgot to plug it in.  After 2 hours, the battery
> > discharged. After plugging back in, when I tried to reboot
> > (kernel-4.9.13-101.fc24), it hung twice trying to start the gui.
> > When I rebooted with kernel-4.9.13-100.fc24, it came up, and the dnf
> > update succeeded!  Gee, now I have 4.9.17 kernel to try!  B^)
>
> That makes it sound like the power supply has something to do with your
> problems.  Maybe it is overheating, or the voltages it provides are
> marginal?  Could there be a lot of dust buildup in the case?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>

Never a bad idea to take an air compressor to a laptop.. or desktop or any
pc for that matter.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Ed Greshko]

On 03/30/17 22:13, Lawrence Graves wrote:
> You installed it and ran as a user (not root) and still it doesn't work?
> That is correct. 


Same, exact, error messages?   If you had to install qt5-qtquickcontrols
I would wonder what else may be missing.

You don't happen to have an LD_LIBRARY_PATH environment variable set?

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Martin Bříza]

On Thu, 30 Mar 2017 16:13:16 +0200, Lawrence Graves   
wrote:





On 3/30/2017 8:05 AM, Ed Greshko wrote:

On 03/30/17 22:00, Lawrence E Graves wrote:


On 03/30/2017 07:56 AM, Ed Greshko wrote:

On 03/30/17 21:44, Lawrence E Graves wrote:

I did as you prescribed and yet there was no results.

What does that mean?

I downloaded qt5-qtquickcontrols and they didn't help. Still can't
launch mediawriter.

You installed it and ran as a user (not root) and still it doesn't work?
That is correct.




Is qt5-qtquickcontrols, qt5-qtbase and qt5-qtdeclarative the same version  
on your system?

You can verify that by running:
  # rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative
The numbers between the dash symbols matter. In my case, the command  
outputs this:

  qt5-qtquickcontrols-5.7.1-4.fc26.x86_64
  qt5-qtbase-5.7.1-15.fc26.x86_64
  qt5-qtdeclarative-5.7.1-7.fc26.x86_64
All three packages are version 5.7.1.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Lawrence Graves]

On 3/30/2017 8:05 AM, Ed Greshko wrote:

On 03/30/17 22:00, Lawrence E Graves wrote:


On 03/30/2017 07:56 AM, Ed Greshko wrote:

On 03/30/17 21:44, Lawrence E Graves wrote:

I did as you prescribed and yet there was no results.

What does that mean?

I downloaded qt5-qtquickcontrols and they didn't help. Still can't
launch mediawriter.

You installed it and ran as a user (not root) and still it doesn't work?
That is correct.


--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: dnf aborting

[stan]

On Wed, 29 Mar 2017 18:01:29 -0400
Kevin Cummings  wrote:

> I had a different solution.  I went off site today (w/laptop) and
> things worked well where I was.  When I got back home, I un-suspended
> the laptop but forgot to plug it in.  After 2 hours, the battery
> discharged. After plugging back in, when I tried to reboot
> (kernel-4.9.13-101.fc24), it hung twice trying to start the gui.
> When I rebooted with kernel-4.9.13-100.fc24, it came up, and the dnf
> update succeeded!  Gee, now I have 4.9.17 kernel to try!  B^)

That makes it sound like the power supply has something to do with your
problems.  Maybe it is overheating, or the voltages it provides are
marginal?  Could there be a lot of dust buildup in the case?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Ed Greshko]

On 03/30/17 22:00, Lawrence E Graves wrote:
>
>
> On 03/30/2017 07:56 AM, Ed Greshko wrote:
>> On 03/30/17 21:44, Lawrence E Graves wrote:
 I did as you prescribed and yet there was no results.
>>
>> What does that mean?
>>
>> I downloaded qt5-qtquickcontrols and they didn't help. Still can't
>> launch mediawriter.
>
You installed it and ran as a user (not root) and still it doesn't work?

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Lawrence E Graves]

On 03/30/2017 07:56 AM, Ed Greshko wrote:

On 03/30/17 21:44, Lawrence E Graves wrote:

I did as you prescribed and yet there was no results.


What does that mean?

I downloaded qt5-qtquickcontrols and they didn't help. Still can't launch 
mediawriter.


--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Ed Greshko]

On 03/30/17 21:44, Lawrence E Graves wrote:
>> I did as you prescribed and yet there was no results.


What does that mean?

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Lawrence E Graves]

On 03/30/2017 07:34 AM, Martin Bříza wrote:
On Thu, 30 Mar 2017 12:55:35 +0200, Lawrence E Graves 
 wrote:



[root@Jehovah ~]# mediawriter
Warning: QQmlApplicationEngine failed to load component ((null):0, 
(null))
Warning: qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not 
installed

qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
  ((null):0, (null))

I am running Fedora 25. What to do?



Hello,
first, please don't run mediawriter as root.
Second, this is because it cannot find the Qt Quick Controls. These 
should be included in the qt5-qtquickcontrols package, which is a 
dependency of mediawriter. Did you modify your installation of one of 
these packages?

-Martin




_I did as you prescribed and yet there was no results.



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


--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Not able to launch mediawriter

[Martin Bříza]

On Thu, 30 Mar 2017 12:55:35 +0200, Lawrence E Graves  
 wrote:



[root@Jehovah ~]# mediawriter
Warning: QQmlApplicationEngine failed to load component ((null):0,  
(null))
Warning: qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not  
installed

qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
  ((null):0, (null))

I am running Fedora 25. What to do?



Hello,
first, please don't run mediawriter as root.
Second, this is because it cannot find the Qt Quick Controls. These should  
be included in the qt5-qtquickcontrols package, which is a dependency of  
mediawriter. Did you modify your installation of one of these packages?

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

Re: Not able to launch mediawriter

[Ed Greshko]

On 03/30/17 18:55, Lawrence E Graves wrote:
> [root@Jehovah ~]# mediawriter
> Warning: QQmlApplicationEngine failed to load component ((null):0,
> (null))
> Warning: qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not
> installed
> qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
> qrc:/main.qml:21 module "QtQuick.Controls" is not installed
> qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
> qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
> qrc:/main.qml:21 module "QtQuick.Controls" is not installed
> qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
> qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
> qrc:/main.qml:21 module "QtQuick.Controls" is not installed
>  ((null):0, (null))
>
> I am running Fedora 25. What to do?
>
Is qt5-qtquickcontrols installed?


-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: BackupPC 4.1.0 testing needed - Any BackupPC users on the group?

[Richard Shaw]

On Thu, Mar 30, 2017 at 8:25 AM, Robert Nichols 
wrote:

>
>> How well are hard-linked files handled? If I restore /var/lib/yum/yumdb
> from the most recent backup, will the restored files be hard-linked the
> same way they were when the backup was made? Will that also be true if I
> restore a version that is _not_ the most recent backup?


Hard links were only used in v3 for deduplication, the restored file would
not be a hard link to my knowledge, however, that question may be better
asked on the backuppc user list.

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

Re: BackupPC 4.1.0 testing needed - Any BackupPC users on the group?

[Robert Nichols]

On 03/30/2017 07:32 AM, Richard Shaw wrote:

I have taken over maintenance of the BackupPC package and have made the update 
to 4.1.0 available through COPR[1] for now for a couple of reasons:

1. It's a huge change, hardlinks are no longer used for deduplication, but v4 
can read v3 backups.

2. Some of the settings in /etc/BackupPC/config.pl  were 
tweaked and need manual attention after the upgrade.

See https://backuppc.github.io/backuppc/BackupPC.html#BackupPC-4.0 for details.

The plan is to update f26 and rawhide to v4 and leave f25 and EPEL alone. Those 
that want to update to v4 can use the COPR.

Thanks,
Richard

[1] https://copr.fedorainfracloud.org/coprs/hobbes1069/BackupPC/


How well are hard-linked files handled? If I restore /var/lib/yum/yumdb from 
the most recent backup, will the restored files be hard-linked the same way 
they were when the backup was made? Will that also be true if I restore a 
version that is _not_ the most recent backup?

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

BackupPC 4.1.0 testing needed - Any BackupPC users on the group?

[Richard Shaw]

I have taken over maintenance of the BackupPC package and have made the
update to 4.1.0 available through COPR[1] for now for a couple of reasons:

1. It's a huge change, hardlinks are no longer used for deduplication, but
v4 can read v3 backups.

2. Some of the settings in /etc/BackupPC/config.pl were tweaked and need
manual attention after the upgrade.

See https://backuppc.github.io/backuppc/BackupPC.html#BackupPC-4.0 for
details.

The plan is to update f26 and rawhide to v4 and leave f25 and EPEL alone.
Those that want to update to v4 can use the COPR.

Thanks,
Richard

[1] https://copr.fedorainfracloud.org/coprs/hobbes1069/BackupPC/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Not able to launch mediawriter

[Lawrence E Graves]

[root@Jehovah ~]# mediawriter
Warning: QQmlApplicationEngine failed to load component ((null):0, (null))
Warning: qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed
qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed
qrc:/main.qml:21 module "QtQuick.Controls" is not installed
 ((null):0, (null))

I am running Fedora 25. What to do?

--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: System alive but can't access from the monitor

[Ed Greshko]

On 03/30/17 14:24, Paolo Galtieri wrote:
> Folks,
>   I have 2 F25 systems that have been updated today.  These 2 systems
> share a monitor.  One system is attached via a kvm switch to the
> monitor, the other system is attached via hdmi.  This morning and
> twice this evening a problem has started to manifest itself.  This
> configuration has been working fine for several years.  I will call
> the systems A and B, system A is attached to the monitor via hdmi,
> system B via VGA.  If I switch to system A for a while and then try to
> switch back to system B the monitor instead of staying on VGA cycles
> from VGA to DVI to HDMI and returns to system A.  I can ssh into
> system B and everything looks fine, i.e. things that were running
> under my user id are still running, e.g. chrome and firefox. I looked
> at /var/log/messages and I see this:
>
> Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0...
> Mar 29 23:00:02 jackstraw systemd: Stopped target Default.
> Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System.
> Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets.
> Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket.
> Mar 29 23:00:02 jackstraw systemd: Stopped target Timers.
> Mar 29 23:00:02 jackstraw systemd: Stopped target Paths.
> Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown.
> Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session...
> Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588
> (kill).
>
> This was at the time I switched from system A to system B.  Each of
> the other times I saw this problem I see the same set of messages in
> the log file.  Can someone explain what they mean and could they be
> the cause of the problem?
>
> I see the same messages on the other system, but there they were part
> of other messages related to rebooting the system.
>
> The only way I can recover is reboot the system.
>
> Here's my video card info:
>
> 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce
> 8500 GT] (rev a1)
>
> Any assistance is appreciated.

Since everything is still running as it was it sounds similar to
problems with monitors not coming back from sleep.

Couple of questions.  

1.  Are you using the nouveau driver or the nVidia driver for your card?
2.  Are you running GNOME under Wayland or X11?

If you are using X11, and since you can ssh into  the system, what is
the output if you do...

ssh systemB
export DISPLAY=:0
xrandr

Using my system as an example, does doing something like this bring the
monitor back?

[egreshko@meimei ~]$ acer
Last login: Thu Mar 30 15:24:26 2017 from 192.168.1.18
[egreshko@acer ~]$ export DISPLAY=:0

[egreshko@acer ~]$ xrandr
Screen 0: minimum 8 x 8, current 1280 x 800, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 connected primary 1280x800+0+0 (normal left inverted right x axis
y axis) 331mm x 207mm
   1280x800  59.91*+
HDMI-0 disconnected (normal left inverted right x axis y axis)

[egreshko@acer ~]$ xrandr --output LVDS-0 --off
[egreshko@acer ~]$ xrandr --output LVDS-0 --auto

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

System alive but can't access from the monitor

[Paolo Galtieri]

Folks,
  I have 2 F25 systems that have been updated today.  These 2 systems 
share a monitor.  One system is attached via a kvm switch to the 
monitor, the other system is attached via hdmi.  This morning and twice 
this evening a problem has started to manifest itself.  This 
configuration has been working fine for several years.  I will call the 
systems A and B, system A is attached to the monitor via hdmi, system B 
via VGA.  If I switch to system A for a while and then try to switch 
back to system B the monitor instead of staying on VGA cycles from VGA 
to DVI to HDMI and returns to system A.  I can ssh into system B and 
everything looks fine, i.e. things that were running under my user id 
are still running, e.g. chrome and firefox. I looked at 
/var/log/messages and I see this:


Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0...
Mar 29 23:00:02 jackstraw systemd: Stopped target Default.
Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System.
Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets.
Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket.
Mar 29 23:00:02 jackstraw systemd: Stopped target Timers.
Mar 29 23:00:02 jackstraw systemd: Stopped target Paths.
Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown.
Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session...
Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588 
(kill).


This was at the time I switched from system A to system B.  Each of the 
other times I saw this problem I see the same set of messages in the log 
file.  Can someone explain what they mean and could they be the cause of 
the problem?


I see the same messages on the other system, but there they were part of 
other messages related to rebooting the system.


The only way I can recover is reboot the system.

Here's my video card info:

01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 
GT] (rev a1)


Any assistance is appreciated.

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