Hi, The update seems to have broke KM somehow. It loaded normally when I turned on my laptop, but when I tried to log in, the user/password box disappeared for a moment, the screen flickered, and it was asking for my user and password. I tried several more times, and even typed the wrong password on purpose. It seems to pick up on the wrong password okay (displays the login failed message), but if the password is correct, it exhibits the behavior I described.
I had to kill kdm/Xorg, login via CLI, then run startx to get into TDE. Everything else seems fine, it's just kdm that seems to be affected.
-- Kristopher Gamrat
On Monday 05 of March 2012 04:02:36 Kristopher Gamrat wrote:
Hi, The update seems to have broke KM somehow. It loaded normally when I turned on my laptop, but when I tried to log in, the user/password box disappeared for a moment, the screen flickered, and it was asking for my user and password. I tried several more times, and even typed the wrong password on purpose. It seems to pick up on the wrong password okay (displays the login failed message), but if the password is correct, it exhibits the behavior I described.
I had to kill kdm/Xorg, login via CLI, then run startx to get into TDE. Everything else seems fine, it's just kdm that seems to be affected.
-- Kristopher Gamrat
Check before logging the selected type sesssion. I do not know why, but for some reason the session is renamed to TDE. Therefore, before the first re-select the name of the session.
Slávek --
Dne po 5. března 2012 Kristopher Gamrat napsal(a):
Hi, The update seems to have broke KM somehow. It loaded normally when I turned on my laptop, but when I tried to log in, the user/password box disappeared for a moment, the screen flickered, and it was asking for my user and password. I tried several more times, and even typed the wrong password on purpose. It seems to pick up on the wrong password okay (displays the login failed message), but if the password is correct, it exhibits the behavior I described.
I had to kill kdm/Xorg, login via CLI, then run startx to get into TDE. Everything else seems fine, it's just kdm that seems to be affected.
-- Kristopher Gamrat
Now I know why it is broken starting TDE as a "default" session!
The updated startkde script (according to bug #675) for determining the TDE path use $0. But if the session is running as a "default", then $0 instead of /opt/trinity/bin/startkde returns /usr/bin/x-session-manager, from which startkde does not detect anything useful.
Therefore, I prepared a patch that adds readlink for canonization.
Unfortunately I will have to update packages kdebase again... and quickly :(
In any case, thank you for the "kick" :)
Slávek --
On Monday 05 March 2012 03:16:43 pm Slávek Banko wrote:
Dne po 5. března 2012 Kristopher Gamrat napsal(a):
Hi, The update seems to have broke KM somehow. It loaded normally when I turned on my laptop, but when I tried to log in, the user/password box disappeared for a moment, the screen flickered, and it was asking for my user and password. I tried several more times, and even typed the wrong password on purpose. It seems to pick up on the wrong password okay (displays the login failed message), but if the password is correct, it exhibits the behavior I described.
I had to kill kdm/Xorg, login via CLI, then run startx to get into TDE. Everything else seems fine, it's just kdm that seems to be affected.
-- Kristopher Gamrat
Now I know why it is broken starting TDE as a "default" session!
The updated startkde script (according to bug #675) for determining the TDE path use $0. But if the session is running as a "default", then $0 instead of /opt/trinity/bin/startkde returns /usr/bin/x-session-manager, from which startkde does not detect anything useful.
Therefore, I prepared a patch that adds readlink for canonization.
Unfortunately I will have to update packages kdebase again... and quickly :(
In any case, thank you for the "kick" :)
I would never kick you OR the tires! Just this stupid thing that "pretends" to be a laptop ;-)
Now to jump over to PIM, I have a bug report there. This one also does not occur in the official packages, hence my reporting it here. This one specifically affects SMTP support in Kmail. Whenever I try to send an email (Kmail or Korganizer), it does not send it. when I click on the up-arrow for the progress report and try to re-send, it shows up with an unrecognized protocol. I normally use port 587 with TLS, though I have also tried 465 with SSL (these are the Gmail settings, IIRC one of these is different on Gmail than on most email systems). I can't try on port 25, neither Gmail nor my ISP will allow it, and Gmail does not allow unsecure access.
For troubleshooting, I tried searching around ~/.trinity/share/* for Kmail-related stuff, and I removed everything I found, then logging out then back in, and re-setting my SMTP settings, with both port 587/TLS and 465/SSL, and they still would not work.
IMAP seems fine, I have not tried POP3.
Now to jump over to PIM, I have a bug report there. This one also does not occur in the official packages, hence my reporting it here. This one specifically affects SMTP support in Kmail. Whenever I try to send an email (Kmail or Korganizer), it does not send it. when I click on the up-arrow for the progress report and try to re-send, it shows up with an unrecognized protocol. I normally use port 587 with TLS, though I have also tried 465 with SSL (these are the Gmail settings, IIRC one of these is different on Gmail than on most email systems). I can't try on port 25, neither Gmail nor my ISP will allow it, and Gmail does not allow unsecure access.
For troubleshooting, I tried searching around ~/.trinity/share/* for Kmail-related stuff, and I removed everything I found, then logging out then back in, and re-setting my SMTP settings, with both port 587/TLS and 465/SSL, and they still would not work.
IMAP seems fine, I have not tried POP3.
Did you build with -DWITH_SASL=ON?
Darrell
On Tue, Mar 6, 2012 at 1:03 AM, Darrell Anderson humanreadable@yahoo.com wrote:
Now to jump over to PIM, I have a bug report there. This one also does not occur in the official packages, hence my reporting it here. This one specifically affects SMTP support in Kmail. Whenever I try to send an email (Kmail or Korganizer), it does not send it. when I click on the up-arrow for the progress report and try to re-send, it shows up with an unrecognized protocol. I normally use port 587 with TLS, though I have also tried 465 with SSL (these are the Gmail settings, IIRC one of these is different on Gmail than on most email systems). I can't try on port 25, neither Gmail nor my ISP will allow it, and Gmail does not allow unsecure access.
For troubleshooting, I tried searching around ~/.trinity/share/* for Kmail-related stuff, and I removed everything I found, then logging out then back in, and re-setting my SMTP settings, with both port 587/TLS and 465/SSL, and they still would not work.
IMAP seems fine, I have not tried POP3.
Did you build with -DWITH_SASL=ON?
No. I didn't build at all. I am using Slavek's packages. That's why I'm reporting it here.
-- Kristopher Gamrat
Did you build with -DWITH_SASL=ON?
No. I didn't build at all. I am using Slavek's packages. That's why I'm reporting it here.
Perhaps forward that to him. I got burned by that too and the default is OFF. Not a good default. :) We probably should patch that.
Darrell
Dne út 6. března 2012 Darrell Anderson napsal(a):
Did you build with -DWITH_SASL=ON?
Darrell
Packages are compiled with the parameters that were in official releases - in debian/rules is shown in DEB_CMAKE_EXTRA_FLAGS -WITH_SASL="ON".
Slávek --
Dne út 6. března 2012 Kristopher Gamrat napsal(a):
I would never kick you OR the tires! Just this stupid thing that "pretends" to be a laptop ;-)
Now to jump over to PIM, I have a bug report there. This one also does not occur in the official packages, hence my reporting it here. This one specifically affects SMTP support in Kmail. Whenever I try to send an email (Kmail or Korganizer), it does not send it. when I click on the up-arrow for the progress report and try to re-send, it shows up with an unrecognized protocol. I normally use port 587 with TLS, though I have also tried 465 with SSL (these are the Gmail settings, IIRC one of these is different on Gmail than on most email systems). I can't try on port 25, neither Gmail nor my ISP will allow it, and Gmail does not allow unsecure access.
For troubleshooting, I tried searching around ~/.trinity/share/* for Kmail-related stuff, and I removed everything I found, then logging out then back in, and re-setting my SMTP settings, with both port 587/TLS and 465/SSL, and they still would not work.
IMAP seems fine, I have not tried POP3.
I tried on the test machine to install kmail and configure by wizard. Then I tried the option to fully SSL (ports 993 and 465) and TLS variant (ports 143 and 25) and both working properly.
I ran into one problem - the wizard set SMTP port to 465, but the way to TLS communication. And of course it was not possible.
Slávek --
On Tue, Mar 6, 2012 at 2:37 PM, Slávek Banko slavek.banko@axis.cz wrote:
Dne út 6. března 2012 Kristopher Gamrat napsal(a):
I would never kick you OR the tires! Just this stupid thing that "pretends" to be a laptop ;-)
Now to jump over to PIM, I have a bug report there. This one also does not occur in the official packages, hence my reporting it here. This one specifically affects SMTP support in Kmail. Whenever I try to send an email (Kmail or Korganizer), it does not send it. when I click on the up-arrow for the progress report and try to re-send, it shows up with an unrecognized protocol. I normally use port 587 with TLS, though I have also tried 465 with SSL (these are the Gmail settings, IIRC one of these is different on Gmail than on most email systems). I can't try on port 25, neither Gmail nor my ISP will allow it, and Gmail does not allow unsecure access.
For troubleshooting, I tried searching around ~/.trinity/share/* for Kmail-related stuff, and I removed everything I found, then logging out then back in, and re-setting my SMTP settings, with both port 587/TLS and 465/SSL, and they still would not work.
IMAP seems fine, I have not tried POP3.
I tried on the test machine to install kmail and configure by wizard. Then I tried the option to fully SSL (ports 993 and 465) and TLS variant (ports 143 and 25) and both working properly.
I ran into one problem - the wizard set SMTP port to 465, but the way to TLS communication. And of course it was not possible.
It should be possible, depending on the setup on the mail server you're using. For example, Gmail doesn't use TLS on 143 or 25, they use port 587 for TLS. This has worked fine for me, but since Kmail doesn't recognize SMTP as a protocol, I can't use Kmail.
-- Kristopher Gamrat
On Tuesday 06 March 2012 02:37:42 pm Slávek Banko wrote:
Dne út 6. března 2012 Kristopher Gamrat napsal(a):
I would never kick you OR the tires! Just this stupid thing that "pretends" to be a laptop ;-)
Now to jump over to PIM, I have a bug report there. This one also does not occur in the official packages, hence my reporting it here. This one specifically affects SMTP support in Kmail. Whenever I try to send an email (Kmail or Korganizer), it does not send it. when I click on the up-arrow for the progress report and try to re-send, it shows up with an unrecognized protocol. I normally use port 587 with TLS, though I have also tried 465 with SSL (these are the Gmail settings, IIRC one of these is different on Gmail than on most email systems). I can't try on port 25, neither Gmail nor my ISP will allow it, and Gmail does not allow unsecure access.
For troubleshooting, I tried searching around ~/.trinity/share/* for Kmail-related stuff, and I removed everything I found, then logging out then back in, and re-setting my SMTP settings, with both port 587/TLS and 465/SSL, and they still would not work.
IMAP seems fine, I have not tried POP3.
I tried on the test machine to install kmail and configure by wizard. Then I tried the option to fully SSL (ports 993 and 465) and TLS variant (ports 143 and 25) and both working properly.
I ran into one problem - the wizard set SMTP port to 465, but the way to TLS communication. And of course it was not possible.
I just ran a purge on all my TDE packages in Synaptic and remove my ~/.trinity directory, then reinstalled your packages. SMTP seems to be working, for now at least. I'll report back if it stop working again.
-- Kris Gamrat
-
Darrell Anderson -
Kristopher Gamrat -
Kristopher John Gamrat
-
Slávek Banko