Hello,
Here are some further notes regarding the 3.5.13 release. The release is on schedule for Nov 1st (in 3 days).
Now is your last chance to send in patches for the release. After Oct 29th a hard freeze will be in effect. No changes past this point will be made. This is to ensure that packagers have enough time to produce packages. After that the final tarballs will be built for the release.
For the 3.5.13 release there will be no Ubuntu LiveCDs. If someone would like to respin a LiveCD for us, we will be happy to host the files.
Oneiric packages are built and ready to install. Please report any problems you find.
For Oneiric installation instructions: http://www.trinitydesktop.org/wiki/bin/view/Developers/NightlyBuilds
Lastly, LibreOffice integration will not be available in Oneiric until the creation, submission, and incorporation of patches into the upstream LibreOffice project.
Thank you,
Calvin Morrison Trinity Desktop Team
On Fri, Oct 28, 2011 at 2:02 AM, Calvin Morrison mutantturkey@gmail.comwrote:
Hello,
Here are some further notes regarding the 3.5.13 release. The release is on schedule for Nov 1st (in 3 days).
Now is your last chance to send in patches for the release. After Oct 29th a hard freeze will be in effect. No changes past this point will be made. This is to ensure that packagers have enough time to produce packages. After that the final tarballs will be built for the release.
For the 3.5.13 release there will be no Ubuntu LiveCDs. If someone would like to respin a LiveCD for us, we will be happy to host the files.
Oneiric packages are built and ready to install. Please report any problems you find.
For Oneiric installation instructions: http://www.trinitydesktop.org/wiki/bin/view/Developers/NightlyBuilds
Lastly, LibreOffice integration will not be available in Oneiric until the creation, submission, and incorporation of patches into the upstream LibreOffice project.
Thank you,
Hi,
I have a bug that needs fixing but the bugzilla is not working ok right now. I leave you the description I was trying to post there:
I can't get either my laptop's keyboard nor the external USB keyboard to unlock the kdeskto_lock widget. I have only connected the external screen and disabled the LVDS output. I have to go to the console and kill kdesktop_lock to be able to restore the desktop environment.
Please provide further questions if you need to reproduce. This is on the SVN builds from yesterday, on Ubuntu 11.04.
Thoughts?
Also, is it possible to have a look at the Kopete Jabber issue?
Best regards, Tiago
Calvin Morrison
Trinity Desktop Team
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi, I have a bug that needs fixing but the bugzilla is not working ok right now. I leave you the description I was trying to post there:
I can't get either my laptop's keyboard nor the external USB keyboard to unlock the kdeskto_lock widget. I have only connected the external screen and disabled the LVDS output. I have to go to the console and kill kdesktop_lock to be able to restore the desktop environment. Please provide further questions if you need to reproduce. This is on the SVN builds from yesterday, on Ubuntu 11.04.
Thoughts? Also, is it possible to have a look at the Kopete Jabber issue? Best regards, Tiago
Hi,
Can you report the bug now? yesterday we had some website downtime.
Thank you Calvin Morrison
Hi,
I have a bug that needs fixing but the bugzilla is not working ok right now.
Service provider went down last night from what I can tell. Working on restoring services this morning.
I leave you the description I was trying to post there:
I can't get either my laptop's keyboard nor the external USB keyboard to unlock the kdeskto_lock widget. I have only connected the external screen and disabled the LVDS output. I have to go to the console and kill kdesktop_lock to be able to restore the desktop environment.
Please provide further questions if you need to reproduce. This is on the SVN builds from yesterday, on Ubuntu 11.04.
Thoughts?
Yes, I suspect that the tsak daemon is not recognizing your keypresses. Are you using a non-US keyboard layout?
Also, is it possible to have a look at the Kopete Jabber issue?
Bug number?
Tim
On Fri, Oct 28, 2011 at 4:21 PM, Timothy Pearson < kb9vqf@pearsoncomputing.net> wrote:
Hi,
I have a bug that needs fixing but the bugzilla is not working ok right now.
Service provider went down last night from what I can tell. Working on restoring services this morning.
I leave you the description I was trying to post there:
I can't get either my laptop's keyboard nor the external USB keyboard to unlock the kdeskto_lock widget. I have only connected the external screen and disabled the LVDS output. I have to go to the console and kill kdesktop_lock to be able to restore the desktop environment.
Please provide further questions if you need to reproduce. This is on the SVN builds from yesterday, on Ubuntu 11.04.
Thoughts?
Yes, I suspect that the tsak daemon is not recognizing your keypresses. Are you using a non-US keyboard layout?
Indeed. pt-latin1 charset. Are you suggesting this is Ubuntu related?
Also, is it possible to have a look at the Kopete Jabber issue?
Bug number?
556. Just updated it.
Best regards, Tiago
Tim
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Yes, I suspect that the tsak daemon is not recognizing your keypresses. Are you using a non-US keyboard layout?
Indeed. pt-latin1 charset. Are you suggesting this is Ubuntu related?
No; the tsak daemon looks for specific keycodes, and it is possible that they are different on non-US keyboard layouts. You can work around this by disabling Secure Attention Key support via the KDM control module. In the future we will need to debug this further; http://git.trinitydesktop.org/viewgit/index.php?a=tree&p=Trinity%20Deskt... contains a copy of the tsak daemon code that can be modified to print the keycodes that are being received on your system (I can assist with this at a later date after release).
Also, is it possible to have a look at the Kopete Jabber issue?
Bug number?
- Just updated it.
OK, thanks.
Tim
On Fri, Oct 28, 2011 at 3:44 PM, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
Yes, I suspect that the tsak daemon is not recognizing your keypresses. Are you using a non-US keyboard layout?
Indeed. pt-latin1 charset. Are you suggesting this is Ubuntu related?
No; the tsak daemon looks for specific keycodes, and it is possible that they are different on non-US keyboard layouts. You can work around this by disabling Secure Attention Key support via the KDM control module. In the future we will need to debug this further; http://git.trinitydesktop.org/viewgit/index.php?a=tree&p=Trinity%20Deskt... contains a copy of the tsak daemon code that can be modified to print the keycodes that are being received on your system (I can assist with this at a later date after release).
>
Also, is it possible to have a look at the Kopete Jabber issue?
Bug number?
- Just updated it.
OK, thanks.
Tim
I also have a pt-latin1 keyboard and also had the same problem and also did the same workaround (disable Secure Attention Key).
But for me it was just a small annoyance, no big deal.
Jorge
-
Calvin Morrison -
Jorge Gonçalves -
Tiago Marques -
Timothy Pearson