Version: unspecified (using KDE 4.7.0) OS: Linux With edge desktop switching enabled, if a program is launched on desktop A, dragged to desktop B, and then closed, a blank space equal to the width of a standard taskbar entry will be created on desktop A's taskbar. (A and B represent any two differently numbered desktops). Here is a video of the bug in action: http://www.youtube.com/watch?v=f8FA1yGM0gA Reproducible: Always Steps to Reproduce: 1) Log in to a clean desktop session with no programs displayed in the task manager (if necessary). 2) Enable System Settings -> Workspace Behavior -> Screen Edges -> Switch desktop on edge: Only When Moving Windows. 3) Launch Dolphin on desktop 1. 4) Drag Dolphin to desktop 2. 5) Close Dolphin. 6) Go back to desktop 1 and launch another instance of Dolphin. You will notice a space to the left of Dolphin's taskbar entry. Actual Results: A blank space is created on the first desktop's taskbar. Expected Results: No blank space to be created. My task manager settings are thus: Force row settings: no Show tooltips: yes Highlight windows: no Maximum rows: 2 Grouping: Manually Sorting: Manually Only show tasks from the current screen: no Only show tasks from the current desktop: yes Only show tasks from the current activity: yes Only show tasks that are minimized: no
I should note that the bug is not triggered when selecting the "To Desktop" option from the window menu--only when dragging through the screen edge.
Having similar problem but it's not just when I move from desktop to desktop but completely random. http://ompldr.org/vOXBhMQ/taskbar-random-spacing.png Settings for taskbar: Force row settings: No Show tooltips: Yes Highlight windows: No Maximum Rows: 2 Grouping: Manually Only when taskbar is full: Yes (disabled) Sorting: Do Not Sort Only show tasks from current screen: Yes Only show tasks from current desktop: Yes Only show tasks from current activity: No Only show tasks that are minimised: No
Created attachment 62386 [details] Screen shot of problem This is since boot into KDE (over 24 hours ago). These tasks refuse to move to proper position.
I confirm this bug with KDE 4.7.0. How I reproduced it: I open an application, it appears in the taskbar. I move this application to another desktop with keyboard shortcuts, then I close it. I go back to the first desktop, then launch another app. A invisible space is created in the taskbar. Settings for taskbar: Force row settings: No Show tooltips: No Highlight windows: Yes Maximum Rows: 1 Grouping: Do Not Group Only when taskbar is full: Yes (disabled) Sorting: Do Not Sort Only show tasks from current screen: Yes Only show tasks from current desktop: Yes Only show tasks from current activity: Yes Only show tasks that are minimised: No
Just to add, since a reboot, I have not been able to reproduce this issue. This has been going for over 24 hours running many tasks, opening/closing windows, repositioning between desktops using the pager, etc.
Okay, and this bug re-appeared after another reboot. So it is intermittent but definitely present.
Andrew, I noticed that this bug doesn't always happen when two different programs are launched, but it always seems to happen e.g. when I launch two instances of Dolphin and move one to the other desktop, etc.
*** This bug has been confirmed by popular vote. ***
I'm seeing this under both of my computers that are running 4.7.0 - Arch Linux and Kubuntu 11.04. It also appears to trigger my taskbar to go to two rows when there are a number of programs running - even though the whole taskbar isn't filled, I'm assuming that some of the blank spaces are counted when it determines it should go to two rows.
*** Bug 279428 has been marked as a duplicate of this bug. ***
*** Bug 279140 has been marked as a duplicate of this bug. ***
*** Bug 278754 has been marked as a duplicate of this bug. ***
*** Bug 279000 has been marked as a duplicate of this bug. ***
*** Bug 279361 has been marked as a duplicate of this bug. ***
*** Bug 279481 has been marked as a duplicate of this bug. ***
*** Bug 279498 has been marked as a duplicate of this bug. ***
*** Bug 279681 has been marked as a duplicate of this bug. ***
This bug was present in an earlier KDE version (maybe 4.5?) but was then fixed, it seems like a regression to me. The biggest problem is that it makes the taskbar switch to two rows, even though its maximum number of rows is set to 1. I already had it that only three windows were shown in two rows, even though I would have had space for at least 4 windows in one row. Eventually I switched to STasks. But that also shows empty space, but this time as a complete window entry which I can hover the mouse over. However, it has no title and the mouseover popup is empty, showing only a small circle (i.e. only the border with 0 pixels content). So this bug might even be KWin related and not caused by the taskbar applet itself.
Additionally, the two problems outlined here (ghost entries and extra rows) sometimes combine to result in a taskbar where more than the maximum allowed number of rows are present but a row is entirely made of the blank entries, thus actual entries in effect lose half their height. Killing and restarting plasma-desktop fixes the problem but only temporarily.
I've got similar problem. https://bugs.kde.org/show_bug.cgi?id=279881 Sorry, I didn't know that more rows, and mess with black windows in task bar could be the same thing. Also this https://bugs.kde.org/show_bug.cgi?id=224447 looks like the same problem. 64 Arch, KDE 4.7. Fresh install.
*** Bug 279879 has been marked as a duplicate of this bug. ***
Can anyone check if Aaron's commit fixed it? It's in master branch, so you need to apply it manually when you are using a KDE/4.7 checkout. https://projects.kde.org/projects/kde/kdebase/kde-workspace/repository/revisions/00b0378
*** Bug 279881 has been marked as a duplicate of this bug. ***
I've grabbed that commit (though konqueror couldn't grab it, I had to use firefox to do so???), and have it installed (through a modification of the gentoo ebuild for 4.7.0). I did a killall plasma-desktop && plasma-desktop, and now we'll see if it can be reproduced :-) Thanks!
I've already got one ghost in my bar... not that I've exited all of kde, only restarting plasma-desktop.
Happens to me even when "System Settings -> Workspace Behavior -> Screen Edges -> Switch desktop on edge:" is set to "Disabled". I cannot believe a bug like this slips unnoticed into a release.
*** Bug 279950 has been marked as a duplicate of this bug. ***
I've reported #279950 which has been closed as duplicated. I would prefer "related" as I report more issues (I configure the task panel just to use a single row but at some point get two rows, and sometimes panel entries are shown really wrongly). See attachments please: http://bugsfiles.kde.org/attachment.cgi?id=62771 http://bugsfiles.kde.org/attachment.cgi?id=62773
(In reply to comment #22) > Can anyone check if Aaron's commit fixed it? It's in master branch, so you need > to apply it manually when you are using a KDE/4.7 checkout. > > https://projects.kde.org/projects/kde/kdebase/kde-workspace/repository/revisions/00b0378 Thanks, patch applied and looks like it is working correctly now. But I'll do more tests.
So after some time, ghost is back :-( Unfortunately I don't know, what exactly caused it.
I can confirm this issue too. Platform Version 4.7.00 (4.7.0) "release 10"
Today, I tried to restart plasma-desktop. After command "kquitapp plasma-desktop", plasma-desktop crashed with this BT. Seems related: Thread 1 (Thread 0x7f25a57fb760 (LWP 4143)): [KCrash Handler] #6 0x0000000007e6830a in ?? () #7 0x00007f25879b75a6 in TaskGroupItem::~TaskGroupItem (this=0x9aaf760, __in_chrg=<optimized out>) at /var/tmp/portage/kde-base/plasma-workspace-4.7.0/work/plasma-workspace-4.7.0/plasma/desktop/applets/tasks/taskgroupitem.cpp:82 #8 0x00007f25879b7609 in TaskGroupItem::~TaskGroupItem (this=0x9aaf760, __in_chrg=<optimized out>) at /var/tmp/portage/kde-base/plasma-workspace-4.7.0/work/plasma-workspace-4.7.0/plasma/desktop/applets/tasks/taskgroupitem.cpp:83 #9 0x00007f25a43d2168 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #10 0x00007f25a3b8aefb in QGraphicsWidget::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #11 0x00007f25a3589c54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #12 0x00007f25a358e7da in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #13 0x00007f25a5175062 in KApplication::notify (this=0x15ab0b0, receiver=0x9aaf760, event=0x8127030) at /var/tmp/portage/kde-base/kdelibs-4.7.0-r1/work/kdelibs-4.7.0/kdeui/kernel/kapplication.cpp:311 #14 0x00007f25a43bdf5b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #15 0x00007f25a43c1714 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #16 0x00007f25a43c1a0f in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #17 0x00007f259512bcb2 in kdemain (argc=1, argv=0x1420d10) at /var/tmp/portage/kde-base/plasma-workspace-4.7.0/work/plasma-workspace-4.7.0/plasma/desktop/shell/main.cpp:120 #18 0x0000000000407cf2 in launch (argc=<optimized out>, _name=0x14a9648 "/usr/bin/plasma-desktop", args=<optimized out>, cwd=0x0, envc=0, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40c2d9 "0") at /var/tmp/portage/kde-base/kdelibs-4.7.0-r1/work/kdelibs-4.7.0/kinit/kinit.cpp:734 #19 0x000000000040892a in handle_launcher_request (sock=<optimized out>, who=<optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.7.0-r1/work/kdelibs-4.7.0/kinit/kinit.cpp:1226 #20 0x0000000000408e02 in handle_requests (waitForPid=0) at /var/tmp/portage/kde-base/kdelibs-4.7.0-r1/work/kdelibs-4.7.0/kinit/kinit.cpp:1419 #21 0x00000000004096d7 in main (argc=2, argv=0x7fff0d8b8268, envp=0x7fff0d8b8280) at /var/tmp/portage/kde-base/kdelibs-4.7.0-r1/work/kdelibs-4.7.0/kinit/kinit.cpp:1907
hey all have exact the same problem... kde 4.7.0 kill plasma-desktop and rerun it will get back normal behavior of taskmanager entries. thanks for fixing thomi
I don't know if this is related to this bug, but I've also observed running programs without icons in the taskbar. Also, the kopete entry in the taskbar often remains after the window is closed.
Good morning It happens also if my machine is doing nothing?!.. My Notebook is running over night.. maybe two or three Apps are open and in the background at 02:00 there us a backup job running. In the Morning i see then a empty taskmanager entry and need to rerun plasma-desktop. Hope this can be fixed soon.. Thanks thomi
(In reply to comment #35) > It happens also if my machine is doing nothing?!.. I confirm it.
I see this happening only when "Only show tasks from current desktop: Yes" is set. Setting to No, I can't produce this in anyway. Hope that helps.
I can confirm Comment #37 is a temporary workaround for me as well.
(In reply to comment #37) > I see this happening only when "Only show tasks from current desktop: Yes" is > set. I can confirm this is also my chosen setting.
I got all the time only tasks from current desktop and screen (? don't know is this correct translation ?) and problem still occurs.
Sorry, I read last comments wrong. Now I'm gonna check what if I switch this off.
I've got another way to reproduce this bug. Using: -KDE 4.7.00 (Kubuntu) -Nvidia TwinView (2 screens) -3 desktops -Only show tasks from the current screen -Only show tasks from the current desktop -Firefox 6 To reproduce: 1. Open multiple Firefox windows on different desktops/screens 2. Restart Firefox using its built in restart feature (as for example when an addon has been updated)* 3. The positions that Firefox held on task manager on the desktops that was not active during restart will remain as holes. Using manual sorting, the holes behaves like normal window, but they can not be closed or removed. * To use the restart feature without having to modify the addons each time there is a addon named "Restartless Restart"
*** Bug 281054 has been marked as a duplicate of this bug. ***
i can now confirm it, that no empty entry will be generated if i set task manager settings like this: http://i.imgur.com/wxQnw.png so.. is there a fix in working progress? or.. even does nvidia cause the problem.. or kdm.. or XOrg? thanks thomi
This issue makes me hating my KDE desktop. It's 99% unusable. Please give it priority. Thanks a lot.
It is not nvidia problem. I have the same on ATI.
This cannot be a nvidia/ATI/whatever-card issue. This is a software issue, sure. A video card cannot "decide" where to put an application in the task bar XD
For what it's worth - my 2 cents. I found a workaround good for me which I'd like to share with you: I got rid of the standard task manager altogether and I'm using smooth tasks applet (just unlock GUI element, remove taskbar from panel, add smooth tasks applet). Smooth tasks applet works similar to Windows 7 taskbar and it can be configured to mimic standard KDE's task manager. And the good thing is that it turns my completely unusable (for me at least as I use multple desktops and multiple screen configuration) KDE4.7 workstation into a nicely working machine. I think smooth tasks applet has other problems - to me it seems that it crashes plasma at times, but plasma respawns nicely after each such case so it's not a big deal for me. Hope it helps somebody, best regards, Michael Kostrzewa
(In reply to comment #48) > I found a workaround good for me which I'd like to share with you: I got rid of > the standard task manager altogether and I'm using smooth tasks applet (just > unlock GUI element, remove taskbar from panel, add smooth tasks applet). The problem also occurs if the task panel exists out of the main bar. I attach a screenshot showing it (plasma-taks-panel-ugly-spaces.png).
Created attachment 63291 [details] Same problem if task panel is an independent widget
Hi, I wasn't advising putting task panel outside the main panel. My workaround is to remove standard manager from the panel and insert another applet, called 'smooth tasks'. It doesn't fix task manager - I'm just using something else which works better for me. > The problem also occurs if the task panel exists out of the main bar. I attach > a screenshot showing it (plasma-taks-panel-ugly-spaces.png).
Disagree, smooth-tasks (and it's new fork) has this problem too and you can find reports which proves that easily...
(In reply to comment #52) > Disagree, smooth-tasks (and it's new fork) has this problem too and you can > find reports which proves that easily... Well, may well be, but it works for me pretty well though. With default task manager I'm getting ghosts after couple of minutes of regular work with the desktop, with smooth-tasks I haven't seen it for 2 days now... I know I'm not helping to fix these issues, I just wanted to point out a temporary solution that may work better as a temporary workaround for people (as it works for me ;)
Created attachment 63294 [details] Problem seen in smooth tasks I, too, thought it a solution (as stated in comment #18). But see attachment for what I get with it. Hence my conclusion that this is (probably) not a problem of the taskbar applet itself, but of kwin.
Very annoying bug. I hate it. Please fix it, I hope you will.
*** Bug 281485 has been marked as a duplicate of this bug. ***
Not sure if it was supposed to be fixed, but the bug is still in 4.7.1.
*** Bug 281538 has been marked as a duplicate of this bug. ***
same here kubuntu natty 11.04 32bit 4 desktops kde 4.7.0 http://i.imgur.com/6WEBN.png the task became very small
KDE 4.7.1 (archlinux): problem still present :(
Created attachment 63557 [details] Output of plasma-desktop on affected system This is the console output of "killall plasma-desktop; plasma-desktop" on my system, affected by this problem. Info: Arch Linux kernel 3.0 - KDE 4.7.1, Qt 4.7.4 4 virtual desktops, search&lunch activity.
Are there news from developers about this ugly regression? This is not a feature request but the most critical issue I've ever seen in kde desktop.
please vote!
I must admit I'm surprised this didn't make it into 4.7.1? Sure I understand there's only so much a human being can do, but I'd think this bug would get top priority since it's so incredibly in-your-face and annoying?! Anyway, let's hope for a 4.7.2 fix then?
IMHO, it's a subtle hint to users that they're supposed to be using activities instead of multiple monitors and virtual desktops :-)
I strongly disagree with Vadym. This is clearly a regression.
(In reply to comment #65) > IMHO, it's a subtle hint to users that they're supposed to be using activities > instead of multiple monitors and virtual desktops :-) I'm KDE user since 2004 and I don't know what "a desktop activity" is, neither I need it. Nobody can force what "the users need" (except if you are Apple).
(In reply to comment #67) > (In reply to comment #65) > > IMHO, it's a subtle hint to users that they're supposed to be using activities > > instead of multiple monitors and virtual desktops :-) > > I'm KDE user since 2004 and I don't know what "a desktop activity" is, neither > I need it. Nobody can force what "the users need" (except if you are Apple). Even with activities, why I should be limited by only one desktop? I'm travelling a lot and virtual desktops are the best solution for me.
Nobody uses activities and nobody cares about it. I don't see how this is related to activities anyway but this bug is still present in 4.7.1
This issue is even worse than just the empty spaces in the taskbar: Many times, when I change from one virtual desktop to another, the taskbar still shows the tasks of the *previous* desktop (I configure the taskbar just to show tasks on the current desktop). It makes annoying to select the desired app and I must deal with ALT+F2.
(In reply to comment #70) > This issue is even worse than just the empty spaces in the taskbar: > > Many times, when I change from one virtual desktop to another, the taskbar > still shows the tasks of the *previous* desktop (I configure the taskbar just > to show tasks on the current desktop). > > It makes annoying to select the desired app and I must deal with ALT+F2. True, whenever I log in in KDE for instance, the taskbar shows applications from all desktops. Quite confusing.
Hi, is there any update about this issue?
Almost 2 months passed.
Probably because it's not a bug, it's a feature ^^ On task bar using scroll I can move between windows but if there is ghost window I can't move over it. # - normal G - ghost [ ] - chosen window [#] # G # :) Scroll down # [#] G # :) Scroll down # [#] G # :( Scroll up [#] # G # :) Scroll up # # G [#] :) Scroll up # # G [#] :(
It seems like this obvious bug is going to live even in 4.7.2...
Will KDE 4.7.2 be announced as a great desktop having this ugly bug?
The bug was reported in 2011-07-30 (two months ago). It currently has 1171 votes. But still it's considered as: - Status: NEW - Resolution: - Target: --- - Priority: NOR - Severity: normal Also there has been just an unsuccessful fix attempt and no comments from developers. IMHO the worst KDE bug in years.
Well, it seems like developers are not affected by this bug.
this report is invalid because: * there is another report with this same issue * the behaviour in this report is unnacceptable. interacting with the community of contributors is a privelege, not a right. it is a privelege earned by being collaborate, respectful and constructive, as outline in our code of conduct. due ot the choices some have made in this report, that privelege is revoked in this report due to abuse of that privelege. i'm not going to mark this report as a duplicate of the other one as i have no desire to see the same bullshit repeated there. also note that i've personally made 3 commits that improve the situation noted in this report, though it isn't fully fixed yet. i have received precisely 0 support for that effort from the likes of those who have commented on this report, though i have had the wonderful experience of reading every single bit of drivel posted here in the meantime. so, good job, one and all. :/
Aaron, I only saw one commit mentioned in this bug report. As you may have noticed, I'm willing to extract commits and apply them locally, though I don't run right from SVN or git or whatever you're currently using. So, please, if there are more commits to test, please update the bug report with them, and some of us who are not busy slagging volunteer devs will attempt to test them out. Thanks,
Which is the other other report? My report got closed as a duplicate, but I would still like to follow progress on fixing this issue.
Aaron I think you're exaggerating. Note that is a very visible report, 1171 votes, so there's plenty of people following it. Most of discussion was rather much civil and polite until a few days ago. And you'll notice it's just a small minority of users making such remarks. What is needed, and I've mentioned this before, is the introduction of moderation features. Block these users from the report. Ban them if you have to. Until such measures are in place this will consistently be an issue. Cheers, J.A. (In reply to comment #79) > this report is invalid because: > > * there is another report with this same issue > > * the behaviour in this report is unnacceptable. > > interacting with the community of contributors is a privelege, not a right. it > is a privelege earned by being collaborate, respectful and constructive, as > outline in our code of conduct. > > due ot the choices some have made in this report, that privelege is revoked in > this report due to abuse of that privelege. > > i'm not going to mark this report as a duplicate of the other one as i have no > desire to see the same bullshit repeated there. > > also note that i've personally made 3 commits that improve the situation noted > in this report, though it isn't fully fixed yet. i have received precisely 0 > support for that effort from the likes of those who have commented on this > report, though i have had the wonderful experience of reading every single bit > of drivel posted here in the meantime. so, good job, one and all. :/
(In reply to comment #82) > Aaron I think you're exaggerating. Note that is a very visible report, 1171 > votes, so there's plenty of people following it. Most of discussion was rather > much civil and polite until a few days ago. And you'll notice it's just a small > minority of users making such remarks. > > What is needed, and I've mentioned this before, is the introduction of > moderation features. Block these users from the report. Ban them if you have > to. Until such measures are in place this will consistently be an issue. I'm one of these users that should be banned. I'm sorry for my previous comments. It was not my intention to disturb the developers. But I use KDE for all (at home, at the work) from long years ago and I'm really desperate due to this issue which is making me crazy (I'm tired of running "killall plasma-desktop && plasma-desktop" every 15 minutes). The lack of comments from developers in the issue does not help at all (being a so voted issue). Also I'm not aware about a duplicated issue being handled (instead of this one). That neither helps. Sorry for my previous comments.
BTW, is this the related (and open) bug?: #224447
Iñaki, I actually doubt that that's the bug Aaron is hiding -- at least, the behaviour leading to the bug I reported (https://bugs.kde.org/show_bug.cgi?id=279000, closed as a duplicate by Christoph Feck with admirable efficiency) started only when I installed 4.7.0. I've considered reopening my bug since obviously it's valid again now that this bug is closed, but frankly, I think that Aaron went way beyond being in any way reasonable here, and I am not going to report bugs on plasma anymore.
Dear Aaron, As the reporter of this bug, I am both saddened and discouraged to see the bug resolved as it has been. When I set out to make this bug report, I wanted to do my part as a KDE community member and make the best bug report I could--easily reproducible, and I even made a YouTube video. This bug has been extremely frustrating for me, but I have been patient, not contributing to the whining and mudslinging. Now I feel that all the work I put into this report has been for naught. It is discouraging that other people can so easily ruin an otherwise helpful bug report. I agree with Jorge (comment #82) that moderation features should be added. Perhaps even the bug reporters could have the ability to delete the unhelpful comments so that the developers don't have to waste their valuable time reading them. Ultimately, I appreciate the work you (and all the other developers) do to make such a wonderful desktop environment. KDE is the closest to computing utopia I have ever come, and there really are only a few minor bugs that keep it from being pure heaven :)
(In reply to comment #83) > The lack of comments from developers in the issue does not help at all (being a > so voted issue). Also I'm not aware about a duplicated issue being handled > (instead of this one). That neither helps. Exactly, this issue should have been closed as duplicate at the beginning.
(In reply to comment #83) > I'm sorry for my previous comments. It was not my intention to disturb the > developers. But I use KDE for all (at home, at the work) from long years ago > and I'm really desperate due to this issue which is making me crazy (I'm tired > of running "killall plasma-desktop && plasma-desktop" every 15 minutes). Please read comment #37 for a workaround. It's not perfect, but you won't have to keep killing plasma-desktop all the time.
(In reply to comment #88) The workaround doesn't work for me running 4.7.0, gaps and multiple rows still present with all combinations of "only show tasks from current desktop/screen", "force rows" and "max rows".
(In reply to comment #88) > Please read comment #37 for a workaround. It's not perfect, but you won't have > to keep killing plasma-desktop all the time. I use 4 virtual desktops. Having every apps in a shared taskpanel is not an option for me. Thanks.
I have noticed right now that empty spaces does not appear when I "Move window to the Desktop 1/2/3/4" (by keyboard shortcut or through window menu). But "Move window to the Left/Right/Up/Down Desktop" or dragging window to the other desktop with mouse creates blank spaces in taskbar. And even more interesting result I get when I set a window to be shown on All Desktops and close it - the window closes but the button of it stays in taskbar, with icon and window preview (I have switched on Window thumbnail preview in Smooth Tasks applet). Hope this info will be helpful.
Aaron, if "there is another report with this same issue", this one should be marked as duplicate *with link to the another report*, shouldn't it?
What are well-meaning user supposed to do when trolls appear? I'm also affected by this bug. I've only been able to find this report and I don't know what other report is relevant or how I can help. It's really frustrating to witness that it only takes a few people to disrupt KDE development just because of lack of moderation. What are the rest of users supposed to do?
https://bugs.kde.org/show_bug.cgi?id=279881 why do you thing *** This bug has been marked as a duplicate of bug 278891 *** was striked in this link?
i have the same trouble in both both tackbar and smooth tasks ubuntu 11.04 kde 4.7.1 this bug makes my work impossible
I don't get it. This is obviously a bug, and a serious one at that, affecting lots of users. Where do we turn? The invalidation by Aaron seems to be a bit of a knee-jerk reaction, though I understand where he's coming from. Still, it leaves us all hung out to dry.
ArchLinux, KDE 4.7.2 bug still exists - http://wstaw.org/m/2011/10/10/2.png Also i confirm comment #91 from Andrew Trabo
The open version of this is bug 277010 So far the only workaround without side-effects (that I know of) is running: $ killall plasma-desktop && plasma-desktop I've put that in the application launcher menu and run it every few hours when it gets too cluttered. Perhaps KDE 4.7.3 should ship with this shortcut in place? It's a killer feature! ^^
Kubuntu 11.10 Got this bug....it sucks, not to mention this thread took some searching to find
(In reply to comment #99) > Kubuntu 11.10 > Got this bug....it sucks, not to mention this thread took some searching to > find This has been fixed on 4.7.3, or at least I haven't been able to reproduce it since upgrading.
(In reply to comment #100) > (In reply to comment #99) > > Kubuntu 11.10 > > Got this bug....it sucks, not to mention this thread took some searching to > > find > > This has been fixed on 4.7.3, or at least I haven't been able to reproduce it > since upgrading. Thanks, for anyone else, the repo to get 4.7.3 sudo apt-add-repository ppa:kubuntu-ppa/ppa