[Bug 1489507] Re: package kaccounts-providers (not installed) failed to install/upgrade: попытка перезаписать «/usr/share/accounts/providers/google.provider», который уже имеется в пакете account-plug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kaccounts-providers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kaccounts-providers in Ubuntu. https://bugs.launchpad.net/bugs/1489507 Title: package kaccounts-providers (not installed) failed to install/upgrade: попытка перезаписать «/usr/share/accounts/providers/google.provider», который уже имеется в пакете account-plugin-google 0.12+15.10.20150723-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1489507/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 447823] Re: kopete crashed with SIGSEGV in KHTMLPart::~KHTMLPart()
Launchpad has imported 180 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=209960. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-10-09T09:58:11+00:00 karaluh wrote: Application that crashed: kopete Version of the application: 0.80.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-12-generic i686 Distribution: Ubuntu karmic (development branch) What I was doing when the application crashed: I was looking throug history. When I closed the history window Kopete crashed. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #6 QWidget::hide (this=0x915dae0, __in_chrg=, __vtt_parm=) at /usr/include/qt4/QtGui/qwidget.h:477 #7 ~KHTMLPart (this=0x915dae0, __in_chrg=, __vtt_parm=) at ../../khtml/khtml_part.cpp:612 #8 0x03fe7e2e in KParts::Part::slotWidgetDestroyed (this=0x915dae0) at ../../kparts/part.cpp:354 #9 0x03fe7f4b in KParts::Part::qt_metacall (this=0x915dae0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfc85398) at ./part.moc:76 #10 0x03fe7fba in KParts::ReadOnlyPart::qt_metacall (this=0x915dae0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfc85398) at ./part.moc:154 #11 0x0291c5aa in KHTMLPart::qt_metacall (this=0x915dae0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfc85398) at ./khtml_part.moc:246 #12 0x08f55263 in QMetaObject::activate (sender=0x9646cc8, from_signal_index=0, to_signal_index=1, argv=0xbfc85398) at kernel/qobject.cpp:3113 #13 0x08f556d8 in QMetaObject::activate (sender=0x9646cc8, m=0x807cb10, from_local_signal_index=0, to_local_signal_index=1, argv=0xbfc85398) at kernel/qobject.cpp:3207 #14 0x08f5576b in QObject::destroyed (this=0x9646cc8, _t1=0x9646cc8) at .moc/release-shared/moc_qobject.cpp:143 #15 0x08f56536 in ~QObject (this=0x9646cc8, __in_chrg=) at kernel/qobject.cpp:757 #16 0x04729ebf in ~QWidget (this=0x9646cc8, __in_chrg=) at kernel/qwidget.cpp:1380 #17 0x08f4e46f in QObjectPrivate::deleteChildren (this=0x95f2fc8) at kernel/qobject.cpp:1847 #18 0x04729d4b in ~QWidget (this=0x91c0238, __in_chrg=) at kernel/qwidget.cpp:1367 #19 0x08f4e46f in QObjectPrivate::deleteChildren (this=0x915d638) at kernel/qobject.cpp:1847 #20 0x0472985b in ~QWidget (this=0x91cb6b8, __in_chrg=) at kernel/qwidget.cpp:1367 #21 0x04add961 in ~QFrame (this=0x91cb6b8, __in_chrg=) at widgets/qframe.cpp:243 #22 0x04b47223 in ~QSplitter (this=0x91cb6b8, __in_chrg=) at widgets/qsplitter.cpp:1008 #23 0x08f4e46f in QObjectPrivate::deleteChildren (this=0x95d60e0) at kernel/qobject.cpp:1847 #24 0x04729d4b in ~QWidget (this=0x91c8550, __in_chrg=) at kernel/qwidget.cpp:1367 #25 0x08f4e46f in QObjectPrivate::deleteChildren (this=0x95f1ae8) at kernel/qobject.cpp:1847 #26 0x0472985b in ~QWidget (this=0x95faa18, __in_chrg=) at kernel/qwidget.cpp:1367 #27 0x04bc5184 in ~QDialog (this=0x95faa18, __in_chrg=) at dialogs/qdialog.cpp:298 #28 0x00d08484 in ~KDialog (this=0x95faa18, __in_chrg=) at ../../kdeui/dialogs/kdialog.cpp:197 #29 0x01992f73 in ~HistoryDialog (this=0x95faa18, __in_chrg=) at ../../../../kopete/plugins/history/historydialog.cpp:187 #30 0x08f4e135 in qDeleteInEventHandler (o=0x0) at kernel/qobject.cpp:3815 #31 0x08f4f62b in QObject::event (this=0x95faa18, e=0x9192308) at kernel/qobject.cpp:1094 #32 0x0472d906 in QWidget::event (this=0x95faa18, event=0x9192308) at kernel/qwidget.cpp:7946 #33 0x046d8f54 in QApplicationPrivate::notify_helper (this=0x906ad58, receiver=0x95faa18, e=0x9192308) at kernel/qapplication.cpp:4056 #34 0x046e05ca in QApplication::notify (this=0xbfc86004, receiver=0x95faa18, e=0x9192308) at kernel/qapplication.cpp:4021 #35 0x00da2bba in KApplication::notify (this=0xbfc86004, receiver=0x95faa18, event=0x9192308) at ../../kdeui/kernel/kapplication.cpp:302 #36 0x08f3f6cb in QCoreApplication::notifyInternal (this=0xbfc86004, receiver=0x95faa18, event=0x9192308) at kernel/qcoreapplication.cpp:610 #37 0x08f402b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x904dd10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #38 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x904dd10) at kernel/qcoreapplication.cpp:1247 #39 0x08f4047d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #40 0x08f6a3ff in QCoreApplication::sendPostedEvents (s=0x9072d68) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #41 postEventSourceDispatch (s=0x9072d68) at kernel/qeventdispatcher_glib.cpp:210 #42 0x04fdde78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #43 0x04fe1720 in ?? () from /lib/libglib-2.0.so.0 #44 0x04fe1853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
[Bug 1521005] [NEW] Something crashes at the end of install
Public bug reported: On rebooting, no net, sound modules loaded, and the system is in an inconsistent state. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubiquity 2.21.37 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Sun Nov 29 22:15:13 2015 InstallCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu ubiquity-2.21.37 wily -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1521005 Title: Something crashes at the end of install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1521005/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1521005] Re: Something crashes at the end of install
Tried updating the installer before installing - no change. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1521005 Title: Something crashes at the end of install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1521005/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1520938] [NEW] libstrigiqtdbusclient0v5 lacks Conflicts: libstrigiqtdbusclient0
Public bug reported: As is the case with all packages depending on v5 ABI for libstdc++, the v5 package conflicts with early versions of the non-v5 library. There should be a Conflicts: or Breaks: package field to reflect this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libstrigiqtdbusclient0v5 (not installed) ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CurrentDesktop: KDE Date: Sun Nov 29 16:14:28 2015 SourcePackage: strigi UpgradeStatus: Upgraded to wily on 2015-11-28 (0 days ago) ** Affects: strigi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to strigi in Ubuntu. https://bugs.launchpad.net/bugs/1520938 Title: libstrigiqtdbusclient0v5 lacks Conflicts: libstrigiqtdbusclient0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strigi/+bug/1520938/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1326335] Re: The 'GTK+' qt theme is buggy
** Tags added: wily -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1326335 Title: The 'GTK+' qt theme is buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1326335/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1520932] [NEW] Installing kubuntu-desktop should not change fonts/desktop settings in unity
Public bug reported: I installed kubuntu-desktop to check out the state of KDE. Finding much lack of polish, I came back to unity, only to find that: a) all of my fonts had been changed b) desktop shortcuts didn't work c) the wallpaper in the unity environment didn't work Removing the gtkrc file and restarting unity restored many of these, although I'm still working on fixing fonts. Installing kubuntu-desktop should not touch unity. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: kubuntu-desktop 1.331 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 29 08:37:43 2015 InstallationDate: Installed on 2014-07-11 (505 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to wily on 2015-11-28 (0 days ago) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1520932 Title: Installing kubuntu-desktop should not change fonts/desktop settings in unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1520932/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
IPORTANT NOTICE: *this* bug entry has long tiem turned a completely poinless mess of various "something does not work" reports on contradicting problem descriptions - often not even KWin related (plasmashell hangs for corrupted cache and whatnot issues) => I'll now close it as WONTFIX. Please abort it completely. Do not post on it. Not even to confirm this stance (to keep this message on top) If you've continuing problems and believe they're related to KWin (whether as window manager or compositor), please open a NEW bug with an exact description of your problem and have us triage them. Ruchir, I'm very sorry that this happened. If your original problem persists, please just re-file it. Sorry again. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
Problem with the bug is the unspecificity (is that a word?). The problem is Nvidia and Nouveau. I solved it, as recommended, by using the proprietary driver. Guess what? If it were not freezing up, I would go back to Nouveau. Flash (OK, time to ditch that!) and Vimeo malfunction or do not work at all. The only thing that is really better with Nvidia's own is flightgear and I do not have enough room for it anyway. > https://bugs.kde.org/show_bug.cgi?id=338999 > > bog...@hlevca.com changed: > >What|Removed |Added > > CC||bog...@hlevca.com > > --- Comment #149 from bog...@hlevca.com --- > I tested extensively in OpenSUSE 42.1 which comes with Plasma 5.3. > Most KDE applications freeze for 30 seconds when you start them. It is not > only kate or okular. It is dophin and many others. > > This happens on my desktop system on which I have a Nvidia Quatro 620 semi > professional video card. > > I have the same system on a laptop with an Intel HD video chip and this > problems do not occur. > > I this thing pissed me off so I did more research and I figured out that if > you change the window manager from kwin5 to something else, for example > Openbox, the problem goes away, There is obviously a problem Kwin5 has with > the Nvidia driver (I have the proprietary one) > > There is no need to keep this unconfirmed just because you don't have an > NVIDIA card and can't reproduce it. > > --- Comment #150 from bog...@hlevca.com --- > I tested extensively in OpenSUSE 42.1 which comes with Plasma 5.3. > Most KDE applications freeze for 30 seconds when you start them. It is not > only kate or okular. It is dophin and many others. > > This happens on my desktop system on which I have a Nvidia Quatro 620 semi > professional video card. > > I have the same system on a laptop with an Intel HD video chip and this > problems do not occur. > > I this thing pissed me off so I did more research and I figured out that if > you change the window manager from kwin5 to something else, for example > Openbox, the problem goes away, There is obviously a problem Kwin5 has with > the Nvidia driver (I have the proprietary one) > > There is no need to keep this unconfirmed just because you don't have an > NVIDIA card and can't reproduce it. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1520910] [NEW] Dolphin crashes when selecting multiple files on wily
Public bug reported: When I selecting multiple files dolphin crashed on wily. tux@Z50:~$ lsb_release -rd Description: Ubuntu 15.10 Release: 15.10 tux@Z50:~$ apt-cache policy dolphin dolphin: Asennettu: 4:15.08.2-0ubuntu1 Ehdokas: 4:15.08.2-0ubuntu1 Versiotaulukko: *** 4:15.08.2-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: wily ** Tags added: wily ** Package changed: kde-baseapps (Ubuntu) => dolphin (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-baseapps in Ubuntu. https://bugs.launchpad.net/bugs/1520910 Title: Dolphin crashes when selecting multiple files on wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1520910/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
I tested extensively in OpenSUSE 42.1 which comes with Plasma 5.3. Most KDE applications freeze for 30 seconds when you start them. It is not only kate or okular. It is dophin and many others. This happens on my desktop system on which I have a Nvidia Quatro 620 semi professional video card. I have the same system on a laptop with an Intel HD video chip and this problems do not occur. I this thing pissed me off so I did more research and I figured out that if you change the window manager from kwin5 to something else, for example Openbox, the problem goes away, There is obviously a problem Kwin5 has with the Nvidia driver (I have the proprietary one) There is no need to keep this unconfirmed just because you don't have an NVIDIA card and can't reproduce it. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
(In reply to bogdan from comment #150) I apologize, Opensuse 42.1 comes with plasms 5.4.3 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
I tested extensively in OpenSUSE 42.1 which comes with Plasma 5.3. Most KDE applications freeze for 30 seconds when you start them. It is not only kate or okular. It is dophin and many others. This happens on my desktop system on which I have a Nvidia Quatro 620 semi professional video card. I have the same system on a laptop with an Intel HD video chip and this problems do not occur. I this thing pissed me off so I did more research and I figured out that if you change the window manager from kwin5 to something else, for example Openbox, the problem goes away, There is obviously a problem Kwin5 has with the Nvidia driver (I have the proprietary one) There is no need to keep this unconfirmed just because you don't have an NVIDIA card and can't reproduce it. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
The problem is NOT the Nouveau driver. I have the proprietary one and I still have the 30 seconds freezing problem when I start a KDE application. There are no issues for non KDE applications. The problem, as I already mentioned in my original message, is kwin with any driver for Nvidia. As soon as I changed the window manager to Openbox ( you can change it in System settings Applications -> Default Application) the problem disappeared. Of course some KDE functionality is lost. In addition Plasma 5 crashes in different circumstances, most related to power management, but these issues are reported in different places and are not related to kwin, it happens with Openbox as well. (In reply to David Baron from comment #152) > Problem with the bug is the unspecificity (is that a word?). > The problem is Nvidia and Nouveau. I solved it, as recommended, by using the > proprietary driver. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 39376]
Three years later and no news to this? Would be really great if this would be fixed. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/39376 Title: Allow hidding of backup files To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/39376/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1258422]
yes it's present in Kde 5 as well. Finally I found a workaround. Install the tint2 panel, and place one 1 pixel high and the same width as the plasma panel. This is able to keep the windows from covering it, and therefore they will not cover the kde panel either. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1258422 Title: Maximized windows go under panel if panel attached to screen edge between two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1258422/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1258422]
Same problem here on dual monitors. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1258422 Title: Maximized windows go under panel if panel attached to screen edge between two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1258422/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1258422]
Never seen it with plasma 4, but now I keep having it on my laptop with plasma 5. Anything I could try out to fix it? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1258422 Title: Maximized windows go under panel if panel attached to screen edge between two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1258422/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
