July 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 828432] lokalize declared GPL-2.0+ but contains GPL-3.0+ src/tm/qamodel.cpp
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=828432 https://bugzilla.novell.com/show_bug.cgi?id=828432#c3 Raymond Wooninck <tittiatcoke(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE --- Comment #3 from Raymond Wooninck <tittiatcoke(a)gmail.com> 2014-07-24 13:33:53 UTC --- Marked as duplicate of 814081 *** This bug has been marked as a duplicate of bug 814081 *** http://bugzilla.novell.com/show_bug.cgi?id=814081 -- 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 885986] New: During boot pressing Esc stops Plymouth at doing something with LVM2
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=885986 https://bugzilla.novell.com/show_bug.cgi?id=885986#c0 Summary: During boot pressing Esc stops Plymouth at doing something with LVM2 Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: freek(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 During the boot process when Plymouth shows the splash screen at full brightness, when I press Esc to see the progress of this process, the last line on the screen shows something with LVM2 and there is no progress anymore. Finally I get a failure to boot and I am asked to enter the root password. I enter the command to see the log and I notice near the end of the log that a number of mounts are not successful. Leaving Plymouth alone, by not pressing Esc, gives me the log in screen. Reproducible: Always Steps to Reproduce: 1. Press key Esc shortly after the Plymouth boot splash screen is at full brightness, before that nothing happens, to watch the progress of the boot process. 2. 3. Actual Results: The system seems to halt doing something with LVM2 Expected Results: See finishing the boot process and the appearance of the log in screen. I have quite a lot of partitions to mount. -- 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 882732] New: Wireshark 1.8.15 maintenance release
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=882732 https://bugzilla.novell.com/show_bug.cgi?id=882732#c0 Summary: Wireshark 1.8.15 maintenance release Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de CC: cyliu(a)suse.com Depends on: 882731 Found By: --- Blocker: --- Dear maintenance team, Wireshark 1.8.15 is the last release in the 1.8.x series. From >From https://www.wireshark.org/docs/relnotes/wireshark-1.8.15.html Wireshark 1.8 will reach end of life on June 21, 2014. This is the last official release of that branch. If you are still running Wireshark 1.8 or earlier we strongly recommend upgrading to Wireshark 1.12 or 1.10. The update in bug 882731 will offer Wireshark 1.8.15 for openSUSE 12.3. Going forward, as per http://en.opensuse.org/openSUSE:Maintenance_policy, please approve the version update to the Wireshark 1.10.x series for openSUSE 12.3. I give the following reasons: * soon discontinued and use dis-encouraged by upstream * non-trivial back-ports of fixes * almost a leaf package (kismet) * 1.10.x is known to build for and work on 12.3 via network:utilities Thanks, Andreas -- 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 814656] New: after booting to runlevel3 there is no login prompt only message that "Multi-User" target has been reached
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=814656 https://bugzilla.novell.com/show_bug.cgi?id=814656#c0 Summary: after booting to runlevel3 there is no login prompt only message that "Multi-User" target has been reached Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: darin(a)darins.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 After performing a distribution upgrade from openSUSE_12.1 to openSUSE_12.3 when the system(s) boot there is no login prompt on the system console. When you hit ESC to view the service status they all start successfully and the last message says "[OK] Reached target Multi-User". The console is on virtual-terminal 7 and I can get to login prompts by using ALT+F[1-6], these system running in vmware, however given these machines have no X and boot to runlevel3 one expects them to be on virtual-terminal-1. If I add plymouth.enable=0 to the kernel command line the system will boot to a login prompt. 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 4

[Bug 762404] New: Without an nvidia module for a new kernel, plymouth doesn't allow a tty prompt
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=762404 https://bugzilla.novell.com/show_bug.cgi?id=762404#c0 Summary: Without an nvidia module for a new kernel, plymouth doesn't allow a tty prompt Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sboyce(a)blueyonder.co.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 Build and install a kernel using grub2. On reboot plymouth progress bar eventually stops and there is no way to get a tty login prompt using CTRL-ALT-F1 or Escape. ssh login from another box works so that the nvidia kernel module can be built or the proprietary nvidia install can take place. CTRL-ALT-DEL works or reboot via ssh after building the module and it boots to a KDE login screen and CTRL-ALT-F1 also works. Reproducible: Always Steps to Reproduce: 1. See Details above. 2. 3. Actual Results: See Details above. Expected Results: There should be a way to get a tty login prompt so that the nvidia module can be built for the new kernel. -- 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

[Bug 886907] New: chromium crash with SIGABRT
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=886907 https://bugzilla.novell.com/show_bug.cgi?id=886907#c0 Summary: chromium crash with SIGABRT Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)ifyouwantblood.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 chromium crash. Reproducible: Always Steps to Reproduce: 1. go to SSL! https://github.com/seveas/chanserv.py 2. right click on the link http://github.com/seveas/chanserv.py 3. save as Actual Results: from gdb SIGABRT [28972:28998:0711/015238:FATAL:url_request.cc(720)] Trying to send secure referrer for insecure load Expected Results: no crash. this is a tumbleweed install. Information for package chromium: --------------------------------- Repository: openSUSE Current updates Name: chromium Version: 35.0.1916.114-37.4 Arch: x86_64 Vendor: openSUSE Installed: Yes Status: up-to-date Installed Size: 143.6 MiB -- 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 882063] New: encoding issues with SLED12 repository metadata
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=882063 https://bugzilla.novell.com/show_bug.cgi?id=882063#c0 Summary: encoding issues with SLED12 repository metadata Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: General AssignedTo: adrian(a)suse.com ReportedBy: bgeuken(a)suse.com QAContact: adrian(a)suse.com CC: jmassaguerpla(a)suse.com Found By: --- Blocker: --- As Jordi figured out there seems to be a difference between 13.1 and SLED12 metadata files, and other repo sources might be affected as well. While 13.1 files are encoded as utf-8, the newer SLED12 files are ISO-8859-1. You can check this by unpacking those 2 files, doing a binary read on both and grep for Adobe Reader: http://download.opensuse.org/source/distribution/13.1/repo/non-oss/suse/set… http://dist.suse.de/install/SLP/SLE-12-Desktop-LATEST/x86_64/DVD1/suse/setu… File.binread("packages.en.131")[/cluding Adobe Rea.*Adobe Reader/] => "cluding Adobe Reader\xC2\xAE (\xE2\x80\x9CAdobe Reader" File.binread("packages.en.sle12")[/cluding Adobe Rea.*Adobe Reader/] => "cluding Adobe Reader\xAE (\"Adobe Reader" This causes the Studio downloader backend to break. -- 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 883260] New: Update of aaa_base removes permissions to /dev/null
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=883260 https://bugzilla.novell.com/show_bug.cgi?id=883260#c0 Summary: Update of aaa_base removes permissions to /dev/null Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jw(a)raven.inka.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 Because of security considerations, I have set umask to 022 and symlinked /root/.bash_history to /dev/null. With this settings, an update of aaa_base sets /dev/null to mode 0600 in its postinstall script. This is a long-standing issue, originally dicussed at http://lists.opensuse.org/opensuse/2009-03/msg00515.html and http://lists.opensuse.org/opensuse/2014-06/msg00748.html. The offending piece of code has been identified in http://lists.opensuse.org/opensuse/2014-06/msg00755.html and http://lists.opensuse.org/opensuse/2014-06/msg00761.html shows that the issue should have been fixed, but the fix addresses only the touch, not the chmod/chown. Reproducible: Always Steps to Reproduce: As root, execute: # umask 077; ln -sf /dev/null /root/.bash_hostory; zypper install -f aaa_base Actual Results: /dev/null is set to mode 0600, breaking all kinds of scripts Expected Results: Don't mess around with /dev/null -- 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 859105] New: server:monitoring/nagios-plugins: Bug: Update Upstream URL to https://www.monitoring-plugins.org
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c0 Summary: server:monitoring/nagios-plugins: Bug: Update Upstream URL to https://www.monitoring-plugins.org Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: schneemann(a)b1-systems.de ReportedBy: michael.friedrich(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: nix(a)opensuse.org Found By: --- Blocker: --- The nagios-plugins.org website has been compromised and the Nagios Plugins Development Team was required to move to a new host at https://www.monitoring-plugins.org whilst renaming their project to Monitoring Plugins. Full the story here: https://www.monitoring-plugins.org/archive/help/2014-January/006503.html I do not suggest to rename the package unless there's the requirement to do so, but update the project url and any (internal) references to source urls in order to stay safe. Kind regards, Michael -- 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

[Bug 888698] New: X11:Bumblebee/nvidia-bumblebee: Bug
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=888698 https://bugzilla.novell.com/show_bug.cgi?id=888698#c0 Summary: X11:Bumblebee/nvidia-bumblebee: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: opensuse-communityscreening(a)forge.provo.novell.com ReportedBy: geneing(a)myrealbox.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- nvidia-bumblebee package doesn't build nvidia_uvm.ko module for driver version 340.24. This module is needed for cuda libraries. -- 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