On 02/14/2012 08:53 AM, Vahis wrote:
> So there was trouble because a newer software package, not because of
> zypper.
correct. zypper does very well what it is told do.
and if you unintentionally tell it to install a conflicting package, it
will…
the ‘secret’ is knowing and managing the repos and paying attention to
the info zypper offers before you decide to say yes or no to any and
every offered instal, patch, update.
unfortunately we sometimes have folks come in to openSUSE with a
background of running a system where 30,000 programmers spend months
putting together and testing testing testing huge supplemental updates,
and their machine doesn’t even ASK if you want the update…it just flows…
so, when they ‘zypper up’ and see half a terminal full of hard to
understand stuff they just click y and press enter…with 10, 20, 30
active repos.
now i know most here would not do that…but, some who read tomorrow might…
“zypper patch” removes most of the possibilities of problems that can be
encountered by a “zypper up”
nothing wrong with zypper…but there is danger between the keyboard
and chair.
I’m not using this machine for trading per se, but I need it to display some extra info on an extra screen and also to collect some information for processing in off trading hours, or at least I think I do.
Here in Thailand our market has seen a very nice recovery since the floods four months ago and got its rating upgraded to “promising emerging market” or some such. Since New Year foreign money has been flowing in like there’s no tomorrow and so far people only worry that they’d be left with expensive stocks if foreigners suddenly pull out.
Never mind.
now, if XYZ 1.2.3-b requires a new KDE library 4.8-b (and you have
installed KDE lib4.8-a) “zypper up” will offer to install a new XYZ and the KDE lib-b, and, it will probably warn you about conflicts and
ask if you wanna install anyway, and if you blink and say yes, you will
soon be the proud owner of a fully functioning XYZ-b with the prettier
icon running happily in the slightly flashier KDE-b!
So the danger is that KDE-b (from the same repo as XYZ-b, I assume) overwrite KDE-a that came with the install and an unknown number of perfectly working programs might stop working as a result?
Generally I assume that KDE-b would be perfectly compatible with earlier versions, at least from Pacman.
I get the same now that Firefox has updated to 10 automatically on OpenSUSE 12.1 (64 bit) it falls over after starting tried altering the java plugin to no avail. Seems to bring down Thunderbird as well though that is unaffected if running without Firefox. I do not have this problem on an OpenSuse 11.4 (64 bit) box.
Once you are logged in open KELiberty window from the menu and click through certificate alert, do not add it permanently, it works for one session only, and on the first time it probably won’t let you in so you’d have to close that window, delete the certificate from Edit-Preferences-Advanced-Encryption-View Certificates and open the window and add the certificate once again. After that it works fine, at least until Firefox is reinstalled.
Then there’s Terms of Use dialog with Agree button and then you finally get to the page itself. It will load html first, then initialize applets, there are four or five on that page, and once the applets start loading stuff Firefox crashes.
BTW, all other browsers get to this stage fine but applets don’t load anything off the internet, I think due to more security warnings, there’s a bit less fuss in IE but only marginally.
I’ve got this behavior confirmed on two machines with Firefox 10.
I’d love to check out some other sites that work for you but nothing comes to mind, someone mentioned to me that Webex works with their FF10 but that requires opening an account, too, so I can’t check it easily. NYTimes Sudoku doesn’t work for me regardless of FF version.
But did it crash the Firefox, Caf4926? And have you updated to FF10? Earlier in this thread you said you are keeping FF9 for now.
As for the site itself - it’s a legacy Java that won’t ever be updated. All new tools are, unfortunately, Windows only, and they work and look much better and do not throw any warnings. There’s also a Flash app that I can access but it’s uniform for all local brokers and it lacks some basic features available even in this old Java, like building 5 min charts with a bunch of indicators.
Starting with an empty profile is a good idea, I guess simply renaming .mozilla folder in home to something else would do the trick.
Locked up is a different issue, I guess, FF9 on my machines works fine, on the second visit it’s only one security warning from FF itself as I believe I clicked java warnings to “always allow”.
I think that this is the same problem that I am having with Barclays Bank (UK) - all worked well until recently when they upgraded their site at almost the same moment that YOU gave me FF10. Symptoms are that log-in and authentication succeed, but clicking on any main-menu item such as “show statements” results in a spinning wheel (that I assume is to indicate some Ajax transaction) that never finishes, the browser remains unresponsive and only way out is to kill it.
After (literally) hours on hold the call centre in India (who kept telling me to use Internet Explorer!) finally put me through to someone in Coventry (England) who said this was the first such issue they had seen following their update, but that FF10 was supposed to be supported. They advised using Google Chromium, which I did and it seems to work for me, though I don’t want to use it for anything else.
It isn’t secret - it’s specifically flagged as viewable by external
customers.
You may have to login in order to see it, though.
But if you can’t see it, there’s essentially no information there other
than the report itself and that it’s been assigned - it was opened on Feb
3, and is a high priority bug, so it’s likely to be addressed fairly
quickly.
Am 20.02.2012 21:19, schrieb Jim Henderson:
> On Mon, 20 Feb 2012 19:36:03 +0000, MQ wrote:
> It isn’t secret - it’s specifically flagged as viewable by external
> customers.
Access denied even if logged in.
>
> You may have to login in order to see it, though.
>
> But if you can’t see it, there’s essentially no information there other
> than the report itself and that it’s been assigned - it was opened on Feb
> 3, and is a high priority bug, so it’s likely to be addressed fairly
> quickly.
Wolfgang Rosenauer already added a comment to make it public. I think
the point is transparency not if there is really valid content.
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.8.0 |
nVidia ION | 3GB Ram
On Mon, 20 Feb 2012 20:38:09 +0000, Martin Helm wrote:
> Am 20.02.2012 21:19, schrieb Jim Henderson:
>> On Mon, 20 Feb 2012 19:36:03 +0000, MQ wrote:
>> It isn’t secret - it’s specifically flagged as viewable by external
>> customers.
>
> Access denied even if logged in.
Interesting, as I look at it I see that it’s flagged “external”, so it
should be visible. I’ll see if I can find out why you can’t see it.
>> You may have to login in order to see it, though.
>>
>> But if you can’t see it, there’s essentially no information there other
>> than the report itself and that it’s been assigned - it was opened on
>> Feb 3, and is a high priority bug, so it’s likely to be addressed
>> fairly quickly.
> Wolfgang Rosenauer already added a comment to make it public. I think
> the point is transparency not if there is really valid content.
In any event, what I posted is the current status - opened and assigned
but nothing more.
I was logged in, though because this was as an openSuSE member rather than as a Suse employee, it is hidden from me. It seems to happen rather frequently that bugs that I report or follow find themselves blocked in this way - and all because bugzilla doesn’t flag this when someone closes one bug as duplicate of another.
But if you can’t see it, there’s essentially no information there other
than the report itself and that it’s been assigned - it was opened on Feb
3, and is a high priority bug, so it’s likely to be addressed fairly
quickly.
Pleased to hear it. Though I should also say that I can’t see the connection between the bug report and the problems reported in this thread, I’ll hope it fixes the problems in this thread.
>> But if you can’t see it, there’s essentially no information there other
>> than the report itself and that it’s been assigned - it was opened on
>> Feb 3, and is a high priority bug, so it’s likely to be addressed
>> fairly quickly.
>
> Pleased to hear it. Though I should also say that I can’t see the
> connection between the bug report and the problems reported in this
> thread, I’ll hope it fixes the problems in this thread.
I think the connection is that the bug you can’t see covers multiple
aspects of the KDE integration of Firefox. I haven’t read this entire
thread, but if the crash is related to KDE integration (which seems
logical just given that the bug Carl opened is referenced and that’s what
it’s essentially about), then that would explain the connection.
have folks come in to openSUSE with a