* Lisufas Linuxfreunde [06-10-12 08:18]:

… 4.8.4 works for me also from K:D:F, so far without any noticeable problems.

+1 only problem is zypper dup wanting to install gnome :^( but there is supposed to be a request submitted to fix this, just hasn't been "accepted"/"built" yet issued "zypper al gdm" as a temporary work-a-round. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Monday, June 11, 2012 07:55:44 AM Constant Brouerius van Nidek wrote:

On Monday, June 11, 2012 07:59:22 AM Scott Newton wrote:

...

Hi Sven <Quote> Can you let us know when it should be safe to update.

Did the update and up to now found no problems. Even KMail still functions. Your experience may differ.

-- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.1 (i586) Kernel: 3.4.1-27-default KDE Development Platform: 4.8.4 (4.8.4) "release 511") 07:53am up 7:28, 3 users, load average: 0.58, 0.79, 0.86 </Quote>

Use kmail 2 4.8.4 and Kontact 4.8.4: I installed 4.8.4 on x86_64 bit machine and kmail does not work correctly. If I select Message--> New message it crashes, also on new message to mailing list. This was working on 4.8.3(allowing creation of message) but the smtp was failing. When I start kmail from the command line it says it cannot access out box. Still looking into this before reporting bug.

-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Russ openSUSE 12.1(3.1.10-1.9-desktop x86_64)|KDE Platform Version 4.8.3 (4.8.3) "release 504"|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS(NVIDIA-Linux-x86_64-295.53) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Mon, Jun 11, 2012 at 1:21 PM, Sebastian Niemeyer wrote:

I can confirm this. The KDE:RELEASE:48 Repo seems to be broken. I have never seen so many Bugs with Bugfix Release!

I'm not sure if it was the kernel update (3.4.1/3.4.2) or the KDE update that did it, but my laptop no longer response to 'function-f4' (which is suspend-to-ram) or the other one which turns on and off the wireless device. Volume keys and mute still work. Can anybody confirm or deny any of this? -- Jon -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Monday, June 11, 2012 10:13:19 AM upscope wrote:

On Monday, June 11, 2012 07:55:44 AM Constant Brouerius van Nidek wrote:

...

On Monday, June 11, 2012 07:59:22 AM Scott Newton wrote:

...

Hi Sven

<Quote>

...

...

Can you let us know when it should be safe to update.

Did the update and up to now found no problems. Even KMail still functions. Your experience may differ.

--

Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.1 (i586) Kernel: 3.4.1-27-default

KDE Development Platform: 4.8.4 (4.8.4) "release 511")

07:53am up 7:28, 3 users, load average: 0.58, 0.79, 0.86

</Quote>

Use kmail 2 4.8.4 and Kontact 4.8.4:

I installed 4.8.4 on x86_64 bit machine and kmail does not work correctly. If I select Message--> New message it crashes, also on new message to mailing list.

This was working on 4.8.3(allowing creation of message) but the smtp was failing.

When I start kmail from the command line it says it cannot access out box. Still looking into this before reporting bug.

...

-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Russ openSUSE 12.1(3.1.10-1.9-desktop x86_64)|KDE Platform Version 4.8.3 (4.8.3) "release 504"|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS(NVIDIA-Linux-x86_64-295.53) I forgot to mention the problems I'm seeing with 4.8.4 are on openSUSE 12.2 Beta1. I have not updated my 12.1 system to 4.8.4 it is still at 4.8.3 release 503. It works! -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Russ openSUSE 12.1(3.1.10-1.9-desktop x86_64)|KDE Platform Version 4.8.3 (4.8.3) "release 504"|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS(NVIDIA-Linux-x86_64-295.53) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 06/17/2012 04:15 PM, Sebastian Niemeyer wrote: On 06/17/2012 04:15 PM, Sebastian Niemeyer wrote:

Am Montag, 11. Juni 2012, 10:13:19 schrieb upscope:

...

Use kmail 2 4.8.4 and Kontact 4.8.4:

I installed 4.8.4 on x86_64 bit machine and kmail does not work correctly. If I select Message--> New message it crashes, also on new message to mailing list.

This was working on 4.8.3(allowing creation of message) but the smtp was failing.

When I start kmail from the command line it says it cannot access out box. Still looking into this before reporting bug.

I updated this morning the KDE stuff from the release repo.

KDE 4.8.4 is still broken here. It is impossible to work with KMail and nepomuk activated.

The complete Nepomuk stuff seems to be broken...

Sebastian

-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot

Am Montag, 11. Juni 2012, 10:13:19 schrieb upscope:

...

Use kmail 2 4.8.4 and Kontact 4.8.4:

I installed 4.8.4 on x86_64 bit machine and kmail does not work correctly. If I select Message--> New message it crashes, also on new message to mailing list.

This was working on 4.8.3(allowing creation of message) but the smtp was failing.

When I start kmail from the command line it says it cannot access out box. Still looking into this before reporting bug.

I updated this morning the KDE stuff from the release repo.

KDE 4.8.4 is still broken here. It is impossible to work with KMail and nepomuk activated.

The complete Nepomuk stuff seems to be broken...

Sebastian

Here I'm now forced to use thunderbird as mailer, due to crashes with kmail2 (hit reply and you're dead) 4.8.4 is a full disaster actually, when 4.8.3 was working (at least with a few segfault) Why there was no decision to unpublish 4.8.4 in kr48 and rebuild it with a working 4.8 version (4.8.3) ??? Gwenview is also segfaulting everytimes, and it was really a pain in A to try to get my holidays pictures downloaded and sorted on my computer ... Please help me to spend my last week of holiday in peace :-) Greetings from Greece. -- Bruno Friedmann openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Quoting Cor Blom :

Op zondag 17 juni 2012 19:46:26 schreef Bruno Friedmann: [...]

...

Here I'm now forced to use thunderbird as mailer, due to crashes with kmail2 (hit reply and you're dead) 4.8.4 is a full disaster actually, when 4.8.3 was working (at least with a few segfault) Why there was no decision to unpublish 4.8.4 in kr48 and rebuild it with a working 4.8 version (4.8.3) ???

Gwenview is also segfaulting everytimes, and it was really a pain in A to try to get my holidays pictures downloaded and sorted on my computer ...

Please help me to spend my last week of holiday in peace :-)

Greetings from Greece.

Someone needs to update kdelibs4 in KDE:Release:48. The fix is already in KDE:Distro:Factory, but not pushed to KR48. And then we have to wait. :)

I synced KR48/kdelibs , sorry for the trouble! Regards. -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Sonntag 17 Juni 2012, 19:46:26 schrieb Bruno Friedmann:

Here I'm now forced to use thunderbird as mailer, due to crashes with kmail2 (hit reply and you're dead)

A workaround to this bug is to run "kmail --composer" from the command line. When then launching Kontact, the composer window crashes but Kontact relaunches it. Keep the composer window open in the background. Replies will work just fine then. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

No, I think any of those without issues use the factory Repo. The problem is soprano and the version in factory repo differs from the version in release. The release Repo is broken there is no doubt about this fact. Sebastian

Any of those without issues using 12.1 KR48 and nepomuk enabled?

Sven

-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Hello Dne 11.6.2012 21:30, Sebastian Niemeyer napsal(a):

No, I think any of those without issues use the factory Repo.

The problem is soprano and the version in factory repo differs from the version in release.

The release Repo is broken there is no doubt about this fact.

Sebastian

...

Any of those without issues using 12.1 KR48 and nepomuk enabled?

I have a lot of problems... KMail is crashing every startup (I reported the bug to KDE bugzilla). Just few minutes ago, Dolphin stopped to open saying in temrinal $ dolphin "/usr/bin/dolphin(6768)" Soprano: "org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." WTF? I also experinced some random crashes of KOrganizer, Kopete, Konversation, Akregator, ... Also several problems with logging in (I use autologin, I had to set it up again). And also Nepomuk. It (well, mostly virtuoso-t) consumes a lot of CPU, but I haven't found how to query it and if it really is useful. :-) Well, I wouldn't call KDE 4.8.4 bug fixing release, I'm thinking about downgrade back to 4.7.4... Today, /KDE:/Release:/48 forced me to report several bugs. :-) Final note: openSUSE 12.1, 64b system.

...

Sven

Best regards, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/cs -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Monday 11 Jun 2012 22:12:16 Sven Burmeister wrote:

I also wonder who switched KR48 to publish and thus caused all these issues. It is not easy to not see that half the repo is red. Apart from the fact that it was apparently not updated to the tarballs KDF uses..

Which packages do you think are not linked to the KDF versions? I just did a quick check of the main ones and they seem to be the same as KDF. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Montag, 11. Juni 2012, 23:13:49 schrieb Sven Burmeister:

Am Montag, 11. Juni 2012, 22:37:40 schrieb Will Stephenson:

...

Which packages do you think are not linked to the KDF versions? I just did a quick check of the main ones and they seem to be the same as KDF.

Soprano seems different as Sebastian pointed out. Digikam is still at 2.5.0, KDF is at 2.6.0. Most tarballs seem to be up-to-date, I did not check the patches.

Still the question remains why somebody would set the repo to publish but not check whether it actually builds for four days and counting.

Raptor is at 2.0.6 for KR48 while KDF uses 2.0.7. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Dienstag, 12. Juni 2012, 08:32:21 schrieb Mathias Homann:

and ruby-qt doesn't even build, I don't even want to know how many other packages will get rebuild once that is sorted out..

Since only packages whose source has changed are scheduled to start building quickly and most packages will stay as they are, rebuilding the whole repo without increased priority on the buildservice takes ~3 days if not interrupted by some commit. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

It could be a good idea to wait a little bit longer. Until now there are no changes on the release repo for some days. I am sure it will not be repaired on friday. Mathias Homann schrieb:

Am Dienstag, 12. Juni 2012, 08:43:05 schrieb Sven Burmeister:

...

Am Dienstag, 12. Juni 2012, 08:32:21 schrieb Mathias Homann:

...

and ruby-qt doesn't even build, I don't even want to know how many other packages will get rebuild once that is sorted out..

Since only packages whose source has changed are scheduled to start building quickly and most packages will stay as they are, rebuilding the whole repo without increased priority on the buildservice takes ~3 days if not interrupted by some commit.

or in other words, since that package has not been fixed yet: do not touch "zypper dup" until friday?

bye, MH

-- gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C

() ascii ribbon campaign against HTML e-mail /\ www.asciiribbon.org

-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Tuesday 12 Jun 2012 14:26:07 Sebastian Niemeyer wrote:

It could be a good idea to wait a little bit longer. Until now there are no changes on the release repo for some days. I am sure it will not be repaired on friday.

Mathias Homann schrieb:

...

Am Dienstag, 12. Juni 2012, 08:43:05 schrieb Sven Burmeister:

...

Am Dienstag, 12. Juni 2012, 08:32:21 schrieb Mathias Homann:

...

and ruby-qt doesn't even build, I don't even want to know how many

other

...

...

packages will get rebuild once that is sorted out..

Since only packages whose source has changed are scheduled to start

building

...

quickly and most packages will stay as they are, rebuilding the whole

repo

...

without increased priority on the buildservice takes ~3 days if not interrupted by some commit.

or in other words, since that package has not been fixed yet: do not touch "zypper dup" until friday?

bye, MH

I'm trying to identify the commit to Soprano that allegedly fixes the crashes all over the place in 4.8.4, I'll have that before Friday. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Op dinsdag 12 juni 2012 21:45:50 schreef Will Stephenson:

On Tuesday 12 Jun 2012 14:26:07 Sebastian Niemeyer wrote:

...

It could be a good idea to wait a little bit longer. Until now there are no changes on the release repo for some days. I am sure it will not be repaired on friday.

Mathias Homann schrieb:

...

Am Dienstag, 12. Juni 2012, 08:43:05 schrieb Sven Burmeister:

...

Am Dienstag, 12. Juni 2012, 08:32:21 schrieb Mathias Homann:

...

and ruby-qt doesn't even build, I don't even want to know how many

other

...

...

packages will get rebuild once that is sorted out..

Since only packages whose source has changed are scheduled to start

building

...

quickly and most packages will stay as they are, rebuilding the whole

repo

...

without increased priority on the buildservice takes ~3 days if not interrupted by some commit.

or in other words, since that package has not been fixed yet: do not touch "zypper dup" until friday?

bye, MH

I'm trying to identify the commit to Soprano that allegedly fixes the crashes all over the place in 4.8.4, I'll have that before Friday.

Will

I have locally rebuild kdelibs with the commit in 4.8.x branch that should solve it, and I have for the last couple of hours not have any problems. Cor -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 14 June 2012 12:50:52 Will Stephenson wrote:

On Thursday 14 Jun 2012 11:18:11 Cor Blom wrote:

...

Op dinsdag 12 juni 2012 21:45:50 schreef Will Stephenson:

...

I'm trying to identify the commit to Soprano that allegedly fixes the crashes all over the place in 4.8.4, I'll have that before Friday.

Will

I have locally rebuild kdelibs with the commit in 4.8.x branch that should solve it, and I have for the last couple of hours not have any problems.

Same here, I have added

76e0376d-kdelibs-soprano-276-1.diff bde5aad1-kdelibs-soprano-276-2.diff

to kdelibs4 and the crash I was able to reproduce (gwenview) has now gone away.

You can test it too with the kdelibs* packages published from home:wstephenson:branches:KDE:Distro:Factory

these builds currently fail... or is that a general OBS failure atm? Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 14 Jun 2012 15:06:43 Will Stephenson wrote:

On Thursday 14 Jun 2012 13:38:49 Nico Kruber wrote:

...

these builds currently fail... or is that a general OBS failure atm?

It was my fault. I had left a hacked soprano package in the same project and kdelibs4 started to build against it, so I manually aborted the build to save a build cycle, leaving the package in failed state, but forgot to trigger a new build.

And it is now built. WIll -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 14 Jun 2012 16:56:43 Carl Fletcher wrote:

On 14/06/12 16:45, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 15:06:43 Will Stephenson wrote:

...

On Thursday 14 Jun 2012 13:38:49 Nico Kruber wrote:

...

these builds currently fail... or is that a general OBS failure atm?

It was my fault. I had left a hacked soprano package in the same project and kdelibs4 started to build against it, so I manually aborted the build to save a build cycle, leaving the package in failed state, but forgot to trigger a new build.

And it is now built.

WIll

Does anyone else see this needing to be removed

python-kdebase4

Yes (on 12.1, haven't checked Factory yet), haven't looked into it. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 14/06/12 22:13, Greg KH wrote:

On Thu, Jun 14, 2012 at 10:14:38PM +0200, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 16:56:43 Carl Fletcher wrote:

...

On 14/06/12 16:45, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 15:06:43 Will Stephenson wrote:

...

...

these builds currently fail... or is that a general OBS failure atm? It was my fault. I had left a hacked soprano package in the same project and kdelibs4 started to build against it, so I manually aborted the build to save a build cycle, leaving the package in failed state, but forgot to

On Thursday 14 Jun 2012 13:38:49 Nico Kruber wrote: trigger a new build. And it is now built.

WIll Does anyone else see this needing to be removed

python-kdebase4 Yes (on 12.1, haven't checked Factory yet), haven't looked into it. So, for Tumbleweed, I should delete it? Doesn't something rely on it?

greg k-h Good question Greg. I removed it on my 12.1 Box (Which didn't shutdown properly after, but I need to test that more, it could be a one off).

I'll look at my Tumbleweed Laptop tomorrow -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thu, Jun 14, 2012 at 10:22:04PM +0100, Carl Fletcher wrote:

On 14/06/12 22:13, Greg KH wrote:

...

On Thu, Jun 14, 2012 at 10:14:38PM +0200, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 16:56:43 Carl Fletcher wrote:

...

On 14/06/12 16:45, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 15:06:43 Will Stephenson wrote:

...

On Thursday 14 Jun 2012 13:38:49 Nico Kruber wrote: >these builds currently fail... >or is that a general OBS failure atm? It was my fault. I had left a hacked soprano package in the same project and kdelibs4 started to build against it, so I manually aborted the build to save a build cycle, leaving the package in failed state, but forgot to trigger a new build. And it is now built.

WIll Does anyone else see this needing to be removed

python-kdebase4 Yes (on 12.1, haven't checked Factory yet), haven't looked into it. So, for Tumbleweed, I should delete it? Doesn't something rely on it?

greg k-h DUH! I already ran zypper dup and yes, it removed

python-kdebase4

Ok, I'll remove it from Tumbleweed and see what happens, thanks. greg k-h -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 14/06/12 22:41, Patrick Shanahan wrote:

* Greg KH [06-14-12 17:13]:

...

On Thu, Jun 14, 2012 at 10:14:38PM +0200, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 16:56:43 Carl Fletcher wrote:

...

On 14/06/12 16:45, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 15:06:43 Will Stephenson wrote:

...

On Thursday 14 Jun 2012 13:38:49 Nico Kruber wrote: > these builds currently fail... > or is that a general OBS failure atm? It was my fault. I had left a hacked soprano package in the same project and kdelibs4 started to build against it, so I manually aborted the build to save a build cycle, leaving the package in failed state, but forgot to trigger a new build. And it is now built.

WIll Does anyone else see this needing to be removed

python-kdebase4 Yes (on 12.1, haven't checked Factory yet), haven't looked into it. So, for Tumbleweed, I should delete it? Doesn't something rely on it? I removed python-kdebase4 which allowed python-kde4 to upgrade and have seen no problems rebooted system just for check.

still my hot-keys do not work. and konqueror appears to hang if konqueror is initiated from konsole, konsole also turn to molasses.

Looks like my reboot issue was a one off All is well with python-kdebase4 removed -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 14 Jun 2012 14:13:29 Greg KH wrote:

On Thu, Jun 14, 2012 at 10:14:38PM +0200, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 16:56:43 Carl Fletcher wrote:

...

On 14/06/12 16:45, Will Stephenson wrote:

...

On Thursday 14 Jun 2012 15:06:43 Will Stephenson wrote:

...

On Thursday 14 Jun 2012 13:38:49 Nico Kruber wrote:

...

these builds currently fail... or is that a general OBS failure atm?

It was my fault. I had left a hacked soprano package in the same project and kdelibs4 started to build against it, so I manually aborted the build to save a build cycle, leaving the package in failed state, but forgot to trigger a new build.

And it is now built.

WIll

Does anyone else see this needing to be removed

python-kdebase4

Yes (on 12.1, haven't checked Factory yet), haven't looked into it.

So, for Tumbleweed, I should delete it? Doesn't something rely on it?

No, as Sven points out, it was just failing, and being removed because of dependencies. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Hello list, On Thu, 14 Jun 2012 17:45:36 +0200, Will Stephenson wrote:

On Thursday 14 Jun 2012 15:06:43 Will Stephenson wrote:

...

On Thursday 14 Jun 2012 13:38:49 Nico Kruber wrote:

...

these builds currently fail... or is that a general OBS failure atm?

It was my fault. I had left a hacked soprano package in the same project and kdelibs4 started to build against it, so I manually aborted the build to save a build cycle, leaving the package in failed state, but forgot to trigger a new build.

And it is now built.

so when can I expect those changes being available on my computer (via a KR48-repo update etc.)? At the moment I am sitting in the office and cannot send mails via KMail - that's... hindering ;-) Thank you M -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Fri, 15 Jun 2012 12:02:39 +0200, Will Stephenson wrote:

On Friday 15 Jun 2012 11:20:57 Marcel Meyer wrote:

...

so when can I expect those changes being available on my computer (via a KR48-repo update etc.)? At the moment I am sitting in the office and cannot send mails via KMail - that's... hindering ;-)

I was hoping someone would test the fixes and report back.

Will

Gwenview works fine now on openSUSE 12.1 with KDE SC 4.8.4 and the new kdelibs4 packages. No chrash anymore. Erwin -- Erwin Lam (erwinlam@dds.nl) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Freitag 15 Juni 2012, 12:02:39 schrieb Will Stephenson:

I was hoping someone would test the fixes and report back.

KMail still crashing when opening the composer window (found a messy work around but no real fix) and Akonadi Nepomuk Feeder also crashes all the time (I disabled it in akonadi_nepomuk_feederrc for the time being). -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 11/06/12 22:01, Vojtěch Zeisek wrote:

...

Am Montag, 11. Juni 2012, 22:02:26 schrieb Vojtěch Zeisek:

...

I have a lot of problems... KMail is crashing every startup (I reported the bug to KDE bugzilla). Just few minutes ago, Dolphin stopped to open saying in temrinal $ dolphin "/usr/bin/dolphin(6768)" Soprano: "org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." WTF? I also experinced some random crashes of KOrganizer, Kopete, Konversation, Akregator, ... Also several problems with logging in (I use autologin, I had to set it up again). And also Nepomuk. It (well, mostly virtuoso-t) consumes a lot of CPU, but I haven't found how to query it and if it really is useful. :-) Well, I wouldn't call KDE 4.8.4 bug fixing release, I'm thinking about downgrade back to 4.7.4... Today, /KDE:/Release:/48 forced me to report several bugs. :-) Final note: openSUSE 12.1, 64b system. I also wonder who switched KR48 to publish and thus caused all these issues. It is not easy to not see that half the repo is red. Apart from the fact that it was apparently not updated to the tarballs KDF uses..

The bugs you have reported might mostly be due to openSUSE's packaging and not actual bugs. Like https://bugs.kde.org/show_bug.cgi?id=301625 ? :-) Honestly, I'm not able to say, but according to link to KDE devel ML in Your original

Dne 11.6.2012 22:12, Sven Burmeister napsal(a): post, I don't think we are only distro affected...

...

Sven Best regards, Vojtěch

Using R48 on 12.1 _64 4.8.4 (4.8.4) "release 511" Seems fine. But I don't use kmail or any of the PIM stuff and indexing is disabled on my machine (always) The move from 4.8.3 > 4.8.4 had packages all Blue for me It was a little messy and I switched Branding from SUSE to Upstream -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Wednesday 20 Jun 2012 10:01:34 con.hennessy@gmail.com wrote:

Hi, I'm not so clear on the status of KR48. Have all issues been resolved ? (I'd especially like to know if kmail is usable - or at least as usable as 4.8.3).

Thanks, CPH

On Sun 10 Jun 2012 and Sven Burmeister wrote:

...

Hi!

Just a small warning that you might want to wait a few days before updating to KDE SC 4.8.4, since there seem to be some genuine issues with the version – apart from the half broken but published anyway KR48 11.4 repo.

http://lists.kde.org/?l=kde-core-devel&m=133932214908691&w=2

I did not want to blog this since it would appear on planetkde.org, but you might want to spread the warning in order to avoid frustrated users.

Sven

For me, Kmail works occasionally since the update. Sometimes it crashes as soon as it accesses a folder in my list or it crashes trying to view a message or just crashes as soon as it displays itself. But today it seems to work. I did log a bug for the folder access crash as it was closed by Laurent the same day as "already fixed", just not sure if the fix had reached the opensuse RPMs. As its worked today, lets hope it keeps working. regards Ian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org