From dutch.glory at yahoo.com Wed Jun 1 00:30:24 2016 From: dutch.glory at yahoo.com (=?UTF-8?Q?Andr=c3=a9_Verwijs?=) Date: Wed, 1 Jun 2016 02:30:24 +0200 Subject: plasma-desktop packages breaks kde-l10n-xx language packages... Message-ID: <05bd4c13-d2c4-f77a-f1ac-e5b8bd64c8fd@yahoo.com> Kubuntu 16.10 - plasma 5.6.4 plasma-desktop packages breaks kde-l10n-xx language packages... i need plasma-desktop or else plasma doesn't start.... is there a work-arround..?? (see kde bug report #363642) thank you ... ___________________________________________________________ La Ventura (heavy metal band) Tumblr page: http://laventurafan.tumblr.com My Twitter Page: http://twitter.com/OpenSimFan My Facebook page (be my friend, please ) http://www.facebook.com/andre.verwijs My Google+ page (follow me please ) André Verwijs - Google+ https://plus.google.com/111310545842863442992 From samorris at netspace.net.au Wed Jun 1 22:39:33 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Thu, 2 Jun 2016 08:39:33 +1000 Subject: No Display Manager in Kubuntu 16.04 After Upgrade From Kubuntu 15.10 In-Reply-To: <18542858.N3WmVmFsn1@jake-latitude-e6420> References: <8ced52ce-574b-2693-05f5-e196ddfee04b@netspace.net.au> <18542858.N3WmVmFsn1@jake-latitude-e6420> Message-ID: On 01/06/16 08:46, Clay Weber wrote: > On Wednesday, June 1, 2016 7:38:14 AM EDT Stephen Morris wrote: >> Hi, >> >> After receiving notification that there was an upgrade for Kubuntu >> available (not that I actually have Kubuntu installed, I have Ubuntu >> installed with KDE installed as an addon), I ran a sudo >> do-release-upgrade to undertake the upgrade. This process downloaded >> between 2500 - 2600 packages. >> >> After the upgrade, when I boot into the os, the boot process wants >> to start SDDM but the start fails, and every re-attempt to start it >> fails. Using systemctl to attempt to start the service manually fails >> with no meaningful messages, and systemctl status sddm.service doesn't >> show any meaningful messages either. If I issue the command, systemctl >> start lightdm.service, that starts the DM quite happily. >> >> I have checked /etc/X11/default-display-manager and that had the >> command /usr/bin/lightdm as the display manager to launch, but that >> location in not the location where lightdm is installed. I have replaced >> this command with /usr/sbin/lightdm, but on a reboot the boot process >> still tries to unsuccessfully load SDDM. I have also noticed that the >> location of SDDM, unlike Lightdm, is actually /usr/bin/sddm. >> >> Is anyone able to shed some light on why the 16.04 boot wants to >> always start SDDM even though the default display manager is set to >> lightdm, and also why sddm cannot actually start? Could it be that the >> sddm.service process is looking for sddm in /usr/sbin when it is >> actually in /usr/bin, and if so, would a symlink in /usr/sbin back to >> /usr/bin/sddm rectify the issue? >> >> regards, >> >> Steve > My guess, not knowing exactly how you installed Plamsa desktop as an "addon" > would be that though sddm was installed it may not have been registered or > activated or whatever with systemd perhaps? "meaningless" output might > actually be useful here. When I installed 15.10 I installed Ubuntu 15.10, then after installation I installed ODE from the repositories as opposed to actually installed Kubuntu 15.10. ODE was working fine in 15.10 with lightdm as the display manager. > > $ sudo systemctl start sddm > shows nothing? Issuing this command just produces a message that it errored with exit-code and status = 1/failed. It also produced messages that the wait time was over and it was restarting the service, then a message that Saddam had been stopped, followed by a message that a restart of Saddam was attempted to soon. All 3 messages had exactly the same timestamp. I could write the exact messages down and add them to the mail if we need them. My mail system is running in Fedora, which is on the same physical machine as Ubuntu, and I'm tri-booting between Windows 10, Fedora and Ubuntu. One thing I have also noticed is that if the command sudo systemctl status Saddam.service is issued the first thing it does is check /etc/X11/default-display-manager to see if it contain /usr/bin/Saddam and if so it says everything is ok and it can be used as a plugin to another process(I'd need to check again exactly what this process is) and if its not set to that it flags and error, but either way it indicates that Saddam can't be started. > > You can try this to register sddm in systemd: > > $ sudo systemctl enable sddm.service -f > > You can also Try running > > $ sudo dpkg-reconfigure lightdm ## or sddm > > this should bring up a dialog to choose which login manager to use as default. > You should be able to select lightdm which is the default for Ubuntu anyway. I issued the sudo dpkg-reconfigure command and that process put /usr/bin/Saddam or /usr/sbin/lightdm into /etc/X11/default-display-manager depending on which one was selected as the default. Given that on my system /etc/X11/default-display-manager had /usr/bin/lightdm it looks to me like 16.04 has installed lightdm into a different location to where it was in 15.10 and the upgrade has set /etc/X11/default-display-manager to reflect the new location. > > > I am not sure if the /etc/X11/default-display-manager specifies what happens > when you use the start x manually rather than what the init starts up. I'm not explicitly using startx manually. What I have now found after using dpkg-reconfigure is that if the default dm is lightdm, the boot process tries to start Saddam regardless, attempts six times to do so and then gives up, dropping me into a console login prompt. If I login and issue sudo systemctl start lightdm.service I get th e normal lightdm login screen and then I can login to ODE quite happily. If I select Saddam as the default dm in dpkg-reconfigure the boot process doesn't produce the errors and starts Saddam. The issue I get at this point seems to vary from boot to boot, the first boot produced a dialog saying that the graphics mode was too and I would need to reconfigure the options (this sounds to me like the upgrade has not upgraded the nvidia proprietary drivers I was using in 15.10 which were installed from the repository), when I pressed enter because ok was the only option, it then displayed a dialog with four radio buttons on it, but I was unable to cycle through the buttons and enter appeared to do nothing, so I couldn't go any further. The 2nd time I booted Saddam started up to the normal blank screen it displays when it is initializing, without any prompts of any kind, but went no further. The 3rd time I booted it went through the same process as the 1st boot with the same results. > > I have no idea where lightdm should go, but I doubt symlinking probably will > do nothing useful. When I did the upgrade I specified do-release-upgrade without any parameters, could my issues be because I didn't explicitly tell it to do a workstation upgrade? If this is the case can it be redone or do I need to download a 16.04 DVD image and redo the install from scratch? regards, Steve > From fsunoles at gmail.com Thu Jun 2 15:03:20 2016 From: fsunoles at gmail.com (Homer) Date: Thu, 2 Jun 2016 09:03:20 -0600 Subject: plasma crashing Message-ID: Kubuntu 14.04 Hello. Plasma suddenly started crashing this morning. I was doing a little pre-work news reading with the chrome browser and suddenly I lost the desktop. At that point I updated the computer and re-booted to the same result. I tried logging in as a different user and more of the same. I've tried renaming .kde to .kde_old but that doesn't help. Searching the google doesn't find any recent postings on the subject. I was getting a application crashed window popping up indicating a seg fault, but that isn't popping up now for some reason. That's about all I have at this moment. Cheers, Gary -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsunoles at gmail.com Thu Jun 2 15:36:20 2016 From: fsunoles at gmail.com (Homer) Date: Thu, 2 Jun 2016 09:36:20 -0600 Subject: plasma crashing In-Reply-To: References: Message-ID: FWIW the nasty gram is appearing again. The error is: Executable: plasma-desktop PID: 4488 Signal: Segmentation fault (11) Time: 06/02/16 09:32:23 AM On Thu, Jun 2, 2016 at 9:03 AM, Homer wrote: > Kubuntu 14.04 > > Hello. Plasma suddenly started crashing this morning. I was doing a > little pre-work news reading with the chrome browser and suddenly I lost > the desktop. At that point I updated the computer and re-booted to the > same result. I tried logging in as a different user and more of the same. > I've tried renaming .kde to .kde_old but that doesn't help. Searching the > google doesn't find any recent postings on the subject. I was getting a > application crashed window popping up indicating a seg fault, but that > isn't popping up now for some reason. > > That's about all I have at this moment. > > Cheers, > Gary > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsunoles at gmail.com Thu Jun 2 16:01:43 2016 From: fsunoles at gmail.com (Homer) Date: Thu, 2 Jun 2016 10:01:43 -0600 Subject: plasma crashing In-Reply-To: References: Message-ID: Also getting similar errors for: ksmserver Bus error kmix Bus error krunner Bus error kwin Bus error Also I've noticed that /var keeps going to 100%. I'm running out of options to free up space there. On Thu, Jun 2, 2016 at 9:36 AM, Homer wrote: > FWIW the nasty gram is appearing again. The error is: > > Executable: plasma-desktop PID: 4488 Signal: Segmentation fault (11) Time: > 06/02/16 09:32:23 AM > > > On Thu, Jun 2, 2016 at 9:03 AM, Homer wrote: > >> Kubuntu 14.04 >> >> Hello. Plasma suddenly started crashing this morning. I was doing a >> little pre-work news reading with the chrome browser and suddenly I lost >> the desktop. At that point I updated the computer and re-booted to the >> same result. I tried logging in as a different user and more of the same. >> I've tried renaming .kde to .kde_old but that doesn't help. Searching the >> google doesn't find any recent postings on the subject. I was getting a >> application crashed window popping up indicating a seg fault, but that >> isn't popping up now for some reason. >> >> That's about all I have at this moment. >> >> Cheers, >> Gary >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsunoles at gmail.com Thu Jun 2 17:01:09 2016 From: fsunoles at gmail.com (Homer) Date: Thu, 2 Jun 2016 11:01:09 -0600 Subject: plasma crashing In-Reply-To: References: Message-ID: At this point I'm about ready to completely purge kde and plasma and reinstall. Is: sudo apt-get autoremove kubuntu-desktop The way to completely purge kde? There is a lot of conflicting info out there on how to remove kde. On Thu, Jun 2, 2016 at 10:01 AM, Homer wrote: > Also getting similar errors for: > > ksmserver Bus error > kmix Bus error > krunner Bus error > kwin Bus error > > Also I've noticed that /var keeps going to 100%. I'm running out of > options to free up space there. > > On Thu, Jun 2, 2016 at 9:36 AM, Homer wrote: > >> FWIW the nasty gram is appearing again. The error is: >> >> Executable: plasma-desktop PID: 4488 Signal: Segmentation fault (11) >> Time: 06/02/16 09:32:23 AM >> >> >> On Thu, Jun 2, 2016 at 9:03 AM, Homer wrote: >> >>> Kubuntu 14.04 >>> >>> Hello. Plasma suddenly started crashing this morning. I was doing a >>> little pre-work news reading with the chrome browser and suddenly I lost >>> the desktop. At that point I updated the computer and re-booted to the >>> same result. I tried logging in as a different user and more of the same. >>> I've tried renaming .kde to .kde_old but that doesn't help. Searching the >>> google doesn't find any recent postings on the subject. I was getting a >>> application crashed window popping up indicating a seg fault, but that >>> isn't popping up now for some reason. >>> >>> That's about all I have at this moment. >>> >>> Cheers, >>> Gary >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsunoles at gmail.com Thu Jun 2 17:44:22 2016 From: fsunoles at gmail.com (Homer) Date: Thu, 2 Jun 2016 11:44:22 -0600 Subject: plasma crashing In-Reply-To: References: Message-ID: If I create a new user account the same thing happens when logging in as the new user. On Thu, Jun 2, 2016 at 11:01 AM, Homer wrote: > At this point I'm about ready to completely purge kde and plasma and > reinstall. Is: > > sudo apt-get autoremove kubuntu-desktop > > The way to completely purge kde? There is a lot of conflicting info out > there on how to remove kde. > > On Thu, Jun 2, 2016 at 10:01 AM, Homer wrote: > >> Also getting similar errors for: >> >> ksmserver Bus error >> kmix Bus error >> krunner Bus error >> kwin Bus error >> >> Also I've noticed that /var keeps going to 100%. I'm running out of >> options to free up space there. >> >> On Thu, Jun 2, 2016 at 9:36 AM, Homer wrote: >> >>> FWIW the nasty gram is appearing again. The error is: >>> >>> Executable: plasma-desktop PID: 4488 Signal: Segmentation fault (11) >>> Time: 06/02/16 09:32:23 AM >>> >>> >>> On Thu, Jun 2, 2016 at 9:03 AM, Homer wrote: >>> >>>> Kubuntu 14.04 >>>> >>>> Hello. Plasma suddenly started crashing this morning. I was doing a >>>> little pre-work news reading with the chrome browser and suddenly I lost >>>> the desktop. At that point I updated the computer and re-booted to the >>>> same result. I tried logging in as a different user and more of the same. >>>> I've tried renaming .kde to .kde_old but that doesn't help. Searching the >>>> google doesn't find any recent postings on the subject. I was getting a >>>> application crashed window popping up indicating a seg fault, but that >>>> isn't popping up now for some reason. >>>> >>>> That's about all I have at this moment. >>>> >>>> Cheers, >>>> Gary >>>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dutch.glory at yahoo.com Thu Jun 2 18:05:17 2016 From: dutch.glory at yahoo.com (=?UTF-8?Q?Andr=c3=a9_Verwijs?=) Date: Thu, 2 Jun 2016 20:05:17 +0200 Subject: plasma crashing In-Reply-To: References: Message-ID: <2f4e026c-05bb-54bf-c1d1-aa7cccf03270@yahoo.com> plasma is always crashing... Op 2-6-2016 om 19:44 schreef Homer: > If I create a new user account the same thing happens when logging in as > the new user. > > On Thu, Jun 2, 2016 at 11:01 AM, Homer > wrote: > > At this point I'm about ready to completely purge kde and plasma and > reinstall. Is: > > sudo apt-get autoremove kubuntu-desktop > > The way to completely purge kde? There is a lot of conflicting info > out there on how to remove kde. > > On Thu, Jun 2, 2016 at 10:01 AM, Homer > wrote: > > Also getting similar errors for: > > ksmserver Bus error > kmix Bus error > krunner Bus error > kwin Bus error > > Also I've noticed that /var keeps going to 100%. I'm running > out of options to free up space there. > > On Thu, Jun 2, 2016 at 9:36 AM, Homer > wrote: > > FWIW the nasty gram is appearing again. The error is: > > Executable: plasma-desktop PID: 4488 Signal: Segmentation > fault (11) Time: 06/02/16 09:32:23 AM > > > > On Thu, Jun 2, 2016 at 9:03 AM, Homer > wrote: > > Kubuntu 14.04 > > Hello. Plasma suddenly started crashing this morning. > I was doing a little pre-work news reading with the > chrome browser and suddenly I lost the desktop. At that > point I updated the computer and re-booted to the same > result. I tried logging in as a different user and more > of the same. I've tried renaming .kde to .kde_old but > that doesn't help. Searching the google doesn't find > any recent postings on the subject. I was getting a > application crashed window popping up indicating a seg > fault, but that isn't popping up now for some reason. > > That's about all I have at this moment. > > Cheers, > Gary > > > > > > > -- ______________________________________________________________________________________ La Ventura (heavy metal band) Tumblr page: http://laventurafan.tumblr.com My Twitter Page: http://twitter.com/OpenSimFan My Facebook page (be my friend, please ) http://www.facebook.com/andre.verwijs My Google+ page (follow me please ) André Verwijs - Google+ https://plus.google.com/111310545842863442992 From fsunoles at gmail.com Thu Jun 2 18:51:13 2016 From: fsunoles at gmail.com (Homer) Date: Thu, 2 Jun 2016 12:51:13 -0600 Subject: plasma crashing In-Reply-To: References: Message-ID: Just ran the following sudo dpkg -1 | grep -i kde sudo dpkg -1 | grep -i plasma and through the magic of some output redirecting and file editing I purged everything and then ran: sudo aptitude install kubuntu-desktop plasma-desktop. Same problem exists. On Thu, Jun 2, 2016 at 11:44 AM, Homer wrote: > If I create a new user account the same thing happens when logging in as > the new user. > > On Thu, Jun 2, 2016 at 11:01 AM, Homer wrote: > >> At this point I'm about ready to completely purge kde and plasma and >> reinstall. Is: >> >> sudo apt-get autoremove kubuntu-desktop >> >> The way to completely purge kde? There is a lot of conflicting info out >> there on how to remove kde. >> >> On Thu, Jun 2, 2016 at 10:01 AM, Homer wrote: >> >>> Also getting similar errors for: >>> >>> ksmserver Bus error >>> kmix Bus error >>> krunner Bus error >>> kwin Bus error >>> >>> Also I've noticed that /var keeps going to 100%. I'm running out of >>> options to free up space there. >>> >>> On Thu, Jun 2, 2016 at 9:36 AM, Homer wrote: >>> >>>> FWIW the nasty gram is appearing again. The error is: >>>> >>>> Executable: plasma-desktop PID: 4488 Signal: Segmentation fault (11) >>>> Time: 06/02/16 09:32:23 AM >>>> >>>> >>>> On Thu, Jun 2, 2016 at 9:03 AM, Homer wrote: >>>> >>>>> Kubuntu 14.04 >>>>> >>>>> Hello. Plasma suddenly started crashing this morning. I was doing a >>>>> little pre-work news reading with the chrome browser and suddenly I lost >>>>> the desktop. At that point I updated the computer and re-booted to the >>>>> same result. I tried logging in as a different user and more of the same. >>>>> I've tried renaming .kde to .kde_old but that doesn't help. Searching the >>>>> google doesn't find any recent postings on the subject. I was getting a >>>>> application crashed window popping up indicating a seg fault, but that >>>>> isn't popping up now for some reason. >>>>> >>>>> That's about all I have at this moment. >>>>> >>>>> Cheers, >>>>> Gary >>>>> >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From karsten.loh at gmx.de Thu Jun 2 19:57:10 2016 From: karsten.loh at gmx.de (Karsten Loh) Date: Thu, 2 Jun 2016 21:57:10 +0200 Subject: plasma crashing In-Reply-To: References: Message-ID: <57508F96.8040106@gmx.de> Did you try booting from a live CD (or USB Stick)? If it crashes from that as well it might not be a software problem. Karsten -- Evil Overlord Rule #122: The gun turrets on my fortress will not rotate enough so that they may direct fire inward or at each other. On 02.06.2016 20:51, Homer wrote: > Just ran the following > > sudo dpkg -1 | grep -i kde > sudo dpkg -1 | grep -i plasma > > and through the magic of some output redirecting and file editing I > purged everything and then ran: > > sudo aptitude install kubuntu-desktop plasma-desktop. > > Same problem exists. > > On Thu, Jun 2, 2016 at 11:44 AM, Homer > wrote: > > If I create a new user account the same thing happens when logging > in as the new user. > > On Thu, Jun 2, 2016 at 11:01 AM, Homer > wrote: > > At this point I'm about ready to completely purge kde and > plasma and reinstall. Is: > > sudo apt-get autoremove kubuntu-desktop > > The way to completely purge kde? There is a lot of > conflicting info out there on how to remove kde. > > On Thu, Jun 2, 2016 at 10:01 AM, Homer > wrote: > > Also getting similar errors for: > > ksmserver Bus error > kmix Bus error > krunner Bus error > kwin Bus error > > Also I've noticed that /var keeps going to 100%. I'm > running out of options to free up space there. > > On Thu, Jun 2, 2016 at 9:36 AM, Homer > wrote: > > FWIW the nasty gram is appearing again. The error is: > > Executable: plasma-desktop PID: 4488 Signal: > Segmentation fault (11) Time: 06/02/16 09:32:23 AM > > > > On Thu, Jun 2, 2016 at 9:03 AM, Homer > > wrote: > > Kubuntu 14.04 > > Hello. Plasma suddenly started crashing this > morning. I was doing a little pre-work news > reading with the chrome browser and suddenly I > lost the desktop. At that point I updated the > computer and re-booted to the same result. I > tried logging in as a different user and more of > the same. I've tried renaming .kde to .kde_old > but that doesn't help. Searching the google > doesn't find any recent postings on the subject. > I was getting a application crashed window popping > up indicating a seg fault, but that isn't popping > up now for some reason. > > That's about all I have at this moment. > > Cheers, > Gary > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsunoles at gmail.com Fri Jun 3 16:42:11 2016 From: fsunoles at gmail.com (Homer) Date: Fri, 3 Jun 2016 10:42:11 -0600 Subject: plasma crashing In-Reply-To: References: Message-ID: While looking at the developer info section of the nasty gram that kept popping up a colleague suggested the following: sudo apt-get install --reinstall libqtcore4 sudo apt-get install --reinstall plasma-desktop sudo apt-get install --reinstall libqt4-script I then deleted .kde again and logged in. No nasty gram, but I also didn't have a default desktop. For example, I had an empty panel rather than the default. I then tried a back-up .kde and was again presented with the error. I ran the above commands again, removed .kde (no nasty), and proceeded to add a default panel and configure the desktop. So far, so good. Not sure what to say about all this. The "solution" is less than satisfying. I'm not sure I have fixed anything, but it's working. On Thu, Jun 2, 2016 at 12:51 PM, Homer wrote: > Just ran the following > > sudo dpkg -1 | grep -i kde > sudo dpkg -1 | grep -i plasma > > and through the magic of some output redirecting and file editing I purged > everything and then ran: > > sudo aptitude install kubuntu-desktop plasma-desktop. > > Same problem exists. > > On Thu, Jun 2, 2016 at 11:44 AM, Homer wrote: > >> If I create a new user account the same thing happens when logging in as >> the new user. >> >> On Thu, Jun 2, 2016 at 11:01 AM, Homer wrote: >> >>> At this point I'm about ready to completely purge kde and plasma and >>> reinstall. Is: >>> >>> sudo apt-get autoremove kubuntu-desktop >>> >>> The way to completely purge kde? There is a lot of conflicting info out >>> there on how to remove kde. >>> >>> On Thu, Jun 2, 2016 at 10:01 AM, Homer wrote: >>> >>>> Also getting similar errors for: >>>> >>>> ksmserver Bus error >>>> kmix Bus error >>>> krunner Bus error >>>> kwin Bus error >>>> >>>> Also I've noticed that /var keeps going to 100%. I'm running out of >>>> options to free up space there. >>>> >>>> On Thu, Jun 2, 2016 at 9:36 AM, Homer wrote: >>>> >>>>> FWIW the nasty gram is appearing again. The error is: >>>>> >>>>> Executable: plasma-desktop PID: 4488 Signal: Segmentation fault (11) >>>>> Time: 06/02/16 09:32:23 AM >>>>> >>>>> >>>>> On Thu, Jun 2, 2016 at 9:03 AM, Homer wrote: >>>>> >>>>>> Kubuntu 14.04 >>>>>> >>>>>> Hello. Plasma suddenly started crashing this morning. I was doing a >>>>>> little pre-work news reading with the chrome browser and suddenly I lost >>>>>> the desktop. At that point I updated the computer and re-booted to the >>>>>> same result. I tried logging in as a different user and more of the same. >>>>>> I've tried renaming .kde to .kde_old but that doesn't help. Searching the >>>>>> google doesn't find any recent postings on the subject. I was getting a >>>>>> application crashed window popping up indicating a seg fault, but that >>>>>> isn't popping up now for some reason. >>>>>> >>>>>> That's about all I have at this moment. >>>>>> >>>>>> Cheers, >>>>>> Gary >>>>>> >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbaptista at opensuse.us Tue Jun 7 13:22:48 2016 From: cbaptista at opensuse.us (Carlos Baptista) Date: Tue, 7 Jun 2016 14:22:48 +0100 Subject: plasma crashing In-Reply-To: References: Message-ID: <5756CAA8.5000601@opensuse.us> Hi, Do you test your ram? I once has a similiar problem and it was a defect ram. Carlos On 02-06-2016 19:51, Homer wrote: > Just ran the following > > sudo dpkg -1 | grep -i kde > sudo dpkg -1 | grep -i plasma > > and through the magic of some output redirecting and file editing I > purged everything and then ran: > > sudo aptitude install kubuntu-desktop plasma-desktop. > > Same problem exists. > > On Thu, Jun 2, 2016 at 11:44 AM, Homer > wrote: > > If I create a new user account the same thing happens when logging > in as the new user. > > On Thu, Jun 2, 2016 at 11:01 AM, Homer > wrote: > > At this point I'm about ready to completely purge kde and > plasma and reinstall. Is: > > sudo apt-get autoremove kubuntu-desktop > > The way to completely purge kde? There is a lot of > conflicting info out there on how to remove kde. > > On Thu, Jun 2, 2016 at 10:01 AM, Homer > wrote: > > Also getting similar errors for: > > ksmserver Bus error > kmix Bus error > krunner Bus error > kwin Bus error > > Also I've noticed that /var keeps going to 100%. I'm > running out of options to free up space there. > > On Thu, Jun 2, 2016 at 9:36 AM, Homer > wrote: > > FWIW the nasty gram is appearing again. The error is: > > Executable: plasma-desktop PID: 4488 Signal: > Segmentation fault (11) Time: 06/02/16 09:32:23 AM > > > > On Thu, Jun 2, 2016 at 9:03 AM, Homer > > wrote: > > Kubuntu 14.04 > > Hello. Plasma suddenly started crashing this > morning. I was doing a little pre-work news > reading with the chrome browser and suddenly I > lost the desktop. At that point I updated the > computer and re-booted to the same result. I > tried logging in as a different user and more of > the same. I've tried renaming .kde to .kde_old > but that doesn't help. Searching the google > doesn't find any recent postings on the subject. > I was getting a application crashed window popping > up indicating a seg fault, but that isn't popping > up now for some reason. > > That's about all I have at this moment. > > Cheers, > Gary > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jackerkh at appstate.edu Wed Jun 8 12:48:39 2016 From: jackerkh at appstate.edu (Kenneth Jacker) Date: Wed, 8 Jun 2016 08:48:39 -0400 Subject: Desktop Icons Have No Text Labels Message-ID: [ Kubuntu 16.04 LTS ] Say I create a text file in my home directory using 'kate' named "foobar". Then I open my home directory using 'dolphin'. After locating the newly created text file in the 'dolphin' window, I "drag" the text file's icon to the desktop. Choosing the "icon" option, the icon appears but without any label, just the icon itself. If I "hover" the cursor over the icon, the name "foobar" appears. But the text is not on the icon itself. How can I get text displayed with/on the icon so that I can determine visually which of possibly many icons on the desktop I might want to open? Thanks for your ideas! --Kenneth -------------- next part -------------- An HTML attachment was scrubbed... URL: From samorris at netspace.net.au Thu Jun 9 21:43:21 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Fri, 10 Jun 2016 07:43:21 +1000 Subject: No Display Manager in Kubuntu 16.04 After Upgrade From Kubuntu 15.10 In-Reply-To: References: <8ced52ce-574b-2693-05f5-e196ddfee04b@netspace.net.au> <18542858.N3WmVmFsn1@jake-latitude-e6420> Message-ID: On 02/06/16 08:39, Stephen Morris wrote: > On 01/06/16 08:46, Clay Weber wrote: >> On Wednesday, June 1, 2016 7:38:14 AM EDT Stephen Morris wrote: >>> Hi, >>> >>> After receiving notification that there was an upgrade for >>> Kubuntu >>> available (not that I actually have Kubuntu installed, I have Ubuntu >>> installed with KDE installed as an addon), I ran a sudo >>> do-release-upgrade to undertake the upgrade. This process downloaded >>> between 2500 - 2600 packages. >>> >>> After the upgrade, when I boot into the os, the boot process >>> wants >>> to start SDDM but the start fails, and every re-attempt to start it >>> fails. Using systemctl to attempt to start the service manually fails >>> with no meaningful messages, and systemctl status sddm.service doesn't >>> show any meaningful messages either. If I issue the command, systemctl >>> start lightdm.service, that starts the DM quite happily. >>> >>> I have checked /etc/X11/default-display-manager and that had the >>> command /usr/bin/lightdm as the display manager to launch, but that >>> location in not the location where lightdm is installed. I have >>> replaced >>> this command with /usr/sbin/lightdm, but on a reboot the boot process >>> still tries to unsuccessfully load SDDM. I have also noticed that the >>> location of SDDM, unlike Lightdm, is actually /usr/bin/sddm. >>> >>> Is anyone able to shed some light on why the 16.04 boot wants to >>> always start SDDM even though the default display manager is set to >>> lightdm, and also why sddm cannot actually start? Could it be that the >>> sddm.service process is looking for sddm in /usr/sbin when it is >>> actually in /usr/bin, and if so, would a symlink in /usr/sbin back to >>> /usr/bin/sddm rectify the issue? >>> >>> regards, >>> >>> Steve >> My guess, not knowing exactly how you installed Plamsa desktop as an >> "addon" >> would be that though sddm was installed it may not have been >> registered or >> activated or whatever with systemd perhaps? "meaningless" output might >> actually be useful here. > When I installed 15.10 I installed Ubuntu 15.10, then after > installation I installed ODE from the repositories as opposed to > actually installed Kubuntu 15.10. ODE was working fine in 15.10 with > lightdm as the display manager. >> >> $ sudo systemctl start sddm >> shows nothing? > Issuing this command just produces a message that it errored with > exit-code and status = 1/failed. It also produced messages that the > wait time was over and it was restarting the service, then a message > that Saddam had been stopped, followed by a message that a restart of > Saddam was attempted to soon. All 3 messages had exactly the same > timestamp. > I could write the exact messages down and add them to the mail if we > need them. My mail system is running in Fedora, which is on the same > physical machine as Ubuntu, and I'm tri-booting between Windows 10, > Fedora and Ubuntu. > One thing I have also noticed is that if the command sudo systemctl > status Saddam.service is issued the first thing it does is check > /etc/X11/default-display-manager to see if it contain /usr/bin/Saddam > and if so it says everything is ok and it can be used as a plugin to > another process(I'd need to check again exactly what this process is) > and if its not set to that it flags and error, but either way it > indicates that Saddam can't be started. >> >> You can try this to register sddm in systemd: >> >> $ sudo systemctl enable sddm.service -f >> >> You can also Try running >> >> $ sudo dpkg-reconfigure lightdm ## or sddm >> >> this should bring up a dialog to choose which login manager to use as >> default. >> You should be able to select lightdm which is the default for Ubuntu >> anyway. > I issued the sudo dpkg-reconfigure command and that process put > /usr/bin/Saddam or /usr/sbin/lightdm into > /etc/X11/default-display-manager depending on which one was selected > as the default. Given that on my system > /etc/X11/default-display-manager had /usr/bin/lightdm it looks to me > like 16.04 has installed lightdm into a different location to where it > was in 15.10 and the upgrade has set /etc/X11/default-display-manager > to reflect the new location. >> >> >> I am not sure if the /etc/X11/default-display-manager specifies what >> happens >> when you use the start x manually rather than what the init starts up. > I'm not explicitly using startx manually. What I have now found after > using dpkg-reconfigure is that if the default dm is lightdm, the boot > process tries to start Saddam regardless, attempts six times to do so > and then gives up, dropping me into a console login prompt. If I login > and issue sudo systemctl start lightdm.service I get th e normal > lightdm login screen and then I can login to ODE quite happily. > If I select Saddam as the default dm in dpkg-reconfigure the boot > process doesn't produce the errors and starts Saddam. The issue I get > at this point seems to vary from boot to boot, the first boot produced > a dialog saying that the graphics mode was too and I would need to > reconfigure the options (this sounds to me like the upgrade has not > upgraded the nvidia proprietary drivers I was using in 15.10 which > were installed from the repository), when I pressed enter because ok > was the only option, it then displayed a dialog with four radio > buttons on it, but I was unable to cycle through the buttons and enter > appeared to do nothing, so I couldn't go any further. The 2nd time I > booted Saddam started up to the normal blank screen it displays when > it is initializing, without any prompts of any kind, but went no > further. The 3rd time I booted it went through the same process as the > 1st boot with the same results. >> >> I have no idea where lightdm should go, but I doubt symlinking >> probably will >> do nothing useful. > When I did the upgrade I specified do-release-upgrade without any > parameters, could my issues be because I didn't explicitly tell it to > do a workstation upgrade? If this is the case can it be redone or do I > need to download a 16.04 DVD image and redo the install from scratch? > > regards, > Steve I have now issued command systemctl status sddm.service and received the following output: systemctl status sddm.service ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-06-10 17:08:06 AEST; 2min 53s ago Docs: man:sddm(1) man:sddm.conf(5) Process: 1193 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/sddm" ] (code=exited, status=1/FAILURE) Jun 10 17:08:05 Home-Desktop systemd[1]: sddm.service: Failed with result 'exit-code'. Jun 10 17:08:06 Home-Desktop systemd[1]: sddm.service: Service hold-off time over, scheduling restart. Jun 10 17:08:06 Home-Desktop systemd[1]: Stopped Simple Desktop Display Manager. Jun 10 17:08:06 Home-Desktop systemd[1]: sddm.service: Start request repeated too quickly. Jun 10 17:08:06 Home-Desktop systemd[1]: Failed to start Simple Desktop Display Manager. I have also noticed that using dpkg-reconfigure to specify the default display manager does nothing, the system tries to start sddm at boot time regardless of what is specified here as the default. The only way I have been able to get the system to boot into lightdm as the display manager is to uninstall sddm. The other thing that is of a concern to me that is slightly off-topic to this thread, is the timestamp that is on the systemctl output above. That timestamp is actually 10 hours ahead of local time, which indicates that Kubuntu assumes the bios time is set to GMT when in reality is isn't, and I don't know where to change that. regards, Steve >> > > From fsunoles at gmail.com Thu Jun 9 22:55:57 2016 From: fsunoles at gmail.com (Homer) Date: Thu, 9 Jun 2016 16:55:57 -0600 Subject: plasma crashing In-Reply-To: <5756CAA8.5000601@opensuse.us> References: <5756CAA8.5000601@opensuse.us> Message-ID: A good suggestion, but I don't think that is the problem. The computer has been running well for about two years. I've also had bad RAM cause weird problems with other machines. I used to run a script that would compile kernels over and over as I read somewhere that was a good way to test RAM. One thought I had was my SSD. I was wondering if bit might have been flipped??? In any case, so far, so good. As soon as I can afford the time at work I'm going to buy a new SSD (I want a bigger one anyway) and reinstall the OS. I think I'm going with Debian next time. The Ubuntu and Kubuntu mailing lists don't seem to generate much traffic any more. Where are the good places to pose Ubuntu/Kubuntu questions these days? On Tue, Jun 7, 2016 at 7:22 AM, Carlos Baptista wrote: > Hi, > > Do you test your ram? I once has a similiar problem and it was a defect > ram. > > Carlos > > > > On 02-06-2016 19:51, Homer wrote: > > Just ran the following > > sudo dpkg -1 | grep -i kde > sudo dpkg -1 | grep -i plasma > > and through the magic of some output redirecting and file editing I purged > everything and then ran: > > sudo aptitude install kubuntu-desktop plasma-desktop. > > Same problem exists. > > On Thu, Jun 2, 2016 at 11:44 AM, Homer wrote: > >> If I create a new user account the same thing happens when logging in as >> the new user. >> >> On Thu, Jun 2, 2016 at 11:01 AM, Homer < >> fsunoles at gmail.com> wrote: >> >>> At this point I'm about ready to completely purge kde and plasma and >>> reinstall. Is: >>> >>> sudo apt-get autoremove kubuntu-desktop >>> >>> The way to completely purge kde? There is a lot of conflicting info out >>> there on how to remove kde. >>> >>> On Thu, Jun 2, 2016 at 10:01 AM, Homer < >>> fsunoles at gmail.com> wrote: >>> >>>> Also getting similar errors for: >>>> >>>> ksmserver Bus error >>>> kmix Bus error >>>> krunner Bus error >>>> kwin Bus error >>>> >>>> Also I've noticed that /var keeps going to 100%. I'm running out of >>>> options to free up space there. >>>> >>>> On Thu, Jun 2, 2016 at 9:36 AM, Homer < >>>> fsunoles at gmail.com> wrote: >>>> >>>>> FWIW the nasty gram is appearing again. The error is: >>>>> >>>>> Executable: plasma-desktop PID: 4488 Signal: Segmentation fault (11) >>>>> Time: 06/02/16 09:32:23 AM >>>>> >>>>> >>>>> On Thu, Jun 2, 2016 at 9:03 AM, Homer < >>>>> fsunoles at gmail.com> wrote: >>>>> >>>>>> Kubuntu 14.04 >>>>>> >>>>>> Hello. Plasma suddenly started crashing this morning. I was doing a >>>>>> little pre-work news reading with the chrome browser and suddenly I lost >>>>>> the desktop. At that point I updated the computer and re-booted to the >>>>>> same result. I tried logging in as a different user and more of the same. >>>>>> I've tried renaming .kde to .kde_old but that doesn't help. Searching the >>>>>> google doesn't find any recent postings on the subject. I was getting a >>>>>> application crashed window popping up indicating a seg fault, but that >>>>>> isn't popping up now for some reason. >>>>>> >>>>>> That's about all I have at this moment. >>>>>> >>>>>> Cheers, >>>>>> Gary >>>>>> >>>>> >>>>> >>>> >>> >> > > > > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From buzzmandt at gmail.com Fri Jun 10 18:37:30 2016 From: buzzmandt at gmail.com (Dale Trombley) Date: Fri, 10 Jun 2016 14:37:30 -0400 Subject: kmymoney on 16.04 Message-ID: getting these errors. anyone know what to try next? heather at heather-Inspiron-3543:~$ sudo apt-get install kmymoney > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > >> The following packages have unmet dependencies: > > kmymoney : Depends: kmymoney-common (= 4.6.6-2) but >> 4.7.2-0ubuntu1~ubuntu14.04~ppa2 is to be installed > > E: Unable to correct problems, you have held broken packages. > > heather at heather-Inspiron-3543:~$ sudo apt-get -f install > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done >> >> > > The following packages were automatically installed and are no longer >> required: >> > > alien appmenu-qt at debugedit kmymoney-common lib32z1 libalkimia4 >> libaqbanking34 libgpgme++2 libgwengui-cpp0 libgwengui-qt4-0 libkholidays4 >> libkpimidentities4 libkpimtextedit4 liblua5.2-0 > > libofx4 libosp5 librpm3 librpmbuild3 librpmio3 librpmsign3 libsigsegv2 >> linux-image-3.16.0-71-generic linux-image-extra-3.16.0-71-generic m4 >> ncurses-term pax rpm rpm-common rpm2cpio > > Use 'sudo apt autoremove' to remove them. >> >> > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > -- *Webmaster and Admin for:* *nghsband.com , depotstreetfarmersmarket.com , netfa.org , mysummerfieldfarm.com , historicthreads.com , crockettfriends.com , traditionsbylittlebird.com , trombleyconstruction.com , tnparks.crockettfriends.com * -------------- next part -------------- An HTML attachment was scrubbed... URL: From clay at claydoh.com Fri Jun 10 18:48:31 2016 From: clay at claydoh.com (Clay Weber) Date: Fri, 10 Jun 2016 14:48:31 -0400 Subject: kmymoney on 16.04 In-Reply-To: References: Message-ID: <1477398.McvIU5hgRF@jake-latitude-e6420> On Friday, June 10, 2016 2:37:30 PM EDT Dale Trombley wrote: > getting these errors. anyone know what to try next? > > heather at heather-Inspiron-3543:~$ sudo apt-get install kmymoney > > > Reading package lists... Done > > > > Building dependency tree > > > > Reading state information... Done > > > > Some packages could not be installed. This may mean that you have > > > > requested an impossible situation or if you are using the unstable > > > > distribution that some required packages have not yet been created > > > > or been moved out of Incoming. > > > > The following information may help to resolve the situation: > >> The following packages have unmet dependencies: > > kmymoney : Depends: kmymoney-common (= 4.6.6-2) but > > > >> 4.7.2-0ubuntu1~ubuntu14.04~ppa2 is to be installed ^^^^ this looks odd, it is trying to install 14.04's package in 16.04? How did you add the ppa info? Most users have zero problems installing KMM in Kubuntu 16.04 using my ppa. > > > > E: Unable to correct problems, you have held broken packages. > > > > heather at heather-Inspiron-3543:~$ sudo apt-get -f install > > > > Reading package lists... Done > > > > Building dependency tree > > > > Reading state information... Done > > > > > > > > The following packages were automatically installed and are no longer > > > >> required: > > alien appmenu-qt at debugedit kmymoney-common lib32z1 libalkimia4 > >> > >> libaqbanking34 libgpgme++2 libgwengui-cpp0 libgwengui-qt4-0 libkholidays4 > >> libkpimidentities4 libkpimtextedit4 liblua5.2-0 > >> > > libofx4 libosp5 librpm3 librpmbuild3 librpmio3 librpmsign3 libsigsegv2 > >> > >> linux-image-3.16.0-71-generic linux-image-extra-3.16.0-71-generic m4 > >> ncurses-term pax rpm rpm-common rpm2cpio > > > > Use 'sudo apt autoremove' to remove them. > > > > > > > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -- Clay Weber From buzzmandt at gmail.com Fri Jun 10 19:15:33 2016 From: buzzmandt at gmail.com (Dale Trombley) Date: Fri, 10 Jun 2016 15:15:33 -0400 Subject: kmymoney on 16.04 In-Reply-To: <1477398.McvIU5hgRF@jake-latitude-e6420> References: <1477398.McvIU5hgRF@jake-latitude-e6420> Message-ID: > > > > ^^^^ this looks odd, it is trying to install 14.04's package in 16.04? How > did > you add the ppa info? Most users have zero problems installing KMM in > Kubuntu > 16.04 using my ppa. > > Clay Weber > > > I had your ppa installed on 14.04 and it did great. I upgraded 14.04 lts to 16.04 lts and it removed kmymoney. trying to install it on here now gives me that error -------------- next part -------------- An HTML attachment was scrubbed... URL: From buzzmandt at gmail.com Fri Jun 10 19:16:29 2016 From: buzzmandt at gmail.com (Dale Trombley) Date: Fri, 10 Jun 2016 15:16:29 -0400 Subject: kmymoney on 16.04 In-Reply-To: References: <1477398.McvIU5hgRF@jake-latitude-e6420> Message-ID: Ok, just re-added your ppa to my system and it's installing now. Thank you for the nudge in the right direction :) On Fri, Jun 10, 2016 at 3:15 PM, Dale Trombley wrote: > >> >> ^^^^ this looks odd, it is trying to install 14.04's package in 16.04? >> How did >> you add the ppa info? Most users have zero problems installing KMM in >> Kubuntu >> 16.04 using my ppa. >> >> Clay Weber >> >> >> I had your ppa installed on 14.04 and it did great. I upgraded 14.04 lts > to 16.04 lts and it removed kmymoney. trying to install it on here now > gives me that error > > -- *Webmaster and Admin for:* *nghsband.com , depotstreetfarmersmarket.com , netfa.org , mysummerfieldfarm.com , historicthreads.com , crockettfriends.com , traditionsbylittlebird.com , trombleyconstruction.com , tnparks.crockettfriends.com * -------------- next part -------------- An HTML attachment was scrubbed... URL: From mfraz74+ubuntu at gmail.com Mon Jun 13 10:21:48 2016 From: mfraz74+ubuntu at gmail.com (Mark Fraser) Date: Mon, 13 Jun 2016 11:21:48 +0100 Subject: Unable to start KMail after upgrade to 16.04 Message-ID: Upgraded to 16.04 yesterday and now I am unable to use KMail or that part of Kontact. Akonadi says something about not being able to connect to the database. I've tried moving .config/akonadi and .local/share/akonadi and starting akonadi, but it doesn't help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From post at volker-wysk.de Mon Jun 13 12:02:02 2016 From: post at volker-wysk.de (Volker Wysk) Date: Mon, 13 Jun 2016 14:02:02 +0200 Subject: Unable to start KMail after upgrade to 16.04 In-Reply-To: References: Message-ID: <2327427.31jWQhhTFa@desktop> Am Montag, 13. Juni 2016, 11:21:48 CEST schrieb Mark Fraser: > Upgraded to 16.04 yesterday and now I am unable to use KMail or that part > of Kontact. Akonadi says something about not being able to connect to the > database. I've tried moving .config/akonadi and .local/share/akonadi and > starting akonadi, but it doesn't help. Have you tried "akonadictl fsck"? Good Luck Volker From mfraz74+ubuntu at gmail.com Tue Jun 14 10:29:48 2016 From: mfraz74+ubuntu at gmail.com (Mark Fraser) Date: Tue, 14 Jun 2016 11:29:48 +0100 Subject: Unable to start KMail after upgrade to 16.04 In-Reply-To: <2327427.31jWQhhTFa@desktop> References: <2327427.31jWQhhTFa@desktop> Message-ID: On 13 June 2016 at 13:02, Volker Wysk wrote: > Am Montag, 13. Juni 2016, 11:21:48 CEST schrieb Mark Fraser: > > Upgraded to 16.04 yesterday and now I am unable to use KMail or that part > > of Kontact. Akonadi says something about not being able to connect to the > > database. I've tried moving .config/akonadi and .local/share/akonadi and > > starting akonadi, but it doesn't help. > > Have you tried "akonadictl fsck"? > Have been running akonadictl fsck for a few hours, but it doesn't seem to be doing anything. Here is the output of akonadictl start: search paths: ("/home/mfraser/bin", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games", "/snap/bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin") Found mysql_install_db: "/usr/bin/mysql_install_db" Found mysqlcheck: "/usr/bin/mysqlcheck" Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/mfraser/.local/share/akonadi/mysql.conf", "--datadir=/home/mfraser/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-mfraser.RtSzbz/mysql.socket") stdout: "" stderr: "" exit code: 1 process error: "Unknown error" terminating service threads terminating connection threads stopping db process mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/akonadi-mfraser.RtSzbz/mysql.socket' (2)' Check that mysqld is running and that the socket: '/tmp/akonadi-mfraser.RtSzbz/mysql.socket' exists! Failed to remove Unix socket Failed to remove runtime connection config file -------------- next part -------------- An HTML attachment was scrubbed... URL: From post at volker-wysk.de Tue Jun 14 12:00:58 2016 From: post at volker-wysk.de (Volker Wysk) Date: Tue, 14 Jun 2016 14:00:58 +0200 Subject: Unable to start KMail after upgrade to 16.04 In-Reply-To: References: <2327427.31jWQhhTFa@desktop> Message-ID: <2114108.a101fqvJ5f@desktop> Am Dienstag, 14. Juni 2016, 11:29:48 CEST schrieb Mark Fraser: > On 13 June 2016 at 13:02, Volker Wysk wrote: > > Am Montag, 13. Juni 2016, 11:21:48 CEST schrieb Mark Fraser: > > > Upgraded to 16.04 yesterday and now I am unable to use KMail or that > > > part > > > of Kontact. Akonadi says something about not being able to connect to > > > the > > > database. I've tried moving .config/akonadi and .local/share/akonadi and > > > starting akonadi, but it doesn't help. > > > > Have you tried "akonadictl fsck"? > > Have been running akonadictl fsck for a few hours, but it doesn't seem to > be doing anything. > > Here is the output of akonadictl start: > ... Sorry, I'm not an expert in Akonadi. Those messages don't tell me anything. Good luck V.W. From list at xenhideout.nl Fri Jun 17 23:35:51 2016 From: list at xenhideout.nl (Xen) Date: Sat, 18 Jun 2016 01:35:51 +0200 Subject: IO blocking under load Message-ID: <7cd1588ebfcc221021ac2d2d2d97e89b@dds.nl> I wonder if anyone can answer the question why or how a system could be experiencing total IO blocking for basically all processes under certain conditions. I am meaning to say that on this current system, I have experienced the majority of processes getting IO blocked (because they were reading from the disk what was seeing the "choke") for as long as 120 seconds or longer. Meaning: the entire system becomes unresponsive (if this is the system disk) if any process actually does try to read from the disk. This IO blocking happens on a per-disk basis, it is not the entire system. I have experienced it on a low SSD but I seem also to have experienced it on a regular HDD now. At least, while the SSD was connected, it was easy to reproduce it on the HDD as well. The way that I reproduce it is by having e.g. a writing DD process and two reading find -> cat processes. If you add a bunch of user programs (GUI programs) from KDE, it often enough to cause complete locking of the interface. If you go for a cup of tea, perhaps by the time you return it will have resolved itself, or not. Eventually the system resolves itself, but it can take a very long time. Basically I was trying to add a SDD to my system, but it didn't take very long for this to start happening. If anyone knows how or why this could happen, I would be much obliged if I had some pointers. For I am meaning to find out if it is due to the harddisk (SSD) or something else. I have not tried changing IO scheduler yet. Regards. From o.sinclair at gmail.com Sun Jun 19 06:11:03 2016 From: o.sinclair at gmail.com (O. Sinclair) Date: Sun, 19 Jun 2016 08:11:03 +0200 Subject: IO blocking under load In-Reply-To: <7cd1588ebfcc221021ac2d2d2d97e89b@dds.nl> References: <7cd1588ebfcc221021ac2d2d2d97e89b@dds.nl> Message-ID: <57663777.9090103@gmail.com> On 18/06/2016 01:35, Xen wrote: > I wonder if anyone can answer the question why or how a system could be > experiencing total IO blocking for basically all processes under certain > conditions. > > I am meaning to say that on this current system, I have experienced the > majority of processes getting IO blocked (because they were reading from > the disk what was seeing the "choke") for as long as 120 seconds or longer. > > Meaning: the entire system becomes unresponsive (if this is the system > disk) if any process actually does try to read from the disk. This IO > blocking happens on a per-disk basis, it is not the entire system. > > I have experienced it on a low SSD but I seem also to have experienced > it on a regular HDD now. At least, while the SSD was connected, it was > easy to reproduce it on the HDD as well. > > The way that I reproduce it is by having e.g. a writing DD process and > two reading find -> cat processes. > > If you add a bunch of user programs (GUI programs) from KDE, it often > enough to cause complete locking of the interface. If you go for a cup > of tea, perhaps by the time you return it will have resolved itself, or > not. Eventually the system resolves itself, but it can take a very long > time. > > Basically I was trying to add a SDD to my system, but it didn't take > very long for this to start happening. > > If anyone knows how or why this could happen, I would be much obliged if > I had some pointers. For I am meaning to find out if it is due to the > harddisk (SSD) or something else. > > I have not tried changing IO scheduler yet. Regards. > I can only give a very short answer: Yes I see it regularly since I started using an SDD instead of HDD. System is 14.10 since any attempt to go Plasma5 crashes totally. Regards, Sinclair From mfraz74+ubuntu at gmail.com Sun Jun 19 15:19:24 2016 From: mfraz74+ubuntu at gmail.com (Mark Fraser) Date: Sun, 19 Jun 2016 16:19:24 +0100 Subject: Unable to start KMail after upgrade to 16.04 In-Reply-To: <2114108.a101fqvJ5f@desktop> References: <2114108.a101fqvJ5f@desktop> Message-ID: <1498280.tycNZONbtG@rachael> On Tuesday, 14 June 2016 14:00:58 BST Volker Wysk wrote: > Am Dienstag, 14. Juni 2016, 11:29:48 CEST schrieb Mark Fraser: > > On 13 June 2016 at 13:02, Volker Wysk wrote: > > > Am Montag, 13. Juni 2016, 11:21:48 CEST schrieb Mark Fraser: > > > > Upgraded to 16.04 yesterday and now I am unable to use KMail or that > > > > part > > > > of Kontact. Akonadi says something about not being able to connect to > > > > the > > > > database. I've tried moving .config/akonadi and .local/share/akonadi > > > > and > > > > starting akonadi, but it doesn't help. > > > > > > Have you tried "akonadictl fsck"? > > > > Have been running akonadictl fsck for a few hours, but it doesn't seem to > > be doing anything. > > > > Here is the output of akonadictl start: > > ... > > Sorry, I'm not an expert in Akonadi. Those messages don't tell me anything. In the end I just created a new user directory and moved all my emails over. I can now see my emails, I just can't search them yet as it still says "still not indexed" -- Registered Linux User #466407 http://counter.li.org From list at xenhideout.nl Mon Jun 27 19:10:37 2016 From: list at xenhideout.nl (Xen) Date: Mon, 27 Jun 2016 21:10:37 +0200 Subject: KDE freezes for me. Message-ID: I just want to mention that I have regular KDE GUI freezes and I have no clue what causes it. It is about as nonspecific as it can get. I suspect the rest of my system keeps functioning as normal, so I just activated dropbear (I hope) as an SSH server so I can at least reset KDE from outside the system. I didn't have this on my previous install on the same computer, slightly (say 2 weeks) before 16.04 was released, and until I installed my new system, some time later. The mouse will freeze, the clock will keep ticking, and animitions continue to animate. The keyboard stop responding. *Sometimes* I am capable of pressing ctrl-alt-F2, but not always. Risk of losing work is excessive now. I am thinking of changing to mate of cinnamon or something so I can at least some work done :-/. Anyway, see ya. Oh, and I also have regular screen flickering. However this can always be solved with a KDE restart (service sddm restart). And it only happens (on ocassion) on a fresh restart, so, at some KDE starts there will be flickering, others (most) won't, and restarting it solves it, and it doesn't suddenly appear during a run (during system operation). This also happens in the Live environment, and I'm not sure if I should file a bug, or where, but I am using Nouveau drivers for an nVidia GPU, for all who care. See ya. From mfraz74+ubuntu at gmail.com Tue Jun 28 10:28:59 2016 From: mfraz74+ubuntu at gmail.com (Mark Fraser) Date: Tue, 28 Jun 2016 11:28:59 +0100 Subject: Problems since upgrading to 16.04 Message-ID: <2631050.ZnrEZOCYKt@rachael> After upgrading to 16.04 I was unable to use anything that required Akonadi as it kept crashing. I tried various things to get it working again, but in the end I decided to create a new user profile. This has worked apart from 3 continuing problems: 1) I have been unable to get indexing of my emails working again. 2) I no longer have the option in Amarok of deleting or moving a track to the waste bin from the context menu. I just have Add to playlist Replace playlist Add position marker Copy to collection Last.fm love Edit track details. 3) In Amarok's edit track details window, the folder icon always opens Dolphin instead of my default Konqueror. Can anyone help solve these problems? -- Registered Linux User #466407 http://counter.li.org From gkourtev at gmail.com Tue Jun 28 13:23:51 2016 From: gkourtev at gmail.com (Georgi Kourtev) Date: Tue, 28 Jun 2016 16:23:51 +0300 Subject: Writing accents Message-ID: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> Hi all, I moved to a new PC with just installed 16.04 with Plasma 5. Before on KDE4 I was able to write accents to letters by pressing the ALT key, the accent and then the actual letter. Now this feature does not work. I looked at the keyboard settings but none is actually making this happen. Any ideas? Thanks, gk From gkourtev at gmail.com Tue Jun 28 13:28:16 2016 From: gkourtev at gmail.com (Georgi Kourtev) Date: Tue, 28 Jun 2016 16:28:16 +0300 Subject: Kmail address book does not work Message-ID: <1950636.N5mR65c3ui@gkourtev-inspiron-5559> Hi, On a fresh installation of 16.04 with Plasma 5. The address book (google in my case) is not accessible in new messages. I can get the address I need only by pressing Select at the right end of the TO field. Only recent addresses show up. The autocompletion in Kmail settings ---> Composer are correct. Browsed internet but could not find a solution. Thanks for any suggestion. gk From sarunas at math.dartmouth.edu Tue Jun 28 14:29:04 2016 From: sarunas at math.dartmouth.edu (Sarunas Burdulis) Date: Tue, 28 Jun 2016 10:29:04 -0400 Subject: Writing accents In-Reply-To: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> References: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> Message-ID: <577289B0.60206@math.dartmouth.edu> On 06/28/2016 09:23 AM, Georgi Kourtev wrote: > Hi all, > > I moved to a new PC with just installed 16.04 with Plasma 5. Before on KDE4 I > was able to write accents to letters by pressing the ALT key, the accent and > then the actual letter. > > Now this feature does not work. I looked at the keyboard settings but none is > actually making this happen. Any ideas? I use "Compose key" setting for this. System Settings → Input dev. → Advanced → Position of Compose key. -- Sarunas Burdulis http://math.dartmouth.edu/~sarunas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From dmcgarrett at optonline.net Tue Jun 28 20:32:16 2016 From: dmcgarrett at optonline.net (Doug) Date: Tue, 28 Jun 2016 15:32:16 -0500 Subject: Writing accents In-Reply-To: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> References: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> Message-ID: <5772DED0.8020600@optonline.net> On 06/28/2016 08:23 AM, Georgi Kourtev wrote: > Hi all, > > I moved to a new PC with just installed 16.04 with Plasma 5. Before on KDE4 I > was able to write accents to letters by pressing the ALT key, the accent and > then the actual letter. > > Now this feature does not work. I looked at the keyboard settings but none is > actually making this happen. Any ideas? > > Thanks, > gk > You were using a COMPOSE key. In your keyboard setup there should be an option to set a compose key. I use the right alt key, but if you have a Windows K/B, then the right Win key would be a logical choice. --doug From zekkerj at gmail.com Tue Jun 28 22:15:20 2016 From: zekkerj at gmail.com (=?UTF-8?Q?Jos=C3=A9_Queiroz?=) Date: Tue, 28 Jun 2016 19:15:20 -0300 Subject: Writing accents In-Reply-To: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> References: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> Message-ID: 2016-06-28 10:23 GMT-03:00 Georgi Kourtev : > Hi all, > > I moved to a new PC with just installed 16.04 with Plasma 5. Before on > KDE4 I > was able to write accents to letters by pressing the ALT key, the accent > and > then the actual letter. > > Now this feature does not work. I looked at the keyboard settings but none > is > actually making this happen. Any ideas? > You may switch to an international keyboard, so the accent keys will automatically compose to the subsequent letters. That's how we use to work in Brasil. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gkourtev at gmail.com Wed Jun 29 06:02:21 2016 From: gkourtev at gmail.com (Georgi Kourtev) Date: Wed, 29 Jun 2016 09:02:21 +0300 Subject: Writing accents In-Reply-To: <5772DED0.8020600@optonline.net> References: <9848713.aE1lC40JkX@gkourtev-inspiron-5559> <5772DED0.8020600@optonline.net> Message-ID: <4860481.cjiLyjiExF@gkourtev-inspiron-5559> On вторник, 28 юни 2016 г. 15:32:16 EEST Doug wrote: > On 06/28/2016 08:23 AM, Georgi Kourtev wrote: > > Hi all, > > > > I moved to a new PC with just installed 16.04 with Plasma 5. Before on > > KDE4 I was able to write accents to letters by pressing the ALT key, the > > accent and then the actual letter. > > > > Now this feature does not work. I looked at the keyboard settings but none > > is actually making this happen. Any ideas? > > > > Thanks, > > gk > > You were using a COMPOSE key. In your keyboard setup there should be an > option to set a compose key. I use the right alt key, but if you have a > Windows > K/B, then the right Win key would be a logical choice. > > --doug Thanks. It is in the keyboard setting Position of the Compose key. gk From kassube at gmx.net Wed Jun 29 06:27:31 2016 From: kassube at gmx.net (Nils Kassube) Date: Wed, 29 Jun 2016 08:27:31 +0200 Subject: KDE freezes for me. In-Reply-To: References: Message-ID: <2578644.2oZ03lN96R@p5915> Xen wrote: > I just want to mention that I have regular KDE GUI freezes and I have > no clue what causes it. > > It is about as nonspecific as it can get. I suspect the rest of my > system keeps functioning as normal, so I just activated dropbear (I > hope) as an SSH server so I can at least reset KDE from outside the > system. > > I didn't have this on my previous install on the same computer, > slightly (say 2 weeks) before 16.04 was released, and until I > installed my new system, some time later. > > The mouse will freeze, the clock will keep ticking, and animitions > continue to animate. The keyboard stop responding. You could try if it makes a difference if you replug your mouse / keyboard. > Oh, and I also have regular screen flickering. However this can always > be solved with a KDE restart (service sddm restart). > > And it only happens (on ocassion) on a fresh restart, so, at some KDE > starts there will be flickering, others (most) won't, and restarting > it solves it, and it doesn't suddenly appear during a run (during > system operation). This also happens in the Live environment, and I'm > not sure if I should file a bug, or where, but I am using Nouveau > drivers for an nVidia GPU, for all who care. I have seen screen flickering with the Nouveau driver, but that's not new with 16.04 - with the nvidia driver I don't see this problem. Maybe you should try the nvidia driver and see if the freezes still happen. Nils From list at xenhideout.nl Thu Jun 30 13:44:02 2016 From: list at xenhideout.nl (Xen) Date: Thu, 30 Jun 2016 15:44:02 +0200 Subject: KDE freezes for me. In-Reply-To: <2578644.2oZ03lN96R@p5915> References: <2578644.2oZ03lN96R@p5915> Message-ID: Nils Kassube schreef op 29-06-2016 8:27: >> The mouse will freeze, the clock will keep ticking, and animitions >> continue to animate. The keyboard stop responding. > > You could try if it makes a difference if you replug your mouse / > keyboard. Hi, thanks, yes, I believe I have already tried that. > I have seen screen flickering with the Nouveau driver, but that's not > new with 16.04 - with the nvidia driver I don't see this problem. Maybe > you should try the nvidia driver and see if the freezes still happen. Yes I initially thought it might be due to the nVidia driver in part, so I uninstalled it after. But it didn't make a difference. Maybe I just need to wipe my KDE dir (homedir), I don't know.