Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
I honestly don't know whether I have ever done this in konqueror in this install. Firefox can access the page so it's not a system-wide problem.
Anne
Quoting Anne Wilson cannewilson@googlemail.com:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
just a shot in the dark: SSL trouble with konqueror in kde4 maybe?
Andreas
On Monday 02 February 2009 15:58:45 Andreas Petzold wrote:
Quoting Anne Wilson cannewilson@googlemail.com:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
just a shot in the dark: SSL trouble with konqueror in kde4 maybe?
Dunno - the Crypto settings in konqueror look much the same as those on the Mandriva laptop, though that is 4.1.3.
Actually, I didn't ask konqueror to do this. I launched dolphin, which gave me a very quick message that it didn't handle web addresses, and promptly closed, opening konqueror to handle it! I've tried opening konqueror cleanly, in case that was part of the problem, but it's just the same.
Anne
On Monday 02 February 2009 18:57:42 Anne Wilson wrote:
On Monday 02 February 2009 15:58:45 Andreas Petzold wrote:
Quoting Anne Wilson cannewilson@googlemail.com:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
Try creating a dummy user and see if that works. If it doesn't I guess a bug report is in order.
Eli
On Monday 02 February 2009 15:58:45 Andreas Petzold wrote:
Quoting Anne Wilson cannewilson@googlemail.com:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
just a shot in the dark: SSL trouble with konqueror in kde4 maybe?
Actually, what I said is not quite accurate. It connects as far as giving me the login page. It's when the login is sent that I get the blank page, with 'Page Loaded' in the status line.
Anne
On Monday 02 February 2009 19:07:03 Anne Wilson wrote:
On Monday 02 February 2009 15:58:45 Andreas Petzold wrote:
Quoting Anne Wilson cannewilson@googlemail.com:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
just a shot in the dark: SSL trouble with konqueror in kde4 maybe?
Actually, what I said is not quite accurate. It connects as far as giving me the login page. It's when the login is sent that I get the blank page, with 'Page Loaded' in the status line.
Anne
Does your router have a java based interface. If so is Konqeror pointing to the right Java Virtual Machine.
But like I said in a previous post. Try creating a dummy user and see if it works.
Eli
On Monday 02 February 2009 17:15:01 Eli Wapniarski wrote:
On Monday 02 February 2009 19:07:03 Anne Wilson wrote:
On Monday 02 February 2009 15:58:45 Andreas Petzold wrote:
Quoting Anne Wilson cannewilson@googlemail.com:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
just a shot in the dark: SSL trouble with konqueror in kde4 maybe?
Actually, what I said is not quite accurate. It connects as far as giving me the login page. It's when the login is sent that I get the blank page, with 'Page Loaded' in the status line.
Anne
Does your router have a java based interface. If so is Konqeror pointing to the right Java Virtual Machine.
No, I'm pretty sure that there's nothing like that.
But like I said in a previous post. Try creating a dummy user and see if it works.
The second user has the same problem, so I lean heavily towards the bug theory. The only thing is, I hesitate to file a bug unless someone else also has problems.
Anne
On Monday 02 February 2009 20:51:31 Anne Wilson wrote:
On Monday 02 February 2009 17:15:01 Eli Wapniarski wrote:
On Monday 02 February 2009 19:07:03 Anne Wilson wrote:
On Monday 02 February 2009 15:58:45 Andreas Petzold wrote:
Quoting Anne Wilson cannewilson@googlemail.com:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
just a shot in the dark: SSL trouble with konqueror in kde4 maybe?
Actually, what I said is not quite accurate. It connects as far as giving me the login page. It's when the login is sent that I get the blank page, with 'Page Loaded' in the status line.
Anne
Does your router have a java based interface. If so is Konqeror pointing to the right Java Virtual Machine.
No, I'm pretty sure that there's nothing like that.
But like I said in a previous post. Try creating a dummy user and see if it works.
The second user has the same problem, so I lean heavily towards the bug theory. The only thing is, I hesitate to file a bug unless someone else also has problems.
Anne
Maybe you can look things up or ask over at KDE's forums. Doctor Google is also a good bet. However, the sooner the bug is registered the sooner the issue gets looked into. The sooner either you will be provided with a solution or the sooner the possibility of the bug getting fixed.
Eli
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anne Wilson wrote:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
I honestly don't know whether I have ever done this in konqueror in this install. Firefox can access the page so it's not a system-wide problem.
Anne
In order to access my router, I have to provide the username. https://user@192.168.1.1. Should get a password prompt at this point.
- --Ben
On Monday 02 February 2009 17:34:31 Ben Boeckel wrote:
Anne Wilson wrote:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
I honestly don't know whether I have ever done this in konqueror in this install. Firefox can access the page so it's not a system-wide problem.
Anne
In order to access my router, I have to provide the username. https://user@192.168.1.1. Should get a password prompt at this point.
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Anne
On Monday 02 February 2009 19:52:45 Anne Wilson wrote:
On Monday 02 February 2009 17:34:31 Ben Boeckel wrote:
Anne Wilson wrote:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
I honestly don't know whether I have ever done this in konqueror in this install. Firefox can access the page so it's not a system-wide problem.
Anne
In order to access my router, I have to provide the username. https://user@192.168.1.1. Should get a password prompt at this point.
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Anne
It looks like I have the same problem, with my Sitecom router. After entering the IP-adress I get a dialog box where I can fill in my name and password. When I press OK the dialog box re-appears, but now i can't enter my name and password. I have to press cancel and a page with an unauthorized message appears. But when I press reload i see my routers home page.
Martin
On Monday 02 February 2009 19:04:04 Martin Kho wrote:
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Anne
It looks like I have the same problem, with my Sitecom router. After entering the IP-adress I get a dialog box where I can fill in my name and password. When I press OK the dialog box re-appears, but now i can't enter my name and password. I have to press cancel and a page with an unauthorized message appears. But when I press reload i see my routers home page.
That gave me hope, for a moment. However, it didn't work for me - I just got back the login page that is unusable.
I think a recent update has caused some problems. I won't mix the thread, but I've got another problem that I think, in fact I'm almost sure, wasn't there yesterday.
Anne
On Monday 02 February 2009 19:04:04 Martin Kho wrote:
On Monday 02 February 2009 19:52:45 Anne Wilson wrote:
On Monday 02 February 2009 17:34:31 Ben Boeckel wrote:
Anne Wilson wrote:
Most odd. Entering the IP for the router's login immediately brings up a blank page with Done on the status line. I have to wait for it to time out before I can access it from another box. Any ideas what could cause this?
I honestly don't know whether I have ever done this in konqueror in this install. Firefox can access the page so it's not a system-wide problem.
In order to access my router, I have to provide the username. https://user@192.168.1.1. Should get a password prompt at this point.
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
It looks like I have the same problem, with my Sitecom router. After entering the IP-adress I get a dialog box where I can fill in my name and password. When I press OK the dialog box re-appears, but now i can't enter my name and password. I have to press cancel and a page with an unauthorized message appears. But when I press reload i see my routers home page.
I am also seeing the behaviour, time to check kde.bugs
Colin
Hi,
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Netgear? I am using a DG834GTB and tried if I can confirm this. I also get the prompt and when entering the correct password it is just showing the page that was shown before. Nothing happens. Using firefox and everything works fine. Don't know what actually went wrong, nor when it broke, cause I am nearly never using the konqueror. But I think it sounds like a bug, if we have any clue whats wrong we should write a bug report. I just tried to get konsole output, but nothing appear. Looks like konqueror is using some kind of wrapper like amarok. Might be interesting to see if he actually tries.
Best regards, Florian
On Tuesday 03 February 2009 07:43:18 Florian Sievert wrote:
Hi,
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Netgear? I am using a DG834GTB and tried if I can confirm this. I also get the prompt and when entering the correct password it is just showing the page that was shown before. Nothing happens. Using firefox and everything works fine. Don't know what actually went wrong, nor when it broke, cause I am nearly never using the konqueror. But I think it sounds like a bug, if we have any clue whats wrong we should write a bug report. I just tried to get konsole output, but nothing appear. Looks like konqueror is using some kind of wrapper like amarok. Might be interesting to see if he actually tries.
OK, so I'm not going insane :-) Now, any ideas how we can investigate this? I'll do some attempts while tailing log-files this afternoon (which log, I wonder?)
Anne
On Tuesday 03 February 2009 08:57:08 Anne Wilson wrote:
On Tuesday 03 February 2009 07:43:18 Florian Sievert wrote:
Hi,
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Netgear? I am using a DG834GTB and tried if I can confirm this. I also get the prompt and when entering the correct password it is just showing the page that was shown before. Nothing happens. Using firefox and everything works fine. Don't know what actually went wrong, nor when it broke, cause I am nearly never using the konqueror. But I think it sounds like a bug, if we have any clue whats wrong we should write a bug report. I just tried to get konsole output, but nothing appear. Looks like konqueror is using some kind of wrapper like amarok. Might be interesting to see if he actually tries.
OK, so I'm not going insane :-) Now, any ideas how we can investigate this? I'll do some attempts while tailing log-files this afternoon (which log, I wonder?)
Anne
In .xsessions-errors I see:
kio_http(2854)/kio (kioslave) KIO::SlaveBase::openPasswordDialog: Can't communicate with kded_kpasswdserver (for queryAuthInfo)!
Martin
On Tuesday 03 February 2009 09:56:10 Martin Kho wrote:
On Tuesday 03 February 2009 08:57:08 Anne Wilson wrote:
On Tuesday 03 February 2009 07:43:18 Florian Sievert wrote:
Hi,
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Netgear? I am using a DG834GTB and tried if I can confirm this. I also get the prompt and when entering the correct password it is just showing the page that was shown before. Nothing happens. Using firefox and everything works fine. Don't know what actually went wrong, nor when it broke, cause I am nearly never using the konqueror. But I think it sounds like a bug, if we have any clue whats wrong we should write a bug report. I just tried to get konsole output, but nothing appear. Looks like konqueror is using some kind of wrapper like amarok. Might be interesting to see if he actually tries.
OK, so I'm not going insane :-) Now, any ideas how we can investigate this? I'll do some attempts while tailing log-files this afternoon (which log, I wonder?)
Anne
In .xsessions-errors I see:
kio_http(2854)/kio (kioslave) KIO::SlaveBase::openPasswordDialog: Can't communicate with kded_kpasswdserver (for queryAuthInfo)!
That seems to imply that you failed to authenticate, whereas both Kishore (kde@mail.kde.org list) and I have clear evidence that our login succeeded. I don't appear to have an .xsessions-errors but I can find nothing in any of the logs that refers to this. More than that, I carefully noted the time of an attempt, then checked /var/log/ - not a single file had a time-stamp matching that attempt.
Anne
On Tuesday 03 February 2009 11:36:53 Anne Wilson wrote:
On Tuesday 03 February 2009 09:56:10 Martin Kho wrote:
On Tuesday 03 February 2009 08:57:08 Anne Wilson wrote:
On Tuesday 03 February 2009 07:43:18 Florian Sievert wrote:
Hi,
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Netgear? I am using a DG834GTB and tried if I can confirm this. I also get the prompt and when entering the correct password it is just showing the page that was shown before. Nothing happens. Using firefox and everything works fine. Don't know what actually went wrong, nor when it broke, cause I am nearly never using the konqueror. But I think it sounds like a bug, if we have any clue whats wrong we should write a bug report. I just tried to get konsole output, but nothing appear. Looks like konqueror is using some kind of wrapper like amarok. Might be interesting to see if he actually tries.
OK, so I'm not going insane :-) Now, any ideas how we can investigate this? I'll do some attempts while tailing log-files this afternoon (which log, I wonder?)
Anne
In .xsessions-errors I see:
kio_http(2854)/kio (kioslave) KIO::SlaveBase::openPasswordDialog: Can't communicate with kded_kpasswdserver (for queryAuthInfo)!
That seems to imply that you failed to authenticate, whereas both Kishore (kde@mail.kde.org list) and I have clear evidence that our login succeeded. I don't appear to have an .xsessions-errors but I can find nothing in any of the logs that refers to this. More than that, I carefully noted the time of an attempt, then checked /var/log/ - not a single file had a time-stamp matching that attempt.
Anne
You don't have ~/.xsession-errors file? So you don't see any other processes crashing e.g. /usr/bin/nepomukservicestub :-)
Martin
On Tuesday 03 February 2009 10:50:19 Martin Kho wrote:
On Tuesday 03 February 2009 11:36:53 Anne Wilson wrote:
On Tuesday 03 February 2009 09:56:10 Martin Kho wrote:
On Tuesday 03 February 2009 08:57:08 Anne Wilson wrote:
On Tuesday 03 February 2009 07:43:18 Florian Sievert wrote:
Hi,
Yes, I wrote the first description from memory, and it was inaccurate. I get the password prompt. It's the next screen, the front page of the Netgear configuration screens, that I don't get.
Netgear? I am using a DG834GTB and tried if I can confirm this. I also get the prompt and when entering the correct password it is just showing the page that was shown before. Nothing happens. Using firefox and everything works fine. Don't know what actually went wrong, nor when it broke, cause I am nearly never using the konqueror. But I think it sounds like a bug, if we have any clue whats wrong we should write a bug report. I just tried to get konsole output, but nothing appear. Looks like konqueror is using some kind of wrapper like amarok. Might be interesting to see if he actually tries.
OK, so I'm not going insane :-) Now, any ideas how we can investigate this? I'll do some attempts while tailing log-files this afternoon (which log, I wonder?)
Anne
In .xsessions-errors I see:
kio_http(2854)/kio (kioslave) KIO::SlaveBase::openPasswordDialog: Can't communicate with kded_kpasswdserver (for queryAuthInfo)!
That seems to imply that you failed to authenticate, whereas both Kishore (kde@mail.kde.org list) and I have clear evidence that our login succeeded. I don't appear to have an .xsessions-errors but I can find nothing in any of the logs that refers to this. More than that, I carefully noted the time of an attempt, then checked /var/log/ - not a single file had a time-stamp matching that attempt.
Anne
You don't have ~/.xsession-errors file? So you don't see any other processes crashing e.g. /usr/bin/nepomukservicestub :-)
No - but then I haven't given much attention to this yet. Nepomuk seems to be ok, but Strigi isn't working. I just see "Failed to contact Strigi indexer (No such method 'currentFolder' in interface 'org.kde.nepomuk.Strigi' at object path '/nepomukstrigiservice' (signature ''))" on the configuration page.
Anne
Anne Wilson wrote:
No - but then I haven't given much attention to this yet. Nepomuk seems to be ok, but Strigi isn't working. I just see "Failed to contact Strigi indexer (No such method 'currentFolder' in interface 'org.kde.nepomuk.Strigi' at object path '/nepomukstrigiservice' (signature ''))" on the configuration page.
Strigi (or at least Nepomuk's version of it, which is what KDE is now using) is disabled by default if you have only the Redland backend (which is the current situation in Fedora because it's a lot of work to package Sesame2 properly - our guidelines forbid just using the binary JARs, everything must be built from source). Maybe there's even some hardcoded disabling, if so we should fix it as that would be a regression from 4.1.
Kevin Kofler
On Tuesday 03 February 2009 17:07:58 Kevin Kofler wrote:
Anne Wilson wrote:
No - but then I haven't given much attention to this yet. Nepomuk seems to be ok, but Strigi isn't working. I just see "Failed to contact Strigi indexer (No such method 'currentFolder' in interface 'org.kde.nepomuk.Strigi' at object path '/nepomukstrigiservice' (signature ''))" on the configuration page.
Strigi (or at least Nepomuk's version of it, which is what KDE is now using) is disabled by default if you have only the Redland backend (which is the current situation in Fedora because it's a lot of work to package Sesame2 properly - our guidelines forbid just using the binary JARs, everything must be built from source). Maybe there's even some hardcoded disabling, if so we should fix it as that would be a regression from 4.1.
Thanks, Kevin. That explains that, then.
Anne
Anne Wilson wrote:
On Tuesday 03 February 2009 17:07:58 Kevin Kofler wrote:
Strigi (or at least Nepomuk's version of it, which is what KDE is now using) is disabled by default if you have only the Redland backend (which is the current situation in Fedora because it's a lot of work to package Sesame2 properly - our guidelines forbid just using the binary JARs, everything must be built from source). Maybe there's even some hardcoded disabling, if so we should fix it as that would be a regression from 4.1.
Thanks, Kevin. That explains that, then.
Try enabling Strigi in systemsettings - does it work? If not, we have some patching to do. It makes sense to disable it by default (it's a huge CPU hog with Redland), but it should be possible to enable it.
Kevin Kofler
On Wednesday 04 February 2009 11:45:27 Kevin Kofler wrote:
Anne Wilson wrote:
On Tuesday 03 February 2009 17:07:58 Kevin Kofler wrote:
Strigi (or at least Nepomuk's version of it, which is what KDE is now using) is disabled by default if you have only the Redland backend (which is the current situation in Fedora because it's a lot of work to package Sesame2 properly - our guidelines forbid just using the binary JARs, everything must be built from source). Maybe there's even some hardcoded disabling, if so we should fix it as that would be a regression from 4.1.
Thanks, Kevin. That explains that, then.
Try enabling Strigi in systemsettings - does it work? If not, we have some patching to do. It makes sense to disable it by default (it's a huge CPU hog with Redland), but it should be possible to enable it.
Hi, Kevin. It's in SystemSettings that I see "Failed to contact Strigi indexer (No such method 'currentFolder' in interface 'org.kde.nepomuk.Strigi' at object path '/nepomukstrigiservice' (signature ''))" - so no, it doesn't work.
Anne
Anne Wilson wrote:
Hi, Kevin. It's in SystemSettings that I see "Failed to contact Strigi indexer (No such method 'currentFolder' in interface 'org.kde.nepomuk.Strigi' at object path '/nepomukstrigiservice' (signature ''))" - so no, it doesn't work.
Systemsettings always reported warnings like this if the indexer was not already running, but you should be able to turn it on there.
Kevin Kofler
On Wednesday 04 February 2009 13:18:13 Kevin Kofler wrote:
Anne Wilson wrote:
Hi, Kevin. It's in SystemSettings that I see "Failed to contact Strigi indexer (No such method 'currentFolder' in interface 'org.kde.nepomuk.Strigi' at object path '/nepomukstrigiservice' (signature ''))" - so no, it doesn't work.
Systemsettings always reported warnings like this if the indexer was not already running, but you should be able to turn it on there.
Well, I checked the box yesterday (day before?) and it still is checked. The warning is still there, and I haven't seen anything that makes me think it is running. It obviously isn't running as a service, so how can I check its status? Or is that statement sufficient to say that it's not running at all?
Anne
Anne Wilson wrote:
Well, I checked the box yesterday (day before?) and it still is checked. The warning is still there, and I haven't seen anything that makes me think it is running. It obviously isn't running as a service, so how can I check its status? Or is that statement sufficient to say that it's not running at all?
Looks indeed like it is sufficient. This should get fixed, Strigi should not refuse to run entirely with the Redland backend. That said, I remember now that in 4.2 prereleases it was crashing somewhere inside RDF-related code, so maybe that's why they disabled it. (They didn't want to fix the Redland code so they just disabled it. :-/ )
Kevin Kofler
I wrote:
Looks indeed like it is sufficient. This should get fixed, Strigi should not refuse to run entirely with the Redland backend. That said, I remember now that in 4.2 prereleases it was crashing somewhere inside RDF-related code, so maybe that's why they disabled it. (They didn't want to fix the Redland code so they just disabled it. :-/ )
For reference, here's the crash: https://bugzilla.redhat.com/show_bug.cgi?id=478509
I think upstream didn't even know about this when they disabled it, it was just for performance reasons. But it does mean that's another problem we'd have to deal with if we want to support Strigi on Redland. Sigh...
Kevin Kofler
I wrote:
For reference, here's the crash: https://bugzilla.redhat.com/show_bug.cgi?id=478509
I think upstream didn't even know about this when they disabled it, it was just for performance reasons. But it does mean that's another problem we'd have to deal with if we want to support Strigi on Redland. Sigh...
Hmmm, that said, that bug report is for strigidaemon, not for the Nepomuk Strigi service, so it may be unrelated entirely.
I think we should just remove the hardcoded disabling and see what happens.
Kevin Kofler
Kevin Kofler wrote:
I wrote:
For reference, here's the crash: https://bugzilla.redhat.com/show_bug.cgi?id=478509
I think upstream didn't even know about this when they disabled it, it was just for performance reasons. But it does mean that's another problem we'd have to deal with if we want to support Strigi on Redland. Sigh...
Hmmm, that said, that bug report is for strigidaemon, not for the Nepomuk Strigi service, so it may be unrelated entirely.
I think we should just remove the hardcoded disabling and see what happens.
How about at least talking to the nepomuk(strigi?) folks first? (Not that I expect their perspective to be swayed by ours, but still...)
-- Rex
On Wednesday 04 February 2009 11:45:27 Kevin Kofler wrote:
Try enabling Strigi in systemsettings - does it work? If not, we have some patching to do. It makes sense to disable it by default (it's a huge CPU hog with Redland), but it should be possible to enable it.
When you say it is a huge CPU hog, do you mean when doing the initial indexing, or always? I'm prepared to let it index overnight, but I don't have sufficient spare CPU, IMO, if it continues to hog.
Anne
Anne Wilson wrote:
On Wednesday 04 February 2009 11:45:27 Kevin Kofler wrote:
Try enabling Strigi in systemsettings - does it work? If not, we have some patching to do. It makes sense to disable it by default (it's a huge CPU hog with Redland), but it should be possible to enable it.
When you say it is a huge CPU hog, do you mean when doing the initial indexing, or always?
In my experience, indexing primarily, when idle, it's ok.
-- Rex
Kevin Kofler wrote:
Strigi (or at least Nepomuk's version of it, which is what KDE is now using) is disabled by default if you have only the Redland backend (which is the current situation in Fedora because it's a lot of work to package Sesame2 properly - our guidelines forbid just using the binary JARs, everything must be built from source). Maybe there's even some hardcoded disabling, if so we should fix it as that would be a regression from 4.1.
The disabling is hardcoded indeed. :-( http://bugs.kde.org/show_bug.cgi?id=161380 http://websvn.kde.org/?view=rev&revision=852681
This is broken. This really ought to be configurable. (What happened to the existing setting from 4.1? Is it ignored?) It's also a feature regression from 4.1.
Kevin Kofler
-
Andreas Petzold -
Anne Wilson -
Ben Boeckel -
Colin J Thomson -
Eli Wapniarski -
Florian Sievert -
Kevin Kofler -
Martin Kho -
Rex Dieter