July 2004 - openSUSE Users - openSUSE Mailing Lists

kmenuedit breaks after latest security updates
by burgeke＠HQ.VerizonWireless.com 01 Jul '04

01 Jul '04

I have SuSE 9.1 pro and also personal (on another machine). At any rate, a stock install allows me to edit the kde menus without difficulty. I can add/remove whatever I want, subfolders, entries etc. After applying the updates to both system, I can still add or remove items, but only once. Any subsequent opening of kmenuedit results in that subfolder being empty. If I try to expand it, nothing is there. Not a major problem as I can still see the items in the KDE menu. However, lets say I add an item to the Utility menu then save the changes. Go back into kmenuedit and I can't change anything again in the Utility menu since it is empty. Any attempt to add something (even though it is empty) appears to work but badly screws up the KDE menu for that category. Any thoughts? Anyone else having this prob? P.S. I tried starting from scratch and whacking the .desktop and menu files kmenuedit creates, still no dice. Thanks - Keith

1 0

Changing GTK Theme
by Davy Brion 01 Jul '04

01 Jul '04

Hi, when i run GTK programs in KDE, they keep using the ThinGeramik theme... i'd prefer it if the GTK applications would use the Industrial theme. I logged into Gnome to change this, and when i log into Gnome it does use Industrial. But when i log back into KDE, my GTK applications still use ThinGeramik. Where can i change it so the GTK applications in KDE use Industrial?

1 1

RE: [SLE] xfce4
by Ben Higginbottom 01 Jul '04

01 Jul '04

>Has anyone used XFCE4 under SuSE 9.1? Wouldn't run a *nix without it. >How did you decide to make XFCE4 available as (a) an option or (b) the default? If your desktop manager is kdm (the default) then you need a xfce4 file in /opt/kde3/share/apps/sessions called xfce4.desktop, I edited the xfce3 entry to reflect the changes, but there is a rpm containing the necessary file about. Best, Ben

6 8

Re: [SLE] https
by steve-ss 01 Jul '04

01 Jul '04

On Thursday 01 July 2004 13:28, you wrote: > What error does it give? An error occurred while loading https://localhost:443: Could not connect to host localhost > Did you remember to make it listen to port 443? Which script is that in? I think it's only listening on 80. > And what about an 'rcpache2 restart' (I don't remember > having started it with startssl)? Still doesn't restart > Did you verify that ssl is in the apache modules? Yes it is. TIA. Steve. > > > Hi and thanks for the help. Still no joy. I copied the > > certificates to /etc/apache2/ssl.key/ > > and /etc/apache2/ssl.crt/ I renamed the certificates to > > server.key server.crt. but when I put > > APACHE_SERVER_FLAGS="-D SSL" and do a rcapache2 > > startssl apache2 won't start. If I remove that line it > > will start but not with ssl. Any ideas? > > > > Thanks, Steve. > > > > --

1 0

UID-Permissions Problem Has Reoccurred
by doc 01 Jul '04

01 Jul '04

I had fixed my UID-Permissions problems following an upgrade from 9 to 9.1 (changed everything from 500 to 1001). The fix had held through multiple restarts, and overnight power down and power up cycles. Yesterday I powered my notebook off at work, brought it home, and powered back up and the same problem has reoccurred forcing me to long in Failsafe instead of KDE. The login window flashes and returns me to login -- only Filsafe works. When Failsafe brings up a window I enter kde and I get the same old "bad font, likely due to a permissions problem" (paraphrased). The only recent changes I recall making are loading and running MPlayer (from the Packman site) and VideoLan. Note: Is it possible that I loaded a mix of i586 and i686 files for those two apps and that could cause this problem -- even though both apps functioned correctly and gave no errors? The strange thing is that everything looks OK when I view the files as Root, they show the correct user and group. I used YaST and the user is 1001. I also looked at groups and it is 100, is that correct? I am also still seeing the odd "wbar10" artifact in Root and I still have no idea where it came from. Thanks for any assistance! doc

3 5

Where's Lisa?
by James Knott 01 Jul '04

01 Jul '04

In SuSE 9.0, LISa can be configured via the control center, under Internet & Network > Local Network Browsing > LISa Daemon. However, in SuSE 9.1, the LISa options don't seem to be available there. LISa is enabled in the run level editor, but doesn't appear to start. Even after manually starting it, I can't browse the network. Any ideas? tnx jk

1 0

Combining mail parts sent by Outlook
by Nico 01 Jul '04

01 Jul '04

Hi, somebody sent me a mail with a massive attachment from Outlook. Outlook divided it into parts. When receiving it in Outlook, the parts are easily recombined to reconstruct the attachment. How do I do it in KMail? Thanks Nico (Apologies if this is a second posting - but I again had a bounce message - seems as if there might be a problem with KMail not always using the correct "from". I will investigate if I can get to repeat the error...)

1 0

Online Update Server
by Ryan McCain 01 Jul '04

01 Jul '04

Anyone else having problems w/ Online Update lately? Also, where does SUSE store the settings for what Online Update server you are using? Thanks, -------------------------------------- Ryan McCain Northrop Grumman Linux System Administrator 3 email: Ryan.McCain(a)dss.state.la.us Phone: 225.219.0556 Fax: 225.219.0540

6 7

RE: [SLE] MozillaFirefox 0.9.1
by Scott Thompson 01 Jul '04

01 Jul '04

I had .90 already installed and set up with themes and extensions. I simply downloaded the .91 archive from the firefox homepage, renamed my .90 directory from firefox to Firefox, used tar to extract the contents of the archive into the same directory that had the .90 installation. My desktop and panel links still worked because the .91 files are in the same location as the .90 files were. Firefox ran fine as user and maintained all of the themes and extensions I had installed in .90. > -----Original Message----- > From: Mads Martin Joergensen [mailto:mmj@mmj.dk] > Sent: Thursday, July 01, 2004 3:17 AM > To: Anders Johansson > Cc: suse-linux-e(a)suse.com > Subject: Re: [SLE] MozillaFirefox 0.9.1 > > > * Anders Johansson <andjoh(a)rydsbo.net> [Jul 01. 2004 10:13]: > > > > This problem still exists in the suse version, if you > run it for > > > > the first time. The problem is when firefox tries to open the > > > > "import settings" window. If you already have the config files > > > > from a previous installation you don't see it > > > > > > Oh, odd. I just installed 0.9.1 yesterday using nothing but 'sudo > > > sux -'. > > > > This isn't about having to run it as root, this is when you > run it for > > the > > first time as a user. Did you already have an old installation? > > > > I installed 0.9 on a system where I already had 0.8 and everything > > worked > > perfectly. Then I cleared out everything, $HOME/.mozilla, > $HOME/.firefox and > > all, and tried again, and then I got the error everyone > else is seeing > > > > It seems to be very timing sensitive. I said the only way > around it is > > to turn > > of authentication, but that's not true. When I > experimented, I found that the > > error also went away when I changed the hash-bang in run-mozilla.sh > > from /bin/sh to /bin/sh -x. That slight change in timing was enough. > > Yeah, it makes sense, and yes, I did have 0.8 before. > > -- > Mads Martin Joergensen, http://mmj.dk > "Why make things difficult, when it is possible to make them > cryptic and totally illogical, with just a little bit more effort?" > -- A. P. J. > > -- > 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

Multipathing with md gives kernel oops
by Multipath 01 Jul '04

01 Jul '04

Hi, i have a problem using md to do multipathing on SuSE 9.1. I have two emulex LP9002 which connect over two separated fabrics to an IPStor Server. Driver is the standard lpfcdd Modul with automap=off and the right bindings. Everything works fine without multipathing, I see the disks over both paths and can access them without problems, i.e. format, write, read, etc. Now I wanted to use md for doing multipathing. I took two disks /dev/sda1 /dev/sdc1, which are only one disk over two paths and made with fdisk /dev/sda1 one partition over the whole disk. After creating the array with mdadm -C /dev/md0 --level=multipath -n 2 /dev/sda1 /dev/sdc1 I can even do a 'mkreiserfs /dev/md0' without problems on it. (Same works for -B) But when I try to mount the disk /dev/md0, I get a kernel oops. Any idea??? What's wrong? Here is the Oops: Jul 1 10:42:30 lpfctest kernel: ReiserFS: md0: found reiserfs format "3.6" with standard journal Jul 1 10:42:30 lpfctest kernel: ReiserFS: md0: using ordered data mode Jul 1 10:42:30 lpfctest kernel: reiserfs: using flush barriers Jul 1 10:42:30 lpfctest kernel: ReiserFS: md0: journal params: device md0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jul 1 10:42:30 lpfctest kernel: ReiserFS: md0: checking transaction log (md0) Jul 1 10:42:31 lpfctest kernel: multipath: IO failure on sda1, disabling IO path. Jul 1 10:42:31 lpfctest kernel: Operation continuing on 1 IO paths. Jul 1 10:42:31 lpfctest kernel: multipath: sda1: rescheduling sector 65751 Jul 1 10:42:31 lpfctest kernel: MULTIPATH conf printout: Jul 1 10:42:31 lpfctest kernel: --- wd:1 rd:2 Jul 1 10:42:31 lpfctest kernel: disk0, o:0, dev:sda1 Jul 1 10:42:31 lpfctest kernel: disk1, o:1, dev:sdc1 Jul 1 10:42:31 lpfctest kernel: MULTIPATH conf printout: Jul 1 10:42:31 lpfctest kernel: --- wd:1 rd:2 Jul 1 10:42:31 lpfctest kernel: disk1, o:1, dev:sdc1 Jul 1 10:42:31 lpfctest kernel: multipath: sda: redirecting sector 65680 to another IO path Jul 1 10:42:31 lpfctest kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000018 Jul 1 10:42:31 lpfctest kernel: printing eip: Jul 1 10:42:31 lpfctest kernel: d115d929 Jul 1 10:42:31 lpfctest kernel: *pde = 00000000 Jul 1 10:42:31 lpfctest kernel: Oops: 0000 [#1] Jul 1 10:42:31 lpfctest kernel: CPU: 0 Jul 1 10:42:31 lpfctest kernel: EIP: 0060:[__crc_drive_is_ready+280767/2688051] Not tainted Jul 1 10:42:31 lpfctest kernel: EIP: 0060:[<d115d929>] Not tainted Jul 1 10:42:31 lpfctest kernel: EFLAGS: 00010246 (2.6.5-7.75-default) Jul 1 10:42:31 lpfctest kernel: EIP is at multipath_end_request+0x59/0xb0 [multipath] Jul 1 10:42:31 lpfctest kernel: eax: 000100cf ebx: c3802788 ecx: 00000000 edx: c69e1ebc Jul 1 10:42:31 lpfctest kernel: esi: c3802780 edi: cfea1c80 ebp: 00000000 esp: c69e1eb4 Jul 1 10:42:31 lpfctest kernel: ds: 007b es: 007b ss: 0068 Jul 1 10:42:31 lpfctest kernel: Process md0_multipath (pid: 4339, threadinfo=c69e0000 task=cd4c9230) Jul 1 10:42:31 lpfctest kernel: Stack: 000100cf 00000000 00000000 c033e750 c69e1ee4 c011af31 cd423f38 00000001 Jul 1 10:42:31 lpfctest kernel: 00000001 00000206 c3802788 00000000 d115d8d0 ffffffa1 c015d5af c3802788 Jul 1 10:42:31 lpfctest kernel: cc999800 00000000 00000001 c0220ece 000100cf 00000000 00000004 00000008 Jul 1 10:42:31 lpfctest kernel: Call Trace: Jul 1 10:42:31 lpfctest kernel: [__wake_up_common+49/96] __wake_up_common+0x31/0x60 Jul 1 10:42:31 lpfctest kernel: [<c011af31>] __wake_up_common+0x31/0x60 Jul 1 10:42:31 lpfctest kernel: [__crc_drive_is_ready+280678/2688051] multipath_end_request+0x0/0xb0 [multipath] Jul 1 10:42:31 lpfctest kernel: [<d115d8d0>] multipath_end_request+0x0/0xb0 [multipath] Jul 1 10:42:31 lpfctest kernel: [bio_endio+63/96] bio_endio+0x3f/0x60 Jul 1 10:42:31 lpfctest kernel: [<c015d5af>] bio_endio+0x3f/0x60 Jul 1 10:42:31 lpfctest kernel: [__make_request+798/1312] __make_request+0x31e/0x520 Jul 1 10:42:31 lpfctest kernel: [<c0220ece>] __make_request+0x31e/0x520 Jul 1 10:42:31 lpfctest kernel: [generic_make_request+269/496] generic_make_request+0x10d/0x1f0 Jul 1 10:42:31 lpfctest kernel: [<c021fc5d>] generic_make_request+0x10d/0x1f0 Jul 1 10:42:31 lpfctest kernel: [__wake_up+14/32] __wake_up+0xe/0x20 Jul 1 10:42:31 lpfctest kernel: [<c011af6e>] __wake_up+0xe/0x20 Jul 1 10:42:31 lpfctest kernel: [printk+285/304] printk+0x11d/0x130 Jul 1 10:42:31 lpfctest kernel: [<c011fa9d>] printk+0x11d/0x130 Jul 1 10:42:31 lpfctest kernel: [disk_name+97/112] disk_name+0x61/0x70 Jul 1 10:42:31 lpfctest kernel: [<c0189031>] disk_name+0x61/0x70 Jul 1 10:42:31 lpfctest kernel: [__crc_drive_is_ready+280397/2688051] multipathd+0xd7/0xf0 [multipath] Jul 1 10:42:31 lpfctest kernel: [<d115d7b7>] multipathd+0xd7/0xf0 [multipath] Jul 1 10:42:31 lpfctest kernel: [md_thread+131/318] md_thread+0x83/0x13e Jul 1 10:42:31 lpfctest kernel: [<c0270733>] md_thread+0x83/0x13e Jul 1 10:42:31 lpfctest kernel: [default_wake_function+0/16] default_wake_function+0x0/0x10 Jul 1 10:42:31 lpfctest kernel: [<c011bee0>] default_wake_function+0x0/0x10 Jul 1 10:42:31 lpfctest kernel: [md_thread+0/318] md_thread+0x0/0x13e Jul 1 10:42:31 lpfctest kernel: [<c02706b0>] md_thread+0x0/0x13e Jul 1 10:42:31 lpfctest kernel: [kernel_thread_helper+5/16] kernel_thread_helper+0x5/0x10 Jul 1 10:42:31 lpfctest kernel: [<c0106005>] kernel_thread_helper+0x5/0x10 Jul 1 10:42:31 lpfctest kernel: Jul 1 10:42:31 lpfctest kernel: Code: 8b 45 18 e8 1f b8 02 ef 50 68 d0 dc 15 d1 e8 44 20 fc ee 83

1 0