November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 733523] New: /var/lock permissions re: arduino, minicom
by bugzilla_noreply＠novell.com 14 Feb '14

14 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=733523 https://bugzilla.novell.com/show_bug.cgi?id=733523#c0 Summary: /var/lock permissions re: arduino, minicom Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: s2(a)forceway.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 It seems something has changed from openSUSE 11.4. Programs like minicom & arduino (IDE) worked fine before if you added your user to the uucp & dialout groups. Now arduino gives an error like: LOCKING /dev/ttyUSB0 lib_lock_dev_lock() lockstatus fail, are you in group 'lock'? .and you are unable to select a serial port in the menu. minicom displays a similar lock error. Adding user to the lock group has no effect. The quick workaround is: sudo chmod g+rwx,o+rwt /var/lock Reproducible: Always Steps to Reproduce: 1. have a serial port. 2. install & run minicom -D /dev/ttyUSB0 (for example) 3. lock error message Actual Results: "Cannot create lockfile..." Expected Results: should be able to create locks somehow -- 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 14

[Bug 672055] New: mmap of area larger than VRAM causes map to fail
by bugzilla_noreply＠novell.com 13 Feb '14

13 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=672055 https://bugzilla.novell.com/show_bug.cgi?id=672055#c0 Summary: mmap of area larger than VRAM causes map to fail Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- The following program will fail to obtain a vma on a system with less than 2 GB in VRAM (physram + swap): --- #include <sys/mman.h> #include <stdio.h> int main(void) { void *p = mmap(NULL, 2000000000, PROT_READ | PROT_WRITE, MAP_SHARED | MAP_ANONYMOUS, 0, 0); printf("%p\n", p); } --- Linux normally does overcommit, does it not? /proc/sys/vm # grep '' overc* overcommit_memory:0 overcommit_ratio:50 The mmap call also fails if one simply tries to map, for example, a large enough DVD image file in read-only mode — a case where no memory allocation should occur at all. -- 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 22

[Bug 574774] New: /etc/initscript tries to set the soft and hard limits in wrong order
by bugzilla_noreply＠novell.com 13 Feb '14

13 Feb '14

http://bugzilla.novell.com/show_bug.cgi?id=574774 http://bugzilla.novell.com/show_bug.cgi?id=574774#c0 Summary: /etc/initscript tries to set the soft and hard limits in wrong order Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mgyhardsoft(a)freestart.hu QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; hu; rv:1.9.2) Gecko/20100115 Firefox/3.6 In /etc/initscript Line 94 sets the soft limits and Line 95 the hard limits - which is in wrong order. Reproducible: Always Steps to Reproduce: It is an example consequence of the actual problem: 1. Set e.g. soft file descriptor limit to 5000. 2. Reboot system. Actual Results: The system displays an error message for /etc/initscript Line 94 stating that the parameter is invalid. Expected Results: Set soft file descriptor limit to 5000. The actual problem is that the soft limit (5000) is tried to be set before the hard limit (8192) so it fails. Resolution is easy: simply change the order of lines 94 and 95: set the hard limits first then the soft limits, and suddenly the error message disappears. -- 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 698516] New: gcal: week starts on Sunday
by bugzilla_noreply＠novell.com 13 Feb '14

13 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=698516 https://bugzilla.novell.com/show_bug.cgi?id=698516#c0 Summary: gcal: week starts on Sunday Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ohering(a)novell.com QAContact: qa(a)suse.de Found By: Outsourced Testing Blocker: --- with 11.3 and 11.2 the week starts on Monday as it should. with 11.4 the week starts on Sunday. env LC_ALL=de_DE.UTF8 gcal | cat Juni 2011 Sonntag 5 12 19 26 Montag 6 13 20 27 Dienstag < 7>14 21 28 Mittwoch 1 8 15 22 29 Donnerstag 2 9 16 23 30 Freitag 3 10 17 24 Samstag 4 11 18 25 -- 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 671491] New: Tag not closed in help sentence
by bugzilla_noreply＠novell.com 12 Feb '14

12 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=671491 https://bugzilla.novell.com/show_bug.cgi?id=671491#c0 Summary: Tag not closed in help sentence Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: gabriel(a)opensuse.org QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b11) Gecko/20100101 Firefox/4.0b11 The tag is not closed in the following sentence: Menu Description File specifies path on root device from which is loaded menu file. 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 3

[Bug 725965] New: No tty at all using grub2-efi-mkconfig default script
by bugzilla_noreply＠novell.com 11 Feb '14

11 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=725965 https://bugzilla.novell.com/show_bug.cgi?id=725965#c0 Summary: No tty at all using grub2-efi-mkconfig default script Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: vljn(a)ovi.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=458368) --> (http://bugzilla.novell.com/attachment.cgi?id=458368) My (non modified) grub.cfg generated file User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Hi, when using grub2-efi-mkconfig to generate a grub.cfg file, the "set gfxpayload=" seems uneffective. When I boot, I have no kernel console at all : the last output of grub (loading kernel... loading initrd...) stays untill X is launched. And ctrl alt Fx just display a black screen, which is problematic if there's a X failure for instance. Manually editing to have set gfxpayload=1024x768x16 makes console appear, but the mkconfig script does not generate it. Reproducible: Always Steps to Reproduce: 1.Ensure you don't boot in KMS mode (to prevent KMS driver to override grub gfxpayload config) 2.Generate a grub.cfg using grub2-efi-mkconfig 3.Boot Actual Results: No console at all Expected Results: There should be a console -- 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 22

[Bug 733170] New: Recent updates to 12.1 causing SEVERE IO issues with IDE connected LS-120
by bugzilla_noreply＠novell.com 07 Feb '14

07 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=733170 https://bugzilla.novell.com/show_bug.cgi?id=733170#c0 Summary: Recent updates to 12.1 causing SEVERE IO issues with IDE connected LS-120 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: roland(a)logikalsolutions.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 This device worked flawlessly with the initial 12.1 release and has worked flawlessly with many versions of many distros. After the last few rounds of updates, it now takes whole seconds between IO operations. Last time something like this happened, it was a broken kernel in Ubuntu. I assume the same "fix" found its way into the kernel now being used here. I don't know how they fixed it over there, but it was quickly fixed. Reproducible: Always Steps to Reproduce: 1. Install 12.1 2. apply all updates 3. insert superfloppy Actual Results: multiple seconds happen between IO operations. Takes eternity to mount. No longer shows up with a mount notification message box. Expected Results: Should pop up the little "what do you want to do" window quickly and allow mounting. -- 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 4

[Bug 628936] New: soft lockup - CPU#0 stuck
by bugzilla_noreply＠novell.com 07 Feb '14

07 Feb '14

http://bugzilla.novell.com/show_bug.cgi?id=628936 http://bugzilla.novell.com/show_bug.cgi?id=628936#c0 Summary: soft lockup - CPU#0 stuck Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: arysin(a)yahoo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=381068) --> (http://bugzilla.novell.com/attachment.cgi?id=381068) system log for soft lockup on resume from RAM User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 Soft lockup is happening more often than not on resuming from RAM on Dell Studio 15. Reproducible: Sometimes Steps to Reproduce: 1.Suspend to RAM 2.Resume Actual Results: Occasionally laptop resume right away but more often it takes minute or two and that's when soft lockup is seeing in the log. Expected Results: Should always resume right away without lockups. -- 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 20

[Bug 721663] New: udev: should we add deps between udev/libudev?
by bugzilla_noreply＠novell.com 04 Feb '14

04 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=721663 https://bugzilla.novell.com/show_bug.cgi?id=721663#c0 Summary: udev: should we add deps between udev/libudev? Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 5 Platform: All OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Prehistory: wanted to have a new systemd on 11.4, so I went to install that, its dependencies (newer versions of filesystem, mkinitrd, udev, etc.) and all xorg-*. Result: input in Xorg does not work, i.e. keypresses and mouse produce no events. Now, I know that half-updated systems are not particularly supported, but it shows that using develproject repositories (and their openSUSE_11.4 output mode) may have similar issues. Well, turns out that libudev0-166, which was still installed since no rpm requirements required its update, is incompatible with udev-173. Updating libudev0-166 to libudev0-173 resolves the Xorg kb/mouse issue. Since it seems that libudev is tied to udev, should we perhaps consider adding a manual Requires tag in some .spec file? -- 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 628298] New: api.o.o flakes out when remote bs_srcserver requests
by bugzilla_noreply＠novell.com 04 Feb '14

04 Feb '14

http://bugzilla.novell.com/show_bug.cgi?id=628298 http://bugzilla.novell.com/show_bug.cgi?id=628298#c0 Summary: api.o.o flakes out when remote bs_srcserver requests Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: Linux 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)novell.com Found By: Beta-Customer Blocker: --- When a OBS local instance is booted, the local scheduler queries the local srcserver for projpacks. # rcobssrcserver status Checking for obssrcserver and running processes: R 4287 29613 GET /getprojpack?withsrcmd5&withdeps&withrepos&withconfig&arch=x86_64 ~same line~ ...=i586 ~same line~ ...=sparcv9 ~same line~ ...=sparc64 All but one of these getprojpack calls hangs, that is, # strace -p 29613 read(4, ^C The srcserver logfile is usually empty: 2010-08-04 12:52:08: bs_srcserver started on port 5352 2010-08-04 12:52:12 [29613]: GET /getprojpack?withsrcmd5&withdeps&withrepos&withconfig&arch=x86_64 2010-08-04 12:52:12 [29615]: GET /getprojpack?withsrcmd5&withdeps&withrepos&withconfig&arch=sparcv9 2010-08-04 12:52:12 [29616]: GET /getprojpack?withsrcmd5&withdeps&withrepos&withconfig&arch=sparc64 2010-08-04 12:52:12 [29619]: GET /getprojpack?withsrcmd5&withdeps&withrepos&withconfig&arch=i586 reading config for Black_Ares:11.2-update/standard x86_64 reading config for Black_Ares:11.2-update/standard i586 reading config for Black_Ares:11.2-update/standard sparcv9 reading config for Black_Ares:11.3/standard sparc64 Without much traces. -- 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 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

[Bug 652818] New: [spec-cleaner] Summary gets put within BuildRequires
by bugzilla_noreply＠novell.com 26 Jan '14

26 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=652818 https://bugzilla.novell.com/show_bug.cgi?id=652818#c0 Summary: [spec-cleaner] Summary gets put within BuildRequires Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: prusnak(a)novell.com ReportedBy: bitdealer(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- If one uses %if not_suse ..... %endif the Summary: tag ends up between said build requires and the main BuildRequires. IMHO the Summary should be right before the description. An example is security:OpenVAS:STABLE:v3/openvas-libraries Excerpt: %if 0%{?suse_version} BuildRequires: libgpgme-devel BuildRequires: libuuid-devel %endif Summary: Support libraries for OpenVAS BuildRequires: bison BuildRequires: cmake >= 2.6.0 BuildRequires: glib2-devel >= 2.12 -- 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 500382] New: zypper and yast2 have different opinions about what needs updating
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=500382 Summary: zypper and yast2 have different opinions about what needs updating Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)eregion.de QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.9) Gecko/2009041500 SUSE/3.0.9-0.1.1 Firefox/3.0.9 i do a "zypper -r up" as root on a commandline and i get this output: sai:~ # zypper -r lu Retrieving repository 'Packman Repository' metadata [done] Building repository 'Packman Repository' cache [done] Loading repository data... Reading installed packages... No updates found. sai:~ # to me that means "no new package versions for the stuff you have installed." Now, if i start yast2, go to "install/remove software" (yast2 sw_single), select "summary", then set the checkmark for "keep" (I see all installed packages now), then right-click somewhere in that list and choose "all in this list -> update if never version is available" i get a message telling me "plasmoid-systemloadviewer-0.6-2.36.i686 needs kdebase4-runtime >= 4.2.2 which is not available", and a list of 100 packages, all belonging to KDE 4.2.2, which should be uninstalled. The culprit is the package kde4-webkitpart-4.2.2.svn958332-2.1 from kde3::backports (which, in my opinion, should not be there at all anyways). If i select "do not install kde4-webkitpart-4.2.2.svn958332-2.1" i dont get any problems. Now, the issue in this bug is, why does yast2 think that kde4-webkitpart needs upgrading, and "zypper -r up" does not? Which of the two ways to update your installation is the one to be trusted and relied on? yast2, or zypper? Reproducible: Always Steps to Reproduce: 1. add the repositories for KDE 4.2 and KDE 3 for opensuse 11.1 2. zypper -r up 3. yast2 sw_single (see above) Actual Results: see summary Expected Results: zypper and yast2 should have the same "ideas" about which packages need updating. -- 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 498556] New: Online Update will Not Install "All Patches" when selected
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=498556 Summary: Online Update will Not Install "All Patches" when selected Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 Online update has never been able to install anything but 'Needed Patches'. The definition of Needed Patches escapes me however, If I display 'All Patches" by filter and the select Patches in this list>Install the patches are changed to a green tick but will never be installed. Reproducible: Always Steps to Reproduce: 1.Open Online Update 2.Filter Patches by - All Patches instead on needed patches 3.Patch>In this list> Install - All Patches are marked for installation 4. Accept. 5. Result nothing is installed and suseconfig runs immediately after nothing has been installed Actual Results: Patches marked for Installation are not installed Expected Results: Patches marked for installation ARE installed. This is 100% reproducible - Please only request yast logs IF for some very strange reason it cannot be re-produced. -- 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 15

[Bug 727911] New: no printer config file (ppd) found by yast
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=727911 https://bugzilla.novell.com/show_bug.cgi?id=727911#c0 Summary: no printer config file (ppd) found by yast Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdd(a)dodin.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I have only network printer - when installing it yast do detect it due to the firewall. but then yast do not find either any ppd file. When instructed to look at the IP, yast find the printer (hp), but do not either find any driver. Hplip have the same problem However, cups at port 631 *do* find the drivers and install the printer. After that yast find all the drivers (I could change the printer driver with yast) 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 28

[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 540587] New: If Yast MUST NOT kill SQUID in middle of system update!
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=540587 Summary: If Yast MUST NOT kill SQUID in middle of system update! Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 I was doing a system update. Normally my web requests go through squid to take advantage of a large local (6GB) disk cache for various downloaded objects. However, yast also pays attention to the global vars HTTP_PROXY and friends, and uses them during its operations. Normally not a problem. However I was doing a Factory update. That just happened to include squid this time. About half way through a 500MB download/update it suddenly lost its connection -- and hung. Restarting squid didn't help. It was dead and required restart -- at which point trying to redo the factory update was futile -- it thought everything was done -- BUT the configuration of every service it updated was *wiped* and set to 'off'. I'm having to go through each service as I find which ones it killed and wiped and reconfig or at least restart them. But in a few cases, the config files have been reinitialized to non-workable values. Examples: xinetd was setup with no tcpmux builtin configure, so installed services like vnc generated errors because the standard vnc-server needs TCPMUX. The arpwatchd was no longer looking on my inside net, but on my outside and talking about bogons because it lost it's local group list. It also was no longer in its own group. named is now generating messages about not having write access to its working directory (don't know if this is a new message, or something was changed). The squid startup script was replaced and the old one wasn't saved -- I had it set to filter some common error messages (restored from an edit backup). Might be a few others -- several services were just 'stopped (chkconfiged 'off') when they had been on. Have yet to do an exhaustive search for problems, as I'm still in firefighting mode. But Yast really needs to be smart enough to check, if it is using a proxy server, AND proxy server is on same system, it needs to be "very circumspect about restarting it (if it should restart it at all, maybe it should ask user or wait for reboot?)...but if it closed all connections and was sure it would restart, then it could auto-restart it just like when log-rotation happens periodically. Marking this Critical, as it has cost a large amount of time to recover from this (still in progress).... and did lose some data (though I probably have earlier backups I could restore from, I'm taking opportunity to recheck configs. I am noticing some (1-2?) incompatible config files with the new versions that were installed. Will try to remember to file more bugs later...but filing bugs takes me away from fixing, and my email is another service that is broken right now. (was trying to fix some configuration problem and I've made things worse! --- ;^) so what else is new...but if it hadn't been broken in the first place, I probably wouldn't have been mucking w/it!...but hey, it *is* a learning experience, so I'm not "angry", more like 'annoyed'...and wanting to create this bug as a notice of the problem. Reproducible: Didn't try Steps to Reproduce: 1. have "alot" of updates (I didn't see all the updates -- it autoselected "A bunch" more than I had picked out...(as usual ;^/ )...dependency hell! 2. I was updating through a proxy server (squid) running on the machine being updated -- I didn't explicitly ask yast todo this, it just took the values from my environment vars (HTTP_PROXY & such)... 3. One of the packages updated, "apparently" was squid...right in the middle of the updates. It left my system in an inconsistent and ill-or-unconfiged state with many serviced turned off (that had been on ). Actual Results: System way messed up. Expected Results: Normal factory upgrade. -- 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 29

[Bug 646093] New: Ghostscript 9.00 fails when building lilypond documentation
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=646093 https://bugzilla.novell.com/show_bug.cgi?id=646093#c0 Summary: Ghostscript 9.00 fails when building lilypond documentation Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: davejplater(a)gmail.com QAContact: jsmeix(a)novell.com CC: werner(a)novell.com Found By: --- Blocker: --- Created an attachment (id=394667) --> (http://bugzilla.novell.com/attachment.cgi?id=394667) File to reproduce the bug gs fails when converting ps to pdf :- gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile="./d6/lily-50e2bfee.png" -r202 "./d6/lily-50e2bfee.eps" -c quit GPL Ghostscript 9.00 (2010-09-14) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Can't handle format 12 Error: /typecheck in --@0x7f798cd8f830-- Operand stack: 1.951 0.0 0.0 uni306B 1.951 0.0 0.0 uni306F 1.951 0.0 0.0 uni308D 1.951 77.7211 -24.8756 --dict:15/17(ro)(L)-- uni3044 uni3044 --nostringval-- Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1910 1 3 %oparray_pop 1909 1 3 %oparray_pop --nostringval-- 1893 1 3 %oparray_pop 1787 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 3 --nostringval-- %repeat_continue --nostringval-- %finish_show --nostringval-- --nostringval-- 6 3 15 --nostringval-- (gs_show_enum) %op_show_continue Dictionary stack: --dict:1177/3371(ro)(G)-- --dict:0/20(G)-- --dict:121/200(L)-- Current allocation mode is local Last OS error: 2 Current file position is 18922 GPL Ghostscript 9.00: Unrecoverable error, exit code 1 For complete build logs with three "Can't handle format 12" failures only the last one faults :- https://build.opensuse.org/stage/package/show?package=lilypond&project=open… I'll attach the offending file to enable reproduction -- 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 17

[Bug 568280] New: ghostscript segfaults building lilypond-2.12.3
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c0 Summary: ghostscript segfaults building lilypond-2.12.3 Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: janneke(a)gnu.org QAContact: jsmeix(a)novell.com Found By: --- Blocker: --- Created an attachment (id=334964) --> (http://bugzilla.novell.com/attachment.cgi?id=334964) lily-65a7b1b1-1.eps modified to read emmentaler-20.otf from cwd User-Agent: Mozilla/5.0 (X11; U; Linux i686; nl; rv:1.9.1.6) Gecko/20091215 Ubuntu/9.10 (karmic) Firefox/3.5.6 Trying to bump lilypond to 2.12.3, I find that the documentation does (still, see #502647) not build in current factory, due to ghostscript segfaulting. There's a new upstream release of ghostscript available: 8.70 that successfully builds the lilypond documentation, you may want to update. I'm attaching the input file: lily-65a7b1b1-1.eps Reproducible: Always Steps to Reproduce: This is the command that fails Run LANG= gs -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="lily-65a7b1b1-1.pdf" -c .setpdfwrite -f "bug.eps" Actual Results: Segmentation fault Expected Results: Clean exit producing lily-65a7b1b1-1.pdf peder:/usr/src/packages/BUILD/lilypond-2.12.3> rpm -qi ghostscript-library Name : ghostscript-library Relocations: (not relocatable) Version : 8.64 Vendor: openSUSE Release : 9.3 Build Date: ma 04 jan 2010 05:06:04 UTC Install Date: ma 04 jan 2010 19:58:14 UTC Build Host: build35 Group : System/Libraries Source RPM: ghostscript-library-8.64-9.3.src.rpm -- 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 30

[Bug 732673] New: windows 7 SP1 and openSUSE12.1 parallel installation fail with error code -1007
by bugzilla_noreply＠novell.com 14 Jan '14

14 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=732673 https://bugzilla.novell.com/show_bug.cgi?id=732673#c0 Summary: windows 7 SP1 and openSUSE12.1 parallel installation fail with error code -1007 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=463994) --> (http://bugzilla.novell.com/attachment.cgi?id=463994) only a screenshot User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I´ve tried a parallel installation in Virtualbox4.1.6. First Windows7 SP1 engl. 64bit debug version was installed. Second openSUSE12.1 64bit should be installed on the same virtual harddrive. I´ve choosen ext4 with separate home partition. During preparing the virtual harddrive I get the error code 1007 for /hde/sda5 A can only provide a screenshot. To handle it with nfs for getting yast2 logs from installation I have not the time in moment. Reproducible: Didn't try Steps to Reproduce: 1.Install Windows 7 Sp1 engl. debug version 64bit on virtualbox 4.1.6 with 80GB dynamical .vdi virtula harddrive. 2.Shutdown the vm after install successes. 3.Attach drive with openSUSE12.1 final 64bit dvd in virtualbox vm settings for the windows 7 machine. 4.Try to install openSUSE12.1 64bit with ext4 and separate home partition(default) -> Shrinking the windows partition is automatically done by the openSUSE installation environment. 7.See the parallel installation fail with eroor code 1007 Actual Results: A parallel installation between Windows 7 Sp1(first OS) and openSUSE12.1(second OS) is not possible. Expected Results: A parallel installation should be possible without errors. A reproduction should be easy and because of virtualbox usage system independent. -- 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 733728] New: PackageKit zypp backend: 'recommended' updates treated as 'important'
by bugzilla_noreply＠novell.com 14 Jan '14

14 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=733728 https://bugzilla.novell.com/show_bug.cgi?id=733728#c0 Summary: PackageKit zypp backend: 'recommended' updates treated as 'important' Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: lnussel(a)suse.com QAContact: qa(a)suse.de CC: dmacvicar(a)suse.com Found By: --- Blocker: --- The zypp backend uses PK_INFO_ENUM_IMPORTANT for recommended updates. 'recommended' doesn't tell anything about severity though. In absence of support for severity I think PK_INFO_ENUM_BUGFIX is the intended tag for non-security updates. Related: bug 733723 -- 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 729348] New: Confusing output when upgrading nscd: Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended.
by bugzilla_noreply＠novell.com 13 Jan '14

13 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=729348 https://bugzilla.novell.com/show_bug.cgi?id=729348#c0 Summary: Confusing output when upgrading nscd: Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended. Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gp(a)suse.com QAContact: qa(a)suse.de Found By: Product Management Blocker: --- Just upgrading Factory, I got: Installing: nscd-2.14.1-17.1 [done] Additional rpm output: redirecting to systemctl Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended. Not sure what "redirecting to systemctl" tries to tell me in the first place, but then the warning is really confusing: if this is recommended, why not just do it as part of the upgrade? -- 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 6

[Bug 726939] New: bash completion for systemctl breaks completion for stdout redirection
by bugzilla_noreply＠novell.com 13 Jan '14

13 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=726939 https://bugzilla.novell.com/show_bug.cgi?id=726939#c0 Summary: bash completion for systemctl breaks completion for stdout redirection Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- Blocker: --- due to some bug reports around systemd I noticed the following (as root): # ls -l sys* -rw-r--r-- 1 root root 1058 Oct 27 09:34 systemctl-failed-1 -rw-r--r-- 1 root root 1058 Oct 27 09:35 systemctl-failed-2 -rw-r--r-- 1 root root 2115 Oct 27 21:40 systemctl_show_home.mount-0 -rw-r--r-- 1 root root 2058 Oct 27 21:46 systemctl_show_home.mount-after-mount -rw-r--r-- 1 root root 1903 Oct 27 21:46 systemctl_show_home.mount-before-mount -rw-r--r-- 1 root root 215408 Oct 26 15:04 systemd-dmesg-1 -rw-r--r-- 1 root root 216315 Oct 26 15:41 systemd-dmesg-2 -rw-r--r-- 1 root root 216061 Oct 27 09:21 systemd-dmesg-3 -rw-r--r-- 1 root root 250241 Oct 27 10:59 systemd-dmesg-4 -rw-r--r-- 1 root root 213067 Oct 27 17:38 systemd-dmesg-5 # systemctl > sys<TAB><TAB> # systemctl > ./s<TAB><TAB> do not show *any* output/completion :-( # systemctl > s<TAB><TAB> shows: set-environment show show-environment snapshot start status stop # complete | grep system complete -F _systemctl systemctl why is that completion relevant for output redirection ? I hate bash completions :-((( -- 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 555222] New: zypper dup should check if mkinitrd succeeds
by bugzilla_noreply＠novell.com 13 Jan '14

13 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=555222 Summary: zypper dup should check if mkinitrd succeeds Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mail(a)philipp-wagner.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-7.1 Firefox/3.5 I updated from 11.1 to 11.2 using zypper dup. My /boot partition was full and mkinitd during the installation of the kernel image probably failed. I didn't see the message as I let the update run unattended and only saw the last lines of output from zypper dup, which seemed to suggest that everything went ok. When rebooting I got a "kernel panic: attempted to kill init". Fortunately I had another kernel installed and were able to boot, remove some old files from /boot and call mkinitrd again. Now the system boots fine. A full /boot partition is not that unlikely (the default partition layout suggests a rather small /boot and installing two testkernels is enough to fill it so that mkinitrd fails. Could zypper dup give a summary of errors that happened while installing all packages in the end of the upgrade process so that the user sees this error before rebooting? 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 6

[Bug 713331] New: kbd: "Loading keymap unknown keysym 'cyrillic_small_letter_short_i"
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=713331 https://bugzilla.novell.com/show_bug.cgi?id=713331#c0 Summary: kbd: "Loading keymap unknown keysym 'cyrillic_small_letter_short_i" Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lazy.kent(a)opensuse.org QAContact: qa(a)suse.de CC: highwaystar.ru(a)gmail.com, lazy.kent(a)opensuse.org, av.linux.dev(a)gmail.com Depends on: 643538 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #643538 +++ User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-3.4 Firefox/3.6.10 kbd failed to start on KDE LiveCD boot with message Loading keymap unknown keysym 'cyrillic_small_letter_short_i' Reproducible: Always Steps to Reproduce: 1. Booot KDE LiveCD 11.4 M2 with Russian language selected in booloader 2. When it boots see boot messages in text terminal (Ctrl+Alt+F1) 3. Try to restart kbd. Actual Results: kbd failed to start on boot, so there is no cyrillic fonts loaded in text terminal -> ureadable messages. When kbd restarted from text terminal fonts are loaded fine and all works ok. Expected Results: kbd should starts fine on boot -- 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 702276] New: Fix XSLT Stylesheet Issues in susedoc
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=702276 https://bugzilla.novell.com/show_bug.cgi?id=702276#c0 Summary: Fix XSLT Stylesheet Issues in susedoc Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: thomas.schraitle(a)novell.com QAContact: ke(a)novell.com Found By: Documentation Blocker: --- There are several issues in our susedoc package in regard of XSLT. This bug collects all issues for easier accessibility. -- 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 40

[Bug 712599] New: Stylesheets: <command> in titles handled differently
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=712599 https://bugzilla.novell.com/show_bug.cgi?id=712599#c0 Summary: Stylesheets: <command> in titles handled differently Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: taroth(a)novell.com QAContact: ke(a)novell.com CC: fs(a)novell.com Found By: Documentation Blocker: --- If a <command> element is used in a title, it is handled differently depending on the section to which the title belongs (and depending on the output - PDF or HTML): PDF: - sect2 title: <command> appears in different font than the rest - sect3 title: <command> appears in the same font like the rest HTML: - <command> appears in different font in both sect2 + sect3 titles I personally prefer to have a markup for a command name even in a title, but I know there are different opinions on that. I would be fine with either solution as long as we make it consistent for all titles and outputs. (I stumbled across that in the current daps version, daps-0.9beta4-16.1.noarch) -- 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 703213] New: FOP: Font Size for Product Name on Titlepage
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=703213 https://bugzilla.novell.com/show_bug.cgi?id=703213#c0 Summary: FOP: Font Size for Product Name on Titlepage Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: taroth(a)novell.com QAContact: ke(a)novell.com Found By: Documentation Blocker: --- Created an attachment (id=437718) --> (http://bugzilla.novell.com/attachment.cgi?id=437718) HA Guide, built with FOP The font size for the product name on the title page is so large that it turns a product name like "SUSE Linux Enterprise High Availability Extension" into a 4-liner (with XEP, it takes 3 lines). -- 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 684418] New: Use serif fonts for b/w (aka printed) PDFs
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=684418 https://bugzilla.novell.com/show_bug.cgi?id=684418#c0 Summary: Use serif fonts for b/w (aka printed) PDFs Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: fs(a)novell.com QAContact: ke(a)novell.com CC: canadapatriot(a)yahoo.com Found By: --- Blocker: --- >From a cutomer mail (see Cc): Concerning the pdf documents, I notice that the last few versions of the manuals are all in sans-serif font. I urge you to consider getting the text body in a serif font (see 11.1 manuals). Sans-serif font is inappropriate for the body text, for it is less comfortable on the eye. On the other hand, serif font is appropriate for titles. The vast majority of print documents are in a serif font, and the pdf document should fit the purpose of printing, unlike the html version. -- 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 8

[Bug 705502] New: suse-ami-tools initscripts shoudn't use $ALL target
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=705502 https://bugzilla.novell.com/show_bug.cgi?id=705502#c0 Summary: suse-ami-tools initscripts shoudn't use $ALL target Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fcrozat(a)novell.com QAContact: qa(a)suse.de Blocks: 696902 Found By: --- Blocker: --- there is no plan in systemd to support SUSE non official $ALL LSB target in initscripts. It should be removed from /etc/init.d/amazon-late initscript in suse-ami-tools package. -- 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 730959] New: zypper up is ignoring interactive option
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=730959 https://bugzilla.novell.com/show_bug.cgi?id=730959#c0 Summary: zypper up is ignoring interactive option Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: i586 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: schoenberg(a)fv-berlin.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 While installing security updates using zypper up -y --skip-interactive the latest kernel 2.6.37.6-0.9-default was installed, not skipped Reproducible: Didn't try Steps to Reproduce: 1. zypper up -y --skip-interactive 2. uname -a 3. rpm -qa |grep kernel Actual Results: uname -a # uname -a Linux 2.6.37.1-1.2-default #1 SMP 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa |grep kernel kernel-default-2.6.37.6-0.9.1.x86_64 Expected Results: Kernel is interactive, should be skipped -- 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