opensuse 12.2 64bit kde
I’ve just updated, first time for several weeks, and ever since all yast dialogs are blank (solid grey). I can still use the text version from a terminal. The problem is only in the desktop. The dialogs look to still work, in that clicking on random positions produces new blank dialogs of sizes that vary with the position clicked. I have no idea really where to look for a fix. Any advice would be most welcomed.
Cheers,
Paul.
A screenshot posted through http://paste.opensuse.org/ might help people “see” your problem
Here you go: SUSE Paste
I’ve just installed 12.3 on another server, and I have the same problem, but it’s only when I access the desktop via vnc. I don’t believe it’s a tightvnc bug, or a kde bug because every other window I open is fine. It’s a recently introduced bug in yast. Where should I report this?
What makes you so sure about Yast. If Yast works OK when locally accessed, the bug is not in Yast, the bug/misconfiguration IMHO should be in the vnc connection.
Not the core of Yast, but the Yast kde app - something descended from the package patterns-openSUSE-kde4_yast, I’d guess - something wrong in the way it updates the screen, so that vnc doesn’t pick up the update. I doubt if its a problem with vnc: I didn’t update vnc; my vncserver is date June 2012. Also, vnc is working perfectly with the windows of every other app. Could be kde itself, I suppose (my startkde is dated 21 Mar 2013, so definitely recently update), but then again, how come every other app displays fine?
I can’t see how it can be a misconfiguration either, since it is happening both with a recently updated 12.2 and a completely fresh install of 12.3. I haven’t had a chance to change anything in the fresh 12.3 install away from the default configuration.
Of course, this is all guess work. I’d welcome any advice on tracking it down more definitely. I’d like to find out exactly what I updated on 21 Mar 2013, but I don’t know where to look for the log.
Am 22.03.2013 23:16, schrieb Glidos:
> I’d like to find out exactly what I updated on
> 21 Mar 2013, but I don’t know where to look for the log.
One simple method
rpm -qa --last | less
scroll down to 21 Mar 2013 what it shows.
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.1 | GTX 650 Ti
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.1 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500
On 2013-03-23 00:43, Martin Helm wrote:
> Am 22.03.2013 23:16, schrieb Glidos:
>> I’d like to find out exactly what I updated on
>> 21 Mar 2013, but I don’t know where to look for the log.
> One simple method
>
> rpm -qa --last | less
>
scroll down to 21 Mar 2013 what it shows.
I have a more complex line:
rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
%{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
%{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}
" \
| sort | cut --fields="2-" --delimiter=\; \
| tee rpmlist.csv | less -S
or
rpm -q -a --queryformat "%{INSTALLTIME} %{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME} %15{VERSION}-%-7{RELEASE} %{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" > rpmlist
>
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Brilliant! Thank you both. Here’s the result:
Thu Mar 21 2013 Tue Feb 19 2013 libzypp 11.8.0-2.8.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Tue Feb 19 2013 zypper-aptitude 1.7.11-1.9.1 noarch openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Tue Feb 19 2013 zypper-log 1.7.11-1.9.1 noarch openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Tue Feb 19 2013 zypper 1.7.11-1.9.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Tue Feb 19 2013 libqdialogsolver1 1.3.0-14.4.3 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Jul 16 2012 libebl1 0.153-2.1.5 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Mar 09 2013 MozillaFirefox 19.0.2-2.37.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 libqt4 4.8.1-2.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Mar 09 2013 krb5 1.10.2-3.12.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 yast2-ncurses 2.22.5-1.4.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Mar 09 2013 krb5-32bit 1.10.2-3.12.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Feb 27 2013 kernel-desktop 3.4.33-2.24.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Mar 04 2013 xorg-x11-Xvnc 7.6_1.12.3-1.25.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Thu Mar 14 2013 timezone 2013b-1.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Mar 09 2013 systemtap-runtime 1.7-3.8.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Mar 11 2013 perl-base 5.16.0-3.5.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Thu Mar 14 2013 microcode_ctl 1.17-137.6.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Feb 27 2013 kernel-devel 3.4.33-2.24.1 noarch openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Thu Mar 14 2013 timezone-java 2013b-1.16.1 noarch openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Mar 09 2013 MozillaFirefox-translations-common 19.0.2-2.37.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 libqt4-sql 4.8.1-2.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 yast2-ncurses-pkg 2.22.8-2.4.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Mar 09 2013 systemtap 1.7-3.8.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Mar 04 2013 xorg-x11-server 7.6_1.12.3-1.25.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Fri Mar 01 2013 sudo 1.8.5p2-2.4.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Mar 11 2013 perl 5.16.0-3.5.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Feb 27 2013 kernel-default-devel 3.4.33-2.24.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Thu Mar 14 2013 java-1_7_0-openjdk 1.7.0.6-3.33.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 libqt4-sql-mysql 4.8.1-2.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 libqt4-sql-sqlite 4.8.1-2.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 libqt4-x11 4.8.1-2.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Feb 27 2013 kernel-desktop-devel 3.4.33-2.24.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 libqt4-qt3support 4.8.1-2.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Feb 27 2013 kernel-source 3.4.33-2.24.1 noarch openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Mon Feb 25 2013 libqt4-devel 4.8.1-2.16.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Feb 27 2013 kernel-xen-devel 3.4.33-2.24.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Feb 27 2013 kernel-syms 3.4.33-2.24.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Tue Mar 12 2013 flash-player 11.2.202.275-1.34.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Tue Mar 12 2013 flash-player-kde4 11.2.202.275-1.34.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Wed Jul 18 2012 patterns-openSUSE-kde4_yast 12.2-5.5.1 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Jun 23 2012 perl-Email-Valid 0.187-2.1.1 noarch openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sat Jun 23 2012 perl-Exporter-Lite 0.02-6.1.1 noarch openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Sun Jul 15 2012 perl-Class-MethodMaker 2.18-6.1.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Fri Feb 15 2013 perl-Lingua-EN-Numbers-Ordinate 1.02-7.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_12.2 (none)
Thu Mar 21 2013 Sun Jul 15 2012 perl-Unicode-String 2.09-153.1.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 12.2 (none)
Thu Mar 21 2013 Tue Feb 12 2013 perl-Email-Find 0.10-1.1 noarch http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_12.2 (none)
Thu Mar 21 2013 Wed Jul 18 2012 perl-Term-ProgressBar 2.10-2.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_12.2 (none)
Thu Mar 21 2013 Sat Mar 02 2013 perl-Lingua-Preferred 0.2.4-4.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_12.2 (none)
Thu Mar 21 2013 Sun Mar 03 2013 perl-Log-TraceMessages 1.4-4.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_12.2 (none)
Thu Mar 21 2013 Tue Feb 12 2013 perl-HTML-FromText 2.05-5.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_12.2 (none)
xorg-x11-Xvnc is in there. I guess it could be that after all, although it’s strange that yast is the only affected app. patterns-openSUSE-kde4_yast is also in there, my original suspicion. Is there a way I can revert to the previous version of either?
The “pattern” packages do not contain software. They trigger the install of a bunch of packages that together form a pattern. This one triggers the use of QT on the Yast modules, so that it will visually integrate nicely in KDE.
So, since Xorg packages were included in the update, I’d say something re. the video driver might be borked, can you reinstall the driver, if you have one installed?
I could give that a go I guess, but I don’t hold up much hope given that I see exactly the same problem on a completely fresh install of 12.3. My intuition (albeit based on not a huge amount of knowledge) says that a problem that occurs in 12.2 just after an update and on 12.3 when just installed, isn’t likelty to be fixed by a reinstall.
Also the problem occures only when accessing the desktop via vnc. It works fine (for the 12.3 system at least) if I use a connected monitor directly. Does that still make sense as a video driver problem?
“Triggereing use of QT on the Yast modules” sounds suspicious to me. Is there any way I can untrigger it?
To the op
I have a bit of a problem with yast on three machines after the installation
of 12.3. I notice when I use the yast2-system-/etc/sysconfig editor
when I attempted to save, there is a pop-up error message
reinstalling the yast2 and yast2 core did the trick.
My guess the installation dvd has the problem.
With the online update of yours try reinstalling the yast2, yast2 core and also you (yast2 online update) package
from the openSUSE repo not from your dvd iso and might solve it. Just a wild guess.
I apologize, got carried away with 12.3 in mind, please disregard my post or to the admin please delete this two posts of mine.:shame:
I have new information as to the cause of this. It is something to do with the use of shared memory. When run from a virtual vnc display yast2 is reporting these errors:
X Error: BadAccess (attempt to access private resource denied) 10
Extension: 130 (MIT-SHM)
Minor opcode: 1 (X_ShmAttach)
Resource id: 0x119
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 5 (X_ShmCreatePixmap)
Resource id: 0x4f
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x2600012
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 54 (X_FreePixmap)
Resource id: 0x2600012
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 2 (X_ShmDetach)
Resource id: 0x2600012
Looks like this bug:
https://bugzilla.novell.com/show_bug.cgi?id=807781
It seems to be a bug in libqt4…
Great thanks. So I guess it’ll get fixed eventually. Do you think that installing the working rpm on my 12.3 system is likely to fix it, or is that more likely to cause other problems?
Well, the problem is, that the package reported as working in the bugreport isn’t available anymore…
For 12.2 you could try an older package from the update repo, 4.8.1-2.12.1 should be ok (change all the libqt4-* packages). But if you install that on 12.3 you will get dependency problems for sure…
Somehow I have the feeling the issue is caused by this change:
Thu Feb 21 09:56:04 UTC 2013 - mvyskocil@suse.com
- fix bnc#802634: information disclosure via QSharedMemory (CVE-2013-0254)
* libqt4-CVE-2013-0254.patch
which fixes this security issue: [Announce] [CVE-2013-0254] Qt Project Security Advisory: System V shared memory segments created world-writeable]([Announce] [CVE-2013-0254] Qt Project Security Advisory: System V shared memory segments created world-writeable)
I have built the latest libqt4 packages without this patch in my home repo:
Index of /repositories/home:/wolfi323:/branches:/KDE:/Qt
Please try them and report back whether they work for you!
Brilliant. Thank you. That worked.
At first, when I installed just libqt4 it didn’t, but I also installed libqt4-devel, libqt4-qt3support and libqt4-x11 from your repo and then yast sprang back to life.
Fine.
At first, when I installed just libqt4 it didn’t, but I also installed libqt4-devel, libqt4-qt3support and libqt4-x11 from your repo and then yast sprang back to life.
According to the bugreport, libqt4-x11 is the one, but it is better to install all of them from the same repo…
Maybe you could join in the bug report and say that those packages fixed it for you?
Sure, no problem. Done. Thanks again.