November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 637481] New: ichain proxy: connections get stuck
by bugzilla_noreply＠novell.com 04 Feb '14

04 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=637481 https://bugzilla.novell.com/show_bug.cgi?id=637481#c0 Summary: ichain proxy: connections get stuck Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Infrastructure AssignedTo: mrueckert(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: lrupp(a)novell.com Found By: Beta-Customer Blocker: --- I have my own BS instance at ares.medozas.de[134.76.83.5], running schedulers for four architectures, and ~8000 package links (osc linkpac'd) to the openSUSE: namespace. When the schedulers start up, they do a /getprojpack on the local bs_srcserver, which in turn contacts api.opensuse.org due to <remoteurl>ing. This creates four connections, handled by srcserver child processes that are visible with `rcobssrcserver status`. It may take 20–25 minutes for one scheduler to do a cold start. The problem now is that the iChain proxy or any other security hardware that secretly sits between the Novell perimeter and api.opensuse.org causes _all but one_ of the connections to get stuck after 5–10 minutes. Running strace -p on one or more of the PIDs as returned by `rcobssrcserver status` sits "read(4, ", which is the socket to 195.135.221.33:443. Only one bssrc subprocess does continue scanning the projects and have constantly flowing open/read output I am aware that there is a "silent period", but it would be _at the end_ of project scanning, which I can be certain is not reached yet once it gets stuck. Since these connections are open for more than 15 minutes in general, it may not seem far fetched that it looks like a Slowloris proceeding to the proxy (but you can't really blame me for that, can you?). If this were however the case, the proxy should close the connection (scheduler will automatically retry later), not sit on it and do nothing. -- 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 714732] New: rpcbind runs as root
by bugzilla_noreply＠novell.com 04 Feb '14

04 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=714732 https://bugzilla.novell.com/show_bug.cgi?id=714732#c0 Summary: rpcbind runs as root Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: okir(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: qa(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- rpcbind runs as root. Please use a dedicated user instead. The configure script already has a switch '--with-rpcuser' for the job. FWIW RH uses 'rpc' as username. http://en.opensuse.org/openSUSE:Security_packaging_policy -- 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 720086] New: can't run gnome-terminal from within KDE?
by bugzilla_noreply＠novell.com 03 Feb '14

03 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=720086 https://bugzilla.novell.com/show_bug.cgi?id=720086#c0 Summary: can't run gnome-terminal from within KDE? Classification: openSUSE Product: openSUSE 11.4 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: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 This is what I get if I try to run gnome-terminal from within KDE (I'm not sure if that has anything to do with it or not): jnelson@worklaptop:~/Documents> gnome-terminal ** ERROR:terminal-app.c:1460:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Aborted jnelson@worklaptop:~/Documents> Missing dependency? 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 13

[Bug 521551] New: Unable to start MozillaFirefox
by bugzilla_noreply＠novell.com 03 Feb '14

03 Feb '14

http://bugzilla.novell.com/show_bug.cgi?id=521551 Summary: Unable to start MozillaFirefox Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: wolfgang(a)rosenauer.org ReportedBy: lrupp(a)novell.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Development MozillaFirefox-3.5.0-7.1 MozillaFirefox-translations-3.5.0-7.1 MozillaFirefox-branding-openSUSE-3.5-10.3 mozilla-xulrunner191-1.9.1.0-9.1 mozilla-xulrunner191-translations-1.9.1.0-9.1 mozilla-xulrunner190-1.9.0.11-1.1.1 mozilla-xulrunner190-gnomevfs-1.9.0.11-1.1.1 mozilla-xulrunner190-translations-1.9.0.11-1.1.1 mozilla-nspr-4.8-1.1 mozilla-nss-3.12.3-6.1 Starting firefox in a console via: lrupp@sonne:~> firefox /usr/lib/firefox/firefox -x /tmp/mozargs.qiYEjv firefox: nss_nis/nis-netgrp.c:75: _nss_nis_setnetgrent: Assertion `malloc_usable_size (netgrp->data) >= len + 1' failed. /usr/bin/firefox: line 126: 6540 Aborted $moz_debugger "$MOZ_PROGRAM" -x $tmpfile Note: moz_debug=1 is set in /usr/bin/firefox /tmp/mozargs.qiYEjv contains: set args run Windowmanager is kde4-kdm (but running KDE3 apps normaly). -- 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 12

[Bug 722602] New: Not all SLE packages are in b.o.o:SUSE:SLE-11.
by bugzilla_noreply＠novell.com 31 Jan '14

31 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=722602 https://bugzilla.novell.com/show_bug.cgi?id=722602#c0 Summary: Not all SLE packages are in b.o.o:SUSE:SLE-11. Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: SLES 11 Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: adrian(a)suse.com Found By: Beta-Customer Blocker: --- Through the update channels, SLE offers, for example, /SLES11-SP1-Updates-x86_64/rpm/x86_64/xz-5.0.3-0.12.1.x86_64.rpm However, xz is nowhere to be found on build.opensuse.org in SUSE:SLE-11:SP1:Updates, or in any of its parent projects. Please sync the b.o.o projects with what's in SLE. -- 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 24

[Bug 673720] New: zypper overwrites files when it probably should not
by bugzilla_noreply＠novell.com 29 Jan '14

29 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=673720 https://bugzilla.novell.com/show_bug.cgi?id=673720#c0 Summary: zypper overwrites files when it probably should not Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Given two packages (foo-a, foo-b) that share a file with the same pathname and different file contents/checksums, rpm will properly report a problem, but zypper just ignores it and papers over without mentioning foo-a at all. jng-0:/usr/src/packages/RPMS/x86_64 # rpm -ihv foo-b-0-0.x86_64.rpm Preparing... ########################################### [100%] file /foobar from install of foo-b-0-0.x86_64 conflicts with file from package foo-a-0-0.x86_64 jng-0:/usr/src/packages/RPMS/x86_64 # zypper in foo-b-0-0.x86_64.rpm Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: foo-b 1 new package to install. Overall download size: 2.0 KiB. After the operation, additional 1.0 KiB will be used. Continue? [y/n/?] (y): Retrieving package foo-b-0-0.x86_64 (1/1), 2.0 KiB (1.0 KiB unpacked) Retrieving package foo-b-0-0.x86_64 (1/1), 2.0 KiB (1.0 KiB unpacked) Installing: foo-b-0-0 [done] --- # do similar for foo-b Name: foo-a Version: 0 Release: 0 Summary: a License: x %description %install mkdir -p "%buildroot" date >"%buildroot/foobar" %files %defattr(-,root,root) /foobar -- 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 19

[Bug 654656] New: PING & DIG not use Internationalized Domain Names (IDN) library
by bugzilla_noreply＠novell.com 28 Jan '14

28 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=654656 https://bugzilla.novell.com/show_bug.cgi?id=654656#c0 Summary: PING & DIG not use Internationalized Domain Names (IDN) library Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: max(a)stranger-team.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; ru) Presto/2.7.39 Version/11.00 Network tools ping, dig don't work with Internationalized Domain Names (IDN), but libidn library installed. ping вело100.рф ping: unknown host вело100.рф dig вело100.рф ; <<>> DiG 9.6.1-P3 <<>> вело100.рф ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59074 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;\208\178\208\181\208\187\208\190100.\209\128\209\132. IN A ;; AUTHORITY SECTION: 10581 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2010111701 1800 900 604800 86400 ;; Query time: 22 msec ;; SERVER: 10.55.55.5#53(10.55.55.5) ;; WHEN: Thu Nov 18 18:30:22 2010 ;; MSG SIZE rcvd: 109 and this workaround works: ping `echo "вело100.рф" | idn --quiet` PING xn--100-eddp0bv.xn--p1ai (90.156.201.105) 56(84) bytes of data. 64 bytes from fe.shared.masterhost.ru (90.156.201.105): icmp_seq=1 ttl=56 time=23.5 ms 64 bytes from fe.shared.masterhost.ru (90.156.201.105): icmp_seq=2 ttl=56 time=22.6 ms .. Reproducible: Always Steps to Reproduce: 1. just ping or dig 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 3

[Bug 669124] New: sender of obs del hermes notifications
by bugzilla_noreply＠novell.com 27 Jan '14

27 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=669124 https://bugzilla.novell.com/show_bug.cgi?id=669124#c0 Summary: sender of obs del hermes notifications Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Hermes AssignedTo: freitag(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: adrian(a)novell.com Found By: --- Blocker: --- package delete notifications contain the owner of the delete request as "From". Previously it used to be "hermes(a)opensuse.org" which is what I used as trigger for a mail filter. I think the "From" header should stay at "hermes(a)opensuse.org" and "Reply-To" could be set to the person who filed the delete request instead. -- 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 732884] New: firewall activation during install(default) causes firewall deactivation with install finishing - user do not see that!
by bugzilla_noreply＠novell.com 27 Jan '14

27 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=732884 https://bugzilla.novell.com/show_bug.cgi?id=732884#c0 Summary: firewall activation during install(default) causes firewall deactivation with install finishing - user do not see that! Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: melchiaros(a)aol.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=464186) --> (http://bugzilla.novell.com/attachment.cgi?id=464186) yast2, message, warn, zypper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I´ve tried it with two independent openSUSE12.1 final 64bit installations: The firewall is set to active during installation by default, but: In the finished installation the firewall is in fact !deactivated!!! -> instead of the default firewall activation setting in the install system(which I have not changed). A user have to manually check thatover the yast2 firewall module and have to activate it manually for the session and also have to activate the firewall start by system start. -> Both has to be done when the firewall activation is set by the installation system! Reproducible: Always Steps to Reproduce: 1.start the openSUSE12.1 final 64bit installation from the full4.7GB DVD 2.Do the default installation of the sytem(I have switched off the seperate home partition) 3.See in the final summary dialog that firewall is set to active by default and let it be like this. 4.Finish the installation and wait for the first start of the system. 5.After the first start of the system call yast2 -> firewall 6.See in the yast2 firewall module that the firewall is not active and also not starting with system start! -> that is the opposite of what the user has chosen!!! Actual Results: Not working firewall after install by activating firewall during installation. -> the opposite behavior of what is chosen in the installation system. Expected Results: The firewall should behave like it is set in the installation dailog. -> By default the firewall should start, when it is set to start during installation( and by default. There are tree thinks to say about that(see it as personal comment): 1.I remember that such a problem was also there in openSUSE11.4 and may be 11.3(and may be before ; do not remember for that). -> When a failure occurs regularly there should be a point in the shipping procedure during development cycle that point on checks for that. 2.I have as standard some server(also apache) installed. Just for figuring arround. To have it quick there when I just need it, so that I do not spend extra time it such moments for installing and enabling. -> I be sure that much other handle it like this. 3.You should think about your packager. A local installation of obs has a working apache server in it´s dependence as far as I remember -> It would be not so greatfull when passwords for the official obs would get lost or spec files would get manipulated that would later find their way unrecognized of the manipulation with upload to the official obs. -- 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 26

[Bug 712171] New: openSUSE:Tools/spec-cleaner: frivolous %make_install breaks SLE_11_SP1
by bugzilla_noreply＠novell.com 26 Jan '14

26 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=712171 https://bugzilla.novell.com/show_bug.cgi?id=712171#c0 Summary: openSUSE:Tools/spec-cleaner: frivolous %make_install breaks SLE_11_SP1 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: adrian(a)novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- spec-cleaner replaces > make install DESTDIR=${RPM_BUILD_ROOT} with > %make_install This trick breaks the build for SLE_11_SP1. + %make_install /var/tmp/rpm-tmp.59594: line 45: fg: no job control -- 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 10