July 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 768967] New: Apache2-ITK From Build Service Fails To Start
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=768967 https://bugzilla.novell.com/show_bug.cgi?id=768967#c0 Summary: Apache2-ITK From Build Service Fails To Start Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: draht(a)suse.com ReportedBy: raphael(a)skyleafdesign.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Other Blocker: No Apache-itk fails to start on SLES 11 SP2 on Amazon EC2 x86_64. The error message is /usr/sbin/httpd2-itk: symbol lookup error: /usr/sbin/httpd2-itk: undefined symbol: apr_reslist_maintain Starting httpd2 (itk) /usr/sbin/httpd2-itk: symbol lookup error: /usr/sbin/httpd2-itk: undefined symbol: apr_reslist_maintain The command line was: /usr/sbin/httpd2-itk -f /etc/apache2/httpd.conf Problem is resolved by manually rebuilding the packages, I rebuilt apache2 apache2-itk and libapr1, and installed the resulting RPM packages... there were about 13 total. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c89 --- Comment #89 from Dr. Werner Fink <werner(a)suse.com> 2012-07-04 11:15:18 UTC --- (In reply to comment #88) Please do not mix two different bugs even if they have similar results. If RUN_PARALLEL="yes" had helped in past then the dependency chains had been broken. With systemd and its increased and abrasive parallelized boot process has has similar behaviour then dependency chains must be corrected. Using local time in CMOS will always produce trouble at least twice a year. Therefore I'd like to enforce every user to set the CMOS clock to the international (network) standard UTC. If you know where e.g. Windows[tm] stores its information about the DTS correction in the CMOS clock we could discuss a change of this policy (nevertheless it would require read/write access to the Windows[tm] file system within initrd to be able to have a benefit about this knowledge). The CMOS clock chips of PC motherboards do not know about time zones nor they have a bit reserved to remember a possible DST switch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c88 --- Comment #88 from Felix Miata <mrmazda(a)earthlink.net> 2012-07-04 10:53:04 UTC --- (In reply to comment #87) > The mkinitrd script creates a clock warp setup if the CMOS clock is not in > UTC for multi boot environments. With this the kernels assumption on the > CMOS clock is corrected and the user space in initrd has its correct local > time back. This is a hard precondition before running fsck on the root file > system and mounting the root file system afterwards. Otherwise the time > stamps are not correct. Could the root of this bug be related to the default in /etc/sysconfig/boot: RUN_PARALLEL="yes" IIRC this seemed to be gone for a while, which may have coincided with setting that to "no" as a workaround to bug 665720. > It should be noted that no system around here has its CMOS clock in local > time. Even the most private systems uses UTC in CMOS ;) This would seem to be an obstacle to recreation and troubleshooting of problems on systems with CMOS clocks set to local. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|werner(a)suse.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c87 --- Comment #87 from Dr. Werner Fink <werner(a)suse.com> 2012-07-04 10:35:17 UTC --- (In reply to comment #86) > In case it wasn't noticed by reading my recent comments, this has been > happening on _many_ systems (and for many years), all of which are multiboot, > most of which include every currently supported openSUSE release, usually plus > Factory, plus at least one out of support openSUSE release, plus at least one > non-openSUSE Linux release from Fedora, Mandriva, Mageia, Knoppix, Debian, > CentOS, Gentoo and/or Kubuntu, plus a primary partition with at least one of > OS/2 or DOS and/or Windows, and > > all but one or two of which (the only two running RAID) have > > ***** CMOS clocks set to local time ***** > > and NTP configured to start on boot. > [...] CMOS in local time without having an initrd which inform the kernel *before* any file system is touched (file system check and mount) is a no go as the time stamps are wrong. This because the kernel assumes that CMOS clock is in UTC and uses this for its internal system clock which has to be in UTC. Otherwise the local time in user space (even the user space in initrd) has a wrong clock. Compare this with http://en.opensuse.org/SDB:Configuring_the_clock The mkinitrd script creates a clock warp setup if the CMOS clock is not in UTC for multi boot environments. With this the kernels assumption on the CMOS clock is corrected and the user space in initrd has its correct local time back. This is a hard precondition before running fsck on the root file system and mounting the root file system afterwards. Otherwise the time stamps are not correct. Even with this setup the problem of DST switches twice a year can cause trouble as the CMOS clock has to be corrected by user its self *before* the system accesses the file system. It should be noted that no system around here has its CMOS clock in local time. Even the most private systems uses UTC in CMOS ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 769921] New: The launcher icon reappers
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=769921 https://bugzilla.novell.com/show_bug.cgi?id=769921#c0 Summary: The launcher icon reappers Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: fintobersaglio(a)yahoo.it QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=497374) --> (http://bugzilla.novell.com/attachment.cgi?id=497374) image of launchers User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20100101 Firefox/13.0.1 if i remove the launcher in the panel, when rebbot the system, the launcher (after removed) reappers Reproducible: Always Steps to Reproduce: 1.remouve the luncher in the pannel (for example dolphjin and firefox) 2.reboot the system 3.launcher firefox and dolphin reappers in the pannel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c86 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|mrmazda(a)earthlink.net |werner(a)suse.com --- Comment #86 from Felix Miata <mrmazda(a)earthlink.net> 2012-07-04 10:16:16 UTC --- (In reply to comment #85) > No I do not have any idea otherwise this would be fixed, only a broken system > setup like wrong CMOS clock not in UTC and/or strange file system setup causing > such recovering due wrong timestamps and/or broken unmount chain. > As no one here can reproduce this here on any system it is up on the reporter to > provide more informations. In case it wasn't noticed by reading my recent comments, this has been happening on _many_ systems (and for many years), all of which are multiboot, most of which include every currently supported openSUSE release, usually plus Factory, plus at least one out of support openSUSE release, plus at least one non-openSUSE Linux release from Fedora, Mandriva, Mageia, Knoppix, Debian, CentOS, Gentoo and/or Kubuntu, plus a primary partition with at least one of OS/2 or DOS and/or Windows, and all but one or two of which (the only two running RAID) have ***** CMOS clocks set to local time ***** and NTP configured to start on boot. All Linux partitions are either swap, EXT2 or EXT3. All of EXT2 and EXT3 were formatted with I=128 and most with bs=1024. Most / partitions are 4800MB, with some 4000, some 4400, a few 7200, and the few largest 10400. Most if not all have had tune2fs -c0 -i0 run on them. I configure so that the oldest of installed kernels and bootloaders are able to access every native partition, if not every non-native partition, as well. For purposes of testing for this difficult not to reproduce bug, I usually do not boot other installations besides the openSUSE one being tested against until update cycles with their associated zypper ups or dups are complete, which usually means one openSUSE kernel is having a newer openSUSE kernel added and next booted to with no other kernel being used in between, which means no other kernels are mounting any partitions in between use of first kernel and upgrade kernel. On those systems that include an OS/2 installation, the master bootloader is IBM Boot Manager. Regardless whether IBM BM is installed, the master Grub bootloader is never on the MBR, and always controlled by me manually rather than by any installed OS, mounted either as /disks/boot or /disks/hda/boot, virtually never as /boot. IBM BM writes to disk on every boot, though I can't say whether this includes writing to MBR sector in every or even any case. Most MBRs carry BIOS compatible legacy code written or originally written by Microsoft or IBM. All Linux installations are configured with a non-empty /etc/exports file and installed nfs-kernel-server, to start on boot when I don't forget to change the "off" installation default to "on". Byte counts for fstabs average well in excess of 6000, with more than 11000 typical of late. Most of their sizes are accounted for most of the time by unpowered hosts, as its rather infrequent I have more than 4 running at once. Much more usual during testing is 3 or 4. Not counting Wine, DOSbox or DOSemu, none of my systems use any kind of virtualization. To provide more information I need to be told exactly what additional information is required. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 769215] New:=?UTF-8?Q?=20=D0=A1an=20not=20add=20a=20screenshot=20to=20the=20package=20on=20software?=.opensuse.org page
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=769215 https://bugzilla.novell.com/show_bug.cgi?id=769215#c0 Summary: Сan not add a screenshot to the package on software.opensuse.org page Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: svalx(a)svalx.net QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1 I can not add a screenshot for the package on the search page if the package is not present in the Debian packages. As far as I know these screenshots are downloaded from the http://screenshots.debian.net service and if the pakage is not present for Debian then you can not upload it there. Reproducible: Always Steps to Reproduce: 1. Create a new unique package in build sevice. 2. Build and publish it. 3. Find it on search page. 4. Sure there are no screenshot and unsuccessfully try to add it. Actual Results: No screenshot on search page. Expected Results: Present screenshot on search page. -- 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 756012] New: /etc/profile.d/profile.{c}sh needs to set proxy vars to empty instead of unset if not all proxy types are supported
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=756012 https://bugzilla.novell.com/show_bug.cgi?id=756012#c0 Summary: /etc/profile.d/profile.{c}sh needs to set proxy vars to empty instead of unset if not all proxy types are supported Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)eregion.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 I'm using a privoxy setup to block popups. Since privoxy does only support http and https, I've only set http_proxy and https_proxy in /etc/sysconfig/proxy, in which case the global profilerc does not set the ftp_proxy variable. Enter libproxy: libproxy in this case falls back to "use http proxy" which according to them is the "expected behaviour", see http://code.google.com/p/libproxy/issues/detail?id=175 Their suggestion for my scenario is to set ftp_proxy and the rest to "" instead of not setting them at all... which would need a change to /etc/profile.d/profile.{c}sh because I also use SCPM and have one stored profile where I actually _DO_ use a ftp proxy. Reproducible: Always Steps to Reproduce: 1. configure http and https proxy through /etc/sysconfig/proxy but no ftp proxy 2. test proxy assignment with libproxy: enter "proxy ftp://ftp.gwdg.de" on a shell Actual Results: lemmy@sai:/etc/profile.d> proxy ftp://ftp.gwdg.de http://kotoko.eregion.home:8080 Expected Results: lemmy@sai:/etc/profile.d> export ftp_proxy="" lemmy@sai:/etc/profile.d> proxy ftp://ftp.gwdg.de direct:// -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 769734] New: YaST crashes when trying to do an installation from live cd
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=769734 https://bugzilla.novell.com/show_bug.cgi?id=769734#c0 Summary: YaST crashes when trying to do an installation from live cd Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: i586 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: idonmez(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=497213) --> (http://bugzilla.novell.com/attachment.cgi?id=497213) Error screenshot How to reproduce 1. Get the live cd from http://w3.suse.de/~idoenmez/openSUSE-12.2-livecd-gnome.x86_64-2.8.0.iso and boot inside qemu 2. Click "Activities" 3. Click "Live Installer" icon Get a crash dialog in the attached screenshot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11