[Bug 1741767]

Are people still seeing this? I do not observe this behavior on Kubuntu 20.10 with muon 5.8.0. Could it have been a packaging issue just on Neon? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to muon in Ubuntu.

[Bug 1399855] Re: kwin_x11doesn't stop after logout

Other image ** Attachment added: Back logged in as me, foo still has kwin_x11 https://bugs.launchpad.net/kubuntu-ppa/+bug/1399855/+attachment/4275251/+files/not_dead3.png -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to Kubuntu PPA.

[Bug 1399855] Re: kwin_x11doesn't stop after logout

More info. I logged in as myself, then created a brand-new user foo. I logged out and logged in as foo. My kwin_x11 was not running, but for some reason my process was. (See image) I did nothing else (other than open the terminal, but I know from other trialls that this is not necessary to

[Bug 1399855] [NEW] kwin_x11doesn't stop after logout

Public bug reported: I have a vintate 2001 System 76 Laptop. It is possibly of relevance that I have an nvidia 560M graphics card and am running the nvidia proprietary driver, legacy version 304. I have installed the 14.10 plasma 5 test DVD on it. Both my son and I have accounts. Both of us

[Bug 1399855] Re: kwin_x11doesn't stop after logout

I note that the reverse situation does not result in the same problem. If I log in and then log out, kwin_x11 does not hang. The main difference between him and me is that I am a sudoer and he is not (he is 6 years old!) and I have configured my plasma (for example to use the classic K menu)

[Bug 1392533] Re: Google chrome do not have hardware acceleration under Plasma 5

I am running plasma 5 on System 76 laptop with an nvidia 560M graphics card using the proprietary driver and it does work for me. Here is what chrome://gpu reports Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration

[Bug 1262748] [NEW] package error upgrading to saucy kde 4.12 from kde-backports

Public bug reported: I am getting this: /var/cache/apt/archives/libakonadi-xml4_4%3a4.12.0-0ubuntu1~ubuntu13.10~ppa1_amd64.deb trying to overwrite '/usr/lib/libakonadi-xml.so.4', which is also in package kdepim-runtime 4:4.11.2-0ubuntu1 when I try to upgrade from muon. From the command

[Bug 131893] Re: konqueror metabar is invisible

Sorry about not replying. I must have missed the request for more information. The bug appears to be gone in Hardy, at least on my current laptop. I will reopen if I see it again. -- konqueror metabar is invisible https://bugs.launchpad.net/bugs/131893 You received this bug notification

[Bug 123914] Re: KNetworkManager doesn't initially connect to wired network

I just noticed an additional, probably related thing: it doesn't reconnect to the Wired Network after a suspend or hibernate. -- KNetworkManager doesn't initially connect to wired network https://bugs.launchpad.net/bugs/123914 You received this bug notification because you are a member of

[Bug 131893] konqueror metabar is invisible

Public bug reported: Binary package hint: kdebase When I open the metabar in Konqueror, I see the KDE theme with the gears, but no information is displayed. When I right click and select reload theme, I can see what appears to be the information in the metabar, but it only flashes and then

[Bug 124976] System Settings - Monitor Display won't set hardware type

Public bug reported: Binary package hint: kde-guidance I installed Kubuntu i386 Gutsy Tribe 2 on a Sony Vaio PCG-XG19. I did the install in safe graphics mode, and so when I was done the system had vesa as the driver in xorg.conf (is that supposed to happen?) At any rate, once the system was

[Bug 124640] artsd crashed with SIGSEGV

Public bug reported: Binary package hint: arts Am running off the live CD on a Sony Vaio PCG-XG19. Was just starting up Adept when the crash occurred. ProblemType: Crash Architecture: i386 Date: Sat Jul 7 22:40:28 2007 Disassembly: 0x18: DistroRelease: Ubuntu 7.10 ExecutablePath:

[Bug 124640] Re: artsd crashed with SIGSEGV

** Attachment added: CoreDump.gz http://launchpadlibrarian.net/8334423/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/8334424/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/8334425/ProcMaps.txt ** Attachment added:

[Bug 123914] Re: KNetworkManager doesn't initially connect to wired network

When I try the same gutsy alpha 2 CD in my other laptop, a Dell Inspiron 6400 with built in ethernet, it *does* connect on login. So this problem appears confined to my old Sony Vaio with the PCMCIA ethernet card. -- KNetworkManager doesn't initially connect to wired network

[Bug 123914] Re: KNetworkManager doesn't initially connect to wired network

Actually, I take that back. While it did connect initially, it doesn't always connect or disconnect when I remove the ethernet cable. -- KNetworkManager doesn't initially connect to wired network https://bugs.launchpad.net/bugs/123914 You received this bug notification because you are a member

[Bug 123914] KNetworkManager doesn't initially connect to wired network

Public bug reported: Binary package hint: knetworkmanager I just found this in Gutsy Alpha 2. Networkmanager / KNetworkmanger worked fine in Feisty and even Gutsy alpha 1. Gutsy alpha 2 has KNetworkManager 0.2 so it may have something to do with that. When I log in to the system, I have no

[Bug 123914] Re: KNetworkManager doesn't initially connect to wired network

I should point out that I am using DHCP not a static internet address, and because of this I have no connection prior to manually connecting using KNetworkmanager. -- KNetworkManager doesn't initially connect to wired network https://bugs.launchpad.net/bugs/123914 You received this bug