Jaunty Release Schedule, Plans, KDE 4.2

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

ALPHA 4

This is still an alpha release. Do not install it on production machines. The final stable version will be released on April 23rd, 2009.

and

NOTE: This is an alpha (pre-) release. Pre-release versions of Jaunty are NOT encouraged for anyone needing a stable system or for anyone who is not comfortable running into occasional, even frequent, breakage. Pre-release versions of Jaunty ARE recommended for Kubuntu developers and those who want to help in testing, reporting, and fixing bugs.' Please do not use this in a production environment with data or workflows that you cannot do without'

> Jaunty Alpha 4 released

and more can be found:

> JauntyJackalope/TechnicalOverview

...
Known Issues

As is to be expected at this stage of the release process, there are several known bugs that users are likely to run into with Jaunty Alpha 4. We have documented them here for your convenience along with any known workarounds, so that you don't need to spend time reporting these bugs again:...

> JauntyJackalope/Alpha4/Kubuntu

New or Improved In Alpha 4

Everything!!...

- KDE 4.2
- Quassel
- KMail/Akonadi/Amarok2
- New KDE4 Network-Manager Plasmoid
- Kdebluetooth
- Kubuntu Documentation

...
Known Issues

• Network manager does not show by default. You can add it to plasma through the Plasma button in the bottom right. For the old version use Alt-F2 and type "knetworkmanager".
• Due to software regression on the latest upload of Plasmoid Network Manager, wireless connection may not work for you. Next update just after the alpha 4 release will fix this issue.
• Kmail sieve functionnality has a bug, doesn't work and causes CPU hang. You shouldn't use it at the moment.

[andybleaden]

Re: Jaunty Release Schedule, Plans, KDE 4.2

Just trying this now...feedback later

[andybleaden]

Re: Jaunty Release Schedule, Plans, KDE 4.2

I have to say that this looks pretty impressive. Had it it set up pretty quickly...had to load amarok on it and a few updates for restricted things which could be put on as standard I would have thought but it worked very well and very quickly too!

First boots of a pen drive soon quickened up and I have to say it looks a very very good package. A few mini crashes but nothing really. Fixed the lack of ctrl alt backspace issue

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

> FeatureFreeze

At this point we stop introducing new features, packages, and APIs, and concentrate on fixing bugs in the development release....

Announcements:

> Feature Freeze this Thursday
> Feature Freeze in place

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

ALHA 5

This is still an alpha release. Do not install it on production machines. The final stable version will be released on April 23rd, 2009.

and

NOTE: This is an alpha (pre-) release. Pre-release versions of Jaunty are NOT encouraged for anyone needing a stable system or for anyone who is not comfortable running into occasional, even frequent, breakage. Pre-release versions of Jaunty ARE recommended for Kubuntu developers and those who want to help in testing, reporting, and fixing bugs.' Please do not use this in a production environment with data or workflows that you cannot do without'

> Jaunty Alpha 5 released

and more can be found:

> JauntyJackalope/TechnicalOverview

...
Known Issues

As is to be expected at this stage of the release process, there are several known bugs that users are likely to run into with Jaunty Alpha 5. We have documented them here for your convenience along with any known workarounds, so that you don't need to spend time reporting these bugs again:...

> JauntyJackalope/Alpha5/Kubuntu

New or Improved In Alpha 5

In short, everything!!...

• Qt 4.5 RC1
• KDE 4.2
• Ubiquity
• Quassel
• KMail/Akonadi/Amarok2
• New KDE 4 Network-Manager Plasmoid
• Kdebluetooth
• choqoK

Kubuntu Documentation

We have reintroduced Kubuntu Documentation in the hopes that people use KHelpCenter. We need volunteers to help update the information from KDE 3- to KDE 4-based applications.

...
Known Issues

• The network manager plasmoid does not show by default. You can add it to plasma through the Plasma button in the bottom right. For the old knetworkmanager applet, use Alt-F2 and type "knetworkmanager".
• Due to a software regression in the latest upload of the network manager plasmoid, wireless connections may not work for you. An update following the Alpha 5 release will resolve this issue.
• Kmail sieve functionality is buggy and causes CPU hang. You shouldn't use it at the moment.

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

Misc Links


Qt

> Topic: Qt 4.5 will be LGP
> Why KDE 4.2 should use Qt 4.5
> Qt Software Releases LGPL'ed Qt 4.5 and Creator 1.0, Provides SDK
>> [ubuntu/jaunty] qt-creator 1.0.0-0ubuntu1 (Accepted)


KDE 4.2.1

> KDE4.2 Release Schedule "March 4th, 2009: Release KDE 4.2.1"
> KDE 4.2.1 tarballs uploaded (try#1)

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

KDE 4.2.1


> KDE 4.2.1 Release Announcement

> KDE 4.2.1 Changelog


> Jaunty-changes Archives

[ubuntu/jaunty] kde4libs 4:4.2.1a-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdeaccessibility 4:4.2.1-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdeadmin 4:4.2.1-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdeartwork 4:4.2.1-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdebase 4:4.2.1-0ubuntu1 (Accepted)
...

[MoonRise]

Re: Jaunty Release Schedule, Plans, KDE 4.2

KDE 4.2.1


> KDE 4.2.1 Release Announcement

> KDE 4.2.1 Changelog


> Jaunty-changes Archives

[ubuntu/jaunty] kde4libs 4:4.2.1a-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdeaccessibility 4:4.2.1-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdeadmin 4:4.2.1-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdeartwork 4:4.2.1-0ubuntu1 (Accepted)
[ubuntu/jaunty] kdebase 4:4.2.1-0ubuntu1 (Accepted)
...

Thanks for this one Rog!

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

Nepomuk (& Strigi)


> Semantic Desktop with KDE
>> Discover Nepomuk As a User


> Trueg's old blog
- Strigi, Nepomuk and KDE 4.2 - hopefully a good team (etc...)

The new Strigi service a blogged about before is in svn trunk now. With it Strigi is now enabled by default. But that is no need to be alarmed. I think it behaves quite nicely. After 1 hour and 42 minutes of initial indexing (I did not feel any slowdown of the system in that time)...

I think indexing 37574 files in 1:42h with a usage of 222.5 MiB of space is very good (the files on hard disk take a total of 43 GiB). Keep in mind that you can now search all these files and properly link them in Nepomuk. And after this you only get updates anyway. So please enjoy.

Edit: I forgot to mention that this is using the Soprano Sesame2 backend. The Redland backend is much slower and uses way more hard disk space.

Note!
The Kubuntu 9.04 Jaunty Jackalope (alpha-5) is coming as default with the Redland backend and the Nepomuk&Strigi won't work with it:

Will not start when using redland Soprano backend due to horrible performance.

More > Topic: Nepomuk&Strigi, enable and use


> Trueg's new blog
-“Are We There Yet?” - The Long Road To a Stable Soprano Virtuoso Backend (KDE 4.3)
- The Possible End to the Java Dependancy in Nepomuk-KDE (KDE 4.3)
- ...


Using Nepomuk search with the Dolphin

> HOWTO: Desktop Search in Ubuntu Intrepid in KDE 4.2

For searching now, open Dolphin and in the topbar enter the following.
nepomuksearch:KEYWORD

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

Alpha 6

This is still an alpha release. Do not install it on production machines. The final stable version will be released on April 23rd, 2009.

> Jaunty Alpha 6 released

Alpha 6 is the sixth in a series of milestone CD images that will be
released throughout the Jaunty development cycle. The Alpha images are
known to be reasonably free of showstopper CD build or installer bugs, while
representing a very recent snapshot of Jaunty. You can download it here:...

> JauntyJackalope/TechnicalOverview

...
Known Issues

As is to be expected at this stage of the release process, there are several known bugs that users are likely to run into with Jaunty Alpha 6. We have documented them here for your convenience along with any known workarounds, so that you don't need to spend time reporting these bugs again:

• The "encrypted home directory" option that was available in the desktop installer in previous alpha milestones has been disabled due to outstanding issues and will not be enabled as an install option for the final release.
• A new XServer, version 1.6, is included in Alpha 6. The binary proprietary fglrx driver is not yet supported for this server and will exhibit various serious issues if run against it. Users of this driver are encouraged to wait or to switch to the open source -ati driver in the meantime.
• Users of Intel i845 or i865 video chipsets are unable to load X, getting an error message of "Fatal server error: Couldn't bind memory for BO front buffer". Users on these systems are advised to wait for a resolution to this bug before upgrading.
• Ctrl-Alt-Backspace is now disabled, to reduce issues experienced by users who accidentally trigger the key combo. Users who do want this function can enable it in their xorg.conf, or via the command dontzap --disable.
• Font sizes may be abnormally small or large on monitors which mis-report their capabilities. If you suspect this may be the case, please see X/Troubleshooting/HugeFonts for steps to troubleshoot this issue.
  

> JauntyJackalope/Alpha6/Kubuntu

New or Improved In Alpha 6

The Jaunty Jackalope Alpha 6 CD release includes a brand new desktop as well as many fixes and new applications. For this release, we are exploring some desktop additions and updates to many common applications as well as bug fixes to some annoyances you may have encountered. We are also progressing with our migration of KDE3 applications and dependencies to KDE4...

• Qt 4.5
• KDE 4.2.1
• KPackageKit
• Ubiquity
• Quassel
• Amarok 2.0.2
• New KDE 4 Network-Manager Plasma Widget
• KTorrent 3.2
• Kdebluetooth 0.3
• choqoK

Kubuntu Documentation

We have reintroduced Kubuntu Documentation in the hopes that people use KHelpCenter. We need volunteers to help update the information from KDE 3- to KDE 4-based applications.

...
Known Issues

• Kmail sieve functionality is buggy and causes CPU hang. You shouldn't use it at the moment.

[MoonRise]

Re: Jaunty Release Schedule, Plans, KDE 4.2

> JauntyJackalope/TechnicalOverview
Quote
...
Known Issues

As is to be expected at this stage of the release process, there are several known bugs that users are likely to run into with Jaunty Alpha 6. We have documented them here for your convenience along with any known workarounds, so that you don't need to spend time reporting these bugs again:

* The "encrypted home directory" option that was available in the desktop installer in previous alpha milestones has been disabled due to outstanding issues and will not be enabled as an install option for the final release.
* A new XServer, version 1.6, is included in Alpha 6. The binary proprietary fglrx driver is not yet supported for this server and will exhibit various serious issues if run against it. Users of this driver are encouraged to wait or to switch to the open source -ati driver in the meantime.
* Users of Intel i845 or i865 video chipsets are unable to load X, getting an error message of "Fatal server error: Couldn't bind memory for BO front buffer". Users on these systems are advised to wait for a resolution to this bug before upgrading.
* Ctrl-Alt-Backspace is now disabled, to reduce issues experienced by users who accidentally trigger the key combo. Users who do want this function can enable it in their xorg.conf, or via the command dontzap --disable.
* Font sizes may be abnormally small or large on monitors which mis-report their capabilities. If you suspect this may be the case, please see X/Troubleshooting/HugeFonts for steps to troubleshoot this issue.

Thanks for this warning!

[bsoderror]

Re: Jaunty Release Schedule, Plans, KDE 4.2

Thanx Rog for keeping us updated, it sure is appreciated!

[andybleaden]

Re: Jaunty Release Schedule, Plans, KDE 4.2

Yes I saw that warning a day late!

Had installed the fglrx thing and then upgraded and then it died on me...would not kdm loaded ...even in recovery and earlier versions which was a pain...had to reinstall However this time I booted with a live cd and copied much needed files across to save me losing lots

However another reinstall, this time of alpha 6 from scratch was lots easier than when I first did 3 or 4 which ever it was. Lots less to update and after running updates I was up and working fine. Looks real cool

Kubuntu load is now lots smaller and looks really good. Very fast start up(just past 1 min) which is excellent

btw amarok was already on this as standard as was lots of other things too which saves a little more time too...now I am debating on a fresh install everytime...hmm

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

Catalyst/fglrx

The Jaunty has a pre-release version of the AMD propietary driver > Unreleased ATI Catalyst Driver Appears In Ubuntu.

It could work with the newer AMD hardware > AMD Dropping R300-R500 Support In Catalyst Driver

There are several topics at the > Threads in (Ubuntu) Forum : Jaunty Jackalope Testing and Discussion (down at the moment: The database has encountered a problem ...)


One more > Open-Source ATI Graphics In Ubuntu 9.04

[Rog131]

Re: Jaunty Release Schedule, Plans, KDE 4.2

For the Testers


> k3b for kde4 in kubuntu jaunty?

Kubuntu developers (Tonio in particular) are looking closely on KDE4 version
of k3b. We would be more than happy to get rid of KDE3 completely for Jaunty.

Tonio has prepared test packages for KDE4 k3b and they are available in his
PPA:
https://launchpad.net/~tonio/+archive/ppa

He updates this packages regularly from KDE SVN, but we have received mixed
results when testing (works for some people, but not all functionality - for
example burning ISO images to DVD-RW was reported to not work for some
people).
We would appreciate any tester from the community that can spend some time on
this. We are interested in testing various functionality of k3b. Please test
and report both success as well as problems to kubuntu-devel at lists.ubuntu.com
or in #kubuntu-devel on IRC...