[opensuse] yast2 over ssh
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, tumbleweed, kde, x11: i recognized that i am not able to use yast2 over ssh any more. this was working before (about 2 or 3 weeks). must i set something special NOW? or is this a know bug? simon@becherer1:~> ssh -X becherer1 Last login: Fri Jun 22 07:53:33 2018 from 127.0.0.1 Have a lot of fun... simon@becherer1:~> su Passwort: becherer1:/home/simon # yast2 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 now a window opens: "Yast-Kontrollzentrum @ becherer1" but the window is empty, no respond. "the wrong ownership......" message, i think is normal this i have had before also (maybe only once), so i think this has nothing to do. same situation if i use ssh to another tumbleweed system. switching off firewalld will not help ssh -X for yast2 to a opensuse 11.4 system works fine. (also no ownership error) from 11.4 to tumbleweed also yast2 work fine. some error messages: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 libGL error: failed to load driver: swrast QXcbShmImage: xcb_shm_attach() failed with error: 10 (BadAccess), sequence: 474, resource id: 473, major code: 147 (Unknown), minor code: 1 working. ========================================== only tumbleweed to tumbleweed did not work. ========================================== starting other graphical tools like clamtk as root, or firefox or thunderbird (as user) will work fine. what is going on here? simoN - -- www.becherer.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJbLJf7AAoJEOuDxDCJWQG+VGYP/Rfaf/ynvz7vNJDFC4DlZnio Einy78sr3xMCwri6zXPmomMfq5I+IAlGZqju+tjtkiKJ+rw49e7Sig1EXHk8Bs1N 8waVadR71ft9daCamc2qmOqQLQWUuABqs0VmMXMWbG7scrzkGpnuWmBJdfMFE6yB T/9TyOYOEo4J06n4bhuWHVAXNuwIkYm9kzJMpxMV5acaQ/RViVk2SBmfg8fUEabL Gx+HjMereGWw3xjg/T7Lq5WGxVYIbv8iYwWI3Z//grMPzxzJHvs8qoqFeCHBSIoC kjYgEMTDJIvqs6VWt9sZJbngEbeaOJNq1r5n0h8SOR1SEu8E+wD7lYed5cYKXqsJ yMkfq5EvN/LybOs053/ejlKOWzrR0YvRsMCljbmKNLC4WxuBU2HufRabQmsvUAUB zQFdjg90HP1E9g4rfAU3+/DQgkUiPDo2vb7HOugnWOxDuh127UGA4PM9+LjYQ4DL EFKvQNUbSf/eebPIXhxUm9f+oT6niS/UQxyphNu5yY+inprYGmHXnTokzngWSJhP MexQQ8XH0sOPeVXuDIxdu0QTaAAbcYLvX8cGNRD26SSMIbweAHbl7ANgZ6z1agxN EF4NDijJLYnFKYe7SMJnxFvRgWIqDGOxAgcoj3N/SiTgpau8O3MtIURQbkJjxZ5d 7qCu+9zHiqX17UtR+i1X =exXl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
tumbleweed, kde, x11:
i recognized that i am not able to use yast2 over ssh any more. this was working before (about 2 or 3 weeks).
must i set something special NOW? or is this a know bug?
...
ssh -X for yast2 to a opensuse 11.4 system works fine. (also no ownership error)
Unfortunately I only have one TW system around, so I cannot test -X-ing between those. But from TW to Leap 42.3 it does work w/o errors, too. Both with direct logins (ssh root@) and the method you use ( ssh user@; su).
========================================== only tumbleweed to tumbleweed did not work. ==========================================
starting other graphical tools like clamtk as root, or firefox or thunderbird (as user) will work fine.
what is going on here?
Weird indeed. I intended to set up another TW here anyhow today/in the comming days. Will try it then... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi , per,
Unfortunately I only have one TW system around, so I cannot test -X-ing between those. But from TW to Leap 42.3 it does work w/o errors, too. Both with direct logins (ssh root@) and the method you use ( ssh user@; su).
simon@becherer1:~> ssh -X becherer1 ====== ======== could you test to ssh your single machine from itself? this also did not work heren simoN - -- www.becherer.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJbLMSbAAoJEOuDxDCJWQG+84QP/ifbz1i/H5a+03pzTl/biJyi dZhgPSRjk93Q39r8QkkgCTCEvr1oBTNBwXbUFTvHewHHKT+klp1Hm4UUdYfYBa+I Xr6z5T+anFP6osHme0uHdEk1Ed0bXfLZiZFhW/0I3gnnW6ij1XKSirCHllncOI4k L0f5bAr/qn0/VTvVbvYkA8KbnTFB0SdodR/p5T6ku+v/M/6u4l5E2mZUqk4HmtYy 5Tj3WnoyXSyNXAAO0qyhDhorUGtAtDfpM7ADag7svJXsM8KtAioG1O2rJfQufZx1 o1ar8WoGTdr3H0HaeUNZXLsk46zYg50aWRycorPj0s+Uj2ri1wRmHO3x6ImBSwka ntLhHVo1gvn6XMt/2SHKXxVl1BMFLuD9ibNINcW5OTd59zM0+Mi83MNts0xyjghz +m4upZIv02ufL1YN+AjVadlt/CGJ8HzsEe8+qPKi44Z29UJAPD0rTmLRnusIlRUn IvD3fS2PDCi19o3t59cMY3fiLm0cixY1UUIAe+QadyXefb+9RFADSXL5WPJ3/FtK MwAdz4UARhb2DsK8nBb7ewWEA4ybMIVO9cI69B988PLrdTPCdxZNNYCBKmpF6/IV zuY6eXvGp0ZefIxBiBeNWqK5I1XqoTw95XdltJFv/lWGAktHqoh8H9TXM+ZZd5Eo 2mVc+8QYtJU4FFC8maj5 =4nmi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi , per,
Unfortunately I only have one TW system around, so I cannot test -X-ing between those. But from TW to Leap 42.3 it does work w/o errors, too. Both with direct logins (ssh root@) and the method you use ( ssh user@; su).
simon@becherer1:~> ssh -X becherer1 ====== ========
could you test to ssh your single machine from itself? this also did not work heren
Ah, smart :D Yes, indeed exactly the same symptom. The window frame opens, but only contains the previous background, no content displayed (no error messages either anywhere). Likely an qt issue? I can start a normal X application like xterm or xv, but qt stuff like yast2 or dolphin fail. Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Peter Suetterlin <pit@astro.su.se> [06-22-18 05:55]:
Simon Becherer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi , per,
Unfortunately I only have one TW system around, so I cannot test -X-ing between those. But from TW to Leap 42.3 it does work w/o errors, too. Both with direct logins (ssh root@) and the method you use ( ssh user@; su).
simon@becherer1:~> ssh -X becherer1 ====== ========
could you test to ssh your single machine from itself? this also did not work heren
Ah, smart :D Yes, indeed exactly the same symptom. The window frame opens, but only contains the previous background, no content displayed (no error messages either anywhere).
Likely an qt issue? I can start a normal X application like xterm or xv, but qt stuff like yast2 or dolphin fail.
I observe the same, empty window outline with no err msg. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 22/06/2018 à 14:03, Patrick Shanahan a écrit :
I observe the same, empty window outline with no err msg.
but then, may be you have access to the logs? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* jdd@dodin.org <jdd@dodin.org> [06-22-18 08:07]:
Le 22/06/2018 à 14:03, Patrick Shanahan a écrit :
I observe the same, empty window outline with no err msg.
but then, may be you have access to the logs?
yes, appears following relevant: 2018-06-22T08:05:48.739499-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined 2018-06-22T08:05:48.757676-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:119:22: Unable to assign [undefined] to QQmlListModel* and 2018-06-22T08:05:50.545352-04:00 Crash plasmashell[12374]: QXcbConnection: XCB error: 2 (BadValue), sequence: 33551, resource id: 50331654, major code: 142 (Unknown), minor code: 3 2018-06-22T08:05:50.727062-04:00 Crash plasmashell[12374]: QXcbConnection: XCB error: 2 (BadValue), sequence: 33569, resource id: 58720270, major code: 142 (Unknown), minor code: 3 2018-06-22T08:05:51.083753-04:00 Crash plasmashell[12374]: QXcbConnection: XCB error: 2 (BadValue), sequence: 33594, resource id: 50331654, major code: 142 (Unknown), minor code: 3 2018-06-22T08:07:27.160537-04:00 Crash kwin_x11[12368]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7392, resource id: 180355073, major code: 18 (ChangeProperty), minor code: 0 2018-06-22T08:07:27.163957-04:00 Crash kwin_x11[12368]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7396, resource id: 180355074, major code: 18 (ChangeProperty), minor code: 0 2018-06-22T08:08:37.206709-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:41: ReferenceError: AppPid is not defined 2018-06-22T08:08:37.206913-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:36: ReferenceError: index is not defined 2018-06-22T08:08:37.206983-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:181: ReferenceError: IsMinimized is not defined 2018-06-22T08:08:37.207035-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:37: ReferenceError: index is not defined 2018-06-22T08:08:37.207112-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:437: ReferenceError: VirtualDesktop is not defined 2018-06-22T08:08:37.207181-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:395: ReferenceError: model is not defined 2018-06-22T08:08:37.207532-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:437: ReferenceError: VirtualDesktop is not defined -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi patrik,
2018-06-22T08:05:48.739499-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined 2018-06-22T08:05:48.757676-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:119:22: Unable to assign [undefined] to QQmlListModel* and
how you got this error log ? could you tell me thecommand to get this? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Simon Becherer <simon@becherer.de> [06-22-18 09:40]:
Hi patrik,
2018-06-22T08:05:48.739499-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined 2018-06-22T08:05:48.757676-04:00 Crash plasmashell[12374]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:119:22: Unable to assign [undefined] to QQmlListModel* and
how you got this error log ? could you tell me thecommand to get this?
I use rsyslog instead of journal, but: most /var/log/messages -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, yes, dolphin as a normal user ssh to same machine also empty window. www.becherer.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJbLOo5AAoJEOuDxDCJWQG+8UIP/3J3VB1xtukeW3fRxkgGCBv+ JaVE/Yy8fy0+5DkQPvyCVw60Hs82YYjolnMJjS5y80xcmaSl1wFGmdibHIb5e/Z8 MDegUnZefAGnMC2O0JHEebCkNQV79G31xZBq8AeV4KAfBilbPwTR1wZk7eMjsD1b 1vrgZoziMae/TPLvRHaagXG5S8k6SoSzy9Kdblh5rQvnP5ZP2jeGRMHnYg0P9xBY liNj9OGSDBrs3vl9FmRz8QI2Y1H/Z2mV3mzlm9xUsfhjsm4vHPCi5cWHPm6riDZM D5FOXHBa0h2Gp6DIwZvTc1SCWkvx6Iy0WpaBm94x8WExFe7CN3V0rBz8l/g2aZ/j MBAuk7WAcPhkqJW+wB5PsYsZ/CxHWaro2gn9I35W4kjSfJMWZdEFrDxrhp+uNTgS g/+D0jglsOIx67pxQzJIBIVnmoUBM2XEPAbrl3kc8LD7bfSlcAhrIq3lMdX9n9Mb TiHgHJJJkpvOb4AW+7tdBwSM7kokeY9fO/d9v2AkeTzcJA33GdTjwTDH3OMrgRF2 BKp8/RidOx4Ay5vkbejDtYPWdBzgr/hSekQw73na9uAxkmg8XuCjbdxxnjGtE1th 8o5049y0lDezhjN1JPg391GMQf6A7hKgc/Tk0iSwyO7hTPoZSZiPjUDqu3WaUe74 ZdmGI8MC9zqTOaUe7FFn =GivC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-22 08:32, Simon Becherer wrote:
Hi,
tumbleweed, kde, x11:
i recognized that i am not able to use yast2 over ssh any more. this was working before (about 2 or 3 weeks).
must i set something special NOW? or is this a know bug?
simon@becherer1:~> ssh -X becherer1 Last login: Fri Jun 22 07:53:33 2018 from 127.0.0.1 Have a lot of fun... simon@becherer1:~> su Passwort: becherer1:/home/simon # yast2 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
I can't test this just now, but two suggestions: 1) ssh -X root@machine which is what I normally do. 2) ssh -X user@machine su - -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi carlos,
I can't test this just now, but two suggestions:
1) ssh -X root@machine
which is what I normally do.
2) ssh -X user@machine su -
first one i could not test, i have some restrictions set (i do not know where) to do not ssh direct as root. second one do exactly same as without "user@" i tried: yast2 --gtk .. the gtk gui has beeen retired, fallung back to qt empty not responding window yast2 --qt same here empty not respons window yast2 --ncurses will start simoN - -- www.becherer.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJbLMmoAAoJEOuDxDCJWQG+/G4QAIsK3UwkED+kjoHeNIV/SlFq 2E7ahnXeCZ9dSQ4nzvmUVtaT73swftfdHnejXFirOjgSMmgR9OeDEA7RIYWlnZ1o l36a+T2DjBD/LLFBpOUiOS/MrJkUcIBdObOeQJyx0gd02FBMTMAaHjMGXJ4e+iE2 794xOO0UBYR5Cdo5W6giZtjz82fnqTJjCuII1OkyXItCKLkokkwxjE54zFoSA0o2 aqFx16tGDFHUXlpa2cq+1HkQbklibAJyKJoL3OvQfBEgJ5UStQ1lixB70OCv0m/o nLkPiIVMFoyTBbID3EjeNoJa7sm/9+DLts1CjFVsIvfMQPBr/GvDcjVceNy+shZx Jb5w4WE6EpvoxjfPz5TnuWFow/uAYalBwqkRM3r5jTfHwsATv8efMzwvZVYxl2RH mdOu6343qHQKRgpSoAWh9Y07ZMlSSsdiksxPfGR3U16un5syGAXxo+AyQO9UlbbB BRxn1zWdH5fmK6VJzzn81ZFhF/A9KFOWWEgp7Sp1OUyA3m+IpR/A5J+7TbNxomOR Ah6Wc7Wk4khlKaXr7WopinczfARxfpiTBp1gu9dXUsuePBbdCNjAM7WHex8vlsq1 aJVj7oYPBxOdHnl3h8Vpw0glKR58svF9e4qGD5VY6W+WMdu2M2u7W93Eni56g3iF pi5wf/LYQnrcrVruX+jr =phQh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 22 Jun 2018 12:04:24 +0200, Simon Becherer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi carlos,
I can't test this just now, but two suggestions:
1) ssh -X root@machine
which is what I normally do.
2) ssh -X user@machine su -
first one i could not test, i have some restrictions set (i do not know where) to do not ssh direct as root.
second one do exactly same as without "user@"
i tried:
yast2 --gtk .. the gtk gui has beeen retired, fallung back to qt empty not responding window
yast2 --qt same here empty not respons window
yast2 --ncurses will start
simoN
Hello: I had similar problem (empty windows) with KDE4 when used vnc through ssh. I could solve it by running on the remote machine in terminal:
export QT_X11_NO_MITSHM=1 su # yast2
Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, istvan,
I had similar problem (empty windows) with KDE4 when used vnc through ssh. I could solve it by running on the remote machine in terminal:
export QT_X11_NO_MITSHM=1 su # yast2
Istvan
bad luck, did not work here. simoN www.becherer.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJbLOvUAAoJEOuDxDCJWQG+2NwP+wbXiSXv5ZT1xBGcoLVElBQn +H+zBW2OhoMsN29TysMI/UiK55iCuII3X2Yk2ut1W8CFQ4Hl+3aYmguoCsdxAxQl cc1ygw0HNQseIr+wy+gyLL0NQmfloyP5J4+YxOahWNKhac7vzeZMcb7xTHaqDyNg 1FuNEEMsyuHLTsxTaQi6qcojacfEgjd4WOcztN1vwU26z9v7rUw8JY7RiPo5ZDzB a8zxJe1qcCAEpYt3K2DwL95nVdX+py+ssTPaeCC8WFfMQT22NE0PkBQO5lSrZHyt QUs3PMnfsuKguzlwBXa7jrtbI+yUQ820j0oPEICzr62fC//mh9igo4/u0W/vm5j9 iqjVhK5Y76LnkR/ja8GTryGxz/TC+wQ4deGQm+5PYlw6qbgMAn6q+SXMNhKCK6Co XNi2dyGvcPQ1YBiqqxzRC0aQNJVLrYGmKeKc40CB1pS81zQxU9UDQmYXOVl2/xxK fcvw582a0c5Ah4AWd5rH8hMxeisTWBLo/Qn1o9BltmoerqAajFBFNIkEk/pfdx1q q8SbVYUkq2wvfQafhw8WgXNCmPSAPvFX+nNbGBHKm3qS853AHocma0kMS3oVIn0W v+/jUdf/sXEOASS46Zf9POz8Tg+KZj5Poc8uPbEXesVnakLfgMhoP/AFqH1WHjPZ lj4f++ETGDY6IQZmsZ5x =4y6a -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 6/22/18 5:30 AM, Simon Becherer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi, istvan,
I had similar problem (empty windows) with KDE4 when used vnc through ssh. I could solve it by running on the remote machine in terminal:
export QT_X11_NO_MITSHM=1 su # yast2
Istvan
bad luck, did not work here.
simoN
I do yast2 over ssh all the time, but X forwarding has to be working -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-22 12:04, Simon Becherer wrote:
Hi carlos,
I can't test this just now, but two suggestions:
1) ssh -X root@machine
which is what I normally do.
2) ssh -X user@machine su -
first one i could not test, i have some restrictions set (i do not know where) to do not ssh direct as root.
second one do exactly same as without "user@"
i tried:
yast2 --gtk .. the gtk gui has beeen retired, fallung back to qt empty not responding window
yast2 --qt same here empty not respons window
yast2 --ncurses will start
Finally I managed to update my test TW system, and I can reproduce the issue. I did "ssh -X root@machine" from 42.3 XFCE to TW. Then I started "yast -qt" and got an empty window that did not respond, I have to forcibly close it. Tumbleweed:~ # yast --qt libGL error: failed to load driver: swrast No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(SingleBuffer), swapInterval 1, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Falling back to using screens root_visual. QXcbShmImage: xcb_shm_create_segment() failed for size 1420440 The X11 connection broke (error 1). Did the X11 server die? Tumbleweed:~ # -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
22.06.2018 20:15, Carlos E. R. пишет:
On 2018-06-22 12:04, Simon Becherer wrote:
Hi carlos,
I can't test this just now, but two suggestions:
1) ssh -X root@machine
which is what I normally do.
2) ssh -X user@machine su -
first one i could not test, i have some restrictions set (i do not know where) to do not ssh direct as root.
second one do exactly same as without "user@"
i tried:
yast2 --gtk .. the gtk gui has beeen retired, fallung back to qt empty not responding window
yast2 --qt same here empty not respons window
yast2 --ncurses will start
Finally I managed to update my test TW system, and I can reproduce the issue.
I did "ssh -X root@machine" from 42.3 XFCE to TW. Then I started "yast -qt" and got an empty window that did not respond, I have to forcibly close it.
Tumbleweed:~ # yast --qt libGL error: failed to load driver: swrast No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(SingleBuffer), swapInterval 1, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Falling back to using screens root_visual. QXcbShmImage: xcb_shm_create_segment() failed for size 1420440
https://lists.opensuse.org/opensuse-factory/2018-06/msg00078.html Looks more like finger pointing to me (i.e. - it worked in the past in Qt, then stopped, then Qt claim it is Xserver fault. Go figure). Anyway, ssh is obviously not the only way to forward sockets from remote to local system, so patch to Xserver which checks for process name looks ridiculous.
The X11 connection broke (error 1). Did the X11 server die? Tumbleweed:~ #
On 06/23/2018 12:27 AM, Andrei Borzenkov wrote:
https://lists.opensuse.org/opensuse-factory/2018-06/msg00078.html
Looks more like finger pointing to me (i.e. - it worked in the past in Qt, then stopped, then Qt claim it is Xserver fault. Go figure).
Anyway, ssh is obviously not the only way to forward sockets from remote to local system, so patch to Xserver which checks for process name looks ridiculous.
No complaints here, ssh -Y host, then su and yast2 http://paste.opensuse.org/38991242 -- David C. Rankin, J.D.,P.E.
On 2018-06-23 07:56, David C. Rankin wrote:
On 06/23/2018 12:27 AM, Andrei Borzenkov wrote:
https://lists.opensuse.org/opensuse-factory/2018-06/msg00078.html
Looks more like finger pointing to me (i.e. - it worked in the past in Qt, then stopped, then Qt claim it is Xserver fault. Go figure).
Anyway, ssh is obviously not the only way to forward sockets from remote to local system, so patch to Xserver which checks for process name looks ridiculous.
No complaints here, ssh -Y host, then su and yast2
cer@Telcontar:~> ssh -Y root@192.168.1.137 Password: Last login: Fri Jun 22 19:11:12 2018 from 192.168.1.14 Have a lot of fun... Tumbleweed:~ # yast --qt libGL error: failed to load driver: swrast No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(SingleBuffer), swapInterval 1, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Falling back to using screens root_visual. -- kill here QXcbShmImage: xcb_shm_create_segment() failed for size 1420440 The X11 connection broke (error 1). Did the X11 server die? Tumbleweed:~ # -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
David C. Rankin wrote:
On 06/23/2018 12:27 AM, Andrei Borzenkov wrote:
https://lists.opensuse.org/opensuse-factory/2018-06/msg00078.html
Looks more like finger pointing to me (i.e. - it worked in the past in Qt, then stopped, then Qt claim it is Xserver fault. Go figure).
Anyway, ssh is obviously not the only way to forward sockets from remote to local system, so patch to Xserver which checks for process name looks ridiculous.
No complaints here, ssh -Y host, then su and yast2
If you read the thread the error is linked to specific versions of TW, so having to mention what your OS status is should be obvious..... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2018 05:36 AM, Peter Suetterlin wrote:
No complaints here, ssh -Y host, then su and yast2 If you read the thread the error is linked to specific versions of TW, so having to mention what your OS status is should be obvious.....
That was a veiled attempt at humor since you are obviously looking at the Qt3 version of yast in that screenshot. I should have included the :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 06/23/2018 05:36 AM, Peter Suetterlin wrote:
No complaints here, ssh -Y host, then su and yast2 If you read the thread the error is linked to specific versions of TW, so having to mention what your OS status is should be obvious.....
That was a veiled attempt at humor since you are obviously looking at the Qt3 version of yast in that screenshot. I should have included the :)
Uh, my bad - that explains things(*). I'm using mutt, so don't see it in the mail, and only follow links that promise something interesting. Plus, the paste image likely is gone if someone reads the thread in the list archive in a month or two.... (I hadn't really expected such an 'error' from you, TBH.....) PS: And yes, I'd rate the qt3-yast a good joke :D -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-23 07:27, Andrei Borzenkov wrote:
22.06.2018 20:15, Carlos E. R. пишет:
Finally I managed to update my test TW system, and I can reproduce the issue.
I did "ssh -X root@machine" from 42.3 XFCE to TW. Then I started "yast -qt" and got an empty window that did not respond, I have to forcibly close it.
Tumbleweed:~ # yast --qt libGL error: failed to load driver: swrast No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(SingleBuffer), swapInterval 1, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Falling back to using screens root_visual. QXcbShmImage: xcb_shm_create_segment() failed for size 1420440
https://lists.opensuse.org/opensuse-factory/2018-06/msg00078.html
Looks more like finger pointing to me (i.e. - it worked in the past in Qt, then stopped, then Qt claim it is Xserver fault. Go figure).
Well, remember I had to kill the window, it was empty. I clicked on its 'X', the 42.3 host Xserver said it was not responding, do I kill it? I said yes, obviously, then got those messages about the Xserver server dying.
Anyway, ssh is obviously not the only way to forward sockets from remote to local system, so patch to Xserver which checks for process name looks ridiculous.
The X11 connection broke (error 1). Did the X11 server die? Tumbleweed:~ #
-- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
* Simon Becherer <simon@becherer.de> [06-22-18 02:35]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
tumbleweed, kde, x11:
i recognized that i am not able to use yast2 over ssh any more. this was working before (about 2 or 3 weeks).
must i set something special NOW? or is this a know bug?
simon@becherer1:~> ssh -X becherer1 Last login: Fri Jun 22 07:53:33 2018 from 127.0.0.1 Have a lot of fun... simon@becherer1:~> su Passwort: becherer1:/home/simon # yast2 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
now a window opens: "Yast-Kontrollzentrum @ becherer1"
but the window is empty, no respond.
"the wrong ownership......" message, i think is normal this i have had before also (maybe only once), so i think this has nothing to do.
same situation if i use ssh to another tumbleweed system. switching off firewalld will not help
ssh -X for yast2 to a opensuse 11.4 system works fine. (also no ownership error)
from 11.4 to tumbleweed also yast2 work fine. some error messages: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 libGL error: failed to load driver: swrast QXcbShmImage: xcb_shm_attach() failed with error: 10 (BadAccess), sequence: 474, resource id: 473, major code: 147 (Unknown), minor code: 1
working.
========================================== only tumbleweed to tumbleweed did not work. ==========================================
starting other graphical tools like clamtk as root, or firefox or thunderbird (as user) will work fine.
what is going on here?
simoN
- -- www.becherer.de
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJbLJf7AAoJEOuDxDCJWQG+VGYP/Rfaf/ynvz7vNJDFC4DlZnio Einy78sr3xMCwri6zXPmomMfq5I+IAlGZqju+tjtkiKJ+rw49e7Sig1EXHk8Bs1N 8waVadR71ft9daCamc2qmOqQLQWUuABqs0VmMXMWbG7scrzkGpnuWmBJdfMFE6yB T/9TyOYOEo4J06n4bhuWHVAXNuwIkYm9kzJMpxMV5acaQ/RViVk2SBmfg8fUEabL Gx+HjMereGWw3xjg/T7Lq5WGxVYIbv8iYwWI3Z//grMPzxzJHvs8qoqFeCHBSIoC kjYgEMTDJIvqs6VWt9sZJbngEbeaOJNq1r5n0h8SOR1SEu8E+wD7lYed5cYKXqsJ yMkfq5EvN/LybOs053/ejlKOWzrR0YvRsMCljbmKNLC4WxuBU2HufRabQmsvUAUB zQFdjg90HP1E9g4rfAU3+/DQgkUiPDo2vb7HOugnWOxDuh127UGA4PM9+LjYQ4DL EFKvQNUbSf/eebPIXhxUm9f+oT6niS/UQxyphNu5yY+inprYGmHXnTokzngWSJhP MexQQ8XH0sOPeVXuDIxdu0QTaAAbcYLvX8cGNRD26SSMIbweAHbl7ANgZ6z1agxN EF4NDijJLYnFKYe7SMJnxFvRgWIqDGOxAgcoj3N/SiTgpau8O3MtIURQbkJjxZ5d 7qCu+9zHiqX17UtR+i1X =exXl -----END PGP SIGNATURE-----
Crash:~ > ssh -XCf root@crash2 yast2 works for me here between two tumbleweed machines both up-to-date and both with kde/plasma and x11 in fact, works correctly both ways between four different tumbleweed machines. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [06-22-18 07:59]:
* Simon Becherer <simon@becherer.de> [06-22-18 02:35]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
tumbleweed, kde, x11:
i recognized that i am not able to use yast2 over ssh any more. this was working before (about 2 or 3 weeks).
must i set something special NOW? or is this a know bug?
simon@becherer1:~> ssh -X becherer1 Last login: Fri Jun 22 07:53:33 2018 from 127.0.0.1 Have a lot of fun... simon@becherer1:~> su Passwort: becherer1:/home/simon # yast2 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
now a window opens: "Yast-Kontrollzentrum @ becherer1"
but the window is empty, no respond.
"the wrong ownership......" message, i think is normal this i have had before also (maybe only once), so i think this has nothing to do.
same situation if i use ssh to another tumbleweed system. switching off firewalld will not help
ssh -X for yast2 to a opensuse 11.4 system works fine. (also no ownership error)
from 11.4 to tumbleweed also yast2 work fine. some error messages: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 libGL error: failed to load driver: swrast QXcbShmImage: xcb_shm_attach() failed with error: 10 (BadAccess), sequence: 474, resource id: 473, major code: 147 (Unknown), minor code: 1
working.
========================================== only tumbleweed to tumbleweed did not work. ==========================================
starting other graphical tools like clamtk as root, or firefox or thunderbird (as user) will work fine.
what is going on here?
simoN
- -- www.becherer.de
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJbLJf7AAoJEOuDxDCJWQG+VGYP/Rfaf/ynvz7vNJDFC4DlZnio Einy78sr3xMCwri6zXPmomMfq5I+IAlGZqju+tjtkiKJ+rw49e7Sig1EXHk8Bs1N 8waVadR71ft9daCamc2qmOqQLQWUuABqs0VmMXMWbG7scrzkGpnuWmBJdfMFE6yB T/9TyOYOEo4J06n4bhuWHVAXNuwIkYm9kzJMpxMV5acaQ/RViVk2SBmfg8fUEabL Gx+HjMereGWw3xjg/T7Lq5WGxVYIbv8iYwWI3Z//grMPzxzJHvs8qoqFeCHBSIoC kjYgEMTDJIvqs6VWt9sZJbngEbeaOJNq1r5n0h8SOR1SEu8E+wD7lYed5cYKXqsJ yMkfq5EvN/LybOs053/ejlKOWzrR0YvRsMCljbmKNLC4WxuBU2HufRabQmsvUAUB zQFdjg90HP1E9g4rfAU3+/DQgkUiPDo2vb7HOugnWOxDuh127UGA4PM9+LjYQ4DL EFKvQNUbSf/eebPIXhxUm9f+oT6niS/UQxyphNu5yY+inprYGmHXnTokzngWSJhP MexQQ8XH0sOPeVXuDIxdu0QTaAAbcYLvX8cGNRD26SSMIbweAHbl7ANgZ6z1agxN EF4NDijJLYnFKYe7SMJnxFvRgWIqDGOxAgcoj3N/SiTgpau8O3MtIURQbkJjxZ5d 7qCu+9zHiqX17UtR+i1X =exXl -----END PGP SIGNATURE-----
Crash:~ > ssh -XCf root@crash2 yast2
works for me here between two tumbleweed machines both up-to-date and both with kde/plasma and x11
in fact, works correctly both ways between four different tumbleweed machines.
note: it does not work, presents empty window outline, if I ssh to another machine and then ssh -XCf back to original machine. but it does not present any error msgs. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi,
works for me here between two tumbleweed machines both up-to-date and both with kde/plasma and x11
cat /etc/os-release mh, i have here 3 machines: 2 times exact same hardware/software: amd ryzen / mesa amd graphics x11 kde/plasma tumbleweed: 20180618 both did have the problem with starting qt applications (dolphin or yast2) over ssh. from or to each other, or from themself. but working fine if i opensuse11.4 (old hardware) ssh to tumbleweed: 20180618 also working fine opposite direction. but: samsung laptop intel, mesa-noveau x11/plasma tumbleweed: 20180530 will work if ssh to it self, and desktop tumbleweed 20180618 ssh to laptop tumbleweed 20180530 working but not if laptop tumbleweed 20180530 ssh to desktop tumbleweed 20180618 qt apps empty windows.
note: it does not work, presents empty window outline, if I ssh to another machine and then ssh -XCf back to original machine. but it does not present any error msgs.
so the problem must be either in the tumbleweed updates after 20180530 or in the hardware. should i report this in the factroy mailing list, or do a bugreport, and if, how to do and how to adress it? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
Hi,
works for me here between two tumbleweed machines both up-to-date and both with kde/plasma and x11
cat /etc/os-release
mh, i have here 3 machines: 2 times exact same hardware/software: amd ryzen / mesa amd graphics x11 kde/plasma tumbleweed: 20180618 both did have the problem with starting qt applications (dolphin or yast2) over ssh. from or to each other, or from themself. but working fine if i opensuse11.4 (old hardware) ssh to tumbleweed: 20180618 also working fine opposite direction.
but: samsung laptop intel, mesa-noveau x11/plasma tumbleweed: 20180530 will work if ssh to it self, and desktop tumbleweed 20180618 ssh to laptop tumbleweed 20180530 working but not if laptop tumbleweed 20180530 ssh to desktop tumbleweed 20180618 qt apps empty windows.
note: it does not work, presents empty window outline, if I ssh to another machine and then ssh -XCf back to original machine. but it does not present any error msgs.
so the problem must be either in the tumbleweed updates after 20180530
ACK. Don't have a 0530 available anymore, my tests were done with two 0618 machines. And I just updated the laptop to 0620, still the same issue.
or in the hardware.
I doubt. Laptop is Skylake (HD530 using modesetting), the other machine is a Coffeelake. Both run modesetting, though I'm not sure if the graphics is properly supported.
should i report this in the factroy mailing list, or do a bugreport, and if, how to do and how to adress it?
Definitely a bugreport on bugzilla, as sugested several times here by 'the officials' ;^> And post bugnumber please, so I can follow it.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi,
And post bugnumber please, so I can follow it....
i created my first bugreport: https://bugzilla.opensuse.org/show_bug.cgi?id=1098911 please if something i have not done correct (as i have here described a lot of times) tell me, or change it there. i am not really able to "name" things, i have assigned this to component "kde workspace(plasma)" no idea if this is correct. similar to hardware: "opensuse factroy", because i have not found opensuse tumbleweed in this list. also i did not knwo what priority and severity i have to set. for me its very high problem. maybe for others no problem. tumbleweed 20180530 is not affected, maybe some newer also not i do not know, was the last i own here who was working. after updating to actual its not working any more, so it has nothing with the other hardware to do. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi,
Wolfgang Bauer changed bug 1098911 A fix is in Factory already and should be available with the next snapshot.
*** This bug has been marked as a duplicate of bug 1097227 ***
and this is exactly the reason why i do not like to write bug reports, i searched for this bug there, but i am not able to "NAME" it, so i will also not find if it is already there....... simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Simon Becherer <simon@becherer.de> [06-23-18 10:19]:
Hi,
Wolfgang Bauer changed bug 1098911 A fix is in Factory already and should be available with the next snapshot.
*** This bug has been marked as a duplicate of bug 1097227 ***
and this is exactly the reason why i do not like to write bug reports, i searched for this bug there, but i am not able to "NAME" it, so i will also not find if it is already there.......
better to go ahead and report. someone will correct for you and it is not a "mark" against you. you are not expected to know all. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
Hi,
Wolfgang Bauer changed bug 1098911 A fix is in Factory already and should be available with the next snapshot.
*** This bug has been marked as a duplicate of bug 1097227 ***
and this is exactly the reason why i do not like to write bug reports, i searched for this bug there, but i am not able to "NAME" it, so i will also not find if it is already there.......
Don't worry. It is definitely better to have duplicates than no bugreport. Happens to me, too. It *is* difficult to report about something you don't really know much about. So don't let this be your first-and-last one ;^> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, per,
So don't let this be your first-and-last one ;^>
i do not think its the last one, but i know the answer from my next one, "wont fix" because i got some reply by people who where inside the changelog of the file...... told me that they are not happy with this decision..... .. made a long time in past... simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-23 15:30, Simon Becherer wrote:
Hi,
And post bugnumber please, so I can follow it....
i created my first bugreport:
https://bugzilla.opensuse.org/show_bug.cgi?id=1098911
please if something i have not done correct (as i have here described a lot of times) tell me, or change it there.
The best starting point is: <https://en.opensuse.org/openSUSE:Submitting_bug_reports> There is a link on the page for submitting reports for Tumbleweed, that goes to: <http://bugzilla.opensuse.org/enter_bug.cgi?product=openSUSE+Tumbleweed&format=guided> It may ask for your login/pass at this point. Then you get to a "guided form" for filling your report. If you get into bugzilla page directly, and click on new report, you may get a list such as this:
All: Show all products (overrides filter)
Internal Novell Products: Internal Novell Products that do not belong to a classification. Mono: Mono Novell Products: Novell Products that do not belong to a classification. openSUSE: openSUSE SUSE Appliance Toolkit: SUSE Appliance Toolkit SUSE CaaS Platform: SUSE CaaS Platform SUSE Customer Center: SCC SUSE Enterprise Storage: SUSE Enterprise Storage SUSE Linux Enterprise Desktop: SUSE Linux Enterprise Desktop SUSE Linux Enterprise High Availability Extension: SUSE Linux Enterprise High Availability Extension SUSE Linux Enterprise Server: SUSE Linux Enterprise Server SUSE Tools: SUSE Tools
Well, the one we need is openSUSE. I got that long list because I was at <https://bugzilla.suse.com>. If instead I start at <https://bugzilla.opensuse.org/> the list is much shorter:
First, you must pick a product on which to enter a bug:
openSUSE: openSUSE openSUSE Backports: openSUSE:Backports project in build.opensuse.org openSUSE Distribution: openSUSE Leap & Stable releases openSUSE Tumbleweed: openSUSE Rolling Release openSUSE.org: The openSUSE project (not the distribution)
The one you needed was "openSUSE Tumbleweed". Ie, "Product openSUSE Tumbleweed" in the bugzilla parlance. So we get to: <https://bugzilla.opensuse.org/enter_bug.cgi?product=openSUSE%20Tumbleweed> By this time, "Product" is already filled, and "reporter" displays your email. The next item is "Component". You were reporting a problem with YaST, so choose YaST. At the bottom. Not all issues have a clearly known component, so in those case choose "other". The rest of the fields (Severity, hardware, OS) don't touch. Ok, you may fill hardware as x86-64 and os as openSUSE factory, but this is redundant information. I never touch Severity. Well, an exception could be "Enhancement" when you are asking for a feature, now that openfate is dead. Assigne. In some cases after asking on the list they tell you to assign to somebody, so change that field. Or add a name after reporting. By default I never change it, in case I do a mistake, I leave the default value. Then go to "Summary", and forget the rest. It is the next "required" field, marked with a red asterisk. This is the tittle of the report. It may simultaneously search for other reports with similar tittle to yours. Finally, fill the description. If you have logs, add them as "attachments". Initially it takes only one, but once submitted, you can add more. :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Thanks carlos, simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Andrei Borzenkov -
Bruce Ferrell -
Carlos E. R. -
David C. Rankin -
Istvan Gabor -
jdd＠dodin.org -
Patrick Shanahan -
Peter Suetterlin -
Simon Becherer