Version: unspecified (using KDE 4.6.1) OS: Linux Plasma notification area in system tray resizes in realtime to accomodate filename changes, a bug that had been fixed in previous versions of KDE (4.3, etc). The width of the detailed popout varies wildly with the filename of the current file in the operation, and there is no way to expand the dialog to show the expected operation details (such as number of files left to copy, speed of transfer, amount of data transferred during mass copy operation as in previous incarnations of KDE such as 4.3). This regression makes the plasma notifications area of the system tray unreadable, as it morphs too quickly to get a handle on what it displays. The conformation continually changes as well, so it is difficult to even click on the buttons. Reproducible: Always Steps to Reproduce: 1. Copy a large amount files from one location to another via dolphin, etc. 2. During the copy operation, expand the file transfer status in the system tray. 3. Part of this behavior should be observed. 4. Click on the "expand" button. The expand button may randomly reposition itself during this process. 5. The status indicator will behave like a pile of Jell-O during a tremor ;) Actual Results: "The status indicator will behave like a pile of Jell-O during a tremor ;)" -- the progress notification will expand and contract very rapidly throughout the transfer process, which may also make the indicator unusable (and certainly unreadable) during the process. -- see Details This behavior does NOT occur when a process (such as a superuser instance of dolphin) attempts the same operation, because such a process will NOT use the system tray notifications system. Expected Results: The notifications should maintain a constant width, or the width should be decided in advance based on the longest filename, etc. Essentially, it should NOT produce this maddening bug that makes the status indicator unusable. All defaults used. Default theme. Default dolphin instance.
*** This bug has been marked as a duplicate of bug 268439 ***