July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 801374] New: DCHP Not Automatically Selected During Network Configuration
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=801374 https://bugzilla.novell.com/show_bug.cgi?id=801374#c0 Summary: DCHP Not Automatically Selected During Network Configuration Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: PC OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: malv_star(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20100101 Firefox/16.0 During installation, the network cable was plugged into the system, and appeared to be functioning correctly. However, when the network configuration page was displayed, the NIC was shown as "Not Configured" instead of the correct default for a plugged-in and active ethernet cable, which should be "DHCP". However, when clicking on the button to "Disable IPv6", suddenly the NIC was shown as being configured with DHCP. Reproducible: Always Steps to Reproduce: 1. Insert active network cable and begin install 2. Get to network configuration screen Actual Results: NIC is shown as "Not Configured" Expected Results: NIC is shown as being configured using DHCP. -- 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 498345] New: ld.so segfaults on /lib/modules/.../vdso.so
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=498345 Summary: ld.so segfaults on /lib/modules/.../vdso.so Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: pbaudis(a)novell.com ReportedBy: mmarek(a)novell.com QAContact: qa(a)suse.de Found By: --- During kernel build, something runs ldd on the vdso.so binary, which results in a segfault in ld.so. Can be reproduced in the live system too: $ ldd /lib/modules/2.6.27.21-0.1-default/vdso/vdso.so ldd: exited with unknown exit code (139) $ /lib64/ld-linux-x86-64.so.2 --verify /lib/modules/2.6.27.21-0.1-default/vdso/vdso.so Segmentation fault -- 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 549447] New: Able to ping, no DNS
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=549447 Summary: Able to ping, no DNS Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chusty(a)attglobal.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.1 Firefox/3.5.3 1. able to ping 2. firefox does not work 3. no repositories available. 4. resolve.conf is blank 5. if in firefox <about:config> and set network.dns.disableIPv6 to true then firefox work. Then I set it back to false as default. 6. Now yast/network devices/network setting/Hostname-DNS and I add the DNS from the router then all is back to normal. 7. resolve.conf ### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the 8. Remove the DNS from the Hostname-DNS field and firefox does not work and the resolve.conf files is blanc again. There is a similar problem under Bug 546213 but I think there are difference. I reported what looks like the same problem under opensuse 11.1 The solution there was perfect. Here are bug reported under 11.1 which I believe is the same. Bug 463015 - Able to ping unable to connect Bug 441947 - getaddrinfo() breaks when resolv.conf points at buggy nameservers Reproducible: Always Steps to Reproduce: 1.able to ping. firefox unable to connect 2.if I change to true <network.dns.disableIPv6> in firefox, it works. 3.If I add DNS servers to the network device everything work Under opensuse 11.1 the problem was resolved replacing glibc. -- 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 827523] New: System crashes when opening the settings in gnome 3 desktop environment
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=827523 https://bugzilla.novell.com/show_bug.cgi?id=827523#c0 Summary: System crashes when opening the settings in gnome 3 desktop environment Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: grundenjd(a)gmail.com 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/28.0.1500.63 Safari/537.36 I upgraded from 12.2 to 12.3 with a network install cd. The install went well except when I try to open the settings. The entire system will crash and I can not recover the system by any other means but to reboot. Reproducible: Always Steps to Reproduce: 1.applications 2.settings 3.system crsh Actual Results: don't open settings Expected Results: works well with no errors I cant provide a printout of the issue considering the entire system will lock up and is not recoverable unless rebooting -- 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 826457] New: dtc: v1.4.0 released upstream
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=826457 https://bugzilla.novell.com/show_bug.cgi?id=826457#c0 Summary: dtc: v1.4.0 released upstream Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: swarren(a)wwwdotorg.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 dtc v1.4.0 has been tagged/released at git://git.jdl.com/software/dtc.git. It'd be great if this could be packaged up, and back-ported into as distro versions as possible. This version brings a slew of new features, some of which: * Are already required for some *.dts files in the Linux kernel. * Will soon be required for the *.dts files in U-Boot. 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 716887] New: Minicom showing intermittent console output thro' /dev/ttyUSB0 port.
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=716887 https://bugzilla.novell.com/show_bug.cgi?id=716887#c0 Summary: Minicom showing intermittent console output thro' /dev/ttyUSB0 port. Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: vrnb05(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 Hi, I am using OpenSuse 11.4 distro on Intel's I7 processor and motherboard. It doesnot have onboard serial port, hence we are forced to use USB to Serial converter. There is no error codes that gets displayed on screen. I am connecting through /dev/ttyUSB0 using PL203 driver. When i connect this to my hardware's console, and then execute 'find /' from my hardware's terminal, i get intermittent output thrown on minicom. As and when do keypress or move a mouse pointer it throws up a screenful of output before it stops. Again i have to keep moving either mouse/do key presses on keyboard to get the console output from my hardware. I am unable to get contineous console output of my hardware(logs). On further experimatation, I have found that it doesnot look to be a minicom issue here. I tried using 'screen /dev/ttyUSB0 115200' and 'putty' (for linux) both are showing the same erratic behaviour mentioned above. My tty configuration as optained from stty is as below: root# stty -a -F /dev/ttyUSB0 speed 115200 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 5; -parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8 -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke root# uname -a Linux srinirao 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux Has anyone came across this issue ? Is there anything i am missing out here with either the ttyUSB0 or Kernel driver or configurations related to ttyUSB0 ? Should i upgrade/downgrade my drivers ?. PLEASE HELP Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: i get intermittent output thrown on minicom Expected Results: I am unable to get contineous console output of my hardware(logs) srinirao:~ # uname -a Linux srinirao 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux srinirao:~ # cat /etc/minirc.dfl # Machine-generated file - use "minicom -s" to change parameters. pu port /dev/ttyUSB0 pu baudrate 115200 pu minit pu mreset -- 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 828507] New: server:monitoring/icinga-web: Bug sql schemas out of date
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=828507 https://bugzilla.novell.com/show_bug.cgi?id=828507#c0 Summary: server:monitoring/icinga-web: Bug sql schemas out of date Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: lrupp(a)suse.com ReportedBy: l.bigonville(a)edpnet.be QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: nix(a)opensuse.org Found By: --- Blocker: --- Hi, All the .sql under the /usr/share/icinga-web/etc/schema/ directory seems to be outdated. For example the mysql one is at 1.8.3 and the sqlite at 1.7.1 These should be kept uptodate with the icinga-web release. Thanks -- 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 820858] New: There are many systemd error messages when starting sendmail
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=820858 https://bugzilla.novell.com/show_bug.cgi?id=820858#c0 Summary: There are many systemd error messages when starting sendmail Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: i586 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nrickert(a)ameritech.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=540234) --> (http://bugzilla.novell.com/attachment.cgi?id=540234) output of "dmesg | grep sendmail" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 A typical message: [ 21.427796] systemd[1]: [/usr/lib/systemd/system/sendmail-client.service:24] Invalid environment assignment, ignoring: SENDMAIL_CLIENT_ARGS=-L sendmail-client -Ac -qp30m [ 21.431376] systemd[1]: logged here: 'Invalid environment assignment, ignoring: SENDMAIL_CLIENT_ARGS=-L sendmail-client -Ac -qp30m': 1 I will attach the output from: dmesg | grep sendmail Reproducible: Always Steps to Reproduce: 1. 2. 3. Sendmail is running, in spite of the error messages. -- 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 828538] New: No desktop after logon with VNC when using lightdm or gdm as displaymanager
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=828538 https://bugzilla.novell.com/show_bug.cgi?id=828538#c0 Summary: No desktop after logon with VNC when using lightdm or gdm as displaymanager Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mgerlach(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=547151) --> (http://bugzilla.novell.com/attachment.cgi?id=547151) Screenshort of VNC viewer window after pressing Login User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 When using lightdm or gdm as windows manager it is not possible to log int via VNC service (Port 5901). The logon screen is shown but after entering username and password the desktop does not appear. When the user is already logged in locally the "Login" button is not present instead there is an "Unlock" button. This happens only with lightdm or gdm as displaymanager kdm and xdm are working. It also used to work on OpenSuse 12.1 Note: /etc/xinetd.d/vnc had to be modified as following: "-SecurityTypes none" has to be added to server_args to make vnc work at all. Reproducible: Always Steps to Reproduce: 1. Connect with VNC Viewer (e.g. TightVNC) to port 5901 2. Enter username and password. 3. Press Login. Actual Results: Desktop does not appear. Expected Results: Desktop should appear. -- 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 828244] New: After Upgrade of Linux Modules (July 2, 2013) System will not Boot
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=828244 https://bugzilla.novell.com/show_bug.cgi?id=828244#c0 Summary: After Upgrade of Linux Modules (July 2, 2013) System will not Boot Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i686 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: davidre_99(a)yahoo.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 Running an Intel i7 Processor with 16 GBytes of memory on the motherboard. Performed a normal upgrade of Linux patches on 2 July 2013. Following the reboot of the system I get the following error: Loading Linux 3.4.42-2.28-desktop Error: file '/boot/vmlinuz-3.4.42-2.28-desktop' not found Loading initial ramdisk ... error: you need to load the kernel first. I have to admit this is the first time I've had this occur following a normal update of patches. Reproducible: Always Steps to Reproduce: 1. Updated patches. 2. Get the same error message. 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 1