Bug 22221

Summary: acroread suddenly won't start - missing adwaita theme
Product: Mageia Reporter: Frank Griffin <ftg>
Component: New RPM package requestAssignee: GNOME maintainers <gnome>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: gnome-themes-standard CVE:
Status comment:
Attachments: Output of journalctl -a --since=2017-12-28 --until=2017-12-29 | grep RPM
journalctl -a --since=2017-12-08 --until=2017-12-29 | grep RPM

Description Frank Griffin 2017-12-18 23:25:50 CET
After the latest cauldron updates, the independently installed Adobe Acrobat Reader rpm fails at startup with the following message, even after urpmi --replacepkgs:

(acroread:31908): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita"

How does a non-MGA acroread even know about adwaita, unless adwaita has been removed but not completely ?
Comment 1 Marja Van Waes 2017-12-19 08:15:44 CET
(In reply to Frank Griffin from comment #0)

> 
> How does a non-MGA acroread even know about adwaita, unless adwaita has been
> removed but not completely ?

Maybe from adwaita-icon-theme?? That comes with several DEs, like Xfce

Anyway, gnome-themes-standard provides the Adwaita theme, so this package request was already fixed before you filed it :-)

CC: (none) => marja11
Resolution: (none) => FIXED
Status: NEW => RESOLVED
Source RPM: adwaita => gnome-themes-standard

Comment 2 Frank Griffin 2017-12-19 15:21:48 CET
I'm not so sure - gnome-themes-standard was last updated 9 months ago:

[ftg@ftglap2 commercial]$ cd /mnt/cauldron/x86_64/media/core/release
[ftg@ftglap2 release]$ ls -l gnome-themes*
-rw-rw-r-- 1 ftg ftg 4366878 Feb  3  2016 gnome-themes-extras-2.22.0-12.mga6.noarch.rpm
-rw-r--r-- 1 ftg ftg 2818288 Mar 22  2017 gnome-themes-standard-3.22.3-1.mga6.x86_64.rpm
[ftg@ftglap2 release]$ 

This problem only started lately.
Comment 3 Frank Griffin 2018-01-03 01:51:13 CET
Sorry, but this error persists through several weeks of cauldron updates.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 4 Marja Van Waes 2018-01-03 08:30:19 CET
If it doesn't work with gnome-themes-standard, does it then maybe work if you install adwaita-gtk2-theme?

Assigning to our Gnome maintainer(s), who know(s) much more about Adwaita than me.

Note that we do not support third-party software, so he's not obliged to help (unless there's something wrong with how the Adwaita theme was packaged).

Assignee: bugsquad => gnome

Comment 5 Marja Van Waes 2018-01-03 09:47:35 CET
(In reply to Frank Griffin from comment #2)
> I'm not so sure - gnome-themes-standard was last updated 9 months ago

True
> 
> This problem only started lately.

Do you mind attaching the list of "the latest cauldron updates" that you received just before filing this bug report?

It is probably best to find them with something like (as root)

   journalctl -a --since=2017-12-28 --until=2017-12-29 | grep RPM
Comment 6 Frank Griffin 2018-01-03 17:16:00 CET
>If it doesn't work with gnome-themes-standard, does it then maybe work if you >install adwaita-gtk2-theme?

Already installed.
Comment 7 Frank Griffin 2018-01-03 17:19:27 CET
Created attachment 9875 [details]
Output of journalctl -a --since=2017-12-28 --until=2017-12-29 | grep RPM
Comment 8 Frank Griffin 2018-01-03 17:25:38 CET
Created attachment 9876 [details]
journalctl -a --since=2017-12-08 --until=2017-12-29 | grep RPM

Expanding the date range since I reported it on Dec 18 and it must have happened before that.
Comment 9 Frank Griffin 2018-02-07 13:40:02 CET
Now fixed.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED