After an update, Firefox, SeaMonkey and Seamonkey Mail crash. Rekonq runs at first, but crashes when I click a bookmark. I had to install Opera just to get here. Has anyone else had this problem? I remember there were Mozilla updates (Firefox and SeaMonkey), and Qt4 “devel” package, I forget if there was anything else. Also, now I can’t get IceWM to run. KDE4 is working still.
If it matters, I used Yast to do the online update, only the “needed” updates. Guess I didn’t “need” them as much as I though
i noticed in seamonkey preferences that some menus were appearing blank
I created new profile and everything was fine
I noticed this when migrating from 2.14==>2.15
I think the same problem is affecting firefox too as SeaMonkey is closing following Firefox release cycles and backend(gecko) nowadays
On 01/12/2013 07:46 AM, HighBloodSugar wrote:
> After an update
i wonder if you have either (following the update) either logged out and
back in, or shutdown and rebooted (not simply sleeping or hibernating)?
if not, then do this in a terminal
zypper ps
and see if you are running any processes using deleted files (the list may be long)…if you are then try logging out and back it, and run
the “zypper ps” command again and then see if any of those crashing
programs are acting right again…
if they remain broken i can only guess you have some conflicting repos
and/or software in the mix somewhere–so please show us the terminal
output and input, as well as the beginning prompt and exit prompt, from
zypper lr -d
uname -a
cat /etc/SuSE-release
copy/paste the in/output back to this thread using the instructions
here: http://goo.gl/i3wnr
and, next time please declare which operating system, desktop
environment and versions are in use…
My problem is that is crashes immediately, I can’t get in to try a new profile. There were other updates along with the Mozilla stuff, so I’m not sure if the problem is Seamonkey & Firefox/Thunderbird, or something else they depend on.
user@linux-fi3i:~> seamonkey
/usr/bin/seamonkey: line 139: 4567 Segmentation fault $MOZ_PROGRAM "$@"
I forgot to mention before, I’m using openSuse 12.1 64 bit version.
For now, I can use Opera, and can get my email from the Verizon web page, it’ll do until this is fixed.
[quote="dd,post:4,topic:86215"]
On 01/12/2013 07:46 AM, HighBloodSugar wrote:
> After an update
i wonder if you have either (following the update) either logged out and
back in, or shutdown and rebooted (not simply sleeping or hibernating)?
if not, then do this in a terminal
zypper ps
and see if you are running any processes using deleted files (the list
_may_ be long)....if you are then try logging out and back it, and run
the "zypper ps" command again and then see if any of those crashing
programs are acting right again..
if they remain broken i can only guess you have some conflicting repos
and/or software in the mix somewhere--so please show us the terminal
output *and* input, as well as the beginning prompt and exit prompt, from
zypper lr -d
uname -a
cat /etc/SuSE-release
copy/paste the in/output back to this thread using the instructions
here: [Posting in Code Tags - A Guide](http://goo.gl/i3wnr)
and, next time please declare which operating system, desktop
environment and versions are in use..
--
dd [DD Caveat](http://tinyurl.com/DD-Caveat)
[/quote]
I'm running openSuse 12.1 64 bit and KDE 4.7.2 Release 5. This happened after the latest Yast online update
Here is what I get:
linux-fi3i:/home/user # zypper ps
No processes using deleted files found.
I rebooted after I noticed troubles, so the above is not from *right after* the updates, if that matters.
linux-fi3i:/home/user # zypper lr -d
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
the repos look pretty okay…but, while i do NOT think it will have any
impact on your current problems, i would suggest you disable the
following repos: 1, 4, and 5…and, cease refreshing 1, 4, 6, 7 and
10. rational given in the paragraph beginning with “IMPORTANT” in this
post http://tinyurl.com/33qc9vu plus there is no need to refresh
disabled repos or those which will never change (like oss and
non-oss)–and not refreshing unneeded repos will SPEED up the activity
of YaST Software Management, YaST Online Update and zypper…
oh, and if you disable the CD (#5) it will stop asking you to insert it
each time…
next: i see these as your command line inputs
> linux-fi3i:/home/user # zypper lr -d
> linux-fi3i:/home/user # uname -a
> linux-fi3i:/home/user # cat /etc/SuSE-release
so, i have to wonder why you did those as root? it has long been the
convention in *nix/bsd/linux to use root powers only when required
(this is a “security thing”–using the least powerful actor always
increases total system security–and is ONE of the principle differences
between Windows and industrial strength systems!)…and, none of those
commands needed root powers!!
so, it also appears (to me) that maybe you have logged into KDE as
root…is that correct??
if yes: that is something you should not do, ever…ask then how to do
administrator duties without logging into KDE as the administrator, and
i will explain further…
user@linux-fi3i:~> uname -a
Linux linux-fi3i 3.1.10-1.16-desktop #1 SMP PREEMPT Wed Jun 27 05:21:40 UTC 2012 (d016078) x86_64 x86_64 x86_64 GNU/Linux
openSUSE 12.1 (x86_64)
VERSION = 12.1
CODENAME = Asparagus
As for the “CD” in the repos, it never has asked for the disk, so I never thought to check that setting. I’ll disable that anyway, and the others you suggested. Thanks for that tip!
On 01/12/2013 09:26 PM, HighBloodSugar wrote:
> I used “su” first, I assumed that was needed.
understand…no problem…but, most folks here who try to give help
will specify to “become root” or “su to root” or something like that
when needed, or else give some kind of ‘hint’…so, i’d say in most
cases you can assume that normal user is what you need…then if it
fails for permissions or whatever, you can “su -” (not just su) and
proceed…
the main thing i was worried about was if you were logging into KDE as
root…don’t.
so, i am all out of ideas, i have no idea why you have the troubles you
do…sorry.
I do know that this happened after the last online update using Yast. Here’s the info for that update session, from /var/log/zypp/history. I did the update on 2013-01-12, but included the info from 2013-01-07 because I saw a warning, figured it might be relevant.
2013-01-04 13:17:54|remove |gnome-subtitles|1.2-2.1.2|x86_64|root@linux-fi3i
2013-01-07 13:52:47|install|libmysqlclient18|5.5.28-3.14.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|29d5b7a1f9b73748439b0b2d907526107eb5553f25fbd88a8ed0e0d93751d702
2013-01-07 13:52:48|install|mysql-community-server-errormessages|5.5.28-3.14.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|c8356fd4702a7b892e3dc7d84d597bc1249d7364fd6848178eb61f61f0460e91
2013-01-07 13:52:49|install|mysql-community-server-client|5.5.28-3.14.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|3b55dcd53d1a369f4458d356351efa2e9718c9250c478dc409f066253f89939a
# 2013-01-07 13:52:59 mysql-community-server-5.5.28-3.14.1.x86_64.rpm installed ok
# Additional rpm output:
# redirecting to systemctl
# redirecting to systemctl
#
2013-01-07 13:52:59|install|mysql-community-server|5.5.28-3.14.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|307eb4323e142dfdea4008036d27d51d756a454535f6061ae882aec868154f0f
# 2013-01-07 13:52:59 libmysqld18-5.5.28-3.14.1.x86_64.rpm installed ok
# Additional rpm output:
# /sbin/ldconfig: relative path `1' used to build cache
# warning: %postun(libmysqld18-5.5.25-3.12.1.x86_64) scriptlet failed, exit status 1
#
2013-01-07 13:52:59|install|libmysqld18|5.5.28-3.14.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|0eceded852b87577967128e506424eaddc92025e251482f0fd3562718a885bcb
2013-01-12 00:20:45|install|libqt4|4.7.4-19.13.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|3b7d81b248098640e233a9022018478c3b27d31f0ad104e7b0b2d1d70f7c9bec
2013-01-12 00:20:45|install|libfreebl3|3.14.1-9.21.3|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|95b8254e7bd4d1a2653bfc2d7ef5efa25dca47ac9265525f69176d728eea75b0
2013-01-12 00:20:46|install|mozilla-nspr|4.9.4-3.11.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|085753fc6800344694806145c63dc25422dec32cc6a0e2dd3b1f79cc3ae63946
2013-01-12 00:20:46|install|libqt4-sql|4.7.4-19.13.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|8465f834eb3ee5961cf9b2f86e1c30f68479202a4645e96e747657ff93de4906
2013-01-12 00:20:46|install|mozilla-nss-certs|3.14.1-9.21.3|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|40b57f7a4a5bb50e4237abb178dc7673f5959302b9681b322b1476eff3e7da83
2013-01-12 00:20:46|install|libqt4-sql-sqlite|4.7.4-19.13.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|d45b23abae94255c3e3dc5e9b5c97001bfe5e12eef7c2e1693dd6c00bb6efa17
2013-01-12 00:20:47|install|libqt4-qt3support|4.7.4-19.13.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|0a6713dd6b85918df23bf91d9c0033a2eb9f1311c0bb2341fe5023c6fd3cf370
2013-01-12 00:20:47|install|libsoftokn3|3.14.1-9.21.3|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|186fbe61542a5e07dc0cbd8d6997e1d8f563f5fb3203fd52be6259391c2fc468
2013-01-12 00:20:49|install|libqt4-x11|4.7.4-19.13.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|07f3eec828cf7ca18622a8ab5fb131dc7b0323e9d68e005a64669e80bf836c92
2013-01-12 00:20:49|install|mozilla-nss|3.14.1-9.21.3|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|3171fb146e96fbcddc6927d63de864030c9e7077e8b780257c057762e5d98c29
2013-01-12 00:20:54|install|libqt4-devel|4.7.4-19.13.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|2ed626f54fa13dc0fdcb6683a438129202c898cd3e246bb067eb9e1ebf8ca14d
2013-01-12 00:20:57|install|seamonkey|2.15-2.49.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|3a17abe157b42a80b9b86b3debeabd21bc14690a37e6f4fbbfdb061fc283a526
2013-01-12 00:21:08|install|MozillaThunderbird|17.0.2-33.47.2|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|dd2db203d1b315ba03007123d463af36e1101c9b218280cf63eacafaf2314184
# 2013-01-12 00:21:14 MozillaFirefox-18.0-2.58.2.x86_64.rpm installed ok
# Additional rpm output:
# Unknown media type in type 'all/all'
# Unknown media type in type 'all/allfiles'
# Unknown media type in type 'uri/mms'
# Unknown media type in type 'uri/mmst'
# Unknown media type in type 'uri/mmsu'
# Unknown media type in type 'uri/pnm'
# Unknown media type in type 'uri/rtspt'
# Unknown media type in type 'uri/rtspu'
# Unknown media type in type 'interface/x-winamp-skin'
#
2013-01-12 00:21:14|install|MozillaFirefox|18.0-2.58.2|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|20202829209ab532e23b81751d3a5d1d2292b684b6723e8d400ae6d195e19c47
2013-01-12 00:21:17|install|flash-player|11.2.202.261-42.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|fe8018ead425097f15f099d6bdf91241444ecc30926e38e6f50aaf16eb738ddc
2013-01-12 00:21:18|install|flash-player-kde4|11.2.202.261-42.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|74147a32e5de273f95e066d0d08a903d2dee319595eb29921891047fcd37d90b
2013-01-12 00:30:21|install|seamonkey|2.14-2.45.1|x86_64|root@linux-fi3i|Updates-for-openSUSE-12.1-12.1-1.4|2aef2afeaf879c4a3afca3fec3c47c415fdf23feea74ec84b8bed1573b498754
2013-01-12 00:42:52|install|seamonkey|2.15-2.49.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|3a17abe157b42a80b9b86b3debeabd21bc14690a37e6f4fbbfdb061fc283a526
2013-01-12 01:10:32|install|seamonkey|2.15-2.49.1|x86_64|root@linux-fi3i|Updates-for-openSUSE-12.1-12.1-1.4|3a17abe157b42a80b9b86b3debeabd21bc14690a37e6f4fbbfdb061fc283a526
# 2013-01-12 01:13:57 opera-12.12-34.1.x86_64.rpm installed ok
# Additional rpm output:
# Unknown media type in type 'all/all'
# Unknown media type in type 'all/allfiles'
# Unknown media type in type 'uri/mms'
# Unknown media type in type 'uri/mmst'
# Unknown media type in type 'uri/mmsu'
# Unknown media type in type 'uri/pnm'
# Unknown media type in type 'uri/rtspt'
# Unknown media type in type 'uri/rtspu'
# Unknown media type in type 'interface/x-winamp-skin'
#
2013-01-12 01:13:57|install|opera|12.12-34.1|x86_64|root@linux-fi3i|Updates-for-openSUSE-12.1-12.1-1.4|6de319a60ae26c206c25127299e5f47ec51b22ab329db6b879212975290a56a7
2013-01-12 01:13:57|install|opera-kde4|12.12-34.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|06d3cb977a9bd830d918e7610a50ea508eee110367f7bfa65ec56fa3e8d5e735
2013-01-12 01:13:57|install|opera-gtk|12.12-34.1|x86_64||Updates-for-openSUSE-12.1-12.1-1.4|49cef57e4a6f8b4b26b448c14c9f136657cce8d54e8e9bff799fe0e2975b4c5e
2013-01-12 01:48:02|install|libgtksourceview-2_0-0|2.10.5-3.1.2|x86_64||repo-oss|f0d9d430fb28808936e245057e88f157a10ff791
2013-01-12 01:48:04|install|balsa|2.4.10-3.1.2|x86_64|root@linux-fi3i|repo-oss|4aef8a4c1dcefa396f1ce5f9cccbd1463569f5fd
2013-01-12 02:10:44|install|libetpan13|0.58-12.1.2|x86_64||repo-oss|82dd6d156aa0cbbd4f5a7152a884a0ac64e45b84
2013-01-12 02:10:45|install|libpisock9|0.12.5-12.1.4|x86_64||repo-oss|693001e68c6bb0fd634c33145b513498d0169c51
2013-01-12 02:10:45|install|pinentry-gtk2|0.8.1-10.2.2|x86_64||repo-oss|8f2ec56b26e324564006b14aad96675788629adb
2013-01-12 02:10:57|install|claws-mail|3.7.10-3.8.1|x86_64|root@linux-fi3i|Updates-for-openSUSE-12.1-12.1-1.4|c29d4d29c327061326e601b31a9386fb5c2faeaac3f7612cc5069b2ecd307256
Hopefully this will give a hint to someone out there. It shows Opera, that is working ok, I installed that just to get back on the Internet. Seamonkey, Seamonkey mail, Firefox, Thunderbird all crash immediately, Rekonq crashes when I click a bookmark, didn’t try typing in and address, though. And IceWM no longer works, I get a one color screen, usually green if I remember. Weird!
I tried rolling back flash, no change, then firefox, still no change. Tonight I also found that Audacious and mplayer no longer run either. This is looking bad, I’m thinking of wiping the drive and installing 12.2. Just need to back up lots of files first.
On 01/13/2013 04:56 AM, HighBloodSugar wrote:
> I tried rolling back flash, no change, then firefox, still no change.
i’m not experienced/competent to actually decide, but i think the root
of your problem is in “libqt4” updates rolled in on 2013-01-12, which
one (of many) i’d have no idea…and, why it hit your 12.1 and not
everyone on the planet is a mystery too…
why i picked libqt4: i think everything not now working needs qt, and
the Opera (which does work) is running in its gtk form…[maybe]
i think, before i would wipe and reinstall i would open YaST Software
Management, search on libqt and right click each ALREADY installed to
Update (green up arrow with green check mark)… those already installed
are marked with a black check–do NOT start adding green check marks to
newly installed packages!)
that might not help at all…but, i GUESS that something got corrupted
during your update on the 12th . . .
it might be wise to wait a while and let the real gurus evaluate and
comment on what i’ve guessed about…
I only see black check marks. Not sure what you mean - is there a difference between “already installed” and “newly installed” ?
If it helps any, here’s the latest list of apps that stopping working: Seamonkey, Firefox, Thunderbird, Rekonq, Audacious, Mplayer, gFTP, DvdStyler, Bluefish, Grip, EasyTag.
For Bluefish, I get this:
user@linux-fi3i:~> bluefish
(bluefish:4520): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
(bluefish:4520): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
Segmentation fault
gFTP gives just “segmentation fault” - It seems like the problem isn’t isolated to Qt4. I dabble in programming some, and my latest project in Qt4 still compiles and runs. I think K3B uses Qt4, that’s still working.
Here’s what I get trying to run Audacious:
user@linux-fi3i:~> audacious
WARNING: Audacious seems to be already running but is not responding.
audacious: symbol lookup error: audacious: undefined symbol: str_get
And gmplayer:
user@linux-fi3i:~> gmplayer
MPlayer dev-SVN-r35127-4.6-openSUSE Linux 12.1 (x86_64)-Packman (C) 2000-2012 MPlayer Team
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
MPlayer interrupted by signal 11 in module: unknown
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible bug.
On 01/13/2013 09:36 PM, HighBloodSugar wrote:
> I only see black check marks. Not sure what you mean - is there a
> difference between “already installed” and “newly installed” ?
sorry i confused you: update all of those which are now
installed…that is to say: all of those with black check marks, right
click and change to update (green check marks with a little up arrow)…
do not add new stuff (if it does not already have a black check mark,
leave it alone.)
what will happen is that all which you now have installed will be
reinstalled, overwritten…the theory is that something is now
garbled and reinstalling may solve the problem…
or it may not…but, it is pretty easy to try it out and see…and a
lot quicker and easier than a full up "I’m thinking of wiping the drive
and installing . . . "
