September 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 691709] New: synergy makes cursor disapear over GVIM windows
by bugzilla_noreply＠novell.com 12 Dec '16

12 Dec '16

https://bugzilla.novell.com/show_bug.cgi?id=691709 https://bugzilla.novell.com/show_bug.cgi?id=691709#c0 Summary: synergy makes cursor disapear over GVIM windows Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: adam(a)mizerski.pl ReportedBy: jmatejek(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- this happens on the computer where synergy server is running, not sure about client to reproduce: 1. start synergy server 2. open gvim window 3. start typing in gvim window (for non-vi folk, you initiate insert mode by typing "i" or pressing Ins) 4. the mouse cursor disappears 5. stop typing and move your mouse expected behavior: mouse curshor should reappear - this is standard behavior, designed so that the cursor is hidden while typing actual behavior: the mouse cursor never reappears. if you move mouse out of gvim's window, cursor is visible, but it is invisible when positioned over the window sorry if you're not the right assignee, but you are the only active user in the X11:Utilities project and you did the last change to synergy, so... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 714551] New: Vim's ":tag" command should search corresponding header file first.
by bugzilla_noreply＠novell.com 12 Dec '16

12 Dec '16

https://bugzilla.novell.com/show_bug.cgi?id=714551 https://bugzilla.novell.com/show_bug.cgi?id=714551#c0 Summary: Vim's ":tag" command should search corresponding header file first. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nn.dm55(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 In a C++ project with many variables with the same name, searching for the definition of a variable mentioned in a ".cpp" file using Ctrl-] gives me the definition of an unrelated variable with the same name. The ":tag" command should prefer the definition in the corresponding header file to any other definitions to make finding the correct definition easier. Reproducible: Always Steps to Reproduce: 1. Download SuperTuxKart 2. Open src/karts/kart_model.cpp in Vim 3. Type "/::attachModel" and press Enter 4. Type "/else" and press Enter 5. Type "/m_mesh" and press Enter. 6. Hold Ctrl and press ], then release both keys Actual Results: You end up looking at the following line in src/graphics/shadow.hpp instead of src/karts/kart_model.hpp: scene::IMesh *m_mesh; Expected Results: I expected Vim to show me these line from src/karts/kart_model.hpp: scene::IAnimatedMesh *m_mesh; This bug happens even without having a .vimrc file. I am using openSUSE 11.3 64-bit. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 743548] New: opensuse wiki misses a WYSIWYG editor
by bugzilla_noreply＠novell.com 05 Dec '16

05 Dec '16

https://bugzilla.novell.com/show_bug.cgi?id=743548 https://bugzilla.novell.com/show_bug.cgi?id=743548#c0 Summary: opensuse wiki misses a WYSIWYG editor Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Wiki AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jw(a)suse.com QAContact: tschmidt(a)suse.com Blocks: 743547 Found By: --- Blocker: --- The wiki should have a WYSIWYG Editor. tinyMCE can be enabled on MediaWiki. It can also be extended to offer templates. The current editor features only a source code view, and a very limited markup support. Typical editing requires multiple Preview-Edit cycles until the results come out as intended. E.g. I myself often need a few attempts to get link target and link labels in the right order with the right seperator in between. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 779147] New: KDE:Release:49/branding-openSUSE_12.2: Bug
by bugzilla_noreply＠novell.com 23 Oct '16

23 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=779147 https://bugzilla.novell.com/show_bug.cgi?id=779147#c0 Summary: KDE:Release:49/branding-openSUSE_12.2: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: toddrme2178(a)gmail.com ReportedBy: lars.altenhain(a)micram.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The post and postun scripts for plymouth-branding-openSUSE set LIBDIR to %{_libdir} before calling plymouth-set-default-theme which then fails on 64bit systems with "/usr/lib/plymouth/script.so does not exist". The "export LIB=%{_libdir}" should be removed from the post and postun scripts as plymouth-set-default-theme contains the following logic to set PLYMOUTH_PLUGIN_PATH variable which uses "plymouth --get-splash-plugin-path" to get the correct path if "LIB" is not set. [ -z "$PLYMOUTH_LIBEXECDIR" ] && PLYMOUTH_LIBEXECDIR="/usr/lib" [ -z "$PLYMOUTH_DATADIR" ] && PLYMOUTH_DATADIR="/usr/share" [ -z "$PLYMOUTH_CONFDIR" ] && PLYMOUTH_CONFDIR="/etc/plymouth/" [ -z "$PLYMOUTH_POLICYDIR" ] && PLYMOUTH_POLICYDIR="/usr/share/plymouth/" if [ -z "$PLYMOUTH_PLUGIN_PATH" ]; then if [ -z "$LIB" ]; then PLYMOUTH_PLUGIN_PATH="$(plymouth --get-splash-plugin-path)" else [ -z "$PLYMOUTH_LIBDIR" ] && PLYMOUTH_LIBDIR="/usr/lib" PLYMOUTH_PLUGIN_PATH=${PLYMOUTH_LIBDIR}/plymouth/ fi fi -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 680148] New: kiwi complains about no clicfs tools if there is no cdrkit compat
by bugzilla_noreply＠novell.com 23 Oct '16

23 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=680148 https://bugzilla.novell.com/show_bug.cgi?id=680148#c0 Summary: kiwi complains about no clicfs tools if there is no cdrkit compat Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: ms(a)novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- I wanted to create a small ISO with clicfs and kiwi complained that there are no tools for clicfs. After digging the code I figured it actually looked for mkisofs first and set the toolerror flag because it's not there. Afaik it's not even using mkisofs but genisoimage -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 688776] New: outdated midnight commander man page
by bugzilla_noreply＠novell.com 14 Oct '16

14 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=688776 https://bugzilla.novell.com/show_bug.cgi?id=688776#c0 Summary: outdated midnight commander man page Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pcerny(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- The manpage of midnight commander seems to be outdated, at least wrt the description of the skins (as compared with the default skin file shipped in the package) - it doesn't contain all recognized keywords (and some might even be not supported any more). Creating a reasonbale skinn is hence impossible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 564306] New: mc can not copy big files via shell to another local networked computer.
by bugzilla_noreply＠novell.com 14 Oct '16

14 Oct '16

http://bugzilla.novell.com/show_bug.cgi?id=564306 http://bugzilla.novell.com/show_bug.cgi?id=564306#c0 Summary: mc can not copy big files via shell to another local networked computer. Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- I try to copy a large .iso file from one computer to another using mc, with its shell link over ssh capability. Of the 4169M file, just 74806Kb are copied to the remote filesystem, while the rest is copied to the localfilesystem instead, to directory ???? To somewhere in the root filesystem I have been unable to locate (yet?). Ah, somehow it has been automatically erased, by mc on exit, I hope. I know it was copied to / somewhere because I saw the available free space decreasing. I did the test twice. However, the command: scp Copia.iso root@nimrodel://Grande/copia/Copia.iso succeeds. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 623388] New: mc midnightcommander wrong $PS1 parser in command line input
by bugzilla_noreply＠novell.com 14 Oct '16

14 Oct '16

http://bugzilla.novell.com/show_bug.cgi?id=623388 http://bugzilla.novell.com/show_bug.cgi?id=623388#c0 Summary: mc midnightcommander wrong $PS1 parser in command line input Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: PC OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: verdelyi(a)windowslive.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 https://bugs.launchpad.net/ubuntu/+source/mc/+bug/330633 http://www.midnight-commander.org/ticket/337 Probably we just need to backport a patch: http://www.midnight-commander.org/changeset/9041e6c81f4b2ae15e7bc3f733016ec… Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 775028] New: KDE 4.9 programs hang in libc's poll() function
by bugzilla_noreply＠novell.com 13 Oct '16

13 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=775028 https://bugzilla.novell.com/show_bug.cgi?id=775028#c0 Summary: KDE 4.9 programs hang in libc's poll() function Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: szotsaki(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; hu) Presto/2.10.289 Version/12.01 I wanted to file at least five different bug reports to the KDE team when I realized that all of the programs faults have one thing in common: libc's poll() function. The symptoms: 1.) Konsole hangs when I try to select some text. Backtrace: #0 0x00007f834def1ff3 in poll () from /lib64/libc.so.6 #1 0x00007f83494b84c0 in socket_do_iteration (transport=0x814410, flags=6, timeout_milliseconds=<optimized out>) at dbus-transport-socket.c:1125 #2 0x00007f83494b739d in _dbus_transport_do_iteration (transport=0x814410, flags=<optimized out>, timeout_milliseconds=<optimized out>) at dbus-transport.c:978 #3 0x00007f83494a2505 in _dbus_connection_do_iteration_unlocked (connection=0x7d1b70, pending=<optimized out>, flags=6, timeout_milliseconds=25000) at dbus-connection.c:1232 #4 0x00007f83494a3889 in _dbus_connection_block_pending_call (pending=0xa270b0) at dbus-connection.c:2405 #5 0x00007f83494a2dec in dbus_connection_send_with_reply_and_block (connection=0x7d1b70, message=0x8149a0, timeout_milliseconds=-1, error=0x7fffd5b72330) at dbus-connection.c:3514 #6 0x00007f834c252f05 in q_dbus_connection_send_with_reply_and_block (error=0x7fffd5b72330, timeout_milliseconds=-1, message=0x8149a0, connection=<optimized out>) at qdbus_symbols_p.h:135 #7 QDBusConnectionPrivate::sendWithReply (this=0x7d1810, message=..., sendMode=<optimized out>, timeout=-1) at qdbusintegrator.cpp:1904 #8 0x00007f834c253819 in QDBusConnectionPrivate::findMetaObject (this=0x7d1810, service=..., path=..., interface=..., error=...) at qdbusintegrator.cpp:2356 #9 0x00007f834c26249b in QDBusInterfacePrivate::QDBusInterfacePrivate (this=0x9fa960, serv=..., p=..., iface=..., con=...) at qdbusinterface.cpp:158 #10 0x00007f834c2625d9 in QDBusInterface::QDBusInterface (this=0x7fffd5b727d0, service=..., path=..., interface=..., connection=..., parent=0x0) at qdbusinterface.cpp:220 #11 0x00007f834f9faf8b in KMimeType::favIconForUrl (url=...) at /usr/src/debug/kdelibs-4.9.0/kdecore/services/kmimetype.cpp:494 #12 0x00007f83486c7162 in lookupIconNameFor (url=..., type=<optimized out>) at /usr/src/debug/kdelibs-4.9.0/kio/kio/kurifilter.cpp:47 #13 0x00007f83486c7f6e in KUriFilterPlugin::iconNameFor (this=<optimized out>, url=..., type=<optimized out>) at /usr/src/debug/kdelibs-4.9.0/kio/kio/kurifilter.cpp:569 #14 0x00007f83343bb2f6 in KAutoWebSearch::populateProvidersList (this=0xae0640, searchProviders=..., data=..., allproviders=<optimized out>) at /usr/src/debug/kde-runtime-4.9.0/kurifilter-plugins/ikws/kuriikwsfilter.cpp:104 … 2.) nepomukcontroller does not shut down normally. Backtrace: #0 0x00007ff259abbff3 in poll () from /lib64/libc.so.6 #1 0x00007ff25719eca6 in g_main_context_iterate.isra.23 () from /usr/lib64/libglib-2.0.so.0 #2 0x00007ff25719edd4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 3.) KMail has 100% CPU load when I try to select a folder. Backtrace: #0 0x00007f0c436d8ff3 in poll () from /lib64/libc.so.6 #1 0x00007f0c3b5f1ca6 in g_main_context_iterate.isra.23 () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f0c3b5f1dd4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f0c44d40dcf in QEventDispatcherGlib::processEvents (this=0x60b000, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007f0c4413869e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #5 0x00007f0c44d10842 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007f0c44d10a97 in QEventLoop::exec (this=0x7fff18592d80, flags=...) at kernel/qeventloop.cpp:204 #7 0x00007f0c44d158b5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #8 0x0000000000402df3 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kdepim-4.9.0/kmail/main.cpp:145 #3 0x00007ff25a233dcf in QEventDispatcherGlib::processEvents (this=0x6170b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007ff25af4069e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #5 0x00007ff25a203842 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007ff25a203a97 in QEventLoop::exec (this=0x7fffee708440, flags=...) at kernel/qeventloop.cpp:204 #7 0x00007ff25a2088b5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #8 0x00000000004073a6 in main (argc=3, argv=0x7fffee708748) at /usr/src/debug/kde-runtime-4.9.0/nepomuk/controller/main.cpp:51 4.) Dolphin starts in 15 seconds. Backtrace: #0 0x00007f834def1ff3 in poll () from /lib64/libc.so.6 #1 0x00007f83494b84c0 in socket_do_iteration (transport=0x8a0120, flags=6, timeout_milliseconds=<optimized out>) at dbus-transport-socket.c:1125 #2 0x00007f83494b739d in _dbus_transport_do_iteration (transport=0x8a0120, flags=<optimized out>, timeout_milliseconds=<optimized out>) at dbus-transport.c:978 #3 0x00007f83494a2505 in _dbus_connection_do_iteration_unlocked (connection=0x843970, pending=<optimized out>, flags=6, timeout_milliseconds=25000) at dbus-connection.c:1232 #4 0x00007f83494a3889 in _dbus_connection_block_pending_call (pending=0xb92ff0) at dbus-connection.c:2405 #5 0x00007f83494a2dec in dbus_connection_send_with_reply_and_block (connection=0x843970, message=0x8b0260, timeout_milliseconds=-1, error=0x7fffd5b73ae0) at dbus-connection.c:3514 #6 0x00007f834c252f05 in q_dbus_connection_send_with_reply_and_block (error=0x7fffd5b73ae0, timeout_milliseconds=-1, message=0x8b0260, connection=<optimized out>) at qdbus_symbols_p.h:135 #7 QDBusConnectionPrivate::sendWithReply (this=0x7ea570, message=..., sendMode=<optimized out>, timeout=-1) at qdbusintegrator.cpp:1904 #8 0x00007f834c253819 in QDBusConnectionPrivate::findMetaObject (this=0x7ea570, service=..., path=..., interface=..., error=...) at qdbusintegrator.cpp:2356 #9 0x00007f834c26249b in QDBusInterfacePrivate::QDBusInterfacePrivate (this=0xa47df0, serv=..., p=..., iface=..., con=...) at qdbusinterface.cpp:158 #10 0x00007f834c2625d9 in QDBusInterface::QDBusInterface (this=0xb4f6b0, service=..., path=..., interface=..., connection=..., parent=0x0) at qdbusinterface.cpp:220 #11 0x00007f834f98dbbb in KSystemTimeZonesPrivate::instance () at /usr/src/debug/kdelibs-4.9.0/kdecore/date/ksystemtimezone.cpp:304 #12 0x00007f834f98e2b9 in KSystemTimeZones::local () at /usr/src/debug/kdelibs-4.9.0/kdecore/date/ksystemtimezone.cpp:201 #13 0x00007f834f978780 in KDateTime::toLocalZone (this=0xb90188) at /usr/src/debug/kdelibs-4.9.0/kdecore/date/kdatetime.cpp:931 #14 0x00007f834868a853 in KFileItemPrivate::setTime (this=<optimized out>, mappedWhich=<optimized out>, time_t_val=<optimized out>) at /usr/src/debug/kdelibs-4.9.0/kio/kio/kfileitem.cpp:316 #15 0x00007f834868a984 in init (this=0xb90110) at /usr/src/debug/kdelibs-4.9.0/kio/kio/kfileitem.cpp:242 #16 KFileItemPrivate::init (this=0xb90110) at /usr/src/debug/kdelibs-4.9.0/kio/kio/kfileitem.cpp:209 … 5.) Akonadi Nepomuk Feeder uses 100% CPU. Backtrace (it's a bit different): #0 0x00007fdd7705b803 in select () from /lib64/libc.so.6 #1 0x00007fdd71f34681 in waitForReadyRead (timeout=30000, this=0x75a210) at /usr/src/debug/soprano-2.8.0/client/socket.cpp:86 #2 Soprano::Socket::waitForReadyRead (this=0x75a210, timeout=30000) at /usr/src/debug/soprano-2.8.0/client/socket.cpp:75 #3 0x00007fdd71f3750a in Soprano::SocketStream::read (this=0x7fff052cfc90, data=0x7fff052cfccc "", size=4) at /usr/src/debug/soprano-2.8.0/client/socketstream.cpp:254 #4 0x00007fdd71f37d96 in Soprano::SocketStream::readUnsignedInt32 (this=0x7fff052cfc90, i=@0x7fff052cfccc: 0) at /usr/src/debug/soprano-2.8.0/client/socketstream.cpp:340 #5 0x00007fdd71f3a52f in Soprano::Client::ClientConnection::executeQuery (this=0x8148f0, modelId=657650309, query=..., type=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at /usr/src/debug/soprano-2.8.0/client/clientconnection.cpp:244 #6 0x00007fdd71f3cc63 in Soprano::Client::ClientModel::executeQuery (this=<optimized out>, query=..., language=<optimized out>, userQueryLanguage=...) at /usr/src/debug/soprano-2.8.0/client/clientmodel.cpp:101 #7 0x00007fdd77aa1c41 in Nepomuk::MainModel::executeQuery (this=0x7fde90, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at /usr/src/debug/kdelibs-4.9.0/nepomuk/core/nepomukmainmodel.cpp:187 #8 0x0000000000412390 in FeederQueue::processNextCollection (this=0x7e3da0) at /usr/src/debug/kdepim-runtime-4.9.0/agents/nepomukfeeder/feederqueue.cpp:149 #9 0x0000000000412dc8 in FeederQueue::collectionFullyIndexed (this=0x7e3da0) at /usr/src/debug/kdepim-runtime-4.9.0/agents/nepomukfeeder/feederqueue.cpp:240 #10 0x0000000000413425 in FeederQueue::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kdepim-runtime-4.9.0/build/agents/nepomukfeeder/feederqueue.moc:169 … I use the http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.1/ repository for KDE 4.9. GLibc version number: 2.14.1-14.27.1, x86_64 (from openSUSE 12.1 Upgrade repo). Kernel: linux-suse 3.1.10-1.16-desktop Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 780621] New: YaST Installer continues to ignore low-vision accessibility
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=780621 https://bugzilla.novell.com/show_bug.cgi?id=780621#c0 Summary: YaST Installer continues to ignore low-vision accessibility Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suseROCKS(a)bryen.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 YaST uses a bright white background for the dialogue windows during installation. This is a big no-no for low-vision users as well as for people with aging eyes. Typically, many low-vision users are extremely sensitive to white on screen. We tend to set our desktops to have a black background with white font. As my vision continues to deteriorate, I am having more difficulty with each openSUSE release to be able to see the screen and select my options. While I know there is a text-based install, even the default for YaST-ncurses is not a low-vision friendly color and requires you to edit a file to change the default color options. (I've never tried this during actual install, only during normal installed usage of openSUSE.) That is simply not an optimal solution for low-vision users, especially new users who may not have experience in how to configure in the background. Please devise a plan to provide alternative visual options for users. Perhaps a toggle-button that automatically inverts the colors of the install dialogues or alternative graphics screen that provides a darker background. This is not a protest statement, but a factual one... with my continued declining vision, if this is not fixed by 12.3, it is quite possible that I will no longer be able to install and use openSUSE. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11