July 2006 - openSUSE Users - openSUSE Mailing Lists

[SLE] Problem detecting parallel printer in latest update to SuSE 10.1?
by David Walker 26 Jul '06

26 Jul '06

Ever since I installed the latest updates to SuSE 10.1 (via zen-updater), my parallel printer is no longer detected. I get the following message in the log: "parport_pc: probe of 00:0a failed with error -22", along with a number of PNP-related kernel errors. Any ideas? I've included what I believe are the relevant records from /var/log/messages and zmd-messages.log* files. David Walker /var/log/messages ----------------- Jul 25 20:27:43 home kernel: setup_irq: irq handler mismatch Jul 25 20:27:43 home kernel: [<c0131baf>] setup_irq+0xd6/0xe9 Jul 25 20:27:43 home kernel: [<c01e17d5>] pnp_test_handler+0x0/0x6 Jul 25 20:27:43 home kernel: [<c0131c31>] request_irq+0x6f/0x8b Jul 25 20:27:43 home kernel: [<c01e1987>] pnp_check_irq+0xb2/0x126 Jul 25 20:27:43 home kernel: [<c01e2338>] pnp_assign_irq+0xd8/0xf3 Jul 25 20:27:43 home kernel: [<c01e25cd>] pnp_assign_resources+0x1c1/0x23f Jul 25 20:27:43 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:27:43 home kernel: [<c01e26aa>] pnp_auto_config_dev+0x5f/0x8d Jul 25 20:27:43 home kernel: [<c01e26f4>] pnp_activate_dev+0x1c/0x42 Jul 25 20:27:43 home kernel: [<c01e1702>] pnp_device_probe+0x3c/0x8e Jul 25 20:27:43 home kernel: [<c020064f>] driver_probe_device+0x3f/0x88 Jul 25 20:27:43 home kernel: [<c0200735>] __driver_attach+0x42/0x67 Jul 25 20:27:43 home kernel: [<c0200180>] bus_for_each_dev+0x39/0x5b Jul 25 20:27:43 home kernel: [<c02005bc>] driver_attach+0x11/0x13 Jul 25 20:27:43 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:27:43 home kernel: [<c01ffe91>] bus_add_driver+0x64/0xfa Jul 25 20:27:43 home kernel: [<c01ac5fa>] pci_get_subsys+0xa9/0xb0 Jul 25 20:27:43 home kernel: [<c01e15c8>] pnp_register_driver+0x1a/0x3f Jul 25 20:27:43 home kernel: [<e682e43b>] parport_pc_init+0x355/0x3ef [parport_pc] Jul 25 20:27:43 home kernel: [<c012afa4>] sys_init_module+0x12d6/0x1444 Jul 25 20:27:43 home kernel: [<c010299b>] sysenter_past_esp+0x54/0x79 Jul 25 20:27:43 home kernel: pnp: Device 00:0a activated. Jul 25 20:27:43 home kernel: pnp: Device 00:0a disabled. Jul 25 20:27:43 home kernel: parport_pc: probe of 00:0a failed with error -22 Jul 25 20:27:43 home kernel: setup_irq: irq handler mismatch Jul 25 20:27:43 home kernel: [<c0131baf>] setup_irq+0xd6/0xe9 Jul 25 20:27:43 home kernel: [<c01e17d5>] pnp_test_handler+0x0/0x6 Jul 25 20:27:43 home kernel: [<c0131c31>] request_irq+0x6f/0x8b Jul 25 20:27:43 home kernel: [<c01e1987>] pnp_check_irq+0xb2/0x126 Jul 25 20:27:43 home kernel: [<c01e2338>] pnp_assign_irq+0xd8/0xf3 Jul 25 20:27:43 home kernel: [<c01e25cd>] pnp_assign_resources+0x1c1/0x23f Jul 25 20:27:43 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:27:43 home kernel: [<c01e26aa>] pnp_auto_config_dev+0x5f/0x8d Jul 25 20:27:43 home kernel: [<c01e26f4>] pnp_activate_dev+0x1c/0x42 Jul 25 20:27:43 home kernel: [<c01e1702>] pnp_device_probe+0x3c/0x8e Jul 25 20:27:43 home kernel: [<c020064f>] driver_probe_device+0x3f/0x88 Jul 25 20:27:43 home kernel: [<c0200735>] __driver_attach+0x42/0x67 Jul 25 20:27:43 home kernel: [<c0200180>] bus_for_each_dev+0x39/0x5b Jul 25 20:27:43 home kernel: [<c02005bc>] driver_attach+0x11/0x13 Jul 25 20:27:43 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:27:43 home kernel: [<c01ffe91>] bus_add_driver+0x64/0xfa Jul 25 20:27:43 home kernel: [<c01ac5fa>] pci_get_subsys+0xa9/0xb0 Jul 25 20:27:43 home kernel: [<c01e15c8>] pnp_register_driver+0x1a/0x3f Jul 25 20:27:43 home kernel: [<e682e43b>] parport_pc_init+0x355/0x3ef [parport_pc] Jul 25 20:27:43 home kernel: [<c012afa4>] sys_init_module+0x12d6/0x1444 Jul 25 20:27:43 home kernel: [<c010299b>] sysenter_past_esp+0x54/0x79 Jul 25 20:27:43 home kernel: pnp: Device 00:0a activated. Jul 25 20:27:43 home kernel: pnp: Device 00:0a disabled. Jul 25 20:27:43 home kernel: parport_pc: probe of 00:0a failed with error -22 Jul 25 20:27:43 home kernel: lp: driver loaded but no devices found Jul 25 20:28:01 home /usr/sbin/cron[4826]: (dhwalker) CMD (/home/dhwalker/bin/processjob) Jul 25 20:28:07 home kernel: st: Version 20050830, fixed bufsize 32768, s/g segs 256 Jul 25 20:28:32 home kernel: setup_irq: irq handler mismatch Jul 25 20:28:32 home kernel: [<c0131baf>] setup_irq+0xd6/0xe9 Jul 25 20:28:32 home kernel: [<c01e17d5>] pnp_test_handler+0x0/0x6 Jul 25 20:28:32 home kernel: [<c0131c31>] request_irq+0x6f/0x8b Jul 25 20:28:32 home kernel: [<c01e1987>] pnp_check_irq+0xb2/0x126 Jul 25 20:28:32 home kernel: [<c01e2338>] pnp_assign_irq+0xd8/0xf3 Jul 25 20:28:32 home kernel: [<c01e25cd>] pnp_assign_resources+0x1c1/0x23f Jul 25 20:28:32 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:28:32 home kernel: [<c01e26aa>] pnp_auto_config_dev+0x5f/0x8d Jul 25 20:28:32 home kernel: [<c01e26f4>] pnp_activate_dev+0x1c/0x42 Jul 25 20:28:32 home kernel: [<c01e1702>] pnp_device_probe+0x3c/0x8e Jul 25 20:28:32 home kernel: [<c020064f>] driver_probe_device+0x3f/0x88 Jul 25 20:28:32 home kernel: [<c0200735>] __driver_attach+0x42/0x67 Jul 25 20:28:32 home kernel: [<c0200180>] bus_for_each_dev+0x39/0x5b Jul 25 20:28:32 home kernel: [<c02005bc>] driver_attach+0x11/0x13 Jul 25 20:28:32 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:28:32 home kernel: [<c01ffe91>] bus_add_driver+0x64/0xfa Jul 25 20:28:32 home kernel: [<c01ac5fa>] pci_get_subsys+0xa9/0xb0 Jul 25 20:28:32 home kernel: [<c01e15c8>] pnp_register_driver+0x1a/0x3f Jul 25 20:28:32 home kernel: [<e682e43b>] parport_pc_init+0x355/0x3ef [parport_pc] Jul 25 20:28:32 home kernel: [<c012afa4>] sys_init_module+0x12d6/0x1444 Jul 25 20:28:32 home kernel: [<c010299b>] sysenter_past_esp+0x54/0x79 Jul 25 20:28:32 home kernel: pnp: Device 00:0a activated. Jul 25 20:28:32 home kernel: pnp: Device 00:0a disabled. Jul 25 20:28:32 home kernel: parport_pc: probe of 00:0a failed with error -22 Jul 25 20:28:32 home kernel: setup_irq: irq handler mismatch Jul 25 20:28:32 home kernel: [<c0131baf>] setup_irq+0xd6/0xe9 Jul 25 20:28:32 home kernel: [<c01e17d5>] pnp_test_handler+0x0/0x6 Jul 25 20:28:32 home kernel: [<c0131c31>] request_irq+0x6f/0x8b Jul 25 20:28:32 home kernel: [<c01e1987>] pnp_check_irq+0xb2/0x126 Jul 25 20:28:32 home kernel: [<c01e2338>] pnp_assign_irq+0xd8/0xf3 Jul 25 20:28:32 home kernel: [<c01e25cd>] pnp_assign_resources+0x1c1/0x23f Jul 25 20:28:32 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:28:32 home kernel: [<c01e26aa>] pnp_auto_config_dev+0x5f/0x8d Jul 25 20:28:32 home kernel: [<c01e26f4>] pnp_activate_dev+0x1c/0x42 Jul 25 20:28:32 home kernel: [<c01e1702>] pnp_device_probe+0x3c/0x8e Jul 25 20:28:32 home kernel: [<c020064f>] driver_probe_device+0x3f/0x88 Jul 25 20:28:32 home kernel: [<c0200735>] __driver_attach+0x42/0x67 Jul 25 20:28:32 home kernel: [<c0200180>] bus_for_each_dev+0x39/0x5b Jul 25 20:28:32 home kernel: [<c02005bc>] driver_attach+0x11/0x13 Jul 25 20:28:32 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:28:32 home kernel: [<c01ffe91>] bus_add_driver+0x64/0xfa Jul 25 20:28:32 home kernel: [<c01ac5fa>] pci_get_subsys+0xa9/0xb0 Jul 25 20:28:32 home kernel: [<c01e15c8>] pnp_register_driver+0x1a/0x3f Jul 25 20:28:32 home kernel: [<e682e43b>] parport_pc_init+0x355/0x3ef [parport_pc] Jul 25 20:28:32 home kernel: [<c012afa4>] sys_init_module+0x12d6/0x1444 Jul 25 20:28:32 home kernel: [<c010299b>] sysenter_past_esp+0x54/0x79 Jul 25 20:28:32 home kernel: pnp: Device 00:0a activated. Jul 25 20:28:32 home kernel: pnp: Device 00:0a disabled. Jul 25 20:28:32 home kernel: parport_pc: probe of 00:0a failed with error -22 Jul 25 20:28:32 home kernel: lp: driver loaded but no devices found Jul 25 20:28:36 home kernel: setup_irq: irq handler mismatch Jul 25 20:28:36 home kernel: [<c0131baf>] setup_irq+0xd6/0xe9 Jul 25 20:28:36 home kernel: [<c01e17d5>] pnp_test_handler+0x0/0x6 Jul 25 20:28:36 home kernel: [<c0131c31>] request_irq+0x6f/0x8b Jul 25 20:28:36 home kernel: [<c01e1987>] pnp_check_irq+0xb2/0x126 Jul 25 20:28:36 home kernel: [<c01e2338>] pnp_assign_irq+0xd8/0xf3 Jul 25 20:28:36 home kernel: [<c01e25cd>] pnp_assign_resources+0x1c1/0x23f Jul 25 20:28:36 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:28:36 home kernel: [<c01e26aa>] pnp_auto_config_dev+0x5f/0x8d Jul 25 20:28:36 home kernel: [<c01e26f4>] pnp_activate_dev+0x1c/0x42 Jul 25 20:28:36 home kernel: [<c01e1702>] pnp_device_probe+0x3c/0x8e Jul 25 20:28:36 home kernel: [<c020064f>] driver_probe_device+0x3f/0x88 Jul 25 20:28:36 home kernel: [<c0200735>] __driver_attach+0x42/0x67 Jul 25 20:28:36 home kernel: [<c0200180>] bus_for_each_dev+0x39/0x5b Jul 25 20:28:36 home kernel: [<c02005bc>] driver_attach+0x11/0x13 Jul 25 20:28:36 home kernel: [<c02006f3>] __driver_attach+0x0/0x67 Jul 25 20:28:36 home kernel: [<c01ffe91>] bus_add_driver+0x64/0xfa Jul 25 20:28:36 home kernel: [<c01ac5fa>] pci_get_subsys+0xa9/0xb0 Jul 25 20:28:36 home kernel: [<c01e15c8>] pnp_register_driver+0x1a/0x3f Jul 25 20:28:36 home kernel: [<e682e43b>] parport_pc_init+0x355/0x3ef [parport_pc] Jul 25 20:28:36 home kernel: [<c012afa4>] sys_init_module+0x12d6/0x1444 Jul 25 20:28:36 home kernel: [<c010299b>] sysenter_past_esp+0x54/0x79 Jul 25 20:28:36 home kernel: pnp: Device 00:0a activated. Jul 25 20:28:36 home kernel: pnp: Device 00:0a disabled. Jul 25 20:28:36 home kernel: parport_pc: probe of 00:0a failed with error -22 zmd-messages.log* ----------------- 20 Jul 2006 21:36:55 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 2 (Install '[S2:1][package]yast2-apparmor-2.0-27.5.noarch') 20 Jul 2006 21:36:58 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 4 (Install '[S2:1][package]apparmor-utils-2.0-23.5.noarch') 20 Jul 2006 21:37:12 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 6 (Install '[S2:1][package]samba-client-3.0.22-13.18.i586') 20 Jul 2006 21:37:32 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 8 (Install '[S2:1][package]rug-7.1.1.0-18.24.i586') 20 Jul 2006 21:37:34 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 10 (Install '[S2:1][package]udev-085-30.11.i586') 20 Jul 2006 21:37:37 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 12 (Install '[S2:1][package]apparmor-parser-2.0-21.5.i586') 20 Jul 2006 21:37:39 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 14 (Install '[S2:1][package]apparmor-docs-2.0-17.5.noarch') 20 Jul 2006 21:37:40 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 16 (Install '[S2:1][package]audit-libs-1.1.3-23.3.i586') 20 Jul 2006 21:37:43 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 18 (Install '[S2:1][package]samba-winbind-3.0.22-13.18.i586') 20 Jul 2006 21:37:50 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 20 (Install '[S2:1][package]samba-3.0.22-13.18.i586') 20 Jul 2006 21:37:55 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 22 (Install '[S2:1][package]audit-1.1.3-23.3.i586') 20 Jul 2006 21:37:57 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 24 (Install '[S2:1][package]apparmor-profiles-2.0-34.9.noarch') 20 Jul 2006 21:37:59 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 26 (Install '[S2:1][package]mkinitrd-1.2-106.15.i586') 20 Jul 2006 21:38:26 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 28 (Install '[S2:1][package]kernel-default-2.6.16.21-0.13.i586') 20 Jul 2006 21:40:30 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 30 (Install '[S2:1][package]novfs-kmp-default-1.2.0_2.6.16.21_0.13-9.2.i586') 22 Jul 2006 19:38:37 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 2 (Install '[S2:1][package]xorg-x11-server-glx-6.9.0-50.17.i586') 22 Jul 2006 19:38:43 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 4 (Install '[S2:1][package]xorg-x11-libs-6.9.0-50.17.i586') 22 Jul 2006 19:39:05 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 6 (Install '[S2:1][package]xkeyboard-config-0.7-19.7.noarch') 22 Jul 2006 19:39:12 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 8 (Install '[S2:1][package]hal-0.5.6-33.11.i586') 22 Jul 2006 19:39:25 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 10 (Install '[S2:1][package]3ddiag-0.735-1.6.i586') 22 Jul 2006 19:39:26 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 12 (Install '[S2:1][package]yast2-backup-2.13.2-3.3.noarch') 22 Jul 2006 19:39:47 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 14 (Install '[S2:1][package]Mesa-6.4.2-19.7.i586') 22 Jul 2006 19:39:58 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 16 (Install '[S2:1][package]control-center2-2.12.2-62.15.i586') 22 Jul 2006 19:40:11 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 18 (Install '[S2:1][package]sax2-tools-2.7-125.19.i586') 22 Jul 2006 19:40:26 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 20 (Install '[S2:1][package]xorg-x11-6.9.0-50.17.i586') 22 Jul 2006 19:40:42 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 22 (Install '[S2:1][package]powersave-libs-0.12.20-0.3.i586') 22 Jul 2006 19:40:45 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 24 (Install '[S2:1][package]xorg-x11-Xnest-6.9.0-50.17.i586') 22 Jul 2006 19:40:49 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 26 (Install '[S2:1][package]hal-gnome-0.5.6-33.11.i586') 22 Jul 2006 19:40:51 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 28 (Install '[S2:1][package]libwnck-2.12.2-28.7.i586') 22 Jul 2006 19:40:59 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 30 (Install '[S2:1][package]sax2-libsax-7.1-125.19.i586') 22 Jul 2006 19:41:10 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 32 (Install '[S2:1][package]xorg-x11-server-6.9.0-50.17.i586') 22 Jul 2006 19:41:16 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 34 (Install '[S2:1][package]gnome-session-2.12.0-106.17.i586') 22 Jul 2006 19:41:20 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 36 (Install '[S2:1][package]powersave-0.12.20-0.3.i586') 22 Jul 2006 19:41:26 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 38 (Install '[S2:1][package]sax2-libsax-perl-7.1-125.19.i586') 22 Jul 2006 19:41:29 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 40 (Install '[S2:1][package]xorg-x11-driver-video-6.9.0-46.15.i586') 22 Jul 2006 19:41:31 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 42 (Install '[S2:1][package]xorg-x11-driver-video-nvidia-6.9.0-46.15.i586') 22 Jul 2006 19:41:31 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 44 (Install '[S2:1][package]sax2-ident-1.7-125.19.i586') 22 Jul 2006 19:41:34 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 46 (Install '[S2:1][package]sax2-7.1-125.19.i586') 22 Jul 2006 19:41:38 INFO RedCarpetBackend+RCTransactionProgress Transaction step. seqno 48 (Install '[S2:1][package]sax2-gui-1.7-125.19.i586') -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

2 1

[SLE] Info: 2.6.16.++ kernels and sensors
by Mark Crean 25 Jul '06

25 Jul '06

In case this helps anyone. A recent kernel patch turns off sensors (lm-sensors, libsensors, etc.) if certain Asus motherboards are detected. In fact, my understanding is that the patch simply keeps the smbus hidden so sensors has nothing to access. The reason is that some Asus motherboards don't do the sensors and smbus thing properly and this can led to severe consequences and general borkage on resuming from sleep or suspend states. The workaround is to recompile the kernel with ACPI sleep off (default is on) or edit /drivers/pci/quirks.c in the kernel sources at your own risk where the relevant code for this Asus stuff is to be found. The affected motherboards are listed in the code here and seem to be only some older ones. So if you have an affected Asus board and update to, say, kernel 2.6.16.21-0.13-default and then find that sensors no longer works, this is probably why. :) Fish -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

[SLE] SLED10: Xsession: login for rmccain is disabled
by Ryan McCain 25 Jul '06

25 Jul '06

Hello, I installed SLED 10, however when trying to login to X, I get "Xsession: login for rmccain is disabled". I configured SLED 10 to use eDir for authentication. that works fine because if i login as the person i entered as the admin for the LUM piece of it during the install, that person can login to X fine. I then su to any user, then su to another user which prompts me for a PW and that works fine. Any ideas? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

[SLE] ntp client -- warning from yast
by Peter Van Lone 25 Jul '06

25 Jul '06

using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says: "Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly" Huh? So, if I have a laptop, that does not at all times have an inet connection, basically I should not use the NTP client? Is there any good way to, once an inet connection IS established, sync time to an NTP server? Yast seems to only give "never" and "on boot" as ntp sync options. If there is a command I can execute from a shell, that would be fine. Peter -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

6 7

[SLE] xmms on OpenSuSE 10.1
by John Andersen 25 Jul '06

25 Jul '06

Whats the trick to getting xmms 1.2.10 to play mp3 files on SuSE 10.1? Juk can mp3s Realplayer 10 can play mp3 Amarok can play mp3s (although it seems to suffer massive memory leaks) Kaffeine can play mp3s Xine can play mp3s (these latter two impose ridiculous CPU loads doing so.) So whats with xmms? Do I have to installed the Packman versions or what? -- _____________________________________ John Andersen

5 10

[SLE] adding KDE repository error
by Michal Hlavac 25 Jul '06

25 Jul '06

# rug sa --type=YUM http://ftp.opensuse.org/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1 KDE Adding YUM service http://ftp.opensuse.org/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1... 33% ERROR: Could not add 'http://ftp.opensuse.org/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1': Failed to parse XML metadata: Can't add repository at http://ftp.opensuse.org/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1: Cannot create the installation source it doesn't depends on security-level thanks, miso -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

2 1

[opensuse] postfix only send
by Frank Berg 25 Jul '06

25 Jul '06

hi group I´m using OpenSuse 10.1 and i need for my apache site the mail() comand. therefor i was install postfix with yast and the mails are correct send but received to. but this little computer in the corner must not receive my private mails, and i need not to install an mail-server to, so now my question: how can i configure postfix: so it send mails out, but not receive mails tnx.. frank

3 3

[opensuse] error in adding KDE repository
by Michal Hlavac 25 Jul '06

25 Jul '06

hello, I tried to add KDE and KDE Backports repositories and I get this error: # rug sa --type=YUM http://ftp.opensuse.org/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1 KDE ERROR: Could not add 'http://ftp.opensuse.org/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1': Failed to parse XML metadata: Can't add repository at http://ftp.opensuse.org/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1: Cannot create the installation source It doesn't depends on security-level. Other repositories also from ftp.opensuse.org are OK. miso --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-help(a)opensuse.org

3 2

[SLE] Samba Domain connections via VPN
by Martin Hochreiter 25 Jul '06

25 Jul '06

Hi! I have serious problems with my knew Samba controlled domain. My network looks like that: Samba PDC (192.168.1.100)------192.168.1.0/255.255.255.0 ------ vpn -------- 192.168.2.0/255.255.255.0----- Samba BDC (192.168.2.6) My previous controller was a Win2000 AD and for that type you could add some srv entries in DNS (Bind) to get the domain controller "visible" from the 192.168.2.0 net. Since I installed Samba as PDC the clients on the 192.168.2.0 net could log on (BDC ??) but are not able to join a domain or if already in the domain (by carrying the Client in the 192.168.1.0 net) then the user could not change the password. My VPN Gateways are able to send Netbios via VPN (as least they say so) but infact I have the above mentioned troubles. Could anyone give me a hint? (Wins was no solution and the AD entries in the DNS also don't work for a samba domain) -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

[SLE] Kinternet problems...
by JB 25 Jul '06

25 Jul '06

Hi all, My mom has SuSE 9.3 on her system and has been using it just fine for almost a year now, but the other day she rebooted and when she got to her desktop, the kinternet button in the taskbar was gone. I added it back to the taskbar by right-clicking and adding it from the menu, but when I click on it to dial in and get online, a window pops up and reads something like 'server refused connection' and then 'maybe smpppd isn't running' (I checked and it is) and to check 'various settings'. I click the 'close' button and then a window pops up about kinternet crashed with a segsev (or something like that). If I boot into root, kinternet works just fine. I've gone into YaST2 and deleted the old modem and provider and redone everything, yet kinternet still won't work, same message(s) and crash window. Anyone have any idea why it would just 'disappear' in the first place and any ideas how to fix it? She's really chomping at the bit to get back online and I really don't want her doing it as root if I can help it. Thanks, John -- "In the beginning of a change, the patriot is a brave and scarce man, hated and scorned. When the cause succeeds, however, the timid join him...for then it costs nothing to be a patriot." - Mark Twain "Calling an illegal alien an undocumented immigrant is like calling a burglar an uninvited house guest." <www.illegalaliens.us> -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

2 2