I keep running into a problem with KDE crashing when using the search bar in Firefox.
For some unknown reason, something gets set in the Firefox profile that will cause KDE to crash when a few chars are typed into the search bar in Firefox’s upper right corner. When this situation occurs, I can log on to Gnome, and use the search bar with no problem. This is something related to KDE only.
The temporary solution is to delete my Firefox profile. This fixes the problem initially, but returns after a few weeks of web browsing. Deleting my browser profile every two weeks is NOT much fun!
Firefox level is 3.6.13. KDE is 4.4.4. Suse is 11.3. I do NOT have Moonlight installed.
Add this using YaST / Software Repositories and give it a priority number lower, which is a higher priority, than all of the openSUSE repositories, like using a 90 for instance. Next, run Software Management. In Software Management, using the View Button, switch to the Repository View. On the left, find the Mozilla Repository you added by the name you gave it and select it. On the Mozilla repository file listing window, there is a switch to this repository selection on the top left of that window. Select it and allow all files you have loaded, that exist in the Mozilla repository, to be reloaded in mass. This will ensure that ALL Firefox files have been compiled together to work from the same repository and then report back if this helped.
On Saturday 15 Jan 2011 14:06, jdmcdaniel3 scribbled:
> Add this using YaST / Software Repositories and give it a priority
> number lower, which is a higher priority, than all of the openSUSE
> repositories, like using a 90 for instance
I noticed some time ago that this prioritising didn’t work any longer and
recall having it confirmed in one of these newsgroups that this was so and
that it was a design feature and not a bug.
The system I was advised to use was to open a “repositories” tab in
YAST/Software-management, click on the required repository, and then click
on "switch system packages . . . ".
–
Graham Davis, Bracknell, Berks. E-mail: change boy to man
On Saturday 15 Jan 2011 14:06, jdmcdaniel3 scribbled:
> Add this using YaST / Software Repositories and give it a priority
> number lower, which is a higher priority, than all of the openSUSE
> repositories, like using a 90 for instance
I noticed some time ago that this prioritizing didn’t work any longer and
recall having it confirmed in one of these newsgroups that this was so and
that it was a design feature and not a bug.
The system I was advised to use was to open a “repositories” tab in
YAST/Software-management, click on the required repository, and then click
on "switch system packages . . . ".
–
Graham Davis, Bracknell, Berks. E-mail: change boy to man
Cloddy, setting the priority is said to work now with the most recent YaST software updates in openSUSE 11.3 and you should use it. More important though for me is another thing that happens. When you put a lower number on a repository and then do an update check, you will find higher priority entries on the top of the available files on the version tab. For instance, I make Packman the highest priority, like using an 80. When I search for a file or get an update listing and go to the versions tab, the higher priority files from Packman show at the top and then a bullet is present for which version I actually have selected. It makes it easy to see when I am using a file that is a lower priority, making it easier to make sure I am using the file from the repository I want to use. I would like to add that if you only add Packman to your repository listing and make it a priority 98 from the default 99 you will be in good shape for updates. Keep in mind that even when using a priority, doing a system wide update still will require manual intervention when a multitude of files must be updated, requiring the switching of other files to a different repository. The priority thing is not the only issue that must be dealt with. I always make Packman a Higher Priority and make every effort to NOT add any other repositories to my setup. You should try to do the same thing as well.
Thanx to all for the suggestions. However, I already have the Mozilla repository added, and the priority set fairly low. I did try the suggestion of reloading all the Firefox modules, but KDE still crashes. I will try (once again) deleting my profile and see if it stays fixed. I suspect that this is NOT a Firefox issue, but a KDE issue. If I startup in Gnome, no problem with the current Firefox profile.
I don’t know if this helps, but I have these messages in /var/log/messages when KDE
crashes:
Jan 16 05:47:32 bigtop kdm[1330]: X server for display :0 terminated unexpectedly
Jan 16 05:47:32 bigtop polkitd(authority=local): Unregistered Authentication Agent for session /org/freedesktop/ConsoleKit/Session2 (system bus name :1.91, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jan 16 05:47:32 bigtop acpid: 1 client rule loaded
Jan 16 05:47:32 bigtop kernel: 2726.118721] [drm:drm_mode_getfb] ERROR invalid framebuffer id
So, as I understand it, the problem happens in Firefox, lets assume the issue is Firefox then. Add the following repository (YaST / Software / Software Repositories), call it Mozilla and give it a higher priority (lower number) than the openSUSE update repository.
Next, start Software Management (YaST / Software / Software Management) and select the View Button (Top Left) and select the Repository view. Select the Repository of Mozilla, as you called it. Now, in the Mozilla File selection window notice the Switch System Packages to the versions in this repository (Mozilla) and elect to Switch System Packages which will replace all Mozilla files that are already loaded from those in the repository you added and called Mozilla. Normally, making such a choice can be problematic, like doing this with Packman, but works just fine with a very small repository like Mozilla and ensures that all Firefox related files were compiled and versioned together to work as a team, thus making sure the reason Firefox locks up KDE is not due to having installed mixed versions of Firefox.
On Saturday 15 Jan 2011 15:36, jdmcdaniel3 scribbled:
>
> Cloddy, setting
> the priority is said to work now with the most recent
> YaST software updates in openSUSE 11.3 and you should use it. More
> important though for me is another thing that happens. When you put a
> lower number on a repository and then do an update check, you will find
> higher priority entries on the top of the available files on the version
> tab.
I’m testing 11.4 at the moment and I see that what you say is correct. It
seems that priorities still work - or work again - in spite of what I was
told. Unfortunately, I see kpackagekit ignores any priorities - or is
unaware of them - and just goes for the highest version number. Anyway, I’ll
raise that in a more suitable newsgroup.
I am very wary of Packman. If I need anything from it, I enable it, install
the package, and then disable it. Got into a mess some years ago with some
very scruffy updates from Packman and the experience has left me rather
nervous.
Thanks,
–
Graham Davis, Bracknell, Berks. E-mail: change boy to man
I think priorities affect only zypper dup. To my knowledge the updater applet performs a crippled version of zypper up so it won’t take priorities into account.
I think priorities affect only zypper dup. To my knowledge the updater applet performs a crippled version of zypper up so it won’t take priorities into account.
