August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 886512] New: After installing bind9 (named) no menue entry for service manager (YaST) to activate named at boot
by bugzilla_noreply＠novell.com 27 Aug '14

27 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c0 Summary: After installing bind9 (named) no menue entry for service manager (YaST) to activate named at boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hfischer(a)eschkitai.de 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 After installing bind9/named there is no menue entry in service manager/YaST to get named starting at system boot. Trying 'systemctl enable [TAB,TAB] does not list a named.service oder a bind.service. Trying 'systemctl enable named.service' I got following message: named.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig named on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). But: Now named is listed in YaST's service manager. Named can be started using the service manager. This setting remains a reboot. Looking at /etc/init.d there was listed an initscript for named. I think, starting named uses the old way over the initd way. It would be very fine, to get an service script for systemd and an entry for the service manager/YaST to enable the service. It was a lucky idea to try 'systemctl enable named.service'. But this can't be a regular solution. Reproducible: Always Steps to Reproduce: 1. Installing bind9/named with the software manager/YaST 2. Try to start/enable named for starting at boot with service manager => no named or bind 3. And now? User/admin can try /etc/init.d/named start and have to search a method for starting the named service at systemboot. (I think, an experience admin look for chkconfig, but using the systemd way is better). Expected Results: After installing bind9/named there should appear the service in the list of YaST's service manager to activate/deactivate and start/stop the service. -- 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 891177] New: ocamlopt, the native code generator of ocaml, is broken in the distribution package.
by bugzilla_noreply＠novell.com 27 Aug '14

27 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=891177 https://bugzilla.novell.com/show_bug.cgi?id=891177#c0 Summary: ocamlopt, the native code generator of ocaml, is broken in the distribution package. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: IA64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dukebright(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2 (.NET CLR 3.5.30729) The openSuSE package ocaml 4.01.0-59.1 has the bug. This package has probably had it for many years. I believe I saw the same bug about 4 years ago, but didn't pursue it. The details are in https://forums.opensuse.org/showthread.php/500178-In-the-13-1-ocaml-package… I suspect there are not many users of ocamlopt in openSuSE, but the MediaWiki Math extension uses it, which is where I encountered the problem. Reproducible: Always Steps to Reproduce: 1. Create the file hw.ml: let () = print_endline "Hello, world!" 2. Execute duke@ee:~/Documents> ocamlopt hw.ml -o hw 3. This is verbatim from http://roscidus.com/blog/blog/2014/07/28/my-first-unikernel/#a-hello-world-… Actual Results: sh: as: command not found File "hw.ml", line 1: Error: Assembler error, input left in file /tmp/camlasmd7b8ce.s I'm reasonably sure the "as" not found is the (or an) assembler in openSuSE. Expected Results: After executing: duke@ee:~/Documents> ./hw Expect: Hello, world! I am told that Ubuntu doesn't have this problem. I'd rather fight than 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 8

[Bug 819517] New: Impossible to change bootloader location using YaST2
by bugzilla_noreply＠novell.com 27 Aug '14

27 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=819517 https://bugzilla.novell.com/show_bug.cgi?id=819517#c0 Summary: Impossible to change bootloader location using YaST2 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: arvidjaar(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 This explains problems several users had - they were unable to change bootloader location whatever they tried. YaST2 *ALWAYS* calls pbl with avoid_init == true: src/routines/lib_iface.ycp: /** * Update the bootloader settings, make updated saved settings active * @return boolean true on success */ global boolean UpdateBootloader () { y2milestone ("Updating bootloader configuration"); boolean ret = System::Bootloader_API::updateBootloader (true); This makes it impossible to actually change bootloader location via yast. But all files (including grub_installdevice) *are* updated making impression everything worked. Making it near to impossible to diagnose problem afterwords (especially when communicating with non-technical users). YaST2 *MUST* call pbl to re-install bootloader if boot location changed. 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 893502] New: gdm does not start
by bugzilla_noreply＠novell.com 27 Aug '14

27 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893502 https://bugzilla.novell.com/show_bug.cgi?id=893502#c0 Summary: gdm does not start Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: meissner(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- gdm no longer starts. -- 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 890098] New: Script /lib/mkinitrd/setup/91-amd_microcode.sh failed
by bugzilla_noreply＠novell.com 26 Aug '14

26 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=890098 https://bugzilla.novell.com/show_bug.cgi?id=890098#c0 Summary: Script /lib/mkinitrd/setup/91-amd_microcode.sh failed Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: antons(a)svedkijs.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=600814) --> (http://bugzilla.novell.com/attachment.cgi?id=600814) Screenshot of the error message User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 Installation fails on the system configuration step and do not boot afterwords. Hardware setup: CPU: AMD Athlon 5350 Mainboard: ASRock AM1B-ITX RAM: 4GB HDDs in software RAID1 Reproducible: Always Steps to Reproduce: 1. Start the default or minimalistic (server) installation 2. Bind online repositories before installation begins 3. Install system Actual Results: Installation fails ongenerating initrd (see attachment) -- 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 893623] New: Bluedevil crashes KDE when trying to pair apple mouse
by bugzilla_noreply＠novell.com 26 Aug '14

26 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893623 https://bugzilla.novell.com/show_bug.cgi?id=893623#c0 Summary: Bluedevil crashes KDE when trying to pair apple mouse Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: jamesrome(a)alum.mit.edu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=603718) --> (http://bugzilla.novell.com/attachment.cgi?id=603718) screen shot User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2114.2 Safari/537.36 OPR/25.0.1597.0 (Edition developer) The mouse is discovered. It fails to connect with org.freedesktop.Dbus.error.NoReply when I try to connect to my Apple mouse model A1197 I also cannot pair the Apple Magic Trackpad, but it does not crash anything. Reproducible: Always Steps to Reproduce: 1. Start bluetoothctl 2. Get the Mac address for the mouse 3. Make sure the mouse is flashing 4. do "connect Mac_address" 5. Fails to connect and crashes desktop. Actual Results: crashes KDE and Bluedevil Expected Results: should connect to mouse or trackpad -- 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 893274] New: yast2 sw_single crashed after reading repos
by bugzilla_noreply＠novell.com 26 Aug '14

26 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893274 https://bugzilla.novell.com/show_bug.cgi?id=893274#c0 Summary: yast2 sw_single crashed after reading repos Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: a.nolting(a)almano.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.13.80 Safari/537.21 Start yast2 select Software Management Repo Updates are read and when finished Software Management ends Reproducible: Always Steps to Reproduce: Start yast2 select Software Management Repo Updates are read and when finished Software Management ends Actual Results: Start yast2 select Software Management Repo Updates are read and when finished Software Management ends Expected Results: Software Management come up with UI -- 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 893603] New: crash when i am browsing gmail
by bugzilla_noreply＠novell.com 26 Aug '14

26 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893603 https://bugzilla.novell.com/show_bug.cgi?id=893603#c0 Summary: crash when i am browsing gmail Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: denis(a)newplan.ug QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 Signature @0xaea568c3 More Reports Search UUID 4eea8e5b-74e1-4ab5-821c-cb3702140825 Date Processed 2014-08-25 11:45:25.463292 Process Type plugin Shockwave Flash Version:11.2.202.400 Filename:libflashplayer.so Uptime 8117 Install Age 2299662 since version was first installed. Install Time 2014-07-29 20:58:02 Product Firefox Version 31.0 Build ID 2014072000 Release Channel release OS Linux OS Version 0.0.0 Linux 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) i686 Build Architecture x86 Build Architecture Info GenuineIntel family 6 model 23 stepping 10 | 2 Crash Reason SIGSEGV Crash Address 0x82 User Comments App Notes OpenGL: Intel Open Source Technology Center -- Mesa DRI Mobile Intel® GM45 Express Chipset x86/MMX/SSE2 -- 2.1 Mesa 9.2.3 -- texture_from_pixmap Processor Notes sp-processor01_phx1_mozilla_com.28425:2012; HybridCrashProcessor; non-integer value of "SecondsSinceLastCrash"; CSignatureTool: No proper signature could be created because no good data for the crashing thread (0) was found EMCheckCompatibility True Winsock LSP Adapter Vendor ID Adapter Device ID Reproducible: Always Steps to Reproduce: 1.open mozilla 2.while logging on to gmail, it crashes 3. Actual Results: keeps crashing -- 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 893057] dnsmasq is not correctly built with security features (PIE, relro, stackprotector, FORTIFY)
by bugzilla_noreply＠novell.com 26 Aug '14

26 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893057 https://bugzilla.novell.com/show_bug.cgi?id=893057#c5 --- Comment #5 from Bernhard Wiedemann <bwiedemann(a)suse.com> 2014-08-26 16:00:26 CEST --- This is an autogenerated message for OBS integration: This bug (893057) was mentioned in https://build.opensuse.org/request/show/246516 Factory / dnsmasq -- 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 843083] New: Comments in package "permissions" still refer to SuSEconfig
by bugzilla_noreply＠novell.com 26 Aug '14

26 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=843083 https://bugzilla.novell.com/show_bug.cgi?id=843083#c0 Summary: Comments in package "permissions" still refer to SuSEconfig Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bjoernv(a)arcor.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 SeaMonkey/2.21 The configuration files /etc/permissions and /etc/permissions.local from package "permissions" (seen in permissions-2013.08.22.1339-3.3.x86_64.rpm) still refer to the old (and now missing) program SuSEconfig: # This file is used by SuSEconfig and chkstat to check or set the modes # and ownerships of files and directories in the installation. Instructions itself are correct: # To change an entry copy the line to permissions.local, modify it # to suit your needs and call "chkstat --system" 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