July 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 630434] New: Server refuses to boot, while used iSCSI based non "/" file system is not available.
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c0 Summary: Server refuses to boot, while used iSCSI based non "/" file system is not available. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: DOlsson(a)WEB.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 On our SLES 11 GM based "mirror" server (running as a virtual XEN guest), we are using iSCSI to attach to our NAS holding the "/data" file system, whereas all other file systems (/, /boot, /var, /home) are placed on local disk. When rebooting the server, it refuses to boot correctly, while it is not able to "fsck" the "/data" file system -- The system stops in "(repair filesystem) #" mode (after having entered the "root" password). Using the "nofail" option for the "/data" file system helps to get the system to reboot correctly, but in this case the "/data" file system is neither being checked nor mounted during the system startup, which therefore -- once again -- makes the system unusable! Using the "nofail" option is part of the "solution" listed in the SLES 11 SP1 documentation, but since the system is unusable, this is *not* the solution to the problem. The problem is that the "mkinitrd" is and the boot scripts are not capable of handling iSCSI attached file systems correctly. The correct way of handling iSCSI attached devices are: - All iSCSI devices having the "onboot" set as node startup setting must be attached during the "initrd" boot sequence (i.e. by "boot.open-iscsi") -- and this *independent* of whether the "/" (root) file system is attached via iSCSI or not, - All iSCSI devices having the "automatic" set as node startup setting need to be attached during the normal booting sequence (i.e. by "open-iscsi"), - All iSCSI devices having the "manual" set as node startup setting should be left alone. Using such a attaching schema will ensure that a server is capable of being booted with all its iSCSI file systems being attached, checked and mounted. Reproducible: Always Steps to Reproduce: 1a. Setup an iSCSI device and mount it e.g. as "/home" (no changes to "/etc/fstab"). 2a. Reboot the system 3a. System fails to boot, while "/home" is not available. 1b. Setup an iSCSI device and mount it e.g. as "/home", and add the "nofail" option in "/etc/fstab" to the "/home" mount point. 2b. Reboot system. 3b. System boots, but "/home" is neither checked nor mounted! Actual Results: When using iSCSI devices for non root file systems - the system is not able to boot, when the file system on the iSCSI device is listed in "/etc/fstab" as a file system that should be mounted or - the system boots boots, when the file system on the iSCSI device has been marked with "nofail" in "/etc/fstab", but the file is neither being checked nor it is being mounted. Expected Results: System boots with all file systems listed in "/etc/fstab" being checked and mounted independently of whether they are on local or iSCSI attached disks. -- 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 91

[Bug 637791] New: libzypp log: wrong error message if gpg not installed
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637791 https://bugzilla.novell.com/show_bug.cgi?id=637791#c0 Summary: libzypp log: wrong error message if gpg not installed Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: dheidler(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- the error message tells you, that the files in the repository are not existing, but the real issue is, that gpg is not installed we should check for gpg installed and greate a more expressive message -- 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 702825] New: IcedTeaPlugin.so gives undefined symbol, plugin_debug, when icedtea-web is installed
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=702825 https://bugzilla.novell.com/show_bug.cgi?id=702825#c0 Summary: IcedTeaPlugin.so gives undefined symbol, plugin_debug, when icedtea-web is installed Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: falolaf(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 After the security update of java-1_6_0-openjdk the icedtea plugin in firefox isn't working. The following is outputed when trying to load an applet: LoadPlugin: failed to initialize shared library /usr/lib64/IcedTeaPlugin.so [/usr/lib64/IcedTeaPlugin.so: undefined symbol: plugin_debug] Installed packages: icedtea-web-1.1-0.2.1 java-1_6_0-openjdk-1.6.0.0_b22.1.10.2-4.3.1 java-1_6_0-openjdk-devel-1.6.0.0_b22.1.10.2-4.3.1 Downgrading to previous version and installation of java-1_6_0-openjdk-plugin and it's working again. Reproducible: Always Steps to Reproduce: See details. Actual Results: See details. Expected Results: See details. -- 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 549849] New: Eclipse doesn't accept mouse clicks on buttons
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=549849 Summary: Eclipse doesn't accept mouse clicks on buttons Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: davor.cengija(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.2 Firefox/3.5.3 As described on Beta and Pre-release forum, http://forums.opensuse.org/pre-release-beta/424021-eclipse-doesnt-accept-mo… I just downloaded the newest Eclipse, just to be sure, but I had the same problem with some older version. Start Eclipse, and for example try to create a new project. Enter the project's name and click Next. The button recognizes that it's being clicked (e.g. gets focus, changes color etc) but nothing happens. Pressing enter works (as the button has focus now). The same thing happens on the next screen with the Finish button. Reproducible: Always Steps to Reproduce: 1. Start Eclipse 2. Click File>New>Java Project 3. Enter project's name, click Next - nothing happens 4. Press Enter button - wizard advances to next step, as expected It seems that this problems is easiliy reproducible, and is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=288909 However, it is quite serios, almost a showstopper for a number of users. If you need additional details, don't hesitate to ask, I'm more than willing to assist here. -- 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 637382] New: (r)quotad init missing /etc/sysconfig/quotad for setting of "-p (port)", etc.
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637382 https://bugzilla.novell.com/show_bug.cgi?id=637382#c0 Summary: (r)quotad init missing /etc/sysconfig/quotad for setting of "-p (port)", etc. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pgngw+dev001+novell.com(a)f-m.fm QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 goal is to set *static* ports for nfs services. refs: http://www.lowth.com/LinWiz/nfs_help.html http://www.novell.com/support/viewContent.do?externalId=7000524&sliceId=1 http://wiki.debian.org/SecuringNFS whereas MOUNTD & STATSD opts can be set/overridden in /etc/sysconfig/nfs, QUOTAD is missing the same option. cat /etc/init.d/quotad ... # /etc/init.d/quotad # # and its symbolic link # # /sbin/rcquotad ... rpm -q --whatprovides /etc/init.d/quotad quota-nfs-3.17-7.2.x86_64 ls -al /etc/sysconfig/*quota* /bin/ls: No match. @ http://www.novell.com/support/viewContent.do?externalId=7000524&sliceId=1 "... /etc/services .. * rquota, : add the port assignment to the file. For example: rquotad 4003/tcp rquotad 4003/udp .. Please note that custom edits of the /etc/init.d/nfsserver are not recommend, nor is it supported. Further, changed /etc/init.d scripts may be replaced during online updates or when updating to a new service pack. " iiuc, /etc/services is NOT guaranteed safe from upgrades/overwrites. I tried to raise the issue in #opensuse-factory, as it's likely an issue in/for 11.4 as well. Told 'not interested' ... Checked @ #opensuse, told that the port mods should be made in /etc/sysconfig/foo, ----------------------------- [12:21] <dev001> since there are some 'packagers' around -- where can I find Packaging Guidelines for if/when to use /etc/sysconfig/blah + /etc/init.d/blah pairs? reading here, http://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros, I see mention -- but not guideline statement/policy. [12:21] <yaloki> dev001: there is no need for a guideline [12:22] <yaloki> dev001: you need /etc/init.d/foo to have a script to start a daemon [12:22] <yaloki> dev001: if you can make it configurable (e.g. port number or such), then you store that configuration in /etc/sysconfig/foo and use those parameters in the init script [12:23] <dev001> yaloki: sure, that makes sense. and that's what I thought. but, it's not what novell does/recommends -- in at least the one case i'm looking at. [12:24] <yaloki> dev001: I'm packaging for SUSE/openSUSE since 10 years, so take my word for it [12:24] <yaloki> dev001: and that's also the convention [12:24] <dev001> yaloki: I'm not disagreeing with you. i'm telling you , however, what Novell does in the case of quotad. they recommend making static port assignments by mod'ing /etc/services. [12:25] <yaloki> dev001: well maybe that's because quotad is not configurable in a different way [12:25] <yaloki> dev001: many daemons look up which port they should listen on in /etc/services [12:25] <yaloki> dev001: (actually it's even a system call in glibc) [12:26] <dev001> yaloki: it most certainly is. adding a "-p port" spec is straightforward, and frequently/widely used. [12:26] <yaloki> dev001: well then the packager simply forgot to do that [12:26] <yaloki> dev001: file a bug ----------------------------- checking man page, man rquotad ------------------------- RQUOTAD(8) NAME rquotad, rpc.rquotad - remote quota server SYNOPSIS rpc.rquotad [ -sSFI ] [ -p port ] .. OPTIONS .. -p port, --port port Listen on alternate port port. .. ------------------------- 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 42

[Bug 637235] New: kernel:huh, entered softirq 3 NET_RX ffffffff813d1a10 preempt_count 00000102, exited with 00000103?
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637235 https://bugzilla.novell.com/show_bug.cgi?id=637235#c0 Summary: kernel:huh, entered softirq 3 NET_RX ffffffff813d1a10 preempt_count 00000102, exited with 00000103? Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: crrodriguez(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: No Using Kernel:HEAD http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/ I get this message repeteadly, machine takes ages to boot or simple freezes. "kernel: [ 1295.239519] huh, entered softirq 3 NET_RX ffffffff813d1a10 preempt_count 00000102, exited with 00000103?" all accompanied with this crash: <6>[ 8.068993] PCI: Discovered peer bus ff <1>[ 8.070635] BUG: unable to handle kernel NULL pointer dereference at 00000000000001a4 <1>[ 8.070860] IP: [<ffffffffa01cee78>] edac_create_mci_instance_attributes+0xe8/0x1a0 [edac_core] <4>[ 8.071055] PGD 13e7d3067 PUD 13c840067 PMD 0 <0>[ 8.071251] Oops: 0000 [#1] PREEMPT SMP <0>[ 8.071445] last sysfs file: /sys/devices/pci0000:ff/0000:ff:06.0/class <4>[ 8.071548] CPU 1 <4>[ 8.071585] Modules linked in: i7core_edac(+) kvm snd_page_alloc r8169 wmi iTCO_wdt sg i2c_i801 usb_storage edac_core cfg80211 pcspkr button serio_raw rfkill iTCO_vendor_support ext4 jbd2 crc16 ata_generic sd_mod pata_jmicron ahci libahci libata scsi_mod fan thermal processor thermal_sys <4>[ 8.072974] <4>[ 8.073067] Pid: 548, comm: modprobe Not tainted 2.6.36-rc3-10-desktop #1 0X501H/Studio XPS 435T/9000 <4>[ 8.073227] RIP: 0010:[<ffffffffa01cee78>] [<ffffffffa01cee78>] edac_create_mci_instance_attributes+0xe8/0x1a0 [edac_core] <4>[ 8.073429] RSP: 0018:ffff88013c8c7b98 EFLAGS: 00010282 <4>[ 8.073527] RAX: 00000000000001a4 RBX: ffffffffa0109eb8 RCX: 0000000000000000 <4>[ 8.073629] RDX: ffff88013e23c0f0 RSI: ffffffffa01d43c0 RDI: ffff88013f3c5450 <4>[ 8.073732] RBP: ffff88013f3c5440 R08: 0000000000000000 R09: ffff88013f3c5440 <4>[ 8.073835] R10: ffff88013fc8a450 R11: 0000000000000000 R12: ffff88013b9e5850 <4>[ 8.073937] R13: ffff88013e23c000 R14: ffff88013f3c5450 R15: ffff88013e23c130 <4>[ 8.074040] FS: 00007f3eaa833700(0000) GS:ffff880001e20000(0000) knlGS:0000000000000000 <4>[ 8.074197] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <4>[ 8.074295] CR2: 00000000000001a4 CR3: 000000013e7d6000 CR4: 00000000000006e0 <4>[ 8.074398] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <4>[ 8.074503] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 <4>[ 8.074607] Process modprobe (pid: 548, threadinfo ffff88013c8c6000, task ffff88013c34e6c0) <0>[ 8.074765] Stack: <4>[ 8.074856] ffff88013c8c7ba8 0000000000000000 ffff88013e23c0f0 ffff88013c8c7fd8 <4>[ 8.075056] <0> ffff88013c0f0460 ffffffffa0109dc8 ffff88013b9e5840 ffff88013e23c0f0 <4>[ 8.075371] <0> ffff88013e23c000 ffff88013b9e5850 ffff88013e23c130 ffffffffa01cee99 <0>[ 8.075778] Call Trace: <4>[ 8.075881] [<ffffffffa01cee99>] edac_create_mci_instance_attributes+0x109/0x1a0 [edac_core] <4>[ 8.076039] [<ffffffffa01cf7b4>] edac_create_sysfs_mci_device+0x64/0x150 [edac_core] <4>[ 8.076197] [<ffffffffa01cdbf6>] edac_mc_add_mc+0x36/0xe0 [edac_core] <4>[ 8.076296] [<ffffffffa0108144>] i7core_register_mci+0x104/0x210 [i7core_edac] <4>[ 8.076450] [<ffffffffa01087c3>] i7core_probe+0x10e/0x185 [i7core_edac] <4>[ 8.076552] [<ffffffff81277515>] local_pci_probe+0x55/0xd0 <4>[ 8.076649] [<ffffffff812786e2>] pci_device_probe+0x132/0x140 <4>[ 8.076747] [<ffffffff81320bb0>] really_probe+0x70/0x260 <4>[ 8.076844] [<ffffffff81320fa7>] driver_probe_device+0x47/0xb0 <4>[ 8.076941] [<ffffffff813210a3>] __driver_attach+0x93/0xa0 <4>[ 8.077036] [<ffffffff8131faee>] bus_for_each_dev+0x4e/0x80 <4>[ 8.077132] [<ffffffff813204f0>] bus_add_driver+0x160/0x330 <4>[ 8.077228] [<ffffffff813212fa>] driver_register+0x6a/0x130 <4>[ 8.077325] [<ffffffff8127895c>] __pci_register_driver+0x4c/0xc0 <4>[ 8.077422] [<ffffffffa010f086>] i7core_init+0x86/0xa8 [i7core_edac] <4>[ 8.077523] [<ffffffff810002da>] do_one_initcall+0x3a/0x170 <4>[ 8.077621] [<ffffffff8109396a>] sys_init_module+0xba/0x210 <4>[ 8.077717] [<ffffffff8100303b>] system_call_fastpath+0x16/0x1b <4>[ 8.077815] [<00007f3eaa19aeda>] 0x7f3eaa19aeda <0>[ 8.077907] Code: 10 4c 89 7d 00 48 8b 54 24 10 48 c7 c6 c0 43 1d a0 4c 89 f7 48 89 45 08 48 89 28 48 8b 43 10 4c 89 6d 58 48 89 45 50 48 8b 43 10 <48> 8b 08 31 c0 e8 4e 8b 08 e1 85 c0 75 22 48 8b 45 50 4c 89 f2 <1>[ 8.080114] RIP [<ffffffffa01cee78>] edac_create_mci_instance_attributes+0xe8/0x1a0 [edac_core] <4>[ 8.080299] RSP <ffff88013c8c7b98> <0>[ 8.080389] CR2: 00000000000001a4 <4>[ 8.080484] ---[ end trace e37de668754c1f33 ]--- went back to stable kernel, but if you need more info, I might try to get it. -- 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 637201] New: YaST Package Manager: window saying ''Starting Package Manager'' when closing YaST
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637201 https://bugzilla.novell.com/show_bug.cgi?id=637201#c0 Summary: YaST Package Manager: window saying ''Starting Package Manager'' when closing YaST Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marcos(a)meebee.ven.bz QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.9.0.15) Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15 Versions: openSUSE 11.3 KDE 4.4.4 YaST Packager 2.19.7-1.5 Libzypp 7.7.5-7.2 ================================================================================= Problem: I opened YaST for removing some packages, but then I decided to close it. There were some conflicts so I passed. When closing, a window stating ''Starting Package Manager'' appears. I don't know the exact sentence (my openSUSE 11.3 is in Spanish). After 1 or 2 seconds, it disappears. I know this isn't very annoying, but, why don't YaST close quickly without ''Starting Package Manager''? Thanks! Reproducible: Always Steps to Reproduce: 1. Open YaST package manager 2. Close it by clicking X in the title bar. Actual Results: The ''Starting Package Manager'' window Expected Results: No window, just YaST closed 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 637187] New: rpmlint/post-build-checks: %run_ldconfig gives incomplete warning message
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637187 https://bugzilla.novell.com/show_bug.cgi?id=637187#c0 Summary: rpmlint/post-build-checks: %run_ldconfig gives incomplete warning message Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- aufs.src:98: W: deprecated-use-of-%run_ldconfig aufs.src:104: W: deprecated-use-of-%run_ldconfig According to the new SUSE Packaging Conventions, the use of %run_ldconfig is deprecated. use %post(un) -p /sbin/ldconfig instead. But my %post section reads %post [ -x /sbin/mkinitrd_setup ] && /sbin/mkinitrd_setup %run_ldconfig So doing %post -p is not a good idea, because ldconfig cannot run mkinitrd_setup. -- 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 637183] New: /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637183 https://bugzilla.novell.com/show_bug.cgi?id=637183#c0 Summary: /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin(a)oneiros.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=387614) --> (http://bugzilla.novell.com/attachment.cgi?id=387614) boot.msg User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 At bootup I get these messages: ------------------ <notice -- Sep 4 15:27:57.953566000> service earlyxdm doneStarting service kdmdone Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 lo done eth0 device: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02) eth0 is controlled by ifplugd eth0 waiting wlan0 device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) wlan0 is controlled by ifplugd wlan0 waiting eth0 device: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02) eth0 ifplugd is running eth0 no cable connected eth0 . . . is just beeing set up eth0 done wlan0 device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) wlan0 ifplugd is running /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument wlan0 no cable connected wlan0 . . . is just beeing set up wlan0 is down wlan0 ------------------ dmesg etc. are attached. The wlan is disabled via kill switch. 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 23

[Bug 637069] New: gdm: Unable to Connect with XDMCP (thin clients)
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637069 https://bugzilla.novell.com/show_bug.cgi?id=637069#c0 Summary: gdm: Unable to Connect with XDMCP (thin clients) Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: drichard(a)largo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 gdm was broken and did not allow XDMCP connections in 11.3 Halfline cooked a patch and I was able to get it to merge and compile and it indeed is now working. I'm uploading the two patches along with the updated gdm.spec file. They are listed as Patch98 and Patch99 in the spec. 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 14