December 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 335521] New: After upgrade from 10. 2 my pam config gets screwed continuously
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=335521 Summary: After upgrade from 10.2 my pam config gets screwed continuously Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gleixner(a)bib-bvb.de QAContact: jsrain(a)novell.com Found By: Customer In 10.2. i had in my /etc/pam.d/common-auth: auth required pam_env.so auth sufficient pam_unix2.so auth sufficient pam_krb5.so use_first_pass auth required pam_deny.so After update the pam_krb5 entry vanished - as expected because i did not use yast to configure the kerberos client. With 10.3 i tried to use yast to configure the client, but it changed the file to: auth required pam_env.so auth sufficient pam_unix2.so auth required pam_krb5.so use_first_pass auth required pam_deny.so which does not work for me - i'm not sure why. I can login using a local user account but not via kerberos. With the older config this worked. -- 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 344236] New: Upgrade to 10.3 breaks pam configuration
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344236 Summary: Upgrade to 10.3 breaks pam configuration Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: R.Escher(a)osram.de QAContact: jsrain(a)novell.com Found By: Customer Created an attachment (id=184835) --> (https://bugzilla.novell.com/attachment.cgi?id=184835) pam.d dir before and after upgrade After upgrade installation of openSUSE 10.3 upon openSUSE 10.2 the login with kerberos didn't work any more. Kerberos (kinit) works. A trace of pam_krb5 shows: pam_krb5 works too. But the login itself fails. I copied /etc/pam.d into /etc/pam.d/after_upgrade and restored from the backup the original pam.d: now the login works. Both directories (before_upgrade with the ok-configuration of 10.2 and after_upgrade with the broken one of 10.3) are in attachment pam_d.tgz. -- 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 340985] New: bootloader writes /dev/sda2 into root in menu.lst
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=340985 Summary: bootloader writes /dev/sda2 into root in menu.lst Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wstephenson(a)novell.com QAContact: jsrain(a)novell.com Found By: --- I configured the root device as /dev/sda2. This was written into menu.lst literally as root=(/dev/sda2,1) - which Grub barfed on. -- 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 2

[Bug 342380] New: No Compiling posible
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=342380 Summary: No Compiling posible Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Mr_Tiger(a)gmx.net QAContact: qa(a)suse.de Found By: Customer When i try to recompile a kernel module make doesn't find the sources even they are installed. -- 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 2

[Bug 160823] /var/adm/mount: Device is busy
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=160823 Klaus Kämpf <kkaempf(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kkaempf(a)novell.com |jsrain(a)novell.com Status|REOPENED |NEW -- 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 160823] /var/adm/mount: Device is busy
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=160823#c15 Klaus Kämpf <kkaempf(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #15 from Klaus Kämpf <kkaempf(a)novell.com> 2007-12-03 08:53:54 MST --- Reopening as of last comment -- 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 345437] New: dumping core in /var/log/samba/cores/smbd
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=345437 Summary: dumping core in /var/log/samba/cores/smbd Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=185537) --> (https://bugzilla.novell.com/attachment.cgi?id=185537) samba log After today's security update, samba dumps core when a Siemens Gigaset M740 AV digital TV receiver (internally a linux 2.4 machine) tries to load a share in my opensuse 10.3 machine. This was working till today. These security patches were installed today: dmapi 2.2.8-22 cifs-mount 3.0.26a-3.3 libsmbclient 3.0.26a-3.3 samba-client 3.0.26a-3.3 samba 3.0.26a-3.3 I can't connect, and these messages start to fill the log by the hundred and I have to restart the server (and no, there is no core in that dir): Dec 2 00:33:04 nimrodel smbd[3686]: [2007/12/02 00:33:04, 0] lib/fault.c:dump_core(181) Dec 2 00:33:04 nimrodel smbd[3686]: dumping core in /var/log/samba/cores/smbd Dec 2 00:33:04 nimrodel smbd[3686]: Dec 2 00:33:04 nimrodel smbd[3687]: [2007/12/02 00:33:04, 0] lib/util.c:smb_panic(1632) Dec 2 00:33:04 nimrodel smbd[3687]: PANIC (pid 3687): push_ascii - dest_len == -1 Dec 2 00:33:04 nimrodel smbd[3687]: [2007/12/02 00:33:04, 0] lib/util.c:log_stack_trace(1736) Dec 2 00:33:04 nimrodel smbd[3687]: BACKTRACE: 14 stack frames: Dec 2 00:33:04 nimrodel smbd[3687]: #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8024ca7d] Dec 2 00:33:04 nimrodel smbd[3687]: #1 /usr/sbin/smbd(smb_panic+0x5d) [0x8024cbad] Dec 2 00:33:04 nimrodel smbd[3687]: #2 /usr/sbin/smbd [0x802351e4] Dec 2 00:33:04 nimrodel smbd[3687]: #3 /usr/sbin/smbd(push_string_fn+0x44) [0x80235234] Dec 2 00:33:04 nimrodel smbd[3687]: #4 /usr/sbin/smbd(srvstr_push_fn+0xa5) [0x800bfd65] Dec 2 00:33:04 nimrodel smbd[3687]: #5 /usr/sbin/smbd [0x800a5886] Dec 2 00:33:04 nimrodel smbd[3687]: #6 /usr/sbin/smbd [0x800b0424] Dec 2 00:33:04 nimrodel smbd[3687]: #7 /usr/sbin/smbd(handle_trans2+0x168) [0x800b16d8] Dec 2 00:33:04 nimrodel smbd[3687]: #8 /usr/sbin/smbd(reply_trans2+0x69c) [0x800b2a3c] Dec 2 00:33:04 nimrodel smbd[3687]: #9 /usr/sbin/smbd [0x800cfaee] Dec 2 00:33:04 nimrodel smbd[3687]: #10 /usr/sbin/smbd(smbd_process+0x4df) [0x800d085f] Dec 2 00:33:04 nimrodel smbd[3687]: #11 /usr/sbin/smbd(main+0xa18) [0x80323ea8] Dec 2 00:33:04 nimrodel smbd[3687]: #12 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7aa1fe0] Dec 2 00:33:04 nimrodel smbd[3687]: #13 /usr/sbin/smbd [0x800542a1] Dec 2 00:33:04 nimrodel smbd[3687]: [2007/12/02 00:33:04, 0] lib/fault.c:dump_core(181) -- 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 2

[Bug 160823] /var/adm/mount: Device is busy
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=160823#c14 --- Comment #14 from Steffen Winterfeldt <snwint(a)novell.com> 2007-12-03 08:44:05 MST --- I can only agree. We've had a similar issue in 10.3, when yast did not unmount the xfs partition and people ended up rebooting a corrupted file system. IMO yast needs to ensure it unmounts every fs it mounts. -- 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 344988] New: Cloning the system: AutoYaST reports wrong HD partition sizes
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344988 Summary: Cloning the system: AutoYaST reports wrong HD partition sizes Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: vmarsik(a)novell.com QAContact: qa(a)suse.de Found By: System Test Problem: ======== 1) When cloning the system using 'yast /usr/share/YaST2/clients/clone_system.ycp', the HD partition sizes are smaller than those that can be calculated from fdisk output. 2) When re-creating the partition schema from the file using AutoYaST, the partitions are made smaller than originally. The data from old partitions may not fit there. Probable reason: ================ Fdisk reports the partitions as pairs (start_cluster, end_cluster). The size equals to cluster_size * (end_cluster - start_cluster + 1) AutoYaST probably computes this as cluster_size * (end_cluster - start_cluster) As a result, the "cloned" partitions are all 1 cluster smaller. Details: ======== Column 2. is counted from fdisk output as (End-Start)+1 Column 3. is counted as (Column 2.) * cluster_size Column 5. is counted as (Column 4.) - (Column 3.) 1. 2. 3. 4. 5. part# fdisk/cyls fdisk/bytes AutoYaST/bytes difference sda1 130 1069286400 1061028352 8258048 sda2 974 8011422720 8003197440 8225280 sda3 974 8011422720 8003197440 8225280 sda4 22243 182954903040 sda5 974 8011422720 8003164672 8258048 sda6 974 8011422720 8003164672 8258048 cluster size : 8225280 bytes Some partitions might be a little smaller due to things like MBR or extended partition table. Fdisk before: ============= Command (m for help): p Disk /dev/sda: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00079b3e Device Boot Start End Blocks Id System /dev/sda1 1 130 1044193+ 82 Linux swap / Solaris /dev/sda2 * 131 1104 7823655 83 Linux /dev/sda3 1105 2078 7823655 83 Linux /dev/sda4 2079 24321 178666897+ 5 Extended /dev/sda5 2079 3052 7823623+ 83 Linux /dev/sda6 3053 4026 7823623+ 83 Linux Fdisk after: ============ Command (m for help): p Disk /dev/sda: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00079b3e Device Boot Start End Blocks Id System /dev/sda1 1 129 1036161 82 Linux swap / Solaris /dev/sda2 130 1102 7815622+ 83 Linux /dev/sda3 1103 2075 7815622+ 83 Linux /dev/sda4 2076 24321 178690995 f W95 Ext'd (LBA) /dev/sda5 2076 3048 7815591 83 Linux /dev/sda6 3049 4021 7815591 83 Linux /root/autoinst.xml: =================== .. <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <mountby config:type="symbol">id</mountby> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1061028352</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">id</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>8003197440</size> </partition> <partition> <create config:type="boolean">true</create> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>8003197440</size> </partition> <partition> <create config:type="boolean">true</create> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>8003197440</size> </partition> <partition> <create config:type="boolean">true</create> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>8003164672</size> </partition> </partitions> <use>all</use> </drive> .. -- 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 180390] Parallel port printing does not function with SLED 10 RC2
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=180390#c96 Thomas Renninger <trenn(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |duwe(a)novell.com AssignedTo|trenn(a)novell.com |jsmeix(a)novell.com Status|ASSIGNED |NEW --- Comment #96 from Thomas Renninger <trenn(a)novell.com> 2007-12-03 08:17:41 MST --- According to Torsten Duwe, we should disable DMA totally. Some already tried and AFAIK all who had problems here had a working parallel port with dma=none Parameter, right? Johannes, I am not sure how risky this is and whether it should be done in 10.3, maybe also SLE[SD]10-SP2. Maybe we should start with stable and let some people test first... The solution should be a line in /etc/modprobe.d/xy: options parport_pc dma=none Johannes, AFAIK you already added the comment, if two parallel ports are found, that parport_pc should get irq=none parameter, can you also add the dma=none uncommented, pls. Some testing whether it still works after reloading parport_pc driver would also be great. -- 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