主页 / ubuntu / 问题 / 625285
Accepted
mkasberg
Asked: 2015-05-19 06:59:37 +0800 CST

Google Chrome 无法启动 - 无法在 module_path 中找到主题引擎：“adwaita”

  • 772

Google Chrome 在最近的apt-get upgrade. 我无法弄清楚我遗漏了什么，并且谷歌没有为这些错误提供很多结果：

$ google-chrome
[1:1:0518/085616:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "adwaita",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "adwaita",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
[5807:5807:0518/085616:ERROR:browser_main_loop.cc(199)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
Aborted (core dumped)


$ google-chrome --version
Google Chrome 42.0.2311.152

升级前，Chrome 在这台机器上运行良好。

gnome

7 个回答

  1. 我的回答的第一部分：

    为了GTK theme error: Unable to locate theme engine in module_path: "pixmap"

    sudo apt-get install  gtk2-engines-pixbuf:i386
    • 3
  2. Best Answer

    该问题似乎只发生在 64 位 Ubuntu 系统上的 i386 版本的 Google Chrome 上。这是 32 位与 64 位问题的暗示是安装:i386某些软件包的版本可以消除一些错误。我能够通过安装 64 位版本让 Chrome 再次工作：

    $ sudo aptitude install google-chrome-stable

The following packages have unmet dependencies:
 libappindicator1 : Conflicts: libappindicator1:i386 but 12.10.1+15.04.20141110-0ubuntu1 is installed.
 libappindicator1:i386 : Conflicts: libappindicator1 but 12.10.1+15.04.20141110-0ubuntu1 is to be installed.
 google-chrome-stable : Conflicts: google-chrome-stable:i386 but 42.0.2311.152-1 is installed.
 google-chrome-stable:i386 : Conflicts: google-chrome-stable but 42.0.2311.152-1 is to be installed.
 libindicator7 : Conflicts: libindicator7:i386 but 12.10.2+14.10.20140922-0ubuntu1 is installed.
 libindicator7:i386 : Conflicts: libindicator7 but 12.10.2+14.10.20140922-0ubuntu1 is to be installed.
The following actions will resolve these dependencies:

     Remove the following packages:
1)     google-chrome-stable:i386   
2)     libappindicator1:i386       
3)     libindicator7:i386          

Accept this solution? [Y/n/q/?]

    我接受了建议的解决方案，将几个软件包升级到 64 位版本，Chrome 又能正常工作了。

    • 1

  3. 不能总是更新应用程序，这对我有用

    $ sudo apt install gnome-themes-standard:i386
    • 1

  4. 我遇到了同样的问题，mkasberg 有解决方案——卸载 32 位并重新安装 64 位。我去了 google.com/chrome 并正常下载了 64 位 .deb。我运行了 .deb 并在软件中心打开了 google-chrome-stable。安装它，一切顺利，但事实证明 google-chrome-stable:i386 被安装了。

    $ sudo apt-get remove google-chrome-stable:i386
$ sudo apt-get install google-chrome-stable
    • 0

  5. 我正在使用带有前缀的 gtk 安装/usr/src/ClawsMail/install。上面的警告是在 (strace) 打印之后打印出来的：

    access("/home/carlo/.gtk-2.0/2.10.0/x86_64-pc-linux-gnu/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/carlo/.gtk-2.0/2.10.0/x86_64-pc-linux-gnu/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/carlo/.gtk-2.0/2.10.0/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/carlo/.gtk-2.0/2.10.0/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/carlo/.gtk-2.0/x86_64-pc-linux-gnu/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/carlo/.gtk-2.0/x86_64-pc-linux-gnu/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/carlo/.gtk-2.0/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/carlo/.gtk-2.0/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/2.10.0/x86_64-pc-linux-gnu/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/2.10.0/x86_64-pc-linux-gnu/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/2.10.0/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/2.10.0/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/x86_64-pc-linux-gnu/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/x86_64-pc-linux-gnu/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/src/ClawsMail/install/lib/gtk-2.0/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/2.10.0/x86_64-pc-linux-gnu/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/2.10.0/x86_64-pc-linux-gnu/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/2.10.0/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/2.10.0/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/x86_64-pc-linux-gnu/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/x86_64-pc-linux-gnu/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/engines/libadwaita.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gtk-2.0/engines/libadwaita.la", F_OK) = -1 ENOENT (No such file or directory)

    假设在我的主目录下没有找到是正常的，并且因为我的安装/usr/src/ClawsMail/install不正常，所以我假设正常libadwaita.so会找到<prefix>/lib/gtk-2.0/...，但我没有在相同的前缀下安装 libadwaita。

    但是 - 在查看之后/usr/src/ClawsMail/install继续查看，/usr/lib/gtk-2.0/...因此如果正常安装在/usr.

    我确实已经libadwaita.so在我的系统上安装了，并且在这里：

    /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libadwaita.so

    请注意，/usr/lib/gtk-2.0它甚至不存在。

    事实证明，此搜索发生在调用

    _gtk_find_module (name=0x5555557ee0e0 "adwaita", type=0x7ffff7b0c776 "engines") at gtkmodules.c:196

    并且搜索的路径是返回的路径

    paths = _gtk_get_module_path (type);

    从中获取三个前缀

    gchar **paths = get_module_path();

    事实证明，最后一个前缀 ( /usr/lib/gtk-2.0) 被称为pre_multiarch_dir，也就是 multiarch 之前的前缀；确实不再使用了。

    因此，我的问题是我没有将引擎安装在与安装 gtk-2.0 的位置相同的前缀中。但是，可以使用环境变量扩展搜索：

    如果GTK_EXE_PREFIX已设置，$GTK_EXE_PREFIX/lib/gtk-2.0则将使用gtk -2.0 本身的安装前缀和 pre_multiarch_dir（因此在现代多体系结构上没有用）。

    如果GTK_PATH已设置，那么它将在其他所有内容之上使用。我相信后者甚至可以是一个以分号分隔的路径列表。

    使用

    export GTK_PATH="/usr/lib/x86_64-linux-gnu/gtk-2.0"

    因此，让我的警告消失了。

    • 0

  6. 对于 Kubuntu 20.04 这对我有用（尝试运行 JavaFX 应用程序时出现此错误）：

    sudo apt install gnome-themes-standard
    • 0

  7. 在我的一个 CentOS-7 机器上，这个烦人的警告/错误已经存在很长时间了。（我预计 Ubuntu 的原因可能相同）。

    今天终于查到了。在 Gtk-2.0 目录中，缺少动态库文件：“libadwaita.so”。每次启动 Gnome/X11 窗口应用程序时，我都会收到此警告消息：

    Gtk-WARNING **：...无法在 module_path 中找到主题引擎：“adwaita”

    “libadwaita.so”文件必须放在目录中：

    /usr/lib64/gtk-2.0/2.10.0/engines

    “adwaita”主题似乎是 Gnome 的默认主题，在一些早期的 Gnome 安装中，动态 lib 文件没有被放入正确的位置。在给出警告错误的机器上，我只有两个文件：“liboxygen-gtk.so”和“libpixmap.so”，而没有问题的机器有所有三个 lib 文件。我通过简单地将正确的“libadwaita.so”库复制到上面的 Gtk-2.0“引擎”目录来解决警告错误消息。无需其他更改。注意：我安装了所有最新版本的 Gnome 主题、引擎等。Linux 内核是 4.4.185-1。

    我刚刚使用 C 构建了一个 Glade/GTK-2.0 应用程序，每次启动时都会出现两个这个烦人的警告错误实例。一切正常，但是警告错误会在调用 xterm 窗口中以亮黄色突出显示的文本弹出，这让我的应用程序看起来有问题，所以我今天不得不追查这个问题。希望此信息有所帮助。

    • 0

相关问题