Bug 397911 - Wallpapers located on other disk reset to default after reboot
Summary: Wallpapers located on other disk reset to default after reboot
Status: RESOLVED DUPLICATE of bug 391706
Alias: None
Product: plasmashell
Classification: Plasma
Component: Image Wallpaper (show other bugs)
Version: 5.12.6
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-27 02:13 UTC by kinghat
Modified: 2018-08-28 17:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
dolphin screenshot (48.61 KB, image/png)
2018-08-27 16:47 UTC, kinghat
Details
info screenshot (42.27 KB, image/png)
2018-08-27 18:54 UTC, kinghat
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kinghat 2018-08-27 02:13:41 UTC
i have 3 monitors on a kubuntu 18.04.1 install. have a pretty clean setup as i just did it but every time i set my wallpapers for each monitor from a drive that is not the OS drive the wallpapers switch back to the defaults after a reboot. i can log out and back on just fine with no issues to the wallpapers. i made a post about it here:

https://www.kubuntuforums.net/showthread.php/74290-set-wallpapers-changing-to-default-after-reboot

and here:

https://forum.kde.org/viewtopic.php?t=153702
Comment 1 kinghat 2018-08-27 03:24:31 UTC
i pulled the wallpapers from the non OS disk and put them in the /home/pictures dir on the OS disk and applied the wallpapers they way i like them again and they seemed to survive a reboot just fine this time. maybe there is a bug there in the wallpaper manager for images stored on the non OS drive?
Comment 2 Nate Graham 2018-08-27 16:26:26 UTC
I wonder if what's happening is that the disk isn't mounted yet when Plasma goes to read the file on it, so the file can't be found, and Plasma reverts to the default wallpaper.

Is the other disk internal or external? Does it auto-mount, or only mount when you access it? What's the filesystem? EXT4, BTRFS, NTFS, etc?
Comment 3 kinghat 2018-08-27 16:47:09 UTC
Created attachment 114637 [details]
dolphin screenshot
Comment 4 kinghat 2018-08-27 16:48:19 UTC
(In reply to Nate Graham from comment #2)
> I wonder if what's happening is that the disk isn't mounted yet when Plasma
> goes to read the file on it, so the file can't be found, and Plasma reverts
> to the default wallpaper.
> 
> Is the other disk internal or external? Does it auto-mount, or only mount
> when you access it? What's the filesystem? EXT4, BTRFS, NTFS, etc?

that could be the case. the disk in question is internal but im not sure if its auto mounted? it shows up as orange on the devices list as well as other internal drives. the only green one is the OS drive '118.7 BiG Hard Drive.' if i click on it to view the contents it turns green. its probably only mounting when i click on it. the drive was used in windows before i set up this dual boot machine so its probably NTFS. im new to linux so im sorry.
Comment 5 Nate Graham 2018-08-27 18:22:44 UTC
That's what I thought: the disk with your wallpaper files is not being auto-mounted. So Plasma can't find the path, can't map the path to the device needing to be mounted so that it then mounts it itself, and falls back to the default wallpaper.

What version of KDE Frameworks do you have? You can find out in the Info Center app. If you have 5.45 or earlier, then this is probably Bug 391706.
Comment 6 kinghat 2018-08-27 18:54:46 UTC
Created attachment 114640 [details]
info screenshot

(In reply to Nate Graham from comment #5)
> That's what I thought: the disk with your wallpaper files is not being
> auto-mounted. So Plasma can't find the path, can't map the path to the
> device needing to be mounted so that it then mounts it itself, and falls
> back to the default wallpaper.
> 
> What version of KDE Frameworks do you have? You can find out in the Info
> Center app. If you have 5.45 or earlier, then this is probably Bug 391706.
Comment 7 Nate Graham 2018-08-27 19:45:10 UTC
Frameworks 5.44. So yeah, this is Bug 391706.

The good news is that you can upgrade to Frameworks 5.47 using the Kubuntu Backports PPA:

sudo add-apt-repository ppa:kubuntu-ppa/backports
sudo apt update
sudo apt upgrade

In the meantime, let me see if we can get the fix for Bug 391706 backported to 5.44 for the vast majority of people who don't want to use the backports PPA. Please follow https://phabricator.kde.org/T9525

*** This bug has been marked as a duplicate of bug 391706 ***
Comment 8 kinghat 2018-08-28 16:40:39 UTC
(In reply to Nate Graham from comment #7)
> Frameworks 5.44. So yeah, this is Bug 391706.
> 
> The good news is that you can upgrade to Frameworks 5.47 using the Kubuntu
> Backports PPA:
> 
> sudo add-apt-repository ppa:kubuntu-ppa/backports
> sudo apt update
> sudo apt upgrade
> 
> In the meantime, let me see if we can get the fix for Bug 391706 backported
> to 5.44 for the vast majority of people who don't want to use the backports
> PPA. Please follow https://phabricator.kde.org/T9525
> 
> *** This bug has been marked as a duplicate of bug 391706 ***

it looks like they are trying to get it pushed to 5.44, but i have no idea how long that would take? would it be months? otherwise ill just go with the backports.
Comment 9 Nate Graham 2018-08-28 17:04:08 UTC
More like weeks. But yeah, the backports PPA would be minutes. :)

Keep in mind that the backports PPA will eventually upgrade Plasma to 5.13, so if you'd prefer to stay with 5.12, don't use it.