|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast can't open display | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Forgotten User Uovvn3Qp0x <forgotten_Uovvn3Qp0x> |
| Component: | YaST2 | Assignee: | openSUSE GNOME <os.gnome.maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dimstar, forgotten_Uovvn3Qp0x, jreidinger |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
output from journalctl
core dump y2logs after `zypper dup` |
||
yast core dumped, please attach archive produced by save_y2logs script. Looks like some problem with dependencies. Created attachment 713873 [details]
core dump
Output from the y2_logs script is archived here: https://drive.google.com/file/d/0B13znJfYws3YZHo3WkwyWWtacjA/view?usp=sharing thanks for logs. reason why it failed is this one 2017-02-12 11:57:35 <3> cbrodt-traitify2(12619) [ui] YUIPlugin.cc(YUIPlugin):50 Could not load UI plugin "qt": /usr/lib64/libharfbuzz.so.0: undefined symbol: FT_Get_Var_Blend_Coordinates so reassigning to maintainer of harfbuzz What versions of freetype and harfbuzz do you have installed? rpm -q libfreetype6 libharfbuzz0 libfreetype6-2.6.3-2.11.x86_64 libharfbuzz0-1.4.2-1.1.x86_64 (In reply to Christopher Brodt from comment #6) > libfreetype6-2.6.3-2.11.x86_64 > libharfbuzz0-1.4.2-1.1.x86_64 these are not the currently provided packages by Tumbleweed. Please properly update your system, ensuring you get libfreetype6-2.7.1 from Tumbleweed For reference: libfreetype6-2.7.1-1.1.x86_64 Created attachment 714288 [details]
y2logs after `zypper dup`
I did a `zypper dup` and now have the proper version of freetype. However, still getting a core dump trying to open Yast2. I've attached the save_y2logs tar.
For thoroughness, this is the log message from journalctl
Feb 15 16:39:42 cbrodt-traitify2 gnomesu-pam-backend[22977]: pam_unix(gnomesu-pam:session): session opened for user root by (uid=1000)
Feb 15 16:39:42 cbrodt-traitify2 gnomesu-pam-backend[22977]: pam_systemd(gnomesu-pam:session): Cannot create session: Already running in a session
Feb 15 16:39:42 cbrodt-traitify2 YaST.desktop[22968]: No protocol specified
Feb 15 16:39:42 cbrodt-traitify2 YaST.desktop[22968]: QXcbConnection: Could not connect to display :0
Feb 15 16:39:42 cbrodt-traitify2 systemd[1]: Started Process Core Dump (PID 22998/UID 0).
Feb 15 16:39:42 cbrodt-traitify2 YaST.desktop[22968]: /sbin/yast2: line 445: 22997 Aborted (core dumped) $y2ccbin $Y2UI_ARGS "$@"
Feb 15 16:39:42 cbrodt-traitify2 systemd-coredump[22999]: Process 22997 (y2controlcenter) of user 0 dumped core.
Feb 15 16:39:43 cbrodt-traitify2 gnomesu-pam-backend[22977]: pam_unix(gnomesu-pam:session): session closed for user root
Are you running in a Wayland session? then you might 'just' be hit by https://bugzilla.opensuse.org/show_bug.cgi?id=955101 workarounds would be using an X-session - or, as documented in the linked bug: before starting yast xhost +LOCAL: (and xhost -LOCAL: once done) Yep, running Wayland. That seems to have fixed it! Thanks for your help. For the record, when I update to the latest Tumbleweed snapshots, I've been doing "zypper up". Should I be doing "zypper dup" instead? (In reply to Christopher Brodt from comment #11) > Yep, running Wayland. That seems to have fixed it! Thanks for your help. Thanks - in this case I mark it as a dup of the old bug; the wayland integration is known to have this problem for now > For the record, when I update to the latest Tumbleweed snapshots, I've been > doing "zypper up". Should I be doing "zypper dup" instead? Not really part of the bug, but: "yes. zypper dup --no-allow-vendor-change is in most cases the right thing to do" See also the (long) mailthread at https://lists.opensuse.org/opensuse-factory/2017-02/msg00240.html *** This bug has been marked as a duplicate of bug 955101 *** |
Created attachment 713791 [details] output from journalctl On latest round of updates, opening yast fails on GNOME Wayland session. Attached log output.