On Wed, Aug 18, 2010 at 10:30 AM, Pierre Schmitz wrote:

On Wed, 18 Aug 2010 10:15:16 +0200, Ronald van Haren wrote:

...

hey guys,

Yesterday I went through all open bug reports for kde 4.5.0 and was able to close all of them (old user config issues/only updated part of packages to testing/etc) except one [1], which seems to be ati/intel related, causing the screen not to be updated when changing some system settings if opengl compositing is used on some ati/intel cards. opengl itself should work, just changing the settings hangs the screen, xrender and no compositing are not affected (there is no fix yet and it may as well be a bug in mesa or some).

As there are no other open kde 4.5.0 bug reports, I suppose it is time to push it to extra and make place in testing now the translations are in place. Should I write an announcement for the above issue?

regards, Ronald

[1] http://bugs.archlinux.org/task/20469

An announcement would be nice. Although there are not much information yet. Maybe we should disable composite by default (people are still able to enable it again in systemsettings). But that depends on how many drivers are actually affected.

/usr/share/config/kwinrc: [Compositing] Enabled=false

-- Pierre Schmitz, https://users.archlinux.de/~pierre

so far I've seen people reporting the following chipsets to be affected, but there may be others intel 910 intel 945 intel 965 ati 3450 does that warrant to disable compositing by default? Ronald

On Wed, 18 Aug 2010 11:19:29 +0200, Jan de Groot wrote:

On Wed, 2010-08-18 at 11:06 +0200, Ronald van Haren wrote:

...

so far I've seen people reporting the following chipsets to be affected, but there may be others intel 910 intel 945 intel 965 ati 3450

Given the fact that AMD and Intel rule the IGP market, I would say yes.

We would still need an announcement as for those who upgrade from previous versions this global configuration wont be effective. We should add to the announcement that people could disable composite by editing ~/.kde4/share/config/kwinrc (if they are no longer able to login) -- Pierre Schmitz, https://users.archlinux.de/~pierre

On Wed, 18 Aug 2010 11:37:55 +0200, Ronald van Haren wrote:

On Wed, Aug 18, 2010 at 11:27 AM, Pierre Schmitz wrote:

...

On Wed, 18 Aug 2010 11:19:29 +0200, Jan de Groot wrote:

...

On Wed, 2010-08-18 at 11:06 +0200, Ronald van Haren wrote:

...

so far I've seen people reporting the following chipsets to be affected, but there may be others intel 910 intel 945 intel 965 ati 3450

Given the fact that AMD and Intel rule the IGP market, I would say yes.

We would still need an announcement as for those who upgrade from previous versions this global configuration wont be effective. We should add to the announcement that people could disable composite by editing ~/.kde4/share/config/kwinrc (if they are no longer able to login)

-- Pierre Schmitz, https://users.archlinux.de/~pierre

you will be able to login, afaik this bug only shows up when changing stuff in system settings. disabling and enabling compositing with the global shortcut should be enough to get it working again.

Ronald

OK, in that case an announcement would probably enough. -- Pierre Schmitz, https://users.archlinux.de/~pierre

On Tue, Aug 24, 2010 at 7:05 PM, Andrea Scarpino wrote:

On Wednesday 18 August 2010 11:06:43 Ronald van Haren wrote:

...

so far I've seen people reporting the following chipsets to be affected, but there may be others intel 910 intel 945 intel 965 ati 3450

After the update to Xorg 1.9 I had to disable compositing (editing ~/.kde4/share/config/kwinrc). I own an intel gm45 chipset.

-- andreascarpino.it Arch Linux Developer

try setting LIBGL_ALWAYS_INDIRECT=1 in ~/.bash_profile if it is the same bug? Ronald

On Wed, Aug 18, 2010 at 11:46 AM, Thomas Bächler wrote:

Am 18.08.2010 10:15, schrieb Ronald van Haren:

...

hey guys,

Yesterday I went through all open bug reports for kde 4.5.0 and was able to close all of them (old user config issues/only updated part of packages to testing/etc) except one [1], which seems to be ati/intel related, causing the screen not to be updated when changing some system settings if opengl compositing is used on some ati/intel cards. opengl itself should work, just changing the settings hangs the screen, xrender and no compositing are not affected (there is no fix yet and it may as well be a bug in mesa or some).

As there are no other open kde 4.5.0 bug reports, I suppose it is time to push it to extra and make place in testing now the translations are in place. Should I write an announcement for the above issue?

I do not experience any serious graphics bugs, but I have three issues which I didn't report yet:

1) Sometimes, when I change settings in 'systemsettings' (forgot which ones, have to investigate again), kwin and/or plasma-desktop freeze and I cannot do anything but move the mouse or switch to VT.

is this different than [1] (upstream [2]) I linked in my first post? What videocard do you have, can you hit alt-shift-f12 twice next it happens to disable/enable compositing? [1] http://bugs.archlinux.org/task/20469 [2] https://bugs.kde.org/show_bug.cgi?id=241402

2) dolphin segfaults. A lot. All the time. It's annoying.

I know this happened on the 4.5 release candidates when tooltips or the information panel were enabled. The fix should have been included in the latest set of source tarballs, but can you test nevertheless if disabling those fixes it?

3) I don't understand why, but starting xbindkeys with KDE's autostart is broken: When I want to use qdbus or dolphin from xbindkeys, nothing happens. When I kill and launch it again later, everything seems to work.

can you start other things from KDE's autostart?

I can live with all of those for now. I cannot reproduce 1) and 2) reliably, or explain why 3) occurs, so don't consider these blockers - just letting you know.

Thomas Bächler wrote:

xbindkeys runs and I can launch everything from it - except KDE applications - and even some of those seem to work. In particular, two settings in xbindkeys fail:

"dolphin"

 mod4 + f

"/usr/bin/qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock"  mod4 + l

I need to kill xbindkeys and start it again for those bindings to work. It gets weirder, because sometimes I have to restart it twice. As I said, I cannot make sense of the problem - running any of those commands from Alt+F2 or from konsole always works (except dolphin segfaulting, of course).

Could it result from a bad interaction with how Kwin or whatever-it-is maps the keys ? I remember having the same problem with XFCE, when calling xbindkeys from a .xsession file, with the additional constraint that I had two keyboards with different mappings: there was only one keyboard working. Since then I use built-in facilities of desktop environments to define shortcuts. So I'd say it's a xbindkeys issue. Do you experience problems when only using standard modifiers in Xbindkeys (like ctrl/shift?). -- Rémy

On Wed, Aug 18, 2010 at 1:42 PM, Thomas Bächler wrote:

...

...

2) dolphin segfaults. A lot. All the time. It's annoying.

I know this happened on the 4.5 release candidates when tooltips or the information panel were enabled. The fix should have been included in the latest set of source tarballs, but can you test nevertheless if disabling those fixes it?

The information panel is always active in my settings, don't know which tooltips you are talking about. And I didn't experience dolphin crashes in the rc's.

you can enable tooltips in dolphin via settings->configure dolphin->general-> tooltips, it will show the same info as in the information panel when hovering an icon. I enabled both earlier today on my system but I still haven't had a single crash, so it doesn't seem the bug I mentioned which I was able to trigger quite a lot.

Another thing I noticed: Whenever I navigate to audiocd:/ and copy the MP3 folder, dolphin crashes and doesn't start the copy. When I do it again, it works.

works fine here. I should note that I have created a new profile, even after the release candidates. I know that normally the old configs should still work but there have been a lot of cases where crashes happened because of it, one time even some settings in the ~/.config directory caused instability. I've been looking on the KDE bug tracker but couldn't find anything related to any of your described dolphin problems. If the problem persists with a clean config/new user, can you provide some more info to go on. Do any other people running kde 4.5.0 experience such instability in dolphin (feel free to contact me off-list if you don't have access here so maybe we can solve this) ? I don't really want to push it into extra if a lot of people have problems with the filemanager. Ronald