August 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 596559] New: Misc fonts not available in fontconfig
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=596559 http://bugzilla.novell.com/show_bug.cgi?id=596559#c0 Summary: Misc fonts not available in fontconfig Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: pgajdos(a)novell.com ReportedBy: mmarek(a)novell.com QAContact: qa(a)suse.de CC: jw(a)novell.com Found By: --- Blocker: --- I can select -misc-fixed-* in xfontsel, but not in applications using fontconfig (such as gvim): $ rm -rf ~/.fontconfig $ fc-cache -vf | grep misc /usr/share/fonts/misc: caching, new cache contents: 136 fonts, 0 dirs /usr/share/fonts/misc: skipping, looped directory detected $ fc-list | grep -i misc $ When I copy the libfontconfig.so.1.3.0 and libfreetype.so.6.3.20 files from 11.2, it looks like this: $ export LD_LIBRARY_PATH=$PWD/usr/lib64 $ fc-cache -vf | grep -i misc /usr/share/fonts/misc: caching, new cache contents: 136 fonts, 0 dirs /usr/share/fonts/misc: skipping, looped directory detected $ fc-list | grep -i misc Misc Fixed:style=Oblique Misc Fixed:style=Bold SemiCondensed Misc Fixed:style=Oblique SemiCondensed Misc Fixed:style=Regular Misc Console:style=Regular Misc Fixed Wide:style=ko Misc Fixed Wide:style=ja Misc Fixed:style=Bold Misc Fixed:style=SemiCondensed $ and gvim uses the correct font. Note that it is not sufficient to only downgrade one of libfontconfig or libfreetype. -- 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 9

[Bug 596526] New: Poor message dialogs and translations in YaST printer setup
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=596526 http://bugzilla.novell.com/show_bug.cgi?id=596526#c0 Summary: Poor message dialogs and translations in YaST printer setup Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: psychonaut(a)nothingisreal.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/2.0.4-3.2 SeaMonkey/2.0.4 When creating or modifying a printer setup in YaST, when finishing the following dialog boxes are displayed, respectively: Created New Printer Setup It takes half a minute until the config files are updated... Modified Printer Setup It takes half a minute until the config files are updated... There are three issues here: 1) If the system is still performing activity and making the user wait, then it's wrong to word the message with the past tense, as if the activity has already been finished. The messages should instead read "Creating New Printer Setup" and "Modifying Printer Setup". 2) "It takes half a minute"? That's rather precise. How does the system know that it's going to take exactly half a minute? Doesn't the processing time depend on the speed of the user's computer, including CPU frequency, disk speed, and system load? Please replace this message with a progress bar, or with a more vague "Updating configuration files..." 3) Even if it is known that the configuration files take exactly thirty minutes to update, the message is grammatically incorrect. It should instead be "It takes half a minute to update the configuration files" or "It will be half a minute until the configuration files are updated". You can't use the present form of "take" with "until". Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 5

[Bug 596519] New: Switch pkg manager to summary mode after resolving pkg conflicts
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=596519 http://bugzilla.novell.com/show_bug.cgi?id=596519#c0 Summary: Switch pkg manager to summary mode after resolving pkg conflicts Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: lslezak(a)novell.com ReportedBy: kmachalkova(a)novell.com QAContact: jsrain(a)novell.com CC: llunak(a)novell.com Found By: Development Blocker: --- Created an attachment (id=354296) --> (http://bugzilla.novell.com/attachment.cgi?id=354296) A patch - switches pkg manager to summary mode after resolving pkg conflicts * Installing some (conflicting) pkgs via 'yast -i' * A conflict dialog pops up * User resolves the conflict Now the user sees a default pkg manager search screen with empty list. She has to switch to 'Installation summary' view to see pkgs that are going to be installed/removed as a result of resolved conflict It is more user-friendly to switch to summary view automatically so as to show the user the changes made - in pretty much the same way as in bug #399795, where the user is presented summary screen to confirm pkg removal. The search view with empty list makes an impression that nothing has happened/changed. Please find a patch resolving the issue attached. -- 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 2

[Bug 596177] New: generate java cacerts at runtime
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=596177 http://bugzilla.novell.com/show_bug.cgi?id=596177#c0 Summary: generate java cacerts at runtime Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de CC: mvyskocil(a)novell.com Found By: --- Blocker: --- It's now possible to generate bundle files for CA certificates at run time. See man update-ca-certificates. Java currently generates it's file at build time, therefore it's not easy for administrators to add custom certificates. A script that calls keytool on each pem file is way too slow so some java code could could be used to speed this up. -- 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 21

[Bug 596163] New: System does not use the hostname from dhcp server
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=596163 http://bugzilla.novell.com/show_bug.cgi?id=596163#c0 Summary: System does not use the hostname from dhcp server Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i386 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mmaher(a)novell.com QAContact: qa(a)suse.de Found By: Component Test Blocker: --- In openSUSE 11.3 Milestone 5 the Machine gets some random hostname. In Milestone 4 the same machine, after the installation got the hostname from the dhcp server. -- 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 11

[Bug 595796] New: "killproc" violates LSB
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595796 http://bugzilla.novell.com/show_bug.cgi?id=595796#c0 Summary: "killproc" violates LSB Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: SLES 11 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: werner(a)novell.com ReportedBy: werner(a)novell.com QAContact: qa(a)suse.de CC: lmb(a)novell.com, ro(a)novell.com, kukuk(a)novell.com Depends on: 578246 Found By: Development Blocker: --- +++ This bug was initially created as a clone of Bug #578246 +++ I've just spent some time hunting down why the cluster daemon was dieing during shutdown, and couldn't find anything in the logs. (Because I somehow didn't expect that a SIGKILL would be send magically out of nowhere.) Then, I stumbled across a suse-specific killproc oddity: killproc sends signals to all processes that use the specified exe‐ cutable. If no signal name is specified, the signal SIGTERM is sent. If this program is not called with the name killproc then SIGHUP is used. Note that if SIGTERM is used and does not terminate a process the signal SIGKILL is send after a few seconds (default is 5 seconds, see option -t). If a program has been terminated successfully and a veri‐ fied pid file was found, this pid file will be removed if the termi‐ nated process didn't already do so. .. -t<sec> The number <sec> specifies the seconds to wait between the sent signal SIGTERM and the subsequentially signal SIGKILL if the first SIGTERM does not show any result within the first few milli seconds. This defaults to 5 seconds. So, if -TERM is specified, this automatically escalates to KILL (this escalation cannot be disabled). However, LSB states (http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-gener…) killproc [-p pidfile] pathname [signal] The killproc function shall stop the specified program. The program is found using the algorithm given above. If a signal is specified, using the -signal_name or -signal_number syntaxes as specified by the kill command, the program is sent that signal. Otherwise, a SIGTERM followed by a SIGKILL after an unspecified number of seconds shall be sent. [...] Note that this says that this automatic escalation only happens if no signal is specified, not if the specified signal happens to be the default SIGTERM. ("killproc" on RHEL/Fedora behaves like this.) I think killproc must differentiate between "No signal specified" versus "SIGTERM explicitly specified". The impact here is real, since it could (and did!) break 3rd party init scripts in unexpected ways. -- 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 595708] New: resolv.conf is modified after livecd installation
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595708 http://bugzilla.novell.com/show_bug.cgi?id=595708#c0 Summary: resolv.conf is modified after livecd installation Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium AssignedTo: coolo(a)novell.com ReportedBy: robin.knapp(a)ts.fujitsu.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 Found this after installation in /var/log/messages and on boot console: Apr 12 12:20:46 linux dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Apr 12 12:20:46 linux dns-resolver: You can find my version in /etc/resolv.conf.netconfig /etc/resolv.conf contains: # Generated by NetworkManager domain localdomain search localdomain nameserver 192.168.126.2 the nameserver is my vmware gw Reproducible: Always Steps to Reproduce: 1. perform live cd installation 2. check boot console and /var/log/messages for above message -- 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 8

[Bug 595702] New: glib2's %post script gives an error
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595702 http://bugzilla.novell.com/show_bug.cgi?id=595702#c0 Summary: glib2's %post script gives an error Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: davejplater(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- when build service build is installing glib2-2.24.0-1.1 there's an error output :- /usr/bin/gio-querymodules-64: error while loading shared libraries: libglib-2.0.so.0: cannot open shared object file: No such file or directory warning: %post(glib2-2.24.0-1.1.x86_64) scriptlet failed, exit status 127 Maybe this will help fix something before it's broken. Same error on i586 build. I've picked up this error in the build log from multimedia:apps solfege. -- 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 595612] New: Configure printer yast dialog should use background threads
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595612 http://bugzilla.novell.com/show_bug.cgi?id=595612#c0 Summary: Configure printer yast dialog should use background threads Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: benderamp(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.2 (like Gecko) SUSE Printer dialog should use background thread for long-running networking operations and should be fail-safe and user-friendly on the rainy-day scenarios - not only when everything is fine (all remote servers are running and accessible). Reproducible: Always Steps to Reproduce: 1. Configure the system to make all printing to remote cups server 2. Switch off computer running this cups server (or disconnect it from network or change ip address or stop cups server running on it) 3. Open yast printer configuration dialog Actual Results: I can see the busy cursor for 1 or 2 minutes, then receive dialog "cups server not accessible" with ok button - click ok and get access to the config dialog, but once I click somewhere on it I again receive busy cursor for 1/2 mins and can do nothing with this. Expected Results: I must be able to interact with the config dialog while it is trying to connect to remote cups server, see the connection progress info and be able to cancel it before it finish. -- 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 11

[Bug 595570] New: mkinitrd: nouveau kernel module not added to initrd
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595570 http://bugzilla.novell.com/show_bug.cgi?id=595570#c0 Summary: mkinitrd: nouveau kernel module not added to initrd Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: eich(a)novell.com ReportedBy: sndirsch(a)novell.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com CC: mhopf(a)novell.com, sndirsch(a)novell.com Found By: --- Blocker: --- mkinitrd doesn't add KMS modules to initrd; probably related to alias in modinfo of nouveau kernel module: alias: pci:v000012D2d*sv*sd*bc03sc*i* alias: pci:v000010DEd*sv*sd*bc03sc*i* -- 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 13