January 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 859218] New: kwrite, using as root , unreadable document due to black background
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=859218 https://bugzilla.novell.com/show_bug.cgi?id=859218#c0 Summary: kwrite, using as root , unreadable document due to black background Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: epistemepromeneur(a)free.fr QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 i launch the dolphin super user mode then i open a text file with kwrite then document is unreadable the background is black then i go to settings to change to white then i can read the document but if i close then open kwrite then again the background is black this occured after an update but what one ? 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 0

[Bug 843598] New: bind/named totally broken
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=843598 https://bugzilla.novell.com/show_bug.cgi?id=843598#c0 Summary: bind/named totally broken Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: max(a)suse.com ReportedBy: werner(a)suse.com QAContact: qa-bugs(a)suse.de CC: meissner(a)suse.com Found By: Development Blocker: --- speedy:named.d # SYSTEMD_NO_WRAP=yes /etc/init.d/named start Starting name server BIND Error: Can not find /lib/YaST/SuSEconfig.functions! This should not happen. Exiting. That is that no /var/lib/named/etc/named.conf.include will be written This was latest bind from https://build.opensuse.org/package/show/network/bind -- 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 1

[Bug 732309] New: KResource Migration delays Konversations startup by ~30 seconds
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=732309 https://bugzilla.novell.com/show_bug.cgi?id=732309#c0 Summary: KResource Migration delays Konversations startup by ~30 seconds Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: ddiss(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- KResource Migration Tool is triggered every time I start Konversation. This blocks usage of Konversation for ~30 seconds. The KResource Migration Tool pop-up window shows: Trying to migrate 'Default Address Book'... Creating instance of type akondi_vcard_resource -- 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 2

[Bug 856476] New: font cache should never be regen'd in foreground while user is waiting
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856476 https://bugzilla.novell.com/show_bug.cgi?id=856476#c0 Summary: font cache should never be regen'd in foreground while user is waiting Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 This has gone from bad to worse. One hopes things will get better, but this is one thing that has not. To generate 1 font-cache takes over 4 minutes: # time gvim -c q 279.20sec 0.06usr 0.02sys (0.02% cpu) --- Worse -- it does it "by surprise" the next time an admin tries to edit a file. It forces them to wait, at almost 5 minutes to over 10 minutes if they have not gone through and uninstalled the entire 32-bit font tool chain (which I did because I don't use or need it). There are multiple issues here. 1) why are there 2 arch-dependent caches for *arch-independent* data (another but is already filed on this but has been ignored. 2) the Fonts are regenerated at the worst time in the worst way -- while the user is waiting and they are blocking the user's next task. I'm not sure why the fonts are regenerating now...oh , I know why I ran a dup-check on the font dir and was meaning to run a redundant name check (but the dup-check which found 2 new duplicate files caused this, I'm sure). I made a special inquiry into what fontconfig needed for it to rerun its cache update -- so I could run it manually ***in background*** while I did other things. It took about 5 minutes (didn't time it).. . But later I had to make a 2 line change to a config file as root -- and got hit with the 5 minute regen again. It's not like you have a choice to put it in background or put it off. It forces the reconfig on you -- stopping all work for the next 5-10 minutes. This reconfig is unacceptably long. What makes it worse (besides it's bad timing), is that if you have the default installs, you spend 10 minutes/font x ~100+ font updates = 1000 minutes or almost 17 hours just to install the fonts in an update. I can't be low key about this -- it is one of the most broken systems I've ever seen in font management. Those same font updates could all be done in 1 batch with out regenerating the cache between each one. When the install is complete, a batch job could be started to regenerate the font cache -- It's likely the user wouldn't even notice the slowdown. The caveat to the user is they can't use newly installed fonts until the reconfig (which will take 5-10+ minutes for the 100 fonts (same time it takes for 1 font). But they could still edit with the old fonts. The major take-away in this bug -- the users should never get a "*surprise*!" 10 minute wait when trying to update a text file. That is an unacceptable system response time to bring up a text editor. (that the font generation takes so long (even for 1 arch (32v.64) is another another problem but likely needs it's own bug. Reproducible: Always Steps to Reproduce: 1.write a cron job to touch /usr/share/fonts/TTF. 2. Notice how root gets completely locked out of the editor -- FOREVER. 3. This is a great way to create a denial of service that locks root out from invoking an editor. Actual Results: Root is locked out of editing. Denial of service. Expected Results: No delay in root bringing up an editor. This is a borderline security issue. -- 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 810456] New: shutdown does not work
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c0 Summary: shutdown does not work Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my Thinkpad X200s shutdown does not work anymore after updating to 12.3. I've already performed some debugging as explained here http://freedesktop.org/wiki/Software/systemd/Debugging#Diagnosing_Shutdown_… - reboot -f and poweroff -f works w/o issues - shutdown never finishes - usually I still get the "System powered off" (or similar; do not remember the exact wording) message on the console but there it stays - tried to enable the debug shell to check what's going on but couldn't enter the tty9 after shutdown was almost complete. The splash screen didn't go away and I couldn't switch ttys at all At that point I'm pretty much lost what to debug. -- 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 859190] New: network:time/ntp: DDOS
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=859190 https://bugzilla.novell.com/show_bug.cgi?id=859190#c0 Summary: network:time/ntp: DDOS Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: max(a)suse.com ReportedBy: opensuse(a)dstoecker.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The current NTP default setup does not differntiate between internal and external access. The default setup should be modified, so that external access is restricted and admins need to remove restrictions when wanted. Probabably 99% of all NTP installations aren't meant to be worldwide visible, but suse defaults are extremely open. E.G. Ubuntu has # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery -- 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 2

[Bug 812709] New: Opensuse 12.3: libreoffice crashes without comment due to what seams an incompatibility between open-jdk and some polyester-style setting
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=812709 https://bugzilla.novell.com/show_bug.cgi?id=812709#c0 Summary: Opensuse 12.3: libreoffice crashes without comment due to what seams an incompatibility between open-jdk and some polyester-style setting Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: stakanov(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/22.0.1207.1 Safari/537.1 The machine on which the problem manifested was a "do not upgrade, reinstall from the scratch by maintaining the home partition unmodified" type of installation. That is the /home did now migrate from 10.1 onwards. The installation was perfect with 12.2 and was then recently upgraded to 12.3. While trying to use libreoffice Writer the program crashed without comment. Starting from terminal gave: libreoffice Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated. profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/nativeapi/mysql_native_resultset_wrapper.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/nativeapi/mysql_native_statement_wrapper.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/nativeapi/mysql_native_connection_wrapper.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/nativeapi/mysql_native_driver_wrapper.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/nativeapi/mysql_client_api.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_uri.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_warning.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_util.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_statement.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_resultset_metadata.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_resultset.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_resultbind.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_ps_resultset_metadata.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_ps_resultset.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_prepared_statement.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_parameter_metadata.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_metadata.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_driver.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_debug.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_connection.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_art_rset_metadata.cpp.gcda:Skip profiling:/home/abuild:Cannot create directory profiling:/home/abuild/rpmbuild/BUILD/mysql-connector-c++-1.1.1/driver/CMakeFiles/mysqlcppconn.dir/mysql_art_resultset.cpp.gcda:Skip Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated. End of listing---- So I tried to create an empty virgin user and it worked right from the start. The problem should have then been a configuration problem. So I renamed to "oldxxx" .libreoffice .fonts and I did install bit bleach to get rid of all old temp, tmp and whatever not more valid config files. As a result I was now able to open "libreoffice office" with the selection. All but writer would crash immediately without notice even in terminal, but with libreoffice writer that gave in terminal: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xaf05cee3, pid=5819, tid=2982295680 # # JRE version: 7.0_17-b02 # Java VM: OpenJDK Client VM (23.7-b01 mixed mode linux-x86 ) # Problematic frame: # C [libpolyester.so+0x1bee3] PolyesterStyle::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const+0x16f3 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/user/hs_err_pid5819.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla Now, I am not a light bulb for what is reasoning but that seemed to me a conflict between java and a precedent polyester installation. I did check in Jast and found polyester (two packages, base and another one installed, I think lang but I am not sure, can investigate if useful). I did eliminate the two packages and restarted the KDE session. And voilà! it works, libreoffice now works flawlessly. As the "trial and error" took me quite some time, I report it as a "normal" bug, I recall having read that somebody else had some problem with polyester (ahhh that plastic thing!) so it may be useful. Reproducible: Always Steps to Reproduce: 1. Install opensuse 12.2 with polyester (with respect to the settings of polyester consider the terminal output delivered. Nvidia driver - always most recent G02 were used). 2. Install 12.3 from the scratch. Start openoffice. It will crash without notice. 3. start openoffice from the terminal, you will get the output as of above. 4. uninstall polyester style = libreoffice runs well. Actual Results: after upgrade, libreoffice crashes inconditonally without notice, running from terminal eventually hints to polyester and a java crash. Expected Results: Libreoffice should work as expected regardless of the presence of polyester. If you contact me within short notice (sorry for eastern, let us say withing tuesday night) I will be able to give you more detailed info. After this I will travel so I will not have physically my hands on the machine. Sorry. (Another "running sneaker admin" I guess). -- 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 5

[Bug 859195] New: Polyester style: libreoffice crashes without comment when polyesterstyle is installed.
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=859195 https://bugzilla.novell.com/show_bug.cgi?id=859195#c0 Summary: Polyester style: libreoffice crashes without comment when polyesterstyle is installed. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: stakanov(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 When I opened after the kde update openoffice it crashed without comment. As this happens only in one user personality, it will have to do with the other settings of the plasma desktop. Polyesterstyle is mentioned in the crash output in console so it seems to be responsible (co-responsible?). Strangely enough this does not happen in other personalities I have running. I paste the output below. a) with both polyester and polyester for qt4 installed. b) without polyester for qt4 c) both uninstalled. With both installed the program libreoffice literally aborts comment less. After uninstalling qt4 it builds a first window but then aborts. c) when polyester is gone: starts normally (despite of the error given in terminal). Reproducible: Always Steps to Reproduce: 1.start libreoffice 2. libreoffice crashes after the flash popup without being able to build up a window. 3. start from terminal indicates the polyester problem. Actual Results: 1.install polyester and qt4 polyester package, set the user according to the below info (crystal, bespin, k-high delight) and the regular libreoffice version from base repo. KDE 4.11.4 installed from repo. 2. start libreoffice 3. crashes after the flash popup without being able to build up a window. Expected Results: should have opened normally a) libreoffice # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f94c292de70, pid=9951, tid=140277373827648 # # JRE version: OpenJDK Runtime Environment (7.0_45-b31) (build 1.7.0_45-b31) # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libpolyester.so+0x18e70] PolyesterStyle::drawPrimitive(QStyle::PrimitiveElement, QStyleOption const*, QPainter*, QWidget const*) const+0xa50 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/jvm-9951/hs_error.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # [error occurred during error reporting , id 0xb] b) libreoffice # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fa256f45713, pid=10140, tid=140335697795648 # # JRE version: OpenJDK Runtime Environment (7.0_45-b31) (build 1.7.0_45-b31) # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libpolyester.so+0x16713] qt_plugin_instance+0xbd23 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/jvm-10140/hs_error.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # [error occurred during error reporting , id 0xb] c) (both uninstalled - libreoffice starts without problems) libreoffice X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 42 (X_SetInputFocus) Resource id: 0x7e00030 I am using a multimonitor setup when at home with a ultrabase (this is a lenovo X201. It could be possible that this personality was last used with openoffice when on this ultrabase so if windowsettings are still present from this particular setup then this could be a reason? I did however start up now since quite some time the user personality without ultrabase. I know we should not "think" when reporting but be descriptive so take this as a hint for an eventual particular setup. Settings of this user are:crystal style 2.2.1, light glare style (lieve bagliore), application style bespinn, icon-style k-high delight. -- 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 1

[Bug 853225] New: fc-cache run twice for "noarch" data for 32+64 bit; happens running editor & too often
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=853225 https://bugzilla.novell.com/show_bug.cgi?id=853225#c0 Summary: fc-cache run twice for "noarch" data for 32+64 bit; happens running editor & too often Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 When I add a font from "noarch", the install process takes a VERY long time building cache files. Not only does it do this for each font file installed (vs. once at end), but it does it *TWICE* -- fc-cache fc-cache32. It is a "no arch" package. There should be nothing that is 32-or 64 bit dependent in the package. So why is it creating 2 different caches (or maybe they are the same) by 2 different cache programs -- each taking 4-6 minutes/font? IT's also the case that if anything touches a timestamp in /usr/share/fonts, then it regens the caches when starting an editor like gvim. Having a 10 minute delay starting up the editor -- 2 or more times/font is too long. If you start gvim as a normal user -- it runs the font-cache as a normal user and since it can't store it in the system cache dir, it has to be run again when root tries running gvim. Tried running root gvim first, but still generated user wait (~1.5 minutes if root done first?)... Reproducible: Always Steps to Reproduce: 1. 2. If any changes are made in font dir, it also regenerates when you start vim as NON-ROOT user (i.e. results are tossed -- can't be stored). 3. Actual Results: Install a bunch of fonts... # find /usr/share/fonts -iname "*.[OTot][tT][FCfc]" |wc -l 21178 touch /usr/share/fonts/truetype Try to run 'gvim'... OR install a font (rpm)... notice it runs fc-cache and fc-cache32 to process the addition on a 64-bit machine. Why does it run fc-cache32 at all?? It's supposed to be arch independent. Expected Results: long wait >4 minutes 1) returned immediate and schedule cache to be built in background 2) only call fc-cache -- not both. -- 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

[Bug 859161] New: firefox,debug,debug installed in strange place
by bugzilla_noreply＠novell.com 17 Jan '14

17 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c0 Summary: firefox,debug,debug installed in strange place Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: epistemepromeneur(a)free.fr QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 kde report generator expects debug symbols in /usr/lib64/firefox but they are in /usr/lib/debug/usr/lib64/firefox/ then no track crash report can be generated see the extract from yast software manager *************************************************************************** /usr/lib/debug/.build-id/f1/c2a8846c52fd97d69734c27fc2422b2b51b84a.debug /usr/lib/debug/.build-id/fb/c6af02b4cfe7baee385528f07f3e97377c15cc /usr/lib/debug/.build-id/fb/c6af02b4cfe7baee385528f07f3e97377c15cc.debug /usr/lib/debug/usr/lib64/firefox/browser/components/libbrowsercomps.so.debug /usr/lib/debug/usr/lib64/firefox/components/libdbusservice.so.debug /usr/lib/debug/usr/lib64/firefox/components/libmozgnome.so.debug /usr/lib/debug/usr/lib64/firefox/crashreporter.debug /usr/lib/debug/usr/lib64/firefox/firefox.debug /usr/lib/debug/usr/lib64/firefox/libmozalloc.so.debug /usr/lib/debug/usr/lib64/firefox/libmozsqlite3.so.debug /usr/lib/debug/usr/lib64/firefox/libxul.so.debug /usr/lib/debug/usr/lib64/firefox/mozilla-xremote-client.debug *********************************************************************** 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 12