Issues after upgrading from F24 -> F25

[Paolo Galtieri]

I upgraded my laptop from F24 to F25 and ran into some issues.

The first issue is when I booted after the install the system came up 
into maintenance mode.  I looked at the log and the only failure I saw 
was it complained of timing out accessing a disk drive. Normally this 
would be of some concern, however, at the time I booted the system the 
drive it was complaining about WASN'T EVEN PLUGGED IN (sorry for yelling 
:-).  As soon as I plugged the drive in and rebooted the system came up 
fine.

Second issue has to do with the Mate desktop.  I wanted to setup a 
program to change the desktop background every 5 minutes.  I googled and 
discovered that there is a program wallpapoz does this.  So I downloaded 
it and ran it and nothing happens.  So I tried it with the Gnome Classic 
desktop and it works just great there.  I did a little investigating and 
I discovered that this was a problem back in 2013. I did a little more 
investigating and discovered that a patch went in to wallpapoz to 
support the Mate desktop which was basically the following:

gsettings set org.mate.background picture-filename <image file>

So I tried running this command with an image, and again nothing 
happens, the desktop background remains the same as before.  I tried doing

gsettings reset org.mate.background picture-filename

and this works. I did verify that the set is getting done by doing:

gsettings get org.mate.background picture-filename

so the image name is getting set, but it does not appear.  This problem 
has existed since at least F22.

The only way to change the desktop background under Mate is by right 
clicking the mouse on the desktop and selecting "Change Desktop 
Background".

The third issue has to do with selecting the "Gnome Classic" desktop.  
When I select it and login I get the Gnome classic layout with the top 
and bottom panels, however, I can't place any application into the 
panel.  Also if I move the mouse to the upper left corner, I get the 
Gnome Shell with the 4 default screens displayed vertically on the right 
and the application bar on the left.  WTF?  Another issue regarding the 
Gnome Classic desktop, which has been reported, is that the desktop 
icons are huge.  I can only place 5 icons vertically under the Gnome 
Classic desktop, but at least a dozen under the Mate desktop.

I looked in bugzilla for bugs regarding these issues, but other than the 
icons one I didn't find anything.  Has anybody else experienced these 
issues?

Paolo

[Joe Zeff]

On 12/17/2016 12:40 PM, Paolo Galtieri wrote:
>  The first issue is when I booted after the install the system came up
>  into maintenance mode.  I looked at the log and the only failure I saw
>  was it complained of timing out accessing a disk drive. Normally this
>  would be of some concern, however, at the time I booted the system the
>  drive it was complaining about WASN'T EVEN PLUGGED IN (sorry for yelling
>  :-).  As soon as I plugged the drive in and rebooted the system came up
>  fine. 
I presume that the drive is listed in /etc/fstab with the default 
options.  If so, the system will try to mount it and consider the 
failure to be a problem.  Using the option nofail will tell mount to 
ignore it if it doesn't mount.

[Paolo Galtieri]

The nofail option was already listed:

# LABEL=NEWDATA2    /media/NEWDATA2            ext4 
defaults,nodev,noexec,nosuid,async,noatime,nofail,noauto,user    1 2


On 12/17/2016 12:49 PM, Joe Zeff wrote:
>  On 12/17/2016 12:40 PM, Paolo Galtieri wrote:
> >
> > The first issue is when I booted after the install the system came up
> > into maintenance mode.  I looked at the log and the only failure I saw
> > was it complained of timing out accessing a disk drive. Normally this
> > would be of some concern, however, at the time I booted the system the
> > drive it was complaining about WASN'T EVEN PLUGGED IN (sorry for yelling
> > :-).  As soon as I plugged the drive in and rebooted the system came up
> > fine.
>
>  I presume that the drive is listed in /etc/fstab with the default 
>  options.  If so, the system will try to mount it and consider the 
>  failure to be a problem.  Using the option nofail will tell mount to 
>  ignore it if it doesn't mount.
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org

[Joe Zeff]

On 12/17/2016 01:24 PM, Paolo Galtieri wrote:
>  The nofail option was already listed:
>
>  # LABEL=NEWDATA2    /media/NEWDATA2            ext4
>  defaults,nodev,noexec,nosuid,async,noatime,nofail,noauto,user    1 2 
OK, what happens if you run mount -a when it's not plugged in?  Also, if 
you check the man page for fstab, you'll see that some of your custom 
options conflict with the defaults.  It might be better to remove that 
to avoid trouble.  I've never included it when I've added custom options 
and it's never been an issue for me.

[Paolo Galtieri]

I booted up into maintenance mode.  When I ran mount -a I get

mount: can't find LABEL=NEWDATA

I removed the defaults entry from the entry in /etc/fstab and did the 
mount -a again and got the same result.  I rebooted the system and again 
in went into maintenance mode.

Paolo

On 12/17/2016 02:16 PM, Joe Zeff wrote:
>  On 12/17/2016 01:24 PM, Paolo Galtieri wrote:
> > The nofail option was already listed:
> >
> > # LABEL=NEWDATA2    /media/NEWDATA2            ext4
> > defaults,nodev,noexec,nosuid,async,noatime,nofail,noauto,user 1 2
>
>  OK, what happens if you run mount -a when it's not plugged in? Also, 
>  if you check the man page for fstab, you'll see that some of your 
>  custom options conflict with the defaults.  It might be better to 
>  remove that to avoid trouble.  I've never included it when I've added 
>  custom options and it's never been an issue for me.
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org

[Joe Zeff]

On 12/17/2016 03:41 PM, Paolo Galtieri wrote:
>  I booted up into maintenance mode.  When I ran mount -a I get
>
>  mount: can't find LABEL=NEWDATA
>
>  I removed the defaults entry from the entry in /etc/fstab and did the
>  mount -a again and got the same result.  I rebooted the system and again
>  in went into maintenance mode. 
OK, are you sure you have the label right?  Remember, it's case 
sensitive.  You might be better off using the UUID instead.