July 2011 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 595550] New: OpenOffice_org-calc-extensions has an interactive script
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595550 http://bugzilla.novell.com/show_bug.cgi?id=595550#c0 Summary: OpenOffice_org-calc-extensions has an interactive script Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: OpenOffice.org AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: dominique.leuenberger(a)tmf-group.com QAContact: cwei(a)novell.com Found By: --- Blocker: --- Installed OpenOffice using zypper, which was hanging 'forever' at Retrieving package OpenOffice_org-calc-extensions-3.2.0.99.2-1.4.x86_64 (41/42), 226.0 KiB (230.0 KiB unpacked) Retrieving: OpenOffice_org-calc-extensions-3.2.0.99.2-1.4.x86_64.rpm [done] Installing: OpenOffice_org-calc-extensions-3.2.0.99.2-1.4 [18%] After killing the 'offending' task using kill, I get this output: Installing: OpenOffice_org-calc-extensions-3.2.0.99.2-1.4 [done] Additional rpm output: Unregistering the older OpenOffice.org Calc extensions... Registering OpenOffice.org Calc extensions... Extension License Agreement: GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 [... entire license textt ...] Read the complete License Agreement displayed above. Accept the License Agreement by typing "yes" on the console then press the Return key. Type "no" to decline and to abort the extension setup. [Enter "yes" or "no"]: Your input was not correct. Please enter "yes" or "no": Your input was not correct. Please enter "yes" or "no": (this continues for many times, as of course nobody ever accepted it: it was not even possible to be accepted.). A license dialog in the --script section is really bad thing. If at all it should be in the package license system. But then: it's LGPL: As the USER of it there is not much I have to 'accept' to it (same discussion as with the distribution license itself: as a user you don't have to accept it to be allowed to *use* the soft) -- 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 19

[Bug 595479] New: obs rosegarden4-10.04-1.2.x86_64 tempo change not effective in notation editor
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595479 http://bugzilla.novell.com/show_bug.cgi?id=595479#c0 Summary: obs rosegarden4-10.04-1.2.x86_64 tempo change not effective in notation editor Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: davejplater(a)gmail.com ReportedBy: m.munnix(a)redcross.be QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- rosegarden4 10.04 svn 11855. when entering tempo changes from notation editor, it is not recorded. In main window it works. Here the message in stdout: load = 1.5009 max usecs: 383.000, spare = 22836.000 load = 1.3211 max usecs: 265.000, spare = 22954.000 Object::connect: No such signal Rosegarden::NotationView::changeTempo(timeT, tempoT, tempoT, TempoDialog::TempoDialogAction) in src/gui/editors/notation/NotationView.cpp:3026 Object::connect: (sender name: 'MinorDialog') -- 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 10

[Bug 595379] New: cannot set rpc.statd startup parameters
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=595379 http://bugzilla.novell.com/show_bug.cgi?id=595379#c0 Summary: cannot set rpc.statd startup parameters Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: honza801(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.9 (KHTML, like Gecko) Chrome/5.0.308.0 Safari/532.9 cannot set parameters for rpc.statd daemon. there are several configuration options is /etc/sysconfig/nfs, but nothing for rpc.statd. actually, i'm running statd with these parameters STATD_PRMS="-p 32765 -o 32766" i'm using nfs-kernel-server-1.1.3-21.3.1.i586 Reproducible: Always Steps to Reproduce: 1. server nfsserver start 2. 3. Actual Results: starts without parameters Expected Results: ability to change some or all of the parameters for rpc.statd -- 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 594981] New: rrdtool always reporting "This RRD was created on another architecture"
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=594981 http://bugzilla.novell.com/show_bug.cgi?id=594981#c0 Summary: rrdtool always reporting "This RRD was created on another architecture" Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kairo(a)kairo.at QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.3a5pre) Gecko/20100408 Lightning/1.1a1pre SeaMonkey/2.1a1pre Not sure if the component is really correct, but I figured rrdtool is most often used with networking stuff. I think it's since about the gcc 4.5 switch that rrdtool on Factory reports "This RRD was created on another architecture" on anything I want to do with any RRD database - even on those the same rrdtool version created itself, and even after doing the export to XML and re-import trick that is recommended when this message pops up due to actual architecture problems. Reproducible: Always Steps to Reproduce: 1. Create an RRD database with rrdtool. 2. Use either rrdtool update to add info or rrdtool graph to get info out of it. Actual Results: "This RRD was created on another architecture" Expected Results: Working updates and graphs. -- 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