From mdhirsch at gmail.com Fri Oct 7 04:51:10 2016 From: mdhirsch at gmail.com (Michael Hirsch) Date: Thu, 6 Oct 2016 22:51:10 -0600 Subject: Akonadi won't start In-Reply-To: References: Message-ID: On Thu, Sep 22, 2016 at 10:49 PM, Michael Hirsch wrote: > On Fri, Sep 16, 2016 at 10:16 AM, Kai Stian Olstad > wrote: >> On 16. sep. 2016 06:28, Michael Hirsch wrote: >>> >>> I put the latest and greatest Kubuntu on my laptop and kontact >>> complains that akonadi won't start. When I start it by hand I get >>> these messages. Can anyone figure out what I'm missing? >> >> >> Did you do a upgrade? If so, from which version? > > No, this is a fresh install of 16.04. Of course, I grab the updates > when they come out. Removing ~/.local/share/akon* sems to have fixed things. I don't know what caused the trouble, but I can read mail, again. :-) Michael From cody.smith at ubuntu.com Fri Oct 7 04:58:56 2016 From: cody.smith at ubuntu.com (Cody Smith) Date: Thu, 6 Oct 2016 21:58:56 -0700 Subject: Akonadi won't start In-Reply-To: References: Message-ID: It could be as simple as a corrupt file in there. There's a lot that a corrupt config file or database could throw a wrench in. --c_smith On Thu, Oct 6, 2016 at 9:51 PM, Michael Hirsch wrote: > On Thu, Sep 22, 2016 at 10:49 PM, Michael Hirsch > wrote: > > On Fri, Sep 16, 2016 at 10:16 AM, Kai Stian Olstad > > wrote: > >> On 16. sep. 2016 06:28, Michael Hirsch wrote: > >>> > >>> I put the latest and greatest Kubuntu on my laptop and kontact > >>> complains that akonadi won't start. When I start it by hand I get > >>> these messages. Can anyone figure out what I'm missing? > >> > >> > >> Did you do a upgrade? If so, from which version? > > > > No, this is a fresh install of 16.04. Of course, I grab the updates > > when they come out. > > Removing ~/.local/share/akon* sems to have fixed things. I don't know > what caused the trouble, but I can read mail, again. > > :-) > > Michael > > -- > 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 tsimonq2 at ubuntu.com Sat Oct 8 15:48:26 2016 From: tsimonq2 at ubuntu.com (Simon Quigley) Date: Sat, 8 Oct 2016 10:48:26 -0500 Subject: Fwd: Yakkety Final weekend testing ISOs In-Reply-To: <20161008154101.GV4433@0c3.net> References: <20161008154101.GV4433@0c3.net> Message-ID: <57F9154A.3020300@ubuntu.com> We need help testing! Some things aren't fully migrated yet, but most of it should work. Please report any problems as a response to this email or to #kubuntu-devel on freenode. Thanks! -------- Forwarded Message -------- Subject: Yakkety Final weekend testing ISOs Date: Sat, 8 Oct 2016 15:41:01 +0000 From: Adam Conrad To: ubuntu-release at lists.ubuntu.com The ISO tracker[1] is posting images for Yakkety Final testing right now. Some are there, some are coming in the next hour or two. These are *not* final images (they'll still claim to be beta, etc), but we need as much testing on them as we can get and bugs reported so we can fix up as many issues as we have time for before we start rolling real RC images on Monday. So, please, don't pop in the IRC channel and say something like "are these the final images, because I don't want to waste my time testing non-final images", if they were final, there'd be no reason to test. We need testing. Lots of it. And fixes to follow the testing. So grab an ISO for your favourite flavour and kick the tires. And the steering wheel. And the fuel pump. And that little dohickey that used to be a cigarette lighter but people now plug their GPS into. ... Adam [1] http://iso.qa.ubuntu.com/qatracker/milestones/368/builds -- Ubuntu-release mailing list Ubuntu-release at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmarsh at bmarsh.com Sat Oct 8 16:14:37 2016 From: bmarsh at bmarsh.com (bmarsh at bmarsh.com) Date: Sat, 8 Oct 2016 12:14:37 -0400 Subject: Yakkety Final weekend testing ISOs In-Reply-To: <57F9154A.3020300@ubuntu.com> References: <20161008154101.GV4433@0c3.net> <57F9154A.3020300@ubuntu.com> Message-ID: I've been using Yakkety for over a week and it has been one of the best releases I've seen yet. I've had only one strange problem (Amd64 version). When I boot/reboot my machine, DNS fails to work locally. I have a local DNS cache server that has been working for years. After a boot I can get addresses outside of my network but not locally. Ok, you say this might be my problem and I might agree with that. However I have never had problems with this setup and everything looks normal. How do I fix the problem? All I have to do to carry on is to edit the /etc/resolv.conf file, without any changes, and file it. And I'm good to go. No changes whatever anywhere. I've tried to track down what does change with the edit but haven't seen any differences. > On Oct 8, 2016, at 11:48 AM, Simon Quigley wrote: > > We need help testing! Some things aren't fully migrated yet, but most of it should work. > > Please report any problems as a response to this email or to #kubuntu-devel on freenode. > > Thanks! > -------- Forwarded Message -------- > Subject: > Yakkety Final weekend testing ISOs > Date: > Sat, 8 Oct 2016 15:41:01 +0000 > From: > Adam Conrad > To: > ubuntu-release at lists.ubuntu.com > The ISO tracker[1] is posting images for Yakkety Final testing right > now. Some are there, some are coming in the next hour or two. > > These are *not* final images (they'll still claim to be beta, etc), > but we need as much testing on them as we can get and bugs reported > so we can fix up as many issues as we have time for before we start > rolling real RC images on Monday. > > So, please, don't pop in the IRC channel and say something like "are > these the final images, because I don't want to waste my time testing > non-final images", if they were final, there'd be no reason to test. > > We need testing. Lots of it. And fixes to follow the testing. So > grab an ISO for your favourite flavour and kick the tires. And the > steering wheel. And the fuel pump. And that little dohickey that > used to be a cigarette lighter but people now plug their GPS into. > > ... Adam > > [1] http://iso.qa.ubuntu.com/qatracker/milestones/368/builds > > -- > Ubuntu-release mailing list > Ubuntu-release at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release > > -- > 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 bmarsh at bmarsh.com Sat Oct 8 16:52:03 2016 From: bmarsh at bmarsh.com (Bruce Marshall) Date: Sat, 8 Oct 2016 12:52:03 -0400 Subject: Yakkety Final weekend testing ISOs In-Reply-To: References: <20161008154101.GV4433@0c3.net> <57F9154A.3020300@ubuntu.com> Message-ID: <57F92433.40601@bmarsh.com> On 10/08/2016 12:14 PM, bmarsh at bmarsh.com wrote: > I've been using Yakkety for over a week and it has been one of the > best releases I've seen yet. > > I've had only one strange problem (Amd64 version). When I boot/reboot > my machine, DNS fails to work locally. I have a local DNS cache > server that has been working for years. After a boot I can get > addresses outside of my network but not locally. > > Ok, you say this might be my problem and I might agree with that. > However I have never had problems with this setup and everything > looks normal. > > How do I fix the problem? All I have to do to carry on is to edit the > /etc/resolv.conf file, without any changes, and file it. And I'm good > to go. No changes whatever anywhere. > > I've tried to track down what does change with the edit but haven't > seen any differences. > > On Oct 8, 2016, at 11:48 AM, Simon Quigley > wrote: A follow up.... Just loaded up all the latest updates (a lot!!) and the problem appears to be gone. -- "...without self-respect, few people are able to feel genuine respect for others." Eleanor Roosevelt -------------- next part -------------- An HTML attachment was scrubbed... URL: From dutch.glory at yahoo.com Sat Oct 8 19:07:56 2016 From: dutch.glory at yahoo.com (=?UTF-8?Q?Andr=c3=a9_Verwijs?=) Date: Sat, 8 Oct 2016 21:07:56 +0200 Subject: Fwd: Yakkety Final weekend testing ISOs In-Reply-To: <57F9154A.3020300@ubuntu.com> References: <20161008154101.GV4433@0c3.net> <57F9154A.3020300@ubuntu.com> Message-ID: installation went fine, but doesn't boot.... Op 8-10-2016 om 17:48 schreef Simon Quigley: > We need help testing! Some things aren't fully migrated yet, but most of it should work. > > Please report any problems as a response to this email or to #kubuntu-devel on freenode. > > Thanks! > > -------- Forwarded Message -------- > > Subject: > > Yakkety Final weekend testing ISOs > > Date: > > Sat, 8 Oct 2016 15:41:01 +0000 > > From: > > Adam Conrad > > To: > > ubuntu-release at lists.ubuntu.com > > The ISO tracker[1] is posting images for Yakkety Final testing right > now. Some are there, some are coming in the next hour or two. > > These are *not* final images (they'll still claim to be beta, etc), > but we need as much testing on them as we can get and bugs reported > so we can fix up as many issues as we have time for before we start > rolling real RC images on Monday. > > So, please, don't pop in the IRC channel and say something like "are > these the final images, because I don't want to waste my time testing > non-final images", if they were final, there'd be no reason to test. > > We need testing. Lots of it. And fixes to follow the testing. So > grab an ISO for your favourite flavour and kick the tires. And the > steering wheel. And the fuel pump. And that little dohickey that > used to be a cigarette lighter but people now plug their GPS into. > > ... Adam > > [1] http://iso.qa.ubuntu.com/qatracker/milestones/368/builds > > -- > Ubuntu-release mailing list > Ubuntu-release at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release > > > > -- ______________________________________________________________________________________ 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 taholmes160 at gmail.com Mon Oct 10 22:17:01 2016 From: taholmes160 at gmail.com (Timothy Holmes) Date: Mon, 10 Oct 2016 22:17:01 +0000 Subject: Odd start up issue Message-ID: I just finished an install of a kubuntu 16.04 system. When I try to boot, it drops me to an initramfs prompt. Whats wrong, and more importantly how do I fix it Tim -- Tim Holmes - W8TAH Sent from my LG Stylo -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmarsh at bmarsh.com Mon Oct 10 22:22:41 2016 From: bmarsh at bmarsh.com (bmarsh at bmarsh.com) Date: Mon, 10 Oct 2016 18:22:41 -0400 Subject: Odd start up issue In-Reply-To: References: Message-ID: Most likely it couldn't mount something.... but the prior messages should tell you that. > On Oct 10, 2016, at 6:17 PM, Timothy Holmes wrote: > > I just finished an install of a kubuntu 16.04 system. When I try to boot, it drops me to an initramfs prompt. Whats wrong, and more importantly how do I fix it > > Tim > -- > Tim Holmes - W8TAH > Sent from my LG Stylo > > -- > 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 taholmes160 at gmail.com Mon Oct 10 22:26:25 2016 From: taholmes160 at gmail.com (Timothy Holmes) Date: Mon, 10 Oct 2016 22:26:25 +0000 Subject: Odd start up issue In-Reply-To: References: Message-ID: Hummmm. Didnt see any, but ill restart and try again On Mon, Oct 10, 2016, 6:23 PM bmarsh at bmarsh.com wrote: > Most likely it couldn't mount something.... but the prior messages should > tell you that. > > On Oct 10, 2016, at 6:17 PM, Timothy Holmes wrote: > > I just finished an install of a kubuntu 16.04 system. When I try to boot, > it drops me to an initramfs prompt. Whats wrong, and more importantly how > do I fix it > > Tim > -- > > Tim Holmes - W8TAH > Sent from my LG Stylo > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > -- Tim Holmes - W8TAH Sent from my LG Stylo -------------- next part -------------- An HTML attachment was scrubbed... URL: From taholmes160 at gmail.com Mon Oct 10 22:32:16 2016 From: taholmes160 at gmail.com (Timothy Holmes) Date: Mon, 10 Oct 2016 22:32:16 +0000 Subject: Odd start up issue In-Reply-To: References: Message-ID: Ok It showed me the grub meny with ubuntu highlighted and then the following BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash) enter 'help' for a list of built in commands (Initramfs) On Mon, Oct 10, 2016, 6:26 PM Timothy Holmes wrote: Hummmm. Didnt see any, but ill restart and try again On Mon, Oct 10, 2016, 6:23 PM bmarsh at bmarsh.com wrote: Most likely it couldn't mount something.... but the prior messages should tell you that. On Oct 10, 2016, at 6:17 PM, Timothy Holmes wrote: I just finished an install of a kubuntu 16.04 system. When I try to boot, it drops me to an initramfs prompt. Whats wrong, and more importantly how do I fix it Tim -- Tim Holmes - W8TAH Sent from my LG Stylo -- kubuntu-users mailing list kubuntu-users at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users -- kubuntu-users mailing list kubuntu-users at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users -- Tim Holmes - W8TAH Sent from my LG Stylo -- Tim Holmes - W8TAH Sent from my LG Stylo -------------- next part -------------- An HTML attachment was scrubbed... URL: From taholmes160 at gmail.com Mon Oct 10 22:36:19 2016 From: taholmes160 at gmail.com (Timothy Holmes) Date: Mon, 10 Oct 2016 22:36:19 +0000 Subject: Odd start up issue In-Reply-To: References: Message-ID: Running fsck/dev/sda1 is fixing a bunch of inode errors On Mon, Oct 10, 2016, 6:32 PM Timothy Holmes wrote: > Ok > It showed me the grub meny with ubuntu highlighted and then the following > > BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash) > enter 'help' for a list of built in commands > > (Initramfs) > > > On Mon, Oct 10, 2016, 6:26 PM Timothy Holmes > wrote: > > Hummmm. Didnt see any, but ill restart and try again > > On Mon, Oct 10, 2016, 6:23 PM bmarsh at bmarsh.com wrote: > > Most likely it couldn't mount something.... but the prior messages should > tell you that. > > On Oct 10, 2016, at 6:17 PM, Timothy Holmes wrote: > > I just finished an install of a kubuntu 16.04 system. When I try to boot, > it drops me to an initramfs prompt. Whats wrong, and more importantly how > do I fix it > > Tim > -- > > Tim Holmes - W8TAH > Sent from my LG Stylo > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > -- > > Tim Holmes - W8TAH > Sent from my LG Stylo > > -- > > Tim Holmes - W8TAH > Sent from my LG Stylo > -- Tim Holmes - W8TAH Sent from my LG Stylo -------------- next part -------------- An HTML attachment was scrubbed... URL: From gatorforge07 at gmail.com Tue Oct 11 10:02:13 2016 From: gatorforge07 at gmail.com (Jim Croft) Date: Tue, 11 Oct 2016 06:02:13 -0400 Subject: Failure of reboot after update Message-ID: I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series computer. The last two updates, when prompted to reboot, I clicked on the prompt and the reboot failed. The computer froze on the initial Toshiba banner page which is supposed to allow access via F2 to Setup Utility or by F12 to Boot Manager. The first time this happened, I tried to boot from a thumb drive. The computer gave a message, but when I attempted a normal boot, it worked, and continued to work, through several reboots, for several days. However, the next time I updated, and clicked the reboot prompt, the reboot again failed, and the previous work-around did not work. The computer will not get beyond the Toshiba introductory banner described previously. Any recommendations? I am not very familiar with Kubuntu, and am only semi-literate on computers in general, so please put it in “baby talk”! -------------- next part -------------- An HTML attachment was scrubbed... URL: From grokit at ajinfosearch.com Tue Oct 11 14:30:49 2016 From: grokit at ajinfosearch.com (Alan Dacey (grokit)) Date: Tue, 11 Oct 2016 10:30:49 -0400 Subject: Failure of reboot after update In-Reply-To: References: Message-ID: <2980471.Gy0npmdZf6@kirk> Going by where the boot process stopped the problem may be your hard drive and not software. Could be your hardware too but let's rule out your hard drive first. Open a terminal any paste the output of the following in your response: sudo smartctl --all /dev/sda If it complains about an ATA device behind a SAT layer then use the following: sudo smartctl -d sat --all /dev/sda That will give an estimate of your disk's health. You then should run a long test, this will take a while, like 45 minutes to an hour and a half depending on the size of your disk. Smartctl will tell you how long it will take so after that time run the command above again and look for any changes. Use the following command to run a long test: sudo smartctl --test=long /dev/sda It is possible but unlikely that you'll need to enable smart logging on your disk. You'll know if you get no real output. Use this command to start logging: smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda If the command 'smartctl' is not found you'll need to install the package first. sudo apt-get install smartmontools You can install a graphical front end with the package gsmartcontrol but if smartctl complained about the layer stuff then you need to go to Options-->Preferences and add "-d sat" (without quotes) in the "Smartctl parameters" box and rescan. On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: > I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series computer. > > The last two updates, when prompted to reboot, I clicked on the prompt and the reboot failed. The computer froze on the initial Toshiba banner page which is supposed to allow access via F2 to Setup Utility or by F12 to Boot Manager. The first time this happened, I tried to boot from a thumb drive. The computer gave a message, but when I attempted a normal boot, it worked, and continued to work, through several reboots, for several days. However, the next time I updated, and clicked the reboot prompt, the reboot again failed, and the previous work-around did not work. The computer will not get beyond the Toshiba introductory banner described previously. Any recommendations? I am not very familiar with Kubuntu, and am only semi-literate on computers in general, so please put it in “baby talk”! -------------- next part -------------- An HTML attachment was scrubbed... URL: From gatorforge07 at gmail.com Tue Oct 11 16:23:37 2016 From: gatorforge07 at gmail.com (Jim Croft) Date: Tue, 11 Oct 2016 12:23:37 -0400 Subject: Failure of reboot after update In-Reply-To: <2980471.Gy0npmdZf6@kirk> References: <2980471.Gy0npmdZf6@kirk> Message-ID: <3297EC7340184357A88D30C20831BA62@JimPC> Thank you for your prompt reply. I am not able to follow the instructions because now I cannot get the computer to boot at all. I will probably have to take it to a shop, and I can’t afford that for a couple of weeks. I do have another computer running Windows 10, so am not desperate. The Kubuntu machine is a toy until I get it working well, and gain enough experience to really use it for practical purposes. Thanks, Jim Croft From: Alan Dacey (grokit) Sent: Tuesday, October 11, 2016 10:30 To: Kubuntu user technical support Subject: Re: Failure of reboot after update Going by where the boot process stopped the problem may be your hard drive and not software. Could be your hardware too but let's rule out your hard drive first. Open a terminal any paste the output of the following in your response: sudo smartctl --all /dev/sda If it complains about an ATA device behind a SAT layer then use the following: sudo smartctl -d sat --all /dev/sda That will give an estimate of your disk's health. You then should run a long test, this will take a while, like 45 minutes to an hour and a half depending on the size of your disk. Smartctl will tell you how long it will take so after that time run the command above again and look for any changes. Use the following command to run a long test: sudo smartctl --test=long /dev/sda It is possible but unlikely that you'll need to enable smart logging on your disk. You'll know if you get no real output. Use this command to start logging: smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda If the command 'smartctl' is not found you'll need to install the package first. sudo apt-get install smartmontools You can install a graphical front end with the package gsmartcontrol but if smartctl complained about the layer stuff then you need to go to Options-->Preferences and add "-d sat" (without quotes) in the "Smartctl parameters" box and rescan. On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: > I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series computer. > > The last two updates, when prompted to reboot, I clicked on the prompt and the reboot failed. The computer froze on the initial Toshiba banner page which is supposed to allow access via F2 to Setup Utility or by F12 to Boot Manager. The first time this happened, I tried to boot from a thumb drive. The computer gave a message, but when I attempted a normal boot, it worked, and continued to work, through several reboots, for several days. However, the next time I updated, and clicked the reboot prompt, the reboot again failed, and the previous work-around did not work. The computer will not get beyond the Toshiba introductory banner described previously. Any recommendations? I am not very familiar with Kubuntu, and am only semi-literate on computers in general, so please put it in “baby talk”! -------------------------------------------------------------------------------- -- 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 bmarsh at bmarsh.com Tue Oct 11 16:44:40 2016 From: bmarsh at bmarsh.com (In motion) Date: Tue, 11 Oct 2016 12:44:40 -0400 Subject: Failure of reboot after update In-Reply-To: <3297EC7340184357A88D30C20831BA62@JimPC> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> Message-ID: > On Oct 11, 2016, at 12:23 PM, Jim Croft wrote: > > Thank you for your prompt reply. > I am not able to follow the instructions because now I cannot get the computer to boot at all. I will probably have to take it to a shop, and I can’t afford that for a couple of weeks. I do have another computer running Windows 10, so am not desperate. The Kubuntu machine is a toy until I get it working well, and gain enough experience to really use it for practical purposes. > > Thanks, > > Jim Croft > Although this doesn't help your situation, I have installed 16.10 on a Toshiba laptop without problems. Kinda points to hardware in your case. > From: Alan Dacey (grokit) > Sent: Tuesday, October 11, 2016 10:30 > To: Kubuntu user technical support > Subject: Re: Failure of reboot after update > > Going by where the boot process stopped the problem may be your hard drive and not software. Could be your hardware too but let's rule out your hard drive first. > Open a terminal any paste the output of the following in your response: > sudo smartctl --all /dev/sda > If it complains about an ATA device behind a SAT layer then use the following: > sudo smartctl -d sat --all /dev/sda > > That will give an estimate of your disk's health. You then should run a long test, this will take a while, like 45 minutes to an hour and a half depending on the size of your disk. Smartctl will tell you how long it will take so after that time run the command above again and look for any changes. > Use the following command to run a long test: > sudo smartctl --test=long /dev/sda > > It is possible but unlikely that you'll need to enable smart logging on your disk. You'll know if you get no real output. > Use this command to start logging: > smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda > > If the command 'smartctl' is not found you'll need to install the package first. > sudo apt-get install smartmontools > You can install a graphical front end with the package gsmartcontrol but if smartctl complained about the layer stuff then you need to go to Options-->Preferences and add "-d sat" (without quotes) in the "Smartctl parameters" box and rescan. > > > On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: > > I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series computer. > > > > The last two updates, when prompted to reboot, I clicked on the prompt and the reboot failed. The computer froze on the initial Toshiba banner page which is supposed to allow access via F2 to Setup Utility or by F12 to Boot Manager. The first time this happened, I tried to boot from a thumb drive. The computer gave a message, but when I attempted a normal boot, it worked, and continued to work, through several reboots, for several days. However, the next time I updated, and clicked the reboot prompt, the reboot again failed, and the previous work-around did not work. The computer will not get beyond the Toshiba introductory banner described previously. Any recommendations? I am not very familiar with Kubuntu, and am only semi-literate on computers in general, so please put it in “baby talk”! > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > -- > 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 list at xenhideout.nl Tue Oct 11 17:19:43 2016 From: list at xenhideout.nl (Xen) Date: Tue, 11 Oct 2016 19:19:43 +0200 Subject: Failure of reboot after update In-Reply-To: <3297EC7340184357A88D30C20831BA62@JimPC> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> Message-ID: <047079369d77855609626d1deb89c7fc@dds.nl> Jim Croft schreef op 11-10-2016 18:23: > Thank you for your prompt reply. > I am not able to follow the instructions because now I cannot get the > computer to boot at all. I will probably have to take it to a shop, > and I can’t afford that for a couple of weeks. I do have another > computer running Windows 10, so am not desperate. The Kubuntu machine > is a toy until I get it working well, and gain enough experience to > really use it for practical purposes. Jim, normally speaking your hard-drive installation can have no influence over whether some USB stick boots or not. Windows normally can have trouble with booting from e.g. DVD when the master boot record of the harddrive is not correct, a very annoying situation. But any Linux boot-stick that will boot without regard of an existing system should boot flawlessly no matter what some Kubuntu update may have done. It is almost impossible that Kubuntu could cause your system to hang at the Toshiba screen because normally whatever goes wrong you should *always* get a grub prompt. It cannot even normally be your harddisk, that could ever cause your stick to fail booting. Should not be possible. So those are the thing that can't be true. So the first thing you would ever need to do at this point is to get your stick to boot (forget about the system in the meantime) or to run some (Kubuntu) live DVD. You must if you can still run Linux and Windows installation DVDs from some external DVD drive, for example. If those things work, then you can go on to the text step. Particularly if you can boot into Linux (Kubuntu) I am sure there are people that could help you troubleshoot from there on. Most importantly you will be able to access your internal harddisk. What Alan meant was accessing the drive to check on S.M.A.R.T. which is a measure of your drive's health. But if you can't even boot an usb stick (or DVD), that won't be necessary. Regardless you *could* take the hard drive out and hook it onto your Windows 10 computer, but can be difficult because of connectors. Or if you think it's fun you could at least take the hard drive out to see if it will boot without it (some usb stick or DVD). Generally for a laptop there is only one other thing you can check and that is the RAM (memory). Typically what you say indicates that either the RAM has gone bad or your laptop has died. Some laptops have very sudden RAM failures, I've been told. Your laptop was released in January, 2014. Perhaps you still have warranty? Having installed Linux on it should not void it (this is a hardware problem). Regards. > > Thanks, > > Jim Croft > > FROM: Alan Dacey (grokit) > SENT: Tuesday, October 11, 2016 10:30 > TO: Kubuntu user technical support > SUBJECT: Re: Failure of reboot after update > > Going by where the boot process stopped the problem may be your hard > drive and not software. Could be your hardware too but let's rule out > your hard drive first. > > Open a terminal any paste the output of the following in your > response: > > sudo smartctl --all /dev/sda > > If it complains about an ATA device behind a SAT layer then use the > following: > > sudo smartctl -d sat --all /dev/sda > > That will give an estimate of your disk's health. You then should run > a long test, this will take a while, like 45 minutes to an hour and a > half depending on the size of your disk. Smartctl will tell you how > long it will take so after that time run the command above again and > look for any changes. > > Use the following command to run a long test: > > sudo smartctl --test=long /dev/sda > > It is possible but unlikely that you'll need to enable smart logging > on your disk. You'll know if you get no real output. > > Use this command to start logging: > > smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda > > If the command 'smartctl' is not found you'll need to install the > package first. > > sudo apt-get install smartmontools > > You can install a graphical front end with the package gsmartcontrol > but if smartctl complained about the layer stuff then you need to go > to Options-->Preferences and add "-d sat" (without quotes) in the > "Smartctl parameters" box and rescan. > > On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: > >> I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series > computer. > >> > >> The last two updates, when prompted to reboot, I clicked on the > prompt and the reboot failed. The computer froze on the initial > Toshiba banner page which is supposed to allow access via F2 to Setup > Utility or by F12 to Boot Manager. The first time this happened, I > tried to boot from a thumb drive. The computer gave a > message, but when I attempted a normal boot, it worked, and continued > to work, through several reboots, for several days. However, the next > time I updated, and clicked the reboot prompt, the reboot again > failed, and the previous work-around did not work. The computer will > not get beyond the Toshiba introductory banner described previously. > Any recommendations? I am not very familiar with Kubuntu, and am only > semi-literate on computers in general, so please put it in “baby > talk”! > > ------------------------- > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users From gatorforge07 at gmail.com Tue Oct 11 18:26:41 2016 From: gatorforge07 at gmail.com (Jim Croft) Date: Tue, 11 Oct 2016 14:26:41 -0400 Subject: Failure of reboot after update In-Reply-To: <047079369d77855609626d1deb89c7fc@dds.nl> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> Message-ID: <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> The thumb drive was not a bootable drive. It had a Kubuntu 16.04 download, but an installation download, not a bootable one, so the fact that it would not boot from there may not mean anything (am I right?) Anyway, I will not bother you any more until I get someone who is tech-savvy to check out the computer. It is older than you wrote, I copied the wrong ID for the machine. It is a Satellite A305-S6872, model PSAG8U-02E018, and is several years old. Thanks, Jim Croft -----Original Message----- From: Xen Sent: Tuesday, October 11, 2016 13:19 To: kubuntu-users at lists.ubuntu.com Subject: Re: Failure of reboot after update Jim Croft schreef op 11-10-2016 18:23: > Thank you for your prompt reply. > I am not able to follow the instructions because now I cannot get the > computer to boot at all. I will probably have to take it to a shop, > and I can’t afford that for a couple of weeks. I do have another > computer running Windows 10, so am not desperate. The Kubuntu machine > is a toy until I get it working well, and gain enough experience to > really use it for practical purposes. Jim, normally speaking your hard-drive installation can have no influence over whether some USB stick boots or not. Windows normally can have trouble with booting from e.g. DVD when the master boot record of the harddrive is not correct, a very annoying situation. But any Linux boot-stick that will boot without regard of an existing system should boot flawlessly no matter what some Kubuntu update may have done. It is almost impossible that Kubuntu could cause your system to hang at the Toshiba screen because normally whatever goes wrong you should *always* get a grub prompt. It cannot even normally be your harddisk, that could ever cause your stick to fail booting. Should not be possible. So those are the thing that can't be true. So the first thing you would ever need to do at this point is to get your stick to boot (forget about the system in the meantime) or to run some (Kubuntu) live DVD. You must if you can still run Linux and Windows installation DVDs from some external DVD drive, for example. If those things work, then you can go on to the text step. Particularly if you can boot into Linux (Kubuntu) I am sure there are people that could help you troubleshoot from there on. Most importantly you will be able to access your internal harddisk. What Alan meant was accessing the drive to check on S.M.A.R.T. which is a measure of your drive's health. But if you can't even boot an usb stick (or DVD), that won't be necessary. Regardless you *could* take the hard drive out and hook it onto your Windows 10 computer, but can be difficult because of connectors. Or if you think it's fun you could at least take the hard drive out to see if it will boot without it (some usb stick or DVD). Generally for a laptop there is only one other thing you can check and that is the RAM (memory). Typically what you say indicates that either the RAM has gone bad or your laptop has died. Some laptops have very sudden RAM failures, I've been told. Your laptop was released in January, 2014. Perhaps you still have warranty? Having installed Linux on it should not void it (this is a hardware problem). Regards. > > Thanks, > > Jim Croft > > FROM: Alan Dacey (grokit) > SENT: Tuesday, October 11, 2016 10:30 > TO: Kubuntu user technical support > SUBJECT: Re: Failure of reboot after update > > Going by where the boot process stopped the problem may be your hard > drive and not software. Could be your hardware too but let's rule out > your hard drive first. > > Open a terminal any paste the output of the following in your > response: > > sudo smartctl --all /dev/sda > > If it complains about an ATA device behind a SAT layer then use the > following: > > sudo smartctl -d sat --all /dev/sda > > That will give an estimate of your disk's health. You then should run > a long test, this will take a while, like 45 minutes to an hour and a > half depending on the size of your disk. Smartctl will tell you how > long it will take so after that time run the command above again and > look for any changes. > > Use the following command to run a long test: > > sudo smartctl --test=long /dev/sda > > It is possible but unlikely that you'll need to enable smart logging > on your disk. You'll know if you get no real output. > > Use this command to start logging: > > smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda > > If the command 'smartctl' is not found you'll need to install the > package first. > > sudo apt-get install smartmontools > > You can install a graphical front end with the package gsmartcontrol > but if smartctl complained about the layer stuff then you need to go > to Options-->Preferences and add "-d sat" (without quotes) in the > "Smartctl parameters" box and rescan. > > On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: > >> I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series > computer. > >> > >> The last two updates, when prompted to reboot, I clicked on the > prompt and the reboot failed. The computer froze on the initial > Toshiba banner page which is supposed to allow access via F2 to Setup > Utility or by F12 to Boot Manager. The first time this happened, I > tried to boot from a thumb drive. The computer gave a > message, but when I attempted a normal boot, it worked, and continued > to work, through several reboots, for several days. However, the next > time I updated, and clicked the reboot prompt, the reboot again > failed, and the previous work-around did not work. The computer will > not get beyond the Toshiba introductory banner described previously. > Any recommendations? I am not very familiar with Kubuntu, and am only > semi-literate on computers in general, so please put it in “baby > talk”! > > ------------------------- > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users -- kubuntu-users mailing list kubuntu-users at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users From list at xenhideout.nl Tue Oct 11 18:34:00 2016 From: list at xenhideout.nl (Xen) Date: Tue, 11 Oct 2016 20:34:00 +0200 Subject: Failure of reboot after update In-Reply-To: <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> Message-ID: Jim Croft schreef op 11-10-2016 20:26: > The thumb drive was not a bootable drive. It had a Kubuntu 16.04 > download, but an installation download, not a bootable one, so the > fact that it would not boot from there may not mean anything (am I > right?) Right. Indeed. > Anyway, I will not bother you any more until I get someone who is > tech-savvy to check out the computer. It is older than you wrote, I > copied the wrong ID for the machine. It is a Satellite A305-S6872, > model PSAG8U-02E018, and is several years old. Well perhaps it is a Kubuntu problem then, but you said that it freezes at the boot prompt (before anything happens) but are you really meaning to say that the F12 prompt still works? Regards. From bmarsh at bmarsh.com Tue Oct 11 22:49:38 2016 From: bmarsh at bmarsh.com (bmarsh at bmarsh.com) Date: Tue, 11 Oct 2016 18:49:38 -0400 Subject: Failure of reboot after update In-Reply-To: <047079369d77855609626d1deb89c7fc@dds.nl> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> Message-ID: <3BBEDB2F-FC5B-4A1C-A056-871D51EC75E4@bmarsh.com> > On Oct 11, 2016, at 1:19 PM, Xen wrote: > > Jim Croft schreef op 11-10-2016 18:23: >> Thank you for your prompt reply. >> I am not able to follow the instructions because now I cannot get the >> computer to boot at all. I will probably have to take it to a shop, >> and I can’t afford that for a couple of weeks. I do have another >> computer running Windows 10, so am not desperate. The Kubuntu machine >> is a toy until I get it working well, and gain enough experience to >> really use it for practical purposes. > > Jim, normally speaking your hard-drive installation can have no influence over whether some USB stick boots or not. > > Windows normally can have trouble with booting from e.g. DVD when the master boot record of the harddrive is not correct, a very annoying situation. But any Linux boot-stick that will boot without regard of an existing system should boot flawlessly no matter what some Kubuntu update may have done. > > It is almost impossible that Kubuntu could cause your system to hang at the Toshiba screen because normally whatever goes wrong you should *always* get a grub prompt. Not necessarily so. When I put the latest ISO to a USB stick, I have three choices of the utility used to build that stick: unetbootin, or the "make starter disk" with either gtk or kde? It usually takes me a couple tries to find the right one... and on the failures, I do not get a grub boot but rather a blank screen. > It cannot even normally be your harddisk, that could ever cause your stick to fail booting. Should not be possible. > > So those are the thing that can't be true. So the first thing you would ever need to do at this point is to get your stick to boot (forget about the system in the meantime) or to run some (Kubuntu) live DVD. You must if you can still run Linux and Windows installation DVDs from some external DVD drive, for example. If those things work, then you can go on to the text step. Particularly if you can boot into Linux (Kubuntu) I am sure there are people that could help you troubleshoot from there on. > > Most importantly you will be able to access your internal harddisk. > > What Alan meant was accessing the drive to check on S.M.A.R.T. which is a measure of your drive's health. But if you can't even boot an usb stick (or DVD), that won't be necessary. Regardless you *could* take the hard drive out and hook it onto your Windows 10 computer, but can be difficult because of connectors. Or if you think it's fun you could at least take the hard drive out to see if it will boot without it (some usb stick or DVD). Generally for a laptop there is only one other thing you can check and that Jim Croft schreef op 11-10-2016 18:23: >> Thank you for your prompt reply. >> I am not able to follow the instructions because now I cannot get the >> computer to boot at all. I will probably have to take it to a shop, >> and I can’t afford that for a couple of weeks. I do have another >> computer running Windows 10, so am not desperate. The Kubuntu machine >> is a toy until I get it working well, and gain enough experience to >> really use it for practical purposes. > > Jim, normally speaking your hard-drive installation can have no influence over whether some USB stick boots or not. > > Windows normally can have trouble with booting from e.g. DVD when the master boot record of the harddrive is not correct, a very annoying situation. But any Linux boot-stick that will boot without regard of an existing system should boot flawlessly no matter what some Kubuntu update may have done. > > It is almost impossible that Kubuntu could cause your system to hang at the Toshiba screen because normally whatever goes wrong you should *always* get a grub prompt. > > It cannot even normally be your harddisk, that could ever cause your stick to fail booting. Should not be possible. > > So those are the thing that can't be true. So the first thing you would ever need to do at this point is to get your stick to boot (forget about the system in the meantime) or to run some (Kubuntu) live DVD. You must if you can still run Linux and Windows installation DVDs from some external DVD drive, for example. If those things work, then you can go on to the text step. Particularly if you can boot into Linux (Kubuntu) I am sure there are people that could help you troubleshoot from there on. > > Most importantly you will be able to access your internal harddisk. > > What Alan meant was accessing the drive to check on S.M.A.R.T. which is a measure of your drive's health. But if you can't even boot an usb stick (or DVD), that won't be necessary. Regardless you *could* take the hard drive out and hook it onto your Windows 10 computer, but can be difficult because of connectors. Or if you think it's fun you could at least take the hard drive out to see if it will boot without it (some usb stick or DVD). Generally for a laptop there is only one other thing you can check and that is the RAM (memory). > > Typically what you say indicates that either the RAM has gone bad or your laptop has died. > > Some laptops have very sudden RAM failures, I've been told. Your laptop was released in January, 2014. Perhaps you still have warranty? Having installed Linux on it should not void it (this is a hardware problem). > > Regards. > > > > > > > > > > > >> Thanks, >> Jim Croft >> FROM: Alan Dacey (grokit) >> SENT: Tuesday, October 11, 2016 10:30 >> TO: Kubuntu user technical support >> SUBJECT: Re: Failure of reboot after update >> Going by where the boot process stopped the problem may be your hard >> drive and not software. Could be your hardware too but let's rule out >> your hard drive first. >> Open a terminal any paste the output of the following in your >> response: >> sudo smartctl --all /dev/sda >> If it complains about an ATA device behind a SAT layer then use the >> following: >> sudo smartctl -d sat --all /dev/sda >> That will give an estimate of your disk's health. You then should run >> a long test, this will take a while, like 45 minutes to an hour and a >> half depending on the size of your disk. Smartctl will tell you how >> long it will take so after that time run the command above again and >> look for any changes. >> Use the following command to run a long test: >> sudo smartctl --test=long /dev/sda >> It is possible but unlikely that you'll need to enable smart logging >> on your disk. You'll know if you get no real output. >> Use this command to start logging: >> smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda >> If the command 'smartctl' is not found you'll need to install the >> package first. >> sudo apt-get install smartmontools >> You can install a graphical front end with the package gsmartcontrol >> but if smartctl complained about the layer stuff then you need to go >> to Options-->Preferences and add "-d sat" (without quotes) in the >> "Smartctl parameters" box and rescan. >>> On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: >>> I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series >> computer. >>> The last two updates, when prompted to reboot, I clicked on the >> prompt and the reboot failed. The computer froze on the initial >> Toshiba banner page which is supposed to allow access via F2 to Setup >> Utility or by F12 to Boot Manager. The first time this happened, I >> tried to boot from a thumb drive. The computer gave a >> message, but when I attempted a normal boot, it worked, and continued >> to work, through several reboots, for several days. However, the next >> time I updated, and clicked the reboot prompt, the reboot again >> failed, and the previous work-around did not work. The computer will >> not get beyond the Toshiba introductory banner described previously. >> Any recommendations? I am not very familiar with Kubuntu, and am only >> semi-literate on computers in general, so please put it in “baby >> talk”! >> ------------------------- >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users From bmarsh at bmarsh.com Tue Oct 11 22:52:10 2016 From: bmarsh at bmarsh.com (bmarsh at bmarsh.com) Date: Tue, 11 Oct 2016 18:52:10 -0400 Subject: Failure of reboot after update In-Reply-To: <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> Message-ID: > On Oct 11, 2016, at 2:26 PM, Jim Croft wrote: > > The thumb drive was not a bootable drive. It had a Kubuntu 16.04 download, but an installation download, not a bootable one, so the fact that it would not boot from there may not mean anything (am I right?) > > Anyway, I will not bother you any more until I get someone who is tech-savvy to check out the computer. It is older than you wrote, I copied the wrong ID for the machine. It is a Satellite A305-S6872, model PSAG8U-02E018, and is several years old. If only several years old, that should not be a problem. I would guess my Toshiba laptop is at least 7 years old and works just fine with 16.10 > > Thanks, > > Jim Croft > > -----Original Message----- From: Xen > Sent: Tuesday, October 11, 2016 13:19 > To: kubuntu-users at lists.ubuntu.com > Subject: Re: Failure of reboot after update > > Jim Croft schreef op 11-10-2016 18:23: >> Thank you for your prompt reply. >> I am not able to follow the instructions because now I cannot get the >> computer to boot at all. I will probably have to take it to a shop, >> and I can’t afford that for a couple of weeks. I do have another >> computer running Windows 10, so am not desperate. The Kubuntu machine >> is a toy until I get it working well, and gain enough experience to >> really use it for practical purposes. > > Jim, normally speaking your hard-drive installation can have no > influence over whether some USB stick boots or not. > > Windows normally can have trouble with booting from e.g. DVD when the > master boot record of the harddrive is not correct, a very annoying > situation. But any Linux boot-stick that will boot without regard of an > existing system should boot flawlessly no matter what some Kubuntu > update may have done. > > It is almost impossible that Kubuntu could cause your system to hang at > the Toshiba screen because normally whatever goes wrong you should > *always* get a grub prompt. > > It cannot even normally be your harddisk, that could ever cause your > stick to fail booting. Should not be possible. > > So those are the thing that can't be true. So the first thing you would > ever need to do at this point is to get your stick to boot (forget about > the system in the meantime) or to run some (Kubuntu) live DVD. You must > if you can still run Linux and Windows installation DVDs from some > external DVD drive, for example. If those things work, then you can go > on to the text step. Particularly if you can boot into Linux (Kubuntu) I > am sure there are people that could help youThe thumb drive was not a bootable drive. It had a Kubuntu 16.04 download, but an installation download, not a bootable one, so the fact that it would not boot from there may not mean anything (am I right?) > > Anyway, I will not bother you any more until I get someone who is tech-savvy to check out the computer. It is older than you wrote, I copied the wrong ID for the machine. It is a Satellite A305-S6872, model PSAG8U-02E018, and is several years old. > > Thanks, > > Jim Croft > > -----Original Message----- From: Xen > Sent: Tuesday, October 11, 2016 13:19 > To: kubuntu-users at lists.ubuntu.com > Subject: Re: Failure of reboot after update > > Jim Croft schreef op 11-10-2016 18:23: >> Thank you for your prompt reply. >> I am not able to follow the instructions because now I cannot get the >> computer to boot at all. I will probably have to take it to a shop, >> and I can’t afford that for a couple of weeks. I do have another >> computer running Windows 10, so am not desperate. The Kubuntu machine >> is a toy until I get it working well, and gain enough experience to >> really use it for practical purposes. > > Jim, normally speaking your hard-drive installation can have no > influence over whether some USB stick boots or not. > > Windows normally can have trouble with booting from e.g. DVD when the > master boot record of the harddrive is not correct, a very annoying > situation. But any Linux boot-stick that will boot without regard of an > existing system should boot flawlessly no matter what some Kubuntu > update may have done. > > It is almost impossible that Kubuntu could cause your system to hang at > the Toshiba screen because normally whatever goes wrong you should > *always* get a grub prompt. > > It cannot even normally be your harddisk, that could ever cause your > stick to fail booting. Should not be possible. > > So those are the thing that can't be true. So the first thing you would > ever need to do at this point is to get your stick to boot (forget about > the system in the meantime) or to run some (Kubuntu) live DVD. You must > if you can still run Linux and Windows installation DVDs from some > external DVD drive, for example. If those things work, then you can go > on to the text step. Particularly if you can boot into Linux (Kubuntu) I > am sure there are people that could help you troubleshoot from there on. > > Most importantly you will be able to access your internal harddisk. > > What Alan meant was accessing the drive to check on S.M.A.R.T. which is > a measure of your drive's health. But if you can't even boot an usb > stick (or DVD), that won't be necessary. Regardless you *could* take the > hard drive out and hook it onto your Windows 10 computer, but can be > difficult because of connectors. Or if you think it's fun you could at > least take the hard drive out to see if it will boot without it (some > usb stick or DVD). Generally for a laptop there is only one other thing > you can check and that is the RAM (memory). > > Typically what you say indicates that either the RAM has gone bad or > your laptop has died. > > Some laptops have very sudden RAM failures, I've been told. Your laptop > was released in January, 2014. Perhaps you still have warranty? Having > installed Linux on it should not void it (this is a hardware problem). > > Regards. > > > > > > > > > > > >> >> Thanks, >> >> Jim Croft >> >> FROM: Alan Dacey (grokit) >> SENT: Tuesday, October 11, 2016 10:30 >> TO: Kubuntu user technical support >> SUBJECT: Re: Failure of reboot after update >> >> Going by where the boot process stopped the problem may be your hard >> drive and not software. Could be your hardware too but let's rule out >> your hard drive first. >> >> Open a terminal any paste the output of the following in your >> response: >> >> sudo smartctl --all /dev/sda >> >> If it complains about an ATA device behind a SAT layer then use the >> following: >> >> sudo smartctl -d sat --all /dev/sda >> >> That will give an estimate of your disk's health. You then should run >> a long test, this will take a while, like 45 minutes to an hour and a >> half depending on the size of your disk. Smartctl will tell you how >> long it will take so after that time run the command above again and >> look for any changes. >> >> Use the following command to run a long test: >> >> sudo smartctl --test=long /dev/sda >> >> It is possible but unlikely that you'll need to enable smart logging >> on your disk. You'll know if you get no real output. >> >> Use this command to start logging: >> >> smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda >> >> If the command 'smartctl' is not found you'll need to install the >> package first. >> >> sudo apt-get install smartmontools >> >> You can install a graphical front end with the package gsmartcontrol >> but if smartctl complained about the layer stuff then you need to go >> to Options-->Preferences and add "-d sat" (without quotes) in the >> "Smartctl parameters" box and rescan. >> >>> On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: >>> >>> I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series >> computer. >> >>> >> >>> The last two updates, when prompted to reboot, I clicked on the >> prompt and the reboot failed. The computer froze on the initial >> Toshiba banner page which is supposed to allow access via F2 to Setup >> Utility or by F12 to Boot Manager. The first time this happened, I >> tried to boot from a thumb drive. The computer gave a >> message, but when I attempted a normal boot, it worked, and continued >> to work, through several reboots, for several days. However, the next >> time I updated, and clicked the reboot prompt, the reboot again >> failed, and the previous work-around did not work. The computer will >> not get beyond the Toshiba introductory banner described previously. >> Any recommendations? I am not very familiar with Kubuntu, and am only >> semi-literate on computers in general, so please put it in “baby >> talk”! >> >> ------------------------- >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users From gatorforge07 at gmail.com Tue Oct 11 23:27:14 2016 From: gatorforge07 at gmail.com (Jim Croft) Date: Tue, 11 Oct 2016 19:27:14 -0400 Subject: Failure of reboot after update In-Reply-To: References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> Message-ID: <9F6E4D46097042D5BF7E70CE04C03B3E@JimPC> No, from the opening page no key stroke has any effect, including -----Original Message----- From: Xen Sent: Tuesday, October 11, 2016 14:34 To: kubuntu-users at lists.ubuntu.com Subject: Re: Failure of reboot after update Jim Croft schreef op 11-10-2016 20:26: > The thumb drive was not a bootable drive. It had a Kubuntu 16.04 > download, but an installation download, not a bootable one, so the > fact that it would not boot from there may not mean anything (am I > right?) Right. Indeed. > Anyway, I will not bother you any more until I get someone who is > tech-savvy to check out the computer. It is older than you wrote, I > copied the wrong ID for the machine. It is a Satellite A305-S6872, > model PSAG8U-02E018, and is several years old. Well perhaps it is a Kubuntu problem then, but you said that it freezes at the boot prompt (before anything happens) but are you really meaning to say that the F12 prompt still works? Regards. -- kubuntu-users mailing list kubuntu-users at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users From cody.smith at ubuntu.com Wed Oct 12 00:07:03 2016 From: cody.smith at ubuntu.com (Cody Smith) Date: Tue, 11 Oct 2016 17:07:03 -0700 Subject: Failure of reboot after update In-Reply-To: <9F6E4D46097042D5BF7E70CE04C03B3E@JimPC> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> <9F6E4D46097042D5BF7E70CE04C03B3E@JimPC> Message-ID: pretty sure ctrl-alt-del isn't used in Linux, it's usually a Windows thing. --c_smith On Tue, Oct 11, 2016 at 4:27 PM, Jim Croft wrote: > No, from the opening page no key stroke has any effect, including > > > -----Original Message----- From: Xen > Sent: Tuesday, October 11, 2016 14:34 > To: kubuntu-users at lists.ubuntu.com > Subject: Re: Failure of reboot after update > > Jim Croft schreef op 11-10-2016 20:26: > >> The thumb drive was not a bootable drive. It had a Kubuntu 16.04 >> download, but an installation download, not a bootable one, so the >> fact that it would not boot from there may not mean anything (am I >> right?) >> > > Right. Indeed. > > Anyway, I will not bother you any more until I get someone who is >> tech-savvy to check out the computer. It is older than you wrote, I >> copied the wrong ID for the machine. It is a Satellite A305-S6872, >> model PSAG8U-02E018, and is several years old. >> > > Well perhaps it is a Kubuntu problem then, but you said that it freezes > at the boot prompt (before anything happens) but are you really meaning > to say that the F12 prompt still works? > > Regards. > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/kubuntu-users > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/kubuntu-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From o.sinclair at gmail.com Wed Oct 12 08:15:57 2016 From: o.sinclair at gmail.com (O. Sinclair) Date: Wed, 12 Oct 2016 10:15:57 +0200 Subject: Failure of reboot after update In-Reply-To: <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> Message-ID: <57FDF13D.5020608@gmail.com> there are Windows utilities to create a bootable USB from an ISO if you have it saved on your Win10 laptop. https://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows then you can try boot from the usb and see if, as suggested, the issue is your hardware or if something went whack with Kubuntu good luck, Sinclair On 10/11/16 20:26, Jim Croft wrote: > The thumb drive was not a bootable drive. It had a Kubuntu 16.04 > download, but an installation download, not a bootable one, so the fact > that it would not boot from there may not mean anything (am I right?) > > Anyway, I will not bother you any more until I get someone who is > tech-savvy to check out the computer. It is older than you wrote, I > copied the wrong ID for the machine. It is a Satellite A305-S6872, model > PSAG8U-02E018, and is several years old. > > Thanks, > > Jim Croft > > -----Original Message----- From: Xen > Sent: Tuesday, October 11, 2016 13:19 > To: kubuntu-users at lists.ubuntu.com > Subject: Re: Failure of reboot after update > > Jim Croft schreef op 11-10-2016 18:23: >> Thank you for your prompt reply. >> I am not able to follow the instructions because now I cannot get the >> computer to boot at all. I will probably have to take it to a shop, >> and I can’t afford that for a couple of weeks. I do have another >> computer running Windows 10, so am not desperate. The Kubuntu machine >> is a toy until I get it working well, and gain enough experience to >> really use it for practical purposes. > > Jim, normally speaking your hard-drive installation can have no > influence over whether some USB stick boots or not. > > Windows normally can have trouble with booting from e.g. DVD when the > master boot record of the harddrive is not correct, a very annoying > situation. But any Linux boot-stick that will boot without regard of an > existing system should boot flawlessly no matter what some Kubuntu > update may have done. > > It is almost impossible that Kubuntu could cause your system to hang at > the Toshiba screen because normally whatever goes wrong you should > *always* get a grub prompt. > > It cannot even normally be your harddisk, that could ever cause your > stick to fail booting. Should not be possible. > > So those are the thing that can't be true. So the first thing you would > ever need to do at this point is to get your stick to boot (forget about > the system in the meantime) or to run some (Kubuntu) live DVD. You must > if you can still run Linux and Windows installation DVDs from some > external DVD drive, for example. If those things work, then you can go > on to the text step. Particularly if you can boot into Linux (Kubuntu) I > am sure there are people that could help you troubleshoot from there on. > > Most importantly you will be able to access your internal harddisk. > > What Alan meant was accessing the drive to check on S.M.A.R.T. which is > a measure of your drive's health. But if you can't even boot an usb > stick (or DVD), that won't be necessary. Regardless you *could* take the > hard drive out and hook it onto your Windows 10 computer, but can be > difficult because of connectors. Or if you think it's fun you could at > least take the hard drive out to see if it will boot without it (some > usb stick or DVD). Generally for a laptop there is only one other thing > you can check and that is the RAM (memory). > > Typically what you say indicates that either the RAM has gone bad or > your laptop has died. > > Some laptops have very sudden RAM failures, I've been told. Your laptop > was released in January, 2014. Perhaps you still have warranty? Having > installed Linux on it should not void it (this is a hardware problem). > > Regards. > > > > > > > > > > > >> >> Thanks, >> >> Jim Croft >> >> FROM: Alan Dacey (grokit) >> SENT: Tuesday, October 11, 2016 10:30 >> TO: Kubuntu user technical support >> SUBJECT: Re: Failure of reboot after update >> >> Going by where the boot process stopped the problem may be your hard >> drive and not software. Could be your hardware too but let's rule out >> your hard drive first. >> >> Open a terminal any paste the output of the following in your >> response: >> >> sudo smartctl --all /dev/sda >> >> If it complains about an ATA device behind a SAT layer then use the >> following: >> >> sudo smartctl -d sat --all /dev/sda >> >> That will give an estimate of your disk's health. You then should run >> a long test, this will take a while, like 45 minutes to an hour and a >> half depending on the size of your disk. Smartctl will tell you how >> long it will take so after that time run the command above again and >> look for any changes. >> >> Use the following command to run a long test: >> >> sudo smartctl --test=long /dev/sda >> >> It is possible but unlikely that you'll need to enable smart logging >> on your disk. You'll know if you get no real output. >> >> Use this command to start logging: >> >> smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda >> >> If the command 'smartctl' is not found you'll need to install the >> package first. >> >> sudo apt-get install smartmontools >> >> You can install a graphical front end with the package gsmartcontrol >> but if smartctl complained about the layer stuff then you need to go >> to Options-->Preferences and add "-d sat" (without quotes) in the >> "Smartctl parameters" box and rescan. >> >> On Tuesday, October 11, 2016 6:02:13 AM Jim Croft wrote: >> >>> I am running Kubuntu 16.04 on a Toshiba Satellite E55t-A5320 series >> computer. >> >>> >> >>> The last two updates, when prompted to reboot, I clicked on the >> prompt and the reboot failed. The computer froze on the initial >> Toshiba banner page which is supposed to allow access via F2 to Setup >> Utility or by F12 to Boot Manager. The first time this happened, I >> tried to boot from a thumb drive. The computer gave a >> message, but when I attempted a normal boot, it worked, and continued >> to work, through several reboots, for several days. However, the next >> time I updated, and clicked the reboot prompt, the reboot again >> failed, and the previous work-around did not work. The computer will >> not get beyond the Toshiba introductory banner described previously. >> Any recommendations? I am not very familiar with Kubuntu, and am only >> semi-literate on computers in general, so please put it in “baby >> talk”! >> >> ------------------------- >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > From list at xenhideout.nl Wed Oct 12 08:42:00 2016 From: list at xenhideout.nl (Xen) Date: Wed, 12 Oct 2016 10:42:00 +0200 Subject: Failure of reboot after update In-Reply-To: <3BBEDB2F-FC5B-4A1C-A056-871D51EC75E4@bmarsh.com> References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> <3BBEDB2F-FC5B-4A1C-A056-871D51EC75E4@bmarsh.com> Message-ID: bmarsh at bmarsh.com schreef op 12-10-2016 0:49: >> It is almost impossible that Kubuntu could cause your system to hang >> at the Toshiba screen because normally whatever goes wrong you should >> *always* get a grub prompt. > > Not necessarily so. When I put the latest ISO to a USB stick, I have > three choices of the utility used to build that stick: unetbootin, or > the "make starter disk" with either gtk or kde? > > It usually takes me a couple tries to find the right one... and on > the failures, I do not get a grub boot but rather a blank screen. The ISO does not use Grub to boot itself. Further I was talking about the base system, installed system. It stands to reason that you could prevent your system from booting by inserting some malfunctioning USB stick. But that is only temporary. Your system should boot or at least give a semblance of a Grub prompt simply because there is virtually nothing that would *wipe* the bootsector or the location of the grub image (boot.img and core.img). Since Grub is embedded in the bootsector (boot.img) and normally an installation cannot prevent the BIOS from reading the bootsector of the harddrive there is simply nothing your system can do to prevent your BIOS from reaching that bootsector other than wiping it clean. If there is one thing few tools do by default then it is clearing the bootsector. Grub certainly would not (it would not wipe its part from there and then fail to install a new one). So generally speaking you cannot have a failing system that will not boot but will also not /at least/ load Grub. From list at xenhideout.nl Wed Oct 12 08:44:48 2016 From: list at xenhideout.nl (Xen) Date: Wed, 12 Oct 2016 10:44:48 +0200 Subject: Failure of reboot after update In-Reply-To: References: <2980471.Gy0npmdZf6@kirk> <3297EC7340184357A88D30C20831BA62@JimPC> <047079369d77855609626d1deb89c7fc@dds.nl> <4D43D6C29C8C4D5DB5C78441BB2C71E5@JimPC> <9F6E4D46097042D5BF7E70CE04C03B3E@JimPC> Message-ID: <44927cb323b773c79e1439d1b9417087@dds.nl> Cody Smith schreef op 12-10-2016 2:07: > pretty sure ctrl-alt-del isn't used in Linux, it's usually a Windows > thing. If you press ctrl-alt-F1 to get some TTY prompt (text screen) and then press ctrl-alt-del you will see that it does at least something ;-). (which is instantly rebooting your computer, before you try and then accuse me of lost work :p). Also I think the BIOS may also respond to ctrl-alt-del. From o.sinclair at gmail.com Wed Oct 12 10:15:20 2016 From: o.sinclair at gmail.com (O. Sinclair) Date: Wed, 12 Oct 2016 12:15:20 +0200 Subject: Dolphin 5 and getting new services Message-ID: <57FE0D38.3030101@gmail.com> Dear all, I regularly use some additional services in Dolphin. That they went missing on upgrade I can live with but: When I try to add them using the installer I just get "installation failed". I like to use root-services now and then and also the encfs I found out why preview was not working on a number of, well, previewers. After installation of say mpegthumpnailer you have to run this command, the bug is documented: sudo ln -s /usr/lib/x86_64-linux-gnu/plugins/* /usr/lib/x86_64-linux-gnu/qt5/plugins/ Can be good to know. But on the "adding services to the menu", anyone have an idea? Searching the web has not come up with anything. kind regards, Sinclair From Sascha.Manns at directbox.com Wed Oct 12 17:39:12 2016 From: Sascha.Manns at directbox.com (Sascha Manns) Date: Wed, 12 Oct 2016 19:39:12 +0200 Subject: Plasma 5.8 Message-ID: <3021293.ooQvFHj21e@sascha-desktop> Hello List, this week was the new Plasma 5.8 announced (https://www.kde.org/announcements/ plasma-5.8.0.php). Does anyone know if a PPA is available to install it in 16.04 and/or 16.10? Greetings Sascha -- Sascha Manns Maifeldstraße 10 56727 Mayen Phone: +49-1573-9242730 (mobile) Phone: +49-2651-4014045 (home) Email: Sascha.Manns at directbox.com Web: http://saigkill.github.io Jabber: saigkill at jabber.org GPG: FA19BD01 @ hkp://keyserver.ubuntu.com S/MIME: 084E5A5C @ cacert.org -------------- next part -------------- A non-text attachment was scrubbed... Name: org.kde.kontact.desktop Type: application/x-desktop Size: 5536 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: This is a digitally signed message part. URL: From valorie.zimmerman at gmail.com Fri Oct 14 04:29:18 2016 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Thu, 13 Oct 2016 21:29:18 -0700 Subject: Kubuntu 16.10 is out! Message-ID: Hi folks, I'm sure most of you have heard by now, but just in case: Kubuntu 16.10 has been released, along with all flavors of Ubuntu. The official announcement: http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html We've got an announcement on the website as well: https://kubuntu.org/news/kubuntu-16-10-released/ Our step-by-step about installing and upgrading lacks some screenshots. Please feel free to help out there if you can: https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu If you want to seed the torrents, the easiest way is to start here: http://torrent.ubuntu.com:6969/ Remember as always to report your bugs. The easiest way is in the commandline: `ubuntu-bug packagename` All the best, Valorie -- http://about.me/valoriez From luca at ventoso.org Fri Oct 14 06:46:54 2016 From: luca at ventoso.org (Luca Olivetti) Date: Fri, 14 Oct 2016 08:46:54 +0200 Subject: Kubuntu 16.10 is out! In-Reply-To: References: Message-ID: El 14/10/16 a les 06:29, Valorie Zimmerman ha escrit: > > Our step-by-step about installing and upgrading lacks some > screenshots. Please feel free to help out there if you can: > https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu there's no such thing as muon-updater in 16.04, it appears it's been replaced by plasma-discovery-updater luca at seis:~$ LC_ALL=C dpkg -l muon-updater Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==================================-======================-======================-========================================================================== ii muon-updater 4:5.6.2-1ubuntu1 all Transitional package (muon-updater -> plasma-discover-updater) luca at seis:~$ LC_ALL=C dpkg -L muon-updater /. /usr /usr/share /usr/share/doc /usr/share/doc/muon-updater /usr/share/doc/muon-updater/copyright /usr/share/doc/muon-updater/changelog.Debian.gz After alt+f2 one should type "plasma-" and select the (localized) update manager (I think). Bye -- Luca From dutch.glory at yahoo.com Sat Oct 15 12:32:51 2016 From: dutch.glory at yahoo.com (Verwijs1969) Date: Sat, 15 Oct 2016 05:32:51 -0700 (MST) Subject: Kubuntu 16.10 is out! In-Reply-To: References: Message-ID: <1476534771116-5143106.post@n6.nabble.com> almost there... installation went fine, (10-12 iso image) only boot sector is being written incorrectly keep hanging on my PC BIOS.. also tried with Debian 8(.6) no problems there... i will try to generate log files... thanks -- View this message in context: http://ubuntu.5.x6.nabble.com/Kubuntu-16-10-is-out-tp5143070p5143106.html Sent from the kubuntu-users mailing list archive at Nabble.com. From igor.mironchik at gmail.com Sat Oct 15 06:07:41 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sat, 15 Oct 2016 09:07:41 +0300 Subject: Time in Kubuntu Message-ID: Hello, Today I've installed all updates in my Kubuntu 16.04, and time in system tray shows incorrectly now. Look...Wrong time What can be the problem? Thank you. -- Best Regards, Igor Mironchik. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: time.png Type: image/png Size: 776107 bytes Desc: not available URL: From kassube at gmx.net Sat Oct 15 20:24:09 2016 From: kassube at gmx.net (Nils Kassube) Date: Sat, 15 Oct 2016 22:24:09 +0200 Subject: Time in Kubuntu In-Reply-To: References: Message-ID: <1897897.m2ecvK8Dbu@p5915> Igor Mironchik wrote: > Today I've installed all updates in my Kubuntu 16.04, and time in > system tray shows incorrectly now. I think there was an update to the package tzdate which may have mangled your time zone setting. I would suggest you run the command sudo dpkg-reconfigure tzdata in a terminal (konsole). Nils From valorie.zimmerman at gmail.com Sat Oct 15 21:16:27 2016 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Sat, 15 Oct 2016 14:16:27 -0700 Subject: Kubuntu 16.10 is out! In-Reply-To: References: Message-ID: On Thu, Oct 13, 2016 at 11:46 PM, Luca Olivetti wrote: > El 14/10/16 a les 06:29, Valorie Zimmerman ha escrit: > >> >> Our step-by-step about installing and upgrading lacks some >> screenshots. Please feel free to help out there if you can: >> https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu > > > there's no such thing as muon-updater in 16.04, it appears it's been > replaced by plasma-discovery-updater Fixed, thank you. -v > luca at seis:~$ LC_ALL=C dpkg -l muon-updater > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture > Description > +++-==================================-======================-======================-========================================================================== > ii muon-updater 4:5.6.2-1ubuntu1 all > Transitional package (muon-updater -> plasma-discover-updater) > luca at seis:~$ LC_ALL=C dpkg -L muon-updater > /. > /usr > /usr/share > /usr/share/doc > /usr/share/doc/muon-updater > /usr/share/doc/muon-updater/copyright > /usr/share/doc/muon-updater/changelog.Debian.gz > > > After alt+f2 one should type "plasma-" and select the (localized) update > manager (I think). > > Bye > -- > Luca From igor.mironchik at gmail.com Sun Oct 16 05:48:35 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 08:48:35 +0300 Subject: Time in Kubuntu In-Reply-To: <1897897.m2ecvK8Dbu@p5915> References: <1897897.m2ecvK8Dbu@p5915> Message-ID: Hi, On 15.10.2016 23:24, Nils Kassube wrote: > Igor Mironchik wrote: >> Today I've installed all updates in my Kubuntu 16.04, and time in >> system tray shows incorrectly now. > I think there was an update to the package tzdate which may have mangled > your time zone setting. I would suggest you run the command > > sudo dpkg-reconfigure tzdata > > in a terminal (konsole). It didn't help. All time in console utils is ok but in system tray and on lock screen doesn't... In system tray time is -6 hours, on lock screen is -3 hours. -- Best Regards, Igor Mironchik. From kassube at gmx.net Sun Oct 16 07:25:26 2016 From: kassube at gmx.net (Nils Kassube) Date: Sun, 16 Oct 2016 09:25:26 +0200 Subject: Time in Kubuntu In-Reply-To: References: <1897897.m2ecvK8Dbu@p5915> Message-ID: <46148324.JnTZOsP69P@p5915> Igor Mironchik wrote: > On 15.10.2016 23:24, Nils Kassube wrote: > > sudo dpkg-reconfigure tzdata > > It didn't help. All time in console utils is ok but in system tray and > on lock screen doesn't... > > In system tray time is -6 hours, on lock screen is -3 hours. It seems rather strange to me that the two offsets aren't even the same. Anyway, you could right-click on the clock in the system tray. There are two options where you can confirure the clock and check / set the time zone. But I have no idea where you can configure the lock screen. Nils From igor.mironchik at gmail.com Sun Oct 16 07:49:58 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 10:49:58 +0300 Subject: Time in Kubuntu In-Reply-To: <46148324.JnTZOsP69P@p5915> References: <1897897.m2ecvK8Dbu@p5915> <46148324.JnTZOsP69P@p5915> Message-ID: Hi, On 16.10.2016 10:25, Nils Kassube wrote: > Igor Mironchik wrote: >> On 15.10.2016 23:24, Nils Kassube wrote: >>> sudo dpkg-reconfigure tzdata >> It didn't help. All time in console utils is ok but in system tray and >> on lock screen doesn't... >> >> In system tray time is -6 hours, on lock screen is -3 hours. > It seems rather strange to me that the two offsets aren't even the same. > Anyway, you could right-click on the clock in the system tray. There are > two options where you can confirure the clock and check / set the time > zone. But I have no idea where you can configure the lock screen. I know it. And that more strange is that in those dialog time is correct. Time is correct everywhere instead of system tray and lock screen. And I don't have any idea... -- Best Regards, Igor Mironchik. From kassube at gmx.net Sun Oct 16 08:28:38 2016 From: kassube at gmx.net (Nils Kassube) Date: Sun, 16 Oct 2016 10:28:38 +0200 Subject: Time in Kubuntu In-Reply-To: References: <46148324.JnTZOsP69P@p5915> Message-ID: <2905484.rzYgF858G7@p5915> Igor Mironchik wrote: > And that more strange is that in those dialog time is > correct. Time is correct everywhere instead of system tray and lock > screen. And I don't have any idea... That's too strange for me ... then I don't have any more ideas what to try. Except - you could create a new user and check if the behaviour is the same for that new user. If the time is correct for the new user, there must be a problem with some config files in your $HOME folder, but I couldn't tell you which file it might be and what to look for. Nils From igor.mironchik at gmail.com Sun Oct 16 10:34:59 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 13:34:59 +0300 Subject: Time in Kubuntu In-Reply-To: <2905484.rzYgF858G7@p5915> References: <46148324.JnTZOsP69P@p5915> <2905484.rzYgF858G7@p5915> Message-ID: <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> On 16.10.2016 11:28, Nils Kassube wrote: > Igor Mironchik wrote: >> And that more strange is that in those dialog time is >> correct. Time is correct everywhere instead of system tray and lock >> screen. And I don't have any idea... > That's too strange for me ... then I don't have any more ideas what to > try. > > Except - you could create a new user and check if the behaviour is the > same for that new user. If the time is correct for the new user, there > must be a problem with some config files in your $HOME folder, but I > couldn't tell you which file it might be and what to look for. The same with the new user... -- Best Regards, Igor Mironchik. From tprannoy at aisch.org Sun Oct 16 11:58:55 2016 From: tprannoy at aisch.org (Prannoy Thakore) Date: Sun, 16 Oct 2016 17:28:55 +0530 Subject: Time in Kubuntu In-Reply-To: <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> References: <46148324.JnTZOsP69P@p5915> <2905484.rzYgF858G7@p5915> <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> Message-ID: Try checking the time with the root user on the terminal. -Prannoy Thakore On Sun, Oct 16, 2016 at 4:04 PM, Igor Mironchik wrote: > > > On 16.10.2016 11:28, Nils Kassube wrote: > >> Igor Mironchik wrote: >> >>> And that more strange is that in those dialog time is >>> correct. Time is correct everywhere instead of system tray and lock >>> screen. And I don't have any idea... >>> >> That's too strange for me ... then I don't have any more ideas what to >> try. >> >> Except - you could create a new user and check if the behaviour is the >> same for that new user. If the time is correct for the new user, there >> must be a problem with some config files in your $HOME folder, but I >> couldn't tell you which file it might be and what to look for. >> > > The same with the new user... > > -- > Best Regards, > Igor Mironchik. > > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/kubuntu-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From igor.mironchik at gmail.com Sun Oct 16 12:16:21 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 15:16:21 +0300 Subject: Time in Kubuntu In-Reply-To: References: <46148324.JnTZOsP69P@p5915> <2905484.rzYgF858G7@p5915> <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> Message-ID: Hi, On 16.10.2016 14:58, Prannoy Thakore wrote: > Try checking the time with the root user on the terminal. In terminal time is correct: igor at gmi:~/Documents$ sudo date Вс окт 16 15:15:00 +03 2016 igor at gmi:~/Documents$ sudo hwclock Вс 16 окт 2016 15:15:05 .405618 seconds Which is 15 PM. Whereas in the system tray I see 9 AM... > > -Prannoy Thakore > > > On Sun, Oct 16, 2016 at 4:04 PM, Igor Mironchik > > wrote: > > > > On 16.10.2016 11:28, Nils Kassube wrote: > > Igor Mironchik wrote: > > And that more strange is that in those dialog time is > correct. Time is correct everywhere instead of system tray > and lock > screen. And I don't have any idea... > > That's too strange for me ... then I don't have any more ideas > what to > try. > > Except - you could create a new user and check if the > behaviour is the > same for that new user. If the time is correct for the new > user, there > must be a problem with some config files in your $HOME folder, > but I > couldn't tell you which file it might be and what to look for. > > > The same with the new user... > > -- > Best Regards, > Igor Mironchik. > > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > > > > -- Best Regards, Igor Mironchik. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tprannoy at aisch.org Sun Oct 16 12:20:11 2016 From: tprannoy at aisch.org (Prannoy Thakore) Date: Sun, 16 Oct 2016 17:50:11 +0530 Subject: Time in Kubuntu In-Reply-To: References: <46148324.JnTZOsP69P@p5915> <2905484.rzYgF858G7@p5915> <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> Message-ID: I have not seen anything like that before. Do you have a hardware clock in your system, or is all software? -Prannoy Thakore On Sun, Oct 16, 2016 at 5:49 PM, Prannoy Thakore wrote: > I have not seen anything like that before. Do you have a hardware clock in > your system, or is all software? > > On Sun, Oct 16, 2016 at 5:46 PM, Igor Mironchik > wrote: > >> Hi, >> >> On 16.10.2016 14:58, Prannoy Thakore wrote: >> >> Try checking the time with the root user on the terminal. >> >> >> In terminal time is correct: >> >> igor at gmi:~/Documents$ sudo date >> Вс окт 16 15:15:00 +03 2016 >> igor at gmi:~/Documents$ sudo hwclock >> Вс 16 окт 2016 15:15:05 .405618 seconds >> >> Which is 15 PM. Whereas in the system tray I see 9 AM... >> >> >> -Prannoy Thakore >> >> >> On Sun, Oct 16, 2016 at 4:04 PM, Igor Mironchik > > wrote: >> >>> >>> >>> On 16.10.2016 11:28, Nils Kassube wrote: >>> >>>> Igor Mironchik wrote: >>>> >>>>> And that more strange is that in those dialog time is >>>>> correct. Time is correct everywhere instead of system tray and lock >>>>> screen. And I don't have any idea... >>>>> >>>> That's too strange for me ... then I don't have any more ideas what to >>>> try. >>>> >>>> Except - you could create a new user and check if the behaviour is the >>>> same for that new user. If the time is correct for the new user, there >>>> must be a problem with some config files in your $HOME folder, but I >>>> couldn't tell you which file it might be and what to look for. >>>> >>> >>> The same with the new user... >>> >>> -- >>> Best Regards, >>> Igor Mironchik. >>> >>> >>> -- >>> kubuntu-users mailing list >>> kubuntu-users at lists.ubuntu.com >>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >>> an/listinfo/kubuntu-users >>> >> >> >> >> >> -- >> Best Regards, >> Igor Mironchik. >> >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/kubuntu-users >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From igor.mironchik at gmail.com Sun Oct 16 13:04:57 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 16:04:57 +0300 Subject: Time in Kubuntu In-Reply-To: References: <46148324.JnTZOsP69P@p5915> <2905484.rzYgF858G7@p5915> <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> Message-ID: <927b4b56-08d5-11c8-0efa-84247095a36b@gmail.com> Hi, On 16.10.2016 15:20, Prannoy Thakore wrote: > I have not seen anything like that before. Do you have a hardware > clock in your system, or is all software? I'm not sure, I use regular Asus Eee PC 1215N and I guess that all is software. I'll reboot later and look into the BIOS... > > -Prannoy Thakore > > > On Sun, Oct 16, 2016 at 5:49 PM, Prannoy Thakore > > wrote: > > I have not seen anything like that before. Do you have a hardware > clock in your system, or is all software? > > On Sun, Oct 16, 2016 at 5:46 PM, Igor Mironchik > > wrote: > > Hi, > > > On 16.10.2016 14:58, Prannoy Thakore wrote: >> Try checking the time with the root user on the terminal. > > In terminal time is correct: > > igor at gmi:~/Documents$ sudo date > Вс окт 16 15:15:00 +03 2016 > igor at gmi:~/Documents$ sudo hwclock > Вс 16 окт 2016 15:15:05 .405618 seconds > > Which is 15 PM. Whereas in the system tray I see 9 AM... >> >> -Prannoy Thakore >> >> >> On Sun, Oct 16, 2016 at 4:04 PM, Igor Mironchik >> > >> wrote: >> >> >> >> On 16.10.2016 11:28, Nils Kassube wrote: >> >> Igor Mironchik wrote: >> >> And that more strange is that in those dialog time is >> correct. Time is correct everywhere instead of >> system tray and lock >> screen. And I don't have any idea... >> >> That's too strange for me ... then I don't have any >> more ideas what to >> try. >> >> Except - you could create a new user and check if the >> behaviour is the >> same for that new user. If the time is correct for >> the new user, there >> must be a problem with some config files in your >> $HOME folder, but I >> couldn't tell you which file it might be and what to >> look for. >> >> >> The same with the new user... >> >> -- >> Best Regards, >> Igor Mironchik. >> >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users >> >> >> >> >> > > -- > Best Regards, > Igor Mironchik. > > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > > > > > -- Best Regards, Igor Mironchik. -------------- next part -------------- An HTML attachment was scrubbed... URL: From igor.mironchik at gmail.com Sun Oct 16 13:12:53 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 16:12:53 +0300 Subject: Time in Kubuntu In-Reply-To: References: <46148324.JnTZOsP69P@p5915> <2905484.rzYgF858G7@p5915> <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> Message-ID: <180eb3ff-b481-75a2-9f94-adfff610aecb@gmail.com> What more strange is that when I change time zone to another all "clocks" show the same time, correct time, but when I change time zone to my (Minsk, Belarus) I see this issue - system tray -6 hours, lock screen - 3 hours. On 16.10.2016 15:20, Prannoy Thakore wrote: > I have not seen anything like that before. Do you have a hardware > clock in your system, or is all software? > > -Prannoy Thakore > > > On Sun, Oct 16, 2016 at 5:49 PM, Prannoy Thakore > > wrote: > > I have not seen anything like that before. Do you have a hardware > clock in your system, or is all software? > > On Sun, Oct 16, 2016 at 5:46 PM, Igor Mironchik > > wrote: > > Hi, > > > On 16.10.2016 14:58, Prannoy Thakore wrote: >> Try checking the time with the root user on the terminal. > > In terminal time is correct: > > igor at gmi:~/Documents$ sudo date > Вс окт 16 15:15:00 +03 2016 > igor at gmi:~/Documents$ sudo hwclock > Вс 16 окт 2016 15:15:05 .405618 seconds > > Which is 15 PM. Whereas in the system tray I see 9 AM... >> >> -Prannoy Thakore >> >> >> On Sun, Oct 16, 2016 at 4:04 PM, Igor Mironchik >> > >> wrote: >> >> >> >> On 16.10.2016 11:28, Nils Kassube wrote: >> >> Igor Mironchik wrote: >> >> And that more strange is that in those dialog time is >> correct. Time is correct everywhere instead of >> system tray and lock >> screen. And I don't have any idea... >> >> That's too strange for me ... then I don't have any >> more ideas what to >> try. >> >> Except - you could create a new user and check if the >> behaviour is the >> same for that new user. If the time is correct for >> the new user, there >> must be a problem with some config files in your >> $HOME folder, but I >> couldn't tell you which file it might be and what to >> look for. >> >> >> The same with the new user... >> >> -- >> Best Regards, >> Igor Mironchik. >> >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users >> >> >> >> >> > > -- > Best Regards, > Igor Mironchik. > > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > > > > > -- Best Regards, Igor Mironchik. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tprannoy at aisch.org Sun Oct 16 13:26:32 2016 From: tprannoy at aisch.org (Prannoy Thakore) Date: Sun, 16 Oct 2016 18:56:32 +0530 Subject: Time in Kubuntu In-Reply-To: References: <46148324.JnTZOsP69P@p5915> <2905484.rzYgF858G7@p5915> <51d1a31e-a154-516c-6483-299dd43d3b5f@gmail.com> <180eb3ff-b481-75a2-9f94-adfff610aecb@gmail.com> Message-ID: I know this isn't the best option, but try reinstalling the whole time package that Nils mentioned. (tzdata) Now before you do this, I would advise a backup of everything that you have on there. Just to be on the safe side. -Prannoy Thakore On Sun, Oct 16, 2016 at 6:56 PM, Prannoy Thakore wrote: > I know this isn't the best option, but try reinstalling the whole time > package that Nils mentioned. (tzdata) Now before you do this, I would > advise a backup of everything that you have on there. Just to be on the > safe side. > > On Sun, Oct 16, 2016 at 6:42 PM, Igor Mironchik > wrote: > >> What more strange is that when I change time zone to another all "clocks" >> show the same time, correct time, but when I change time zone to my (Minsk, >> Belarus) I see this issue - system tray -6 hours, lock screen - 3 hours. >> >> On 16.10.2016 15:20, Prannoy Thakore wrote: >> >> I have not seen anything like that before. Do you have a hardware clock >> in your system, or is all software? >> >> -Prannoy Thakore >> >> >> On Sun, Oct 16, 2016 at 5:49 PM, Prannoy Thakore < >> tprannoy21 at aischennai.org> wrote: >> >>> I have not seen anything like that before. Do you have a hardware clock >>> in your system, or is all software? >>> >>> On Sun, Oct 16, 2016 at 5:46 PM, Igor Mironchik < >>> igor.mironchik at gmail.com> wrote: >>> >>>> Hi, >>>> >>>> On 16.10.2016 14:58, Prannoy Thakore wrote: >>>> >>>> Try checking the time with the root user on the terminal. >>>> >>>> >>>> In terminal time is correct: >>>> >>>> igor at gmi:~/Documents$ sudo date >>>> Вс окт 16 15:15:00 +03 2016 >>>> igor at gmi:~/Documents$ sudo hwclock >>>> Вс 16 окт 2016 15:15:05 .405618 seconds >>>> >>>> Which is 15 PM. Whereas in the system tray I see 9 AM... >>>> >>>> >>>> -Prannoy Thakore >>>> >>>> >>>> On Sun, Oct 16, 2016 at 4:04 PM, Igor Mironchik < >>>> igor.mironchik at gmail.com> wrote: >>>> >>>>> >>>>> >>>>> On 16.10.2016 11:28, Nils Kassube wrote: >>>>> >>>>>> Igor Mironchik wrote: >>>>>> >>>>>>> And that more strange is that in those dialog time is >>>>>>> correct. Time is correct everywhere instead of system tray and lock >>>>>>> screen. And I don't have any idea... >>>>>>> >>>>>> That's too strange for me ... then I don't have any more ideas what to >>>>>> try. >>>>>> >>>>>> Except - you could create a new user and check if the behaviour is the >>>>>> same for that new user. If the time is correct for the new user, there >>>>>> must be a problem with some config files in your $HOME folder, but I >>>>>> couldn't tell you which file it might be and what to look for. >>>>>> >>>>> >>>>> The same with the new user... >>>>> >>>>> -- >>>>> Best Regards, >>>>> Igor Mironchik. >>>>> >>>>> >>>>> -- >>>>> kubuntu-users mailing list >>>>> kubuntu-users at lists.ubuntu.com >>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >>>>> an/listinfo/kubuntu-users >>>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> Igor Mironchik. >>>> >>>> >>>> -- >>>> kubuntu-users mailing list >>>> kubuntu-users at lists.ubuntu.com >>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >>>> an/listinfo/kubuntu-users >>>> >>>> >>> >> >> >> >> -- >> Best Regards, >> Igor Mironchik. >> >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/kubuntu-users >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kassube at gmx.net Sun Oct 16 14:03:08 2016 From: kassube at gmx.net (Nils Kassube) Date: Sun, 16 Oct 2016 16:03:08 +0200 Subject: Time in Kubuntu In-Reply-To: <180eb3ff-b481-75a2-9f94-adfff610aecb@gmail.com> References: <180eb3ff-b481-75a2-9f94-adfff610aecb@gmail.com> Message-ID: <10188120.NJklshoFNq@p5915> Igor Mironchik wrote: > What more strange is that when I change time zone to another all > "clocks" show the same time, correct time, but when I change time zone > to my (Minsk, Belarus) I see this issue - system tray -6 hours, lock > screen - 3 hours. What happens if you select another time zone with the same offset from UTC as your real time zone? Could that be a workaround? Nils From igor.mironchik at gmail.com Sun Oct 16 14:53:02 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 17:53:02 +0300 Subject: Time in Kubuntu In-Reply-To: <10188120.NJklshoFNq@p5915> References: <180eb3ff-b481-75a2-9f94-adfff610aecb@gmail.com> <10188120.NJklshoFNq@p5915> Message-ID: <1db48d6c-886f-dcec-8100-7027735e75f1@gmail.com> On 16.10.2016 17:03, Nils Kassube wrote: > Igor Mironchik wrote: >> What more strange is that when I change time zone to another all >> "clocks" show the same time, correct time, but when I change time zone >> to my (Minsk, Belarus) I see this issue - system tray -6 hours, lock >> screen - 3 hours. > What happens if you select another time zone with the same offset from > UTC as your real time zone? Could that be a workaround? If I change time zone to Kiev, for example. Time is correct in the system tray. Kiev and Minsk is in the same time zone, but I'm not sure about daylight time... I will try to reinstall whole Kubuntu... > > > Nils > > -- Best Regards, Igor Mironchik. From kassube at gmx.net Sun Oct 16 15:06:36 2016 From: kassube at gmx.net (Nils Kassube) Date: Sun, 16 Oct 2016 17:06:36 +0200 Subject: Time in Kubuntu In-Reply-To: <1db48d6c-886f-dcec-8100-7027735e75f1@gmail.com> References: <10188120.NJklshoFNq@p5915> <1db48d6c-886f-dcec-8100-7027735e75f1@gmail.com> Message-ID: <12518305.hQBAffmGmk@p5915> Igor Mironchik wrote: > On 16.10.2016 17:03, Nils Kassube wrote: > > Igor Mironchik wrote: > >> What more strange is that when I change time zone to another all > >> "clocks" show the same time, correct time, but when I change time > >> zone to my (Minsk, Belarus) I see this issue - system tray -6 > >> hours, lock screen - 3 hours. > > > > What happens if you select another time zone with the same offset > > from UTC as your real time zone? Could that be a workaround? > > If I change time zone to Kiev, for example. Time is correct in the > system tray. Kiev and Minsk is in the same time zone, but I'm not sure > about daylight time... I will try to reinstall whole Kubuntu... I think you should not waste that much time. It looks more like a bug in the tzdata package. Then you will get that same problem with the newly installed system again. I'd rather use the working time zone of Kiev for now and hope for a bug fix. You could also file a bug report. Nils From kassube at gmx.net Sun Oct 16 15:19:58 2016 From: kassube at gmx.net (Nils Kassube) Date: Sun, 16 Oct 2016 17:19:58 +0200 Subject: Time in Kubuntu In-Reply-To: <1db48d6c-886f-dcec-8100-7027735e75f1@gmail.com> References: <10188120.NJklshoFNq@p5915> <1db48d6c-886f-dcec-8100-7027735e75f1@gmail.com> Message-ID: <2723883.qMNH8t4tL7@p5915> Igor Mironchik wrote: > If I change time zone to Kiev, for example. Time is correct in the > system tray. Kiev and Minsk is in the same time zone, but I'm not sure > about daylight time... I will try to reinstall whole Kubuntu... Additionally to my previous mail, I made some experiments: If I select the Minsk time zone I get the wrong time on the system tray, just like you described - and the Kiev time is correct. But only on the 16.04 system - if I try the same with 16.10, the time is correct for the Minsk time zone as well. Now I'm not so sure any more that the faulty package is tzdata. Instead I suppose it is rather some package related to plasma (but I have no idea which one). Nils From igor.mironchik at gmail.com Sun Oct 16 17:59:17 2016 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Sun, 16 Oct 2016 20:59:17 +0300 Subject: Time in Kubuntu In-Reply-To: <2723883.qMNH8t4tL7@p5915> References: <10188120.NJklshoFNq@p5915> <1db48d6c-886f-dcec-8100-7027735e75f1@gmail.com> <2723883.qMNH8t4tL7@p5915> Message-ID: <73743dd1-fffd-b3a0-0ec7-38f5832b5b8e@gmail.com> Hi, On 16.10.2016 18:19, Nils Kassube wrote: > Igor Mironchik wrote: >> If I change time zone to Kiev, for example. Time is correct in the >> system tray. Kiev and Minsk is in the same time zone, but I'm not sure >> about daylight time... I will try to reinstall whole Kubuntu... > Additionally to my previous mail, I made some experiments: If I select > the Minsk time zone I get the wrong time on the system tray, just like > you described - and the Kiev time is correct. But only on the 16.04 > system - if I try the same with 16.10, the time is correct for the Minsk > time zone as well. Now I'm not so sure any more that the faulty package > is tzdata. Instead I suppose it is rather some package related to plasma > (but I have no idea which one). Yes, I checked on 16.10 and there time is correct. Thank you Nils for your time. Can you tell me what the time separator in 16.10? This is dot or colon? From kassube at gmx.net Sun Oct 16 19:16:36 2016 From: kassube at gmx.net (Nils Kassube) Date: Sun, 16 Oct 2016 21:16:36 +0200 Subject: Time in Kubuntu In-Reply-To: <73743dd1-fffd-b3a0-0ec7-38f5832b5b8e@gmail.com> References: <2723883.qMNH8t4tL7@p5915> <73743dd1-fffd-b3a0-0ec7-38f5832b5b8e@gmail.com> Message-ID: <14203002.bWfF1Jp8QU@p5915> Igor Mironchik wrote: > On 16.10.2016 18:19, Nils Kassube wrote: > > Igor Mironchik wrote: > >> If I change time zone to Kiev, for example. Time is correct in the > >> system tray. Kiev and Minsk is in the same time zone, but I'm not > >> sure about daylight time... I will try to reinstall whole > >> Kubuntu...> > > Additionally to my previous mail, I made some experiments: If I > > select the Minsk time zone I get the wrong time on the system tray, > > just like you described - and the Kiev time is correct. But only on > > the 16.04 system - if I try the same with 16.10, the time is > > correct for the Minsk time zone as well. Now I'm not so sure any > > more that the faulty package is tzdata. Instead I suppose it is > > rather some package related to plasma (but I have no idea which > > one). > > Yes, I checked on 16.10 and there time is correct. Thank you Nils for > your time. You're welcome. > Can you tell me what the time separator in 16.10? This is dot or > colon? Here it is colon if I select Minsk time zone, but maybe it doesn't depend on the time zone but other regional settings. Nils From tgasoft at gmail.com Tue Oct 18 09:11:41 2016 From: tgasoft at gmail.com (Teimuraz Abashidze) Date: Tue, 18 Oct 2016 09:11:41 +0000 Subject: Time in Kubuntu In-Reply-To: References: Message-ID: I've got the same issue. Kubuntu 16.04, time in system tray is 4 hours different from system time. Before it it was always OK. Also as I had set it to show time in 24 hour format, it didn't, just showing e.g. 10:20 (or 10:20 AM if I swithc 24 hours showing off). After number of swith on/swith off and other experiments, now it shows correct time in stsrem tray, even 24 hours format- 22:21. but system time is: Mon Oct 17 06:21:37 +04 2016 My timezone is really +4 Tbilisi/Asia, but local time is actually 22:21. It seems that it shows UTC time as local in console. And also: # hwclock hwclock: Warning: unrecognized third line in adjtime file (Expected: `UTC' or `LOCAL' or nothing.) Mon 17 Oct 2016 10:23:34 AM +04 .901510 seconds Maybe that is the reason? I've checked /etc/adjtime: # cat /etc/adjtime 0.0 0 0.0 0 LOCAL It seems that this is correct, isn't it? So what can be the reason of such strange behavior? On Sat, Oct 15, 2016 at 11:13 PM Igor Mironchik wrote: > Hello, > > Today I've installed all updates in my Kubuntu 16.04, and time in system > tray shows incorrectly now. > > Look... > > What can be the problem? Thank you. > > -- > Best Regards, > Igor Mironchik. > > -- > 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 kassube at gmx.net Tue Oct 18 18:18:46 2016 From: kassube at gmx.net (Nils Kassube) Date: Tue, 18 Oct 2016 20:18:46 +0200 Subject: Time in Kubuntu In-Reply-To: References: Message-ID: <3293318.aCBp4FA9yd@p5915> Teimuraz Abashidze wrote: > I've got the same issue. Kubuntu 16.04, time in system tray is 4 hours > different from system time. Before it it was always OK. > Also as I had set it to show time in 24 hour format, it didn't, just > showing e.g. 10:20 (or 10:20 AM if I swithc 24 hours showing off). So you have found even more errors than Igor. > After number of swith on/swith off and other experiments, now it shows > correct time in stsrem tray, even 24 hours format- 22:21. but system > time is: > > Mon Oct 17 06:21:37 +04 2016 > > My timezone is really +4 Tbilisi/Asia, but local time is actually > 22:21. It seems that it shows UTC time as local in console. You mean with the "date" command? > And also: > > # hwclock > hwclock: Warning: unrecognized third line in adjtime file > (Expected: `UTC' or `LOCAL' or nothing.) > Mon 17 Oct 2016 10:23:34 AM +04 .901510 seconds > > Maybe that is the reason? I've checked /etc/adjtime: > > # cat /etc/adjtime > 0.0 0 0.0 > 0 > LOCAL > > It seems that this is correct, isn't it? So what can be the reason of > such strange behavior? Maybe there is a missing newline or an additional space at the end of the third line. Both would give the error message above. But I can't imagine that it would be the reason for the wrong display because on my system the adjtime file is OK. Still if I set the time zone to Tbilisi or Kiev, the system tray clock is wrong, like you and Igor explained. My conclusion: Either the fault is caused by some bad time zone files which came with the recent update of the tzdata package, or there is a bug in the way the clock widget (or some other component of KDE) reads those files. As a workaround you could revert the update of the tzdata package or you could set a different time zone which has the same offset from UTC as your time zone (until a future update corrects the fault). Nils From tgasoft at gmail.com Tue Oct 18 19:27:33 2016 From: tgasoft at gmail.com (Teimuraz Abashidze) Date: Tue, 18 Oct 2016 19:27:33 +0000 Subject: Time in Kubuntu In-Reply-To: <3293318.aCBp4FA9yd@p5915> References: <3293318.aCBp4FA9yd@p5915> Message-ID: >As a workaround you could revert the update of the tzdata package or you >could set a different time zone which has the same offset from UTC as >your time zone (until a future update corrects the fault). To Nils Kassube: Man, you're genios! ;-) I've changed my timezone to Tehran (it's the same +4) and now it shows correct time everywhere! It's interesting, timezone files for Ukraine and Georgia ONLY where damaged? On Tue, Oct 18, 2016 at 10:26 PM Nils Kassube wrote: > Teimuraz Abashidze wrote: > > I've got the same issue. Kubuntu 16.04, time in system tray is 4 hours > > different from system time. Before it it was always OK. > > Also as I had set it to show time in 24 hour format, it didn't, just > > showing e.g. 10:20 (or 10:20 AM if I swithc 24 hours showing off). > > So you have found even more errors than Igor. > > > After number of swith on/swith off and other experiments, now it shows > > correct time in stsrem tray, even 24 hours format- 22:21. but system > > time is: > > > > Mon Oct 17 06:21:37 +04 2016 > > > > My timezone is really +4 Tbilisi/Asia, but local time is actually > > 22:21. It seems that it shows UTC time as local in console. > > You mean with the "date" command? > > > And also: > > > > # hwclock > > hwclock: Warning: unrecognized third line in adjtime file > > (Expected: `UTC' or `LOCAL' or nothing.) > > Mon 17 Oct 2016 10:23:34 AM +04 .901510 seconds > > > > Maybe that is the reason? I've checked /etc/adjtime: > > > > # cat /etc/adjtime > > 0.0 0 0.0 > > 0 > > LOCAL > > > > It seems that this is correct, isn't it? So what can be the reason of > > such strange behavior? > > Maybe there is a missing newline or an additional space at the end of > the third line. Both would give the error message above. > > But I can't imagine that it would be the reason for the wrong display > because on my system the adjtime file is OK. Still if I set the time > zone to Tbilisi or Kiev, the system tray clock is wrong, like you and > Igor explained. > > My conclusion: Either the fault is caused by some bad time zone files > which came with the recent update of the tzdata package, or there is a > bug in the way the clock widget (or some other component of KDE) reads > those files. > > As a workaround you could revert the update of the tzdata package or you > could set a different time zone which has the same offset from UTC as > your time zone (until a future update corrects the fault). > > > Nils > > > -- > 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 kassube at gmx.net Tue Oct 18 20:18:46 2016 From: kassube at gmx.net (Nils Kassube) Date: Tue, 18 Oct 2016 22:18:46 +0200 Subject: Time in Kubuntu In-Reply-To: References: <3293318.aCBp4FA9yd@p5915> Message-ID: <3438668.adNI2jfsJ1@p5915> Teimuraz Abashidze wrote: > >As a workaround you could revert the update of the tzdata package or > >you could set a different time zone which has the same offset from > >UTC as your time zone (until a future update corrects the fault). > > To Nils Kassube: > > Man, you're genios! ;-) That's not my idea - some time ago I read it on one of the mailing lists I'm subscribed to (but I don't remember who was the genius who had written about it). > I've changed my timezone to Tehran (it's the > same +4) and now it shows correct time everywhere! > > It's interesting, timezone files for Ukraine and Georgia ONLY where > damaged? Sorry, I mixed up Kiev and Minsk. Igor is in the Belarus/Minsk time zone which is displayed wrong, while for the Kiev time zone it is OK. But I don't know if those are the only time zones which are currently broken. Nils From samorris at netspace.net.au Tue Oct 18 22:12:47 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Wed, 19 Oct 2016 09:12:47 +1100 Subject: Kubuntu 16.10 is out! In-Reply-To: References: Message-ID: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> On 14/10/16 15:29, Valorie Zimmerman wrote: > Hi folks, I'm sure most of you have heard by now, but just in case: > Kubuntu 16.10 has been released, along with all flavors of Ubuntu. > > The official announcement: > http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html > > We've got an announcement on the website as well: > https://kubuntu.org/news/kubuntu-16-10-released/ > > Our step-by-step about installing and upgrading lacks some > screenshots. Please feel free to help out there if you can: > https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu > > If you want to seed the torrents, the easiest way is to start here: > http://torrent.ubuntu.com:6969/ > > Remember as always to report your bugs. The easiest way is in the > commandline: `ubuntu-bug packagename` > > All the best, > > Valorie > Hi, I have Kubuntu 16.04 LTS installed (that was installed from scratch on a new system) and tried to upgrade using the instructions in your third link above. The problem I have is that neither Muon nor Plasma-Discovery have the options specified in the screen shots to invoke the configuration settings. The only way I could find on my system to change the update settings back to "normal" was to use the update setting options in Synaptic and to set those to "Any version". Having done this Plasma-Discovery then prompted to do an upgrade, but when I clicked on the upgrade button it did nothing. The only way I could find to actually upgrade was to issue a 'sudo do-release-upgrade' from a shell, which then proceeded to undertake the upgrade (before switching to "Any Version" in Synaptic this command returned the message that there were No Releases Available). Having done the upgrade the system quite happily booted to the Lightdm display manager, but was then not able to start Unity, Plasma or Gnome. Gnome and Unity both produced a garbled graphic display and immediately dropped back to Lightdm. Plasma produced 'Internal System Error' messages and when I clicked on 'Details' it said that it was /user/bin/Kwin_X11 that was failing, and, if I click on 'Ignore all future messages of this type', used ctrl+alt+delete to drop back to Lightdm, and restarted Plasma it produced the same failure message, but this time is was in /usr/bin/compiz. I'm probably not surprised that Compiz had issues as I thought it required an accelerated video driver, and, from the display I was getting it looked like the Nvidia proprietary driver I had installed in 16.04 had been removed by the upgrade and it could not be reinstalled as it appeared that the repositories did not have the necessary component to allow a reinstall. How do I now downgrade to 16.04, or do I need to wipe the root, boot and home partitions and re-install 16.04 from scratch, or can I download a 16.10 ISO that I can burn to DVD and do a fresh/clean install from that? regards, Steve From samorris at netspace.net.au Tue Oct 18 22:44:42 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Wed, 19 Oct 2016 09:44:42 +1100 Subject: Time in Kubuntu In-Reply-To: <3438668.adNI2jfsJ1@p5915> References: <3293318.aCBp4FA9yd@p5915> <3438668.adNI2jfsJ1@p5915> Message-ID: On 19/10/16 07:18, Nils Kassube wrote: > Teimuraz Abashidze wrote: >>> As a workaround you could revert the update of the tzdata package or >>> you could set a different time zone which has the same offset from >>> UTC as your time zone (until a future update corrects the fault). >> To Nils Kassube: >> >> Man, you're genios! ;-) > That's not my idea - some time ago I read it on one of the mailing lists > I'm subscribed to (but I don't remember who was the genius who had > written about it). > >> I've changed my timezone to Tehran (it's the >> same +4) and now it shows correct time everywhere! >> >> It's interesting, timezone files for Ukraine and Georgia ONLY where >> damaged? > Sorry, I mixed up Kiev and Minsk. Igor is in the Belarus/Minsk time zone > which is displayed wrong, while for the Kiev time zone it is OK. But I > don't know if those are the only time zones which are currently broken. > > > Nils In another thread where I was querying why a fresh clean install on empty partitions always wanted to unsuccessfully use SDDM as the display manager irrespective of what the default display manager was (the only way to stop this behavior was to uninstall SDDM), I indicated that I had a similar problem to this but slightly different. I am in Australia and we are 10 hours ahead of GMT and like the other people in this thread I am using local time. For the mentioned thread I needed to show some Systemctl output, and I queried in that thread why the timestamp on the output was actually 10 hours ahead of Local time, so it looked to me like the system thought the hardware clock was set to GMT time so it adjusted it to local time, but from what I remember the system tray time displayed correctly. I had 16.04 LTS. I can't check these again now as I have attempted to upgrade to 16.10 via the method I understood to be the Ubuntu preferred upgrade method (do-release-upgrade, as the method documented in the instructions linked to by the announcement thread didn't work for me) and the upgrade has completely destroyed my system. regards, Steve From valorie.zimmerman at gmail.com Thu Oct 20 22:34:24 2016 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Thu, 20 Oct 2016 15:34:24 -0700 Subject: Kubuntu 16.10 is out! In-Reply-To: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> Message-ID: Removing the -devel list since this is a support question. On Tue, Oct 18, 2016 at 3:12 PM, Stephen Morris wrote: > On 14/10/16 15:29, Valorie Zimmerman wrote: >> >> Hi folks, I'm sure most of you have heard by now, but just in case: >> Kubuntu 16.10 has been released, along with all flavors of Ubuntu. >> >> The official announcement: >> >> http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html >> >> We've got an announcement on the website as well: >> https://kubuntu.org/news/kubuntu-16-10-released/ >> >> Our step-by-step about installing and upgrading lacks some >> screenshots. Please feel free to help out there if you can: >> https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu >> >> If you want to seed the torrents, the easiest way is to start here: >> http://torrent.ubuntu.com:6969/ >> >> Remember as always to report your bugs. The easiest way is in the >> commandline: `ubuntu-bug packagename` >> >> All the best, >> >> Valorie >> > Hi, > I have Kubuntu 16.04 LTS installed (that was installed from scratch on a > new system) and tried to upgrade using the instructions in your third link > above. The problem I have is that neither Muon nor Plasma-Discovery have the > options specified in the screen shots to invoke the configuration settings. > The only way I could find on my system to change the update settings back to > "normal" was to use the update setting options in Synaptic and to set those > to "Any version". Having done this Plasma-Discovery then prompted to do an > upgrade, but when I clicked on the upgrade button it did nothing. The only > way I could find to actually upgrade was to issue a 'sudo > do-release-upgrade' from a shell, which then proceeded to undertake the > upgrade (before switching to "Any Version" in Synaptic this command returned > the message that there were No Releases Available). That should work, yes. > Having done the upgrade the system quite happily booted to the Lightdm > display manager, but was then not able to start Unity, Plasma or Gnome. > Gnome and Unity both produced a garbled graphic display and immediately > dropped back to Lightdm. Plasma produced 'Internal System Error' messages > and when I clicked on 'Details' it said that it was /user/bin/Kwin_X11 that > was failing, and, if I click on 'Ignore all future messages of this type', > used ctrl+alt+delete to drop back to Lightdm, and restarted Plasma it > produced the same failure message, but this time is was in /usr/bin/compiz. > I'm probably not surprised that Compiz had issues as I thought it required > an accelerated video driver, and, from the display I was getting it looked > like the Nvidia proprietary driver I had installed in 16.04 had been removed > by the upgrade and it could not be reinstalled as it appeared that the > repositories did not have the necessary component to allow a reinstall. > How do I now downgrade to 16.04, or do I need to wipe the root, boot and > home partitions and re-install 16.04 from scratch, or can I download a 16.10 > ISO that I can burn to DVD and do a fresh/clean install from that? > > regards, > Steve Hi Steve, First, downgrade isn't supported. We haven't used Lightdm for a long time, perhaps two years? We've used SDDM since then, and that should support booting into both Unity and GNOME desktops, as well as the Plasma session. So my advice is: first try removing lightdm and installing sddm, if it is not installed. From the commandline, you can always check to see what you have installed with the command apt-cache. Like: `apt-cache policy lightdm` or `apt-cache policy sddm`. Notice that sudo is not used with this command, since it only looks up what you have installed. Then I would do `sudo apt remove lightdm && sudo apt install sddm`. If you find that sddm is already installed, instead do: `sudo apt remove lightdm && sudo dpkg-reconfigure sddm` The reason you want to chain those commands together with "&&" is so that they work sequentially, and you aren't left with no manager at all. When you run into problems, the most useful command is `sudo apt install -f`. The -f flag stands for fix, and that's what apt will attempt to do. If you have misconfiguration problems, `sudo dpkg-reconfigure -a` will try to reconfigure all, and then you can again try install -f. It is certainly possible to download the 16.10 ISO and reinstall, but you will lose your unity and gnome sessions. https://kubuntu.org/alternative-downloads/ As for the nvidia driver: others will have to answer. Valorie From luca at ventoso.org Fri Oct 21 07:00:21 2016 From: luca at ventoso.org (Luca Olivetti) Date: Fri, 21 Oct 2016 09:00:21 +0200 Subject: Kubuntu 16.10 is out! In-Reply-To: References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> Message-ID: <2544586b-604d-f887-16a1-83520fc48c6b@ventoso.org> El 21/10/16 a les 00:34, Valorie Zimmerman ha escrit: >> Having done this Plasma-Discovery then prompted to do an >> upgrade, but when I clicked on the upgrade button it did nothing. The only >> way I could find to actually upgrade was to issue a 'sudo >> do-release-upgrade' from a shell, which then proceeded to undertake the >> upgrade (before switching to "Any Version" in Synaptic this command returned >> the message that there were No Releases Available). This mirrors my experience on one machine (an acer aspire one) where I installed 16.04 form scratch, while on my main laptop (upgraded from 15 something) the upgrade button worked. > We haven't used Lightdm for a long time, perhaps two years? We've used > SDDM since then, and that should support booting into both Unity and > GNOME desktops, as well as the Plasma session. IIRC when I upgraded to 16.04 (or was it 15 something? I'm not really sure) I had a similar issue: the system didn't automatically install sddm but left the previous, non-functional, display manager. > As for the nvidia driver: others will have to answer. No problem[*] here with nvidia, but I had manually installed nvidia-367 prior to the upgrade (in fact I had it installed for a long time). I know for a fact that it wouldn't automatically upgrade to that version in 16.04. [*] apart from some visual artifacts with compositing enabled and some missing/incomplete letters on the lock screen, but those problems have always been there. Bye -- Luca From a.mani.cms at gmail.com Fri Oct 21 22:49:12 2016 From: a.mani.cms at gmail.com (A. Mani) Date: Sat, 22 Oct 2016 04:19:12 +0530 Subject: Kubuntu 16.10 is out! In-Reply-To: References: Message-ID: On Fri, Oct 14, 2016 at 9:59 AM, Valorie Zimmerman wrote: > The official announcement: > http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html I found severe issues with display on AMD64 (kaveri) scenario fresh install Initially display was fine except for issues with default compositor. problems happened after installing other desktops. switching display managers does not help Will file a report later Best A. Mani Prof(Miss) A. Mani CU, ASL, AMS, ISRS, CLC, CMS HomePage: http://www.logicamani.in Blog: http://logicamani.blogspot.in/ http://about.me/logicamani sip:girlprofessor at ekiga.net From samorris at netspace.net.au Sat Oct 22 01:13:09 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Sat, 22 Oct 2016 12:13:09 +1100 Subject: Kubuntu 16.10 is out! In-Reply-To: References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> Message-ID: <722de724-f0ea-1cae-946a-a61b9c053eff@netspace.net.au> On 21/10/16 09:34, Valorie Zimmerman wrote: > Removing the -devel list since this is a support question. > > On Tue, Oct 18, 2016 at 3:12 PM, Stephen Morris > wrote: >> On 14/10/16 15:29, Valorie Zimmerman wrote: >>> Hi folks, I'm sure most of you have heard by now, but just in case: >>> Kubuntu 16.10 has been released, along with all flavors of Ubuntu. >>> >>> The official announcement: >>> >>> http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html >>> >>> We've got an announcement on the website as well: >>> https://kubuntu.org/news/kubuntu-16-10-released/ >>> >>> Our step-by-step about installing and upgrading lacks some >>> screenshots. Please feel free to help out there if you can: >>> https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu >>> >>> If you want to seed the torrents, the easiest way is to start here: >>> http://torrent.ubuntu.com:6969/ >>> >>> Remember as always to report your bugs. The easiest way is in the >>> commandline: `ubuntu-bug packagename` >>> >>> All the best, >>> >>> Valorie >>> >> Hi, >> I have Kubuntu 16.04 LTS installed (that was installed from scratch on a >> new system) and tried to upgrade using the instructions in your third link >> above. The problem I have is that neither Muon nor Plasma-Discovery have the >> options specified in the screen shots to invoke the configuration settings. >> The only way I could find on my system to change the update settings back to >> "normal" was to use the update setting options in Synaptic and to set those >> to "Any version". Having done this Plasma-Discovery then prompted to do an >> upgrade, but when I clicked on the upgrade button it did nothing. The only >> way I could find to actually upgrade was to issue a 'sudo >> do-release-upgrade' from a shell, which then proceeded to undertake the >> upgrade (before switching to "Any Version" in Synaptic this command returned >> the message that there were No Releases Available). > That should work, yes. > >> Having done the upgrade the system quite happily booted to the Lightdm >> display manager, but was then not able to start Unity, Plasma or Gnome. >> Gnome and Unity both produced a garbled graphic display and immediately >> dropped back to Lightdm. Plasma produced 'Internal System Error' messages >> and when I clicked on 'Details' it said that it was /user/bin/Kwin_X11 that >> was failing, and, if I click on 'Ignore all future messages of this type', >> used ctrl+alt+delete to drop back to Lightdm, and restarted Plasma it >> produced the same failure message, but this time is was in /usr/bin/compiz. >> I'm probably not surprised that Compiz had issues as I thought it required >> an accelerated video driver, and, from the display I was getting it looked >> like the Nvidia proprietary driver I had installed in 16.04 had been removed >> by the upgrade and it could not be reinstalled as it appeared that the >> repositories did not have the necessary component to allow a reinstall. >> How do I now downgrade to 16.04, or do I need to wipe the root, boot and >> home partitions and re-install 16.04 from scratch, or can I download a 16.10 >> ISO that I can burn to DVD and do a fresh/clean install from that? >> >> regards, >> Steve > Hi Steve, > > First, downgrade isn't supported. > > We haven't used Lightdm for a long time, perhaps two years? We've used > SDDM since then, and that should support booting into both Unity and > GNOME desktops, as well as the Plasma session. > > So my advice is: first try removing lightdm and installing sddm, if it > is not installed. From the commandline, you can always check to see > what you have installed with the command apt-cache. Like: `apt-cache > policy lightdm` or `apt-cache policy sddm`. Notice that sudo is not > used with this command, since it only looks up what you have > installed. > > Then I would do `sudo apt remove lightdm && sudo apt install sddm`. If > you find that sddm is already installed, instead do: `sudo apt remove > lightdm && sudo dpkg-reconfigure sddm` > > The reason you want to chain those commands together with "&&" is so > that they work sequentially, and you aren't left with no manager at > all. > > When you run into problems, the most useful command is `sudo apt > install -f`. The -f flag stands for fix, and that's what apt will > attempt to do. If you have misconfiguration problems, `sudo > dpkg-reconfigure -a` will try to reconfigure all, and then you can > again try install -f. Thanks Valorie, I'll try the fix commands and see what happens. I would prefer not to use SDDM because in Ubuntu and the other distribution I use I have found that it doesn't work properly and I've always used LightDM for years, ever since Ubuntu standardised on that in preference to KDM and GDM. In my view the KDE foundation should never have replaced KDM with SDDM as, in my view, SDDM does not compete, KDM is a significantly better product. If the fixes don't rectify the issue (some of my problems could that there were file conflicts in a number of packages being upgrade in the process, for example, I think one of the issues was with Plasma-Amity which wanted to install Amity along with it but there was a file conflict between the two, so I think Plasma-Amity didn't get installed because Amity was always installed first) I could always erase the partitions and reinstall 16.04 LTS from scratch and attempt the upgrade again after installing synaptic so that I can change the update options, because the version of Plasma-Discovery in 16.04 LTS (and the version of Plasma-Discovery in the other distribution i use) does not provide the dialog boxes shown in your screenshots. The only product I could find that provided the tabbed dialog (with the Update tab) was Synaptic, but its version setting was different. regards, Steve > > It is certainly possible to download the 16.10 ISO and reinstall, but > you will lose your unity and gnome sessions. > https://kubuntu.org/alternative-downloads/ > > As for the nvidia driver: others will have to answer. > > Valorie > From valorie.zimmerman at gmail.com Sat Oct 22 23:39:34 2016 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Sat, 22 Oct 2016 16:39:34 -0700 Subject: Kubuntu 16.10 is out! In-Reply-To: <722de724-f0ea-1cae-946a-a61b9c053eff@netspace.net.au> References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> <722de724-f0ea-1cae-946a-a61b9c053eff@netspace.net.au> Message-ID: Reply inline. On Fri, Oct 21, 2016 at 6:13 PM, Stephen Morris wrote: > On 21/10/16 09:34, Valorie Zimmerman wrote: >> >> Removing the -devel list since this is a support question. >> >> On Tue, Oct 18, 2016 at 3:12 PM, Stephen Morris >> wrote: >>> >>> On 14/10/16 15:29, Valorie Zimmerman wrote: >>>> >>>> Hi folks, I'm sure most of you have heard by now, but just in case: >>>> Kubuntu 16.10 has been released, along with all flavors of Ubuntu. >>>> >>>> The official announcement: >>>> >>>> >>>> http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html >>>> >>>> We've got an announcement on the website as well: >>>> https://kubuntu.org/news/kubuntu-16-10-released/ >>>> >>>> Our step-by-step about installing and upgrading lacks some >>>> screenshots. Please feel free to help out there if you can: >>>> https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu >>>> >>>> If you want to seed the torrents, the easiest way is to start here: >>>> http://torrent.ubuntu.com:6969/ >>>> >>>> Remember as always to report your bugs. The easiest way is in the >>>> commandline: `ubuntu-bug packagename` >>>> >>>> All the best, >>>> >>>> Valorie >>>> >>> Hi, >>> I have Kubuntu 16.04 LTS installed (that was installed from scratch >>> on a >>> new system) and tried to upgrade using the instructions in your third >>> link >>> above. The problem I have is that neither Muon nor Plasma-Discovery have >>> the >>> options specified in the screen shots to invoke the configuration >>> settings. >>> The only way I could find on my system to change the update settings back >>> to >>> "normal" was to use the update setting options in Synaptic and to set >>> those >>> to "Any version". Having done this Plasma-Discovery then prompted to do >>> an >>> upgrade, but when I clicked on the upgrade button it did nothing. The >>> only >>> way I could find to actually upgrade was to issue a 'sudo >>> do-release-upgrade' from a shell, which then proceeded to undertake the >>> upgrade (before switching to "Any Version" in Synaptic this command >>> returned >>> the message that there were No Releases Available). >> >> That should work, yes. >> >>> Having done the upgrade the system quite happily booted to the >>> Lightdm >>> display manager, but was then not able to start Unity, Plasma or Gnome. >>> Gnome and Unity both produced a garbled graphic display and immediately >>> dropped back to Lightdm. Plasma produced 'Internal System Error' messages >>> and when I clicked on 'Details' it said that it was /user/bin/Kwin_X11 >>> that >>> was failing, and, if I click on 'Ignore all future messages of this >>> type', >>> used ctrl+alt+delete to drop back to Lightdm, and restarted Plasma it >>> produced the same failure message, but this time is was in >>> /usr/bin/compiz. >>> I'm probably not surprised that Compiz had issues as I thought it >>> required >>> an accelerated video driver, and, from the display I was getting it >>> looked >>> like the Nvidia proprietary driver I had installed in 16.04 had been >>> removed >>> by the upgrade and it could not be reinstalled as it appeared that the >>> repositories did not have the necessary component to allow a reinstall. >>> How do I now downgrade to 16.04, or do I need to wipe the root, boot >>> and >>> home partitions and re-install 16.04 from scratch, or can I download a >>> 16.10 >>> ISO that I can burn to DVD and do a fresh/clean install from that? >>> >>> regards, >>> Steve >> >> Hi Steve, >> >> First, downgrade isn't supported. >> >> We haven't used Lightdm for a long time, perhaps two years? We've used >> SDDM since then, and that should support booting into both Unity and >> GNOME desktops, as well as the Plasma session. >> >> So my advice is: first try removing lightdm and installing sddm, if it >> is not installed. From the commandline, you can always check to see >> what you have installed with the command apt-cache. Like: `apt-cache >> policy lightdm` or `apt-cache policy sddm`. Notice that sudo is not >> used with this command, since it only looks up what you have >> installed. >> >> Then I would do `sudo apt remove lightdm && sudo apt install sddm`. If >> you find that sddm is already installed, instead do: `sudo apt remove >> lightdm && sudo dpkg-reconfigure sddm` >> >> The reason you want to chain those commands together with "&&" is so >> that they work sequentially, and you aren't left with no manager at >> all. >> >> When you run into problems, the most useful command is `sudo apt >> install -f`. The -f flag stands for fix, and that's what apt will >> attempt to do. If you have misconfiguration problems, `sudo >> dpkg-reconfigure -a` will try to reconfigure all, and then you can >> again try install -f. > > Thanks Valorie, I'll try the fix commands and see what happens. I would > prefer not to use SDDM because in Ubuntu and the other distribution I use I > have found that it doesn't work properly and I've always used LightDM for > years, ever since Ubuntu standardised on that in preference to KDM and GDM. It did work well in the few years we used it, yes. > In my view the KDE foundation should never have replaced KDM with SDDM as, > in my view, SDDM does not compete, KDM is a significantly better product. The KDE e.V. has no say in software choice, or programming decisions. What happened is that KDM stopped being developed. LightDM is owned by Canonical, rather than being entirely Free Software. KDE devels were not willing to sign the required documents to be allowed to work on LightDM, which left SDDM as the only alternative. > If the fixes don't rectify the issue (some of my problems could that there > were file conflicts in a number of packages being upgrade in the process, > for example, I think one of the issues was with Plasma-Amity which wanted to > install Amity along with it but there was a file conflict between the two, > so I think Plasma-Amity didn't get installed because Amity was always > installed first) I could always erase the partitions and reinstall 16.04 LTS > from scratch and attempt the upgrade again after installing synaptic so that > I can change the update options, because the version of Plasma-Discovery in > 16.04 LTS (and the version of Plasma-Discovery in the other distribution i > use) does not provide the dialog boxes shown in your screenshots. The only > product I could find that provided the tabbed dialog (with the Update tab) > was Synaptic, but its version setting was different. I have no clue what Plasma-Amity is, but I'm glad you found a way to do what you want. > regards, > Steve > >> >> It is certainly possible to download the 16.10 ISO and reinstall, but >> you will lose your unity and gnome sessions. >> https://kubuntu.org/alternative-downloads/ >> >> As for the nvidia driver: others will have to answer. >> >> Valorie From samorris at netspace.net.au Sun Oct 23 21:10:39 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Mon, 24 Oct 2016 08:10:39 +1100 Subject: Kubuntu 16.10 is out! In-Reply-To: References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> <722de724-f0ea-1cae-946a-a61b9c053eff@netspace.net.au> Message-ID: <8b74858c-601c-b4f1-5a0b-65d89b3a1139@netspace.net.au> On 23/10/16 10:39, Valorie Zimmerman wrote: > Reply inline. > > On Fri, Oct 21, 2016 at 6:13 PM, Stephen Morris > wrote: >> On 21/10/16 09:34, Valorie Zimmerman wrote: >>> Removing the -devel list since this is a support question. >>> >>> On Tue, Oct 18, 2016 at 3:12 PM, Stephen Morris >>> wrote: >>>> On 14/10/16 15:29, Valorie Zimmerman wrote: >>>>> Hi folks, I'm sure most of you have heard by now, but just in case: >>>>> Kubuntu 16.10 has been released, along with all flavors of Ubuntu. >>>>> >>>>> The official announcement: >>>>> >>>>> >>>>> http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html >>>>> >>>>> We've got an announcement on the website as well: >>>>> https://kubuntu.org/news/kubuntu-16-10-released/ >>>>> >>>>> Our step-by-step about installing and upgrading lacks some >>>>> screenshots. Please feel free to help out there if you can: >>>>> https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu >>>>> >>>>> If you want to seed the torrents, the easiest way is to start here: >>>>> http://torrent.ubuntu.com:6969/ >>>>> >>>>> Remember as always to report your bugs. The easiest way is in the >>>>> commandline: `ubuntu-bug packagename` >>>>> >>>>> All the best, >>>>> >>>>> Valorie >>>>> >>>> Hi, >>>> I have Kubuntu 16.04 LTS installed (that was installed from scratch >>>> on a >>>> new system) and tried to upgrade using the instructions in your third >>>> link >>>> above. The problem I have is that neither Muon nor Plasma-Discovery have >>>> the >>>> options specified in the screen shots to invoke the configuration >>>> settings. >>>> The only way I could find on my system to change the update settings back >>>> to >>>> "normal" was to use the update setting options in Synaptic and to set >>>> those >>>> to "Any version". Having done this Plasma-Discovery then prompted to do >>>> an >>>> upgrade, but when I clicked on the upgrade button it did nothing. The >>>> only >>>> way I could find to actually upgrade was to issue a 'sudo >>>> do-release-upgrade' from a shell, which then proceeded to undertake the >>>> upgrade (before switching to "Any Version" in Synaptic this command >>>> returned >>>> the message that there were No Releases Available). >>> That should work, yes. >>> >>>> Having done the upgrade the system quite happily booted to the >>>> Lightdm >>>> display manager, but was then not able to start Unity, Plasma or Gnome. >>>> Gnome and Unity both produced a garbled graphic display and immediately >>>> dropped back to Lightdm. Plasma produced 'Internal System Error' messages >>>> and when I clicked on 'Details' it said that it was /user/bin/Kwin_X11 >>>> that >>>> was failing, and, if I click on 'Ignore all future messages of this >>>> type', >>>> used ctrl+alt+delete to drop back to Lightdm, and restarted Plasma it >>>> produced the same failure message, but this time is was in >>>> /usr/bin/compiz. >>>> I'm probably not surprised that Compiz had issues as I thought it >>>> required >>>> an accelerated video driver, and, from the display I was getting it >>>> looked >>>> like the Nvidia proprietary driver I had installed in 16.04 had been >>>> removed >>>> by the upgrade and it could not be reinstalled as it appeared that the >>>> repositories did not have the necessary component to allow a reinstall. >>>> How do I now downgrade to 16.04, or do I need to wipe the root, boot >>>> and >>>> home partitions and re-install 16.04 from scratch, or can I download a >>>> 16.10 >>>> ISO that I can burn to DVD and do a fresh/clean install from that? >>>> >>>> regards, >>>> Steve >>> Hi Steve, >>> >>> First, downgrade isn't supported. >>> >>> We haven't used Lightdm for a long time, perhaps two years? We've used >>> SDDM since then, and that should support booting into both Unity and >>> GNOME desktops, as well as the Plasma session. >>> >>> So my advice is: first try removing lightdm and installing sddm, if it >>> is not installed. From the commandline, you can always check to see >>> what you have installed with the command apt-cache. Like: `apt-cache >>> policy lightdm` or `apt-cache policy sddm`. Notice that sudo is not >>> used with this command, since it only looks up what you have >>> installed. >>> >>> Then I would do `sudo apt remove lightdm && sudo apt install sddm`. If >>> you find that sddm is already installed, instead do: `sudo apt remove >>> lightdm && sudo dpkg-reconfigure sddm` >>> >>> The reason you want to chain those commands together with "&&" is so >>> that they work sequentially, and you aren't left with no manager at >>> all. >>> >>> When you run into problems, the most useful command is `sudo apt >>> install -f`. The -f flag stands for fix, and that's what apt will >>> attempt to do. If you have misconfiguration problems, `sudo >>> dpkg-reconfigure -a` will try to reconfigure all, and then you can >>> again try install -f. >> Thanks Valorie, I'll try the fix commands and see what happens. I would >> prefer not to use SDDM because in Ubuntu and the other distribution I use I >> have found that it doesn't work properly and I've always used LightDM for >> years, ever since Ubuntu standardised on that in preference to KDM and GDM. > It did work well in the few years we used it, yes. > >> In my view the KDE foundation should never have replaced KDM with SDDM as, >> in my view, SDDM does not compete, KDM is a significantly better product. > The KDE e.V. has no say in software choice, or programming decisions. > What happened is that KDM stopped being developed. LightDM is owned by > Canonical, rather than being entirely Free Software. KDE devels were > not willing to sign the required documents to be allowed to work on > LightDM, which left SDDM as the only alternative. > >> If the fixes don't rectify the issue (some of my problems could that there >> were file conflicts in a number of packages being upgrade in the process, >> for example, I think one of the issues was with Plasma-Amity which wanted to >> install Amity along with it but there was a file conflict between the two, >> so I think Plasma-Amity didn't get installed because Amity was always >> installed first) I could always erase the partitions and reinstall 16.04 LTS >> from scratch and attempt the upgrade again after installing synaptic so that >> I can change the update options, because the version of Plasma-Discovery in >> 16.04 LTS (and the version of Plasma-Discovery in the other distribution i >> use) does not provide the dialog boxes shown in your screenshots. The only >> product I could find that provided the tabbed dialog (with the Update tab) >> was Synaptic, but its version setting was different. > I have no clue what Plasma-Amity is, but I'm glad you found a way to > do what you want. Thanks Valorie. I had to reinstall Ubuntu 16.04 as 'sudo apt install -f' did nothing, and, 'sudo dpkg-reconfigure' did not support the '-a' parameter and without the parameter did nothing. Having reinstalled 16.04, which only installed Unity, I upgraded to 16.10, which seemed to upgrade fine with Unity still working. I then proceeded to install Gnome using the gnome package which the description said was the full Gnome (doing this was the starting point to get my system back, after getting Gnome installed as set up I will then install Plasma). The subsequent boot of Gnome is showing that I may not have all the necessary packages installed. When I start the Gnome desktop, the Top Bar has an Activities Menu entry instead of the Applications entry I am expecting. Clicking on the Activities Menu entry brings up the same screen as pressing 'Left-super', where from the side bar on the left of the display I can click on an applicatons button to bring up a 'list' of the applications installed, but this 'list' is all applications not a categorized list like the Applications Menu or the Plasma/KDE Launcher does. Am I missing some packages or is this the way Gnome is meant to function in Ubuntu? Once I get the Gnome issues sorted out I'll then install Plasma via the Plasma package as a starting point to getting Plasma back. I'll query the multiple entries for Plasma in the Display Manager Options at a later date if the reinstall puts both back again. regards, Steve > >> regards, >> Steve >> >>> It is certainly possible to download the 16.10 ISO and reinstall, but >>> you will lose your unity and gnome sessions. >>> https://kubuntu.org/alternative-downloads/ >>> >>> As for the nvidia driver: others will have to answer. >>> >>> Valorie From list at xenhideout.nl Sun Oct 23 22:41:51 2016 From: list at xenhideout.nl (Xen) Date: Mon, 24 Oct 2016 00:41:51 +0200 Subject: Kubuntu 16.10 is out! In-Reply-To: <8b74858c-601c-b4f1-5a0b-65d89b3a1139@netspace.net.au> References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> <722de724-f0ea-1cae-946a-a61b9c053eff@netspace.net.au> <8b74858c-601c-b4f1-5a0b-65d89b3a1139@netspace.net.au> Message-ID: <1c9e23c5a67f46d8ce8188bf74544581@dds.nl> Stephen Morris schreef op 23-10-2016 23:10: > Thanks Valorie. I had to reinstall Ubuntu 16.04 as 'sudo apt install > -f' did nothing, and, 'sudo dpkg-reconfigure' did not support the '-a' > parameter and without the parameter did nothing. For what it's worth, I get confused with that too, but it is "dpkg --configure -a" instead of "dpkg-reconfigure -a". From d_corkrey at rogers.com Mon Oct 24 01:44:12 2016 From: d_corkrey at rogers.com (David Corkrey Sr.) Date: Sun, 23 Oct 2016 21:44:12 -0400 Subject: Time Problems in Kubuntu 16.04 and 16.10 Message-ID: I have a dual boot Lenovo Flex 3 with Windows 10 and a flavor of Kubuntu. When I had 16.04 and later 16.10 installed (both from clean installs), the time displayed in the status and elsewhere appeared to be correct. After a reboot into Windows 10, the time displayed in Windows was 4 hours off (later). This did not occur with Kubuntu 14.04 LTS. Changing back to Kubuntu and the correct time was displayed in Kubuntu. But I noticed a flicker on start up that showed the time to be 4 hours earlier, then changing to the correct time. If I manually set the Kubuntu time to be 4 hours earlier, then reboot into Windows, the Windows time displayed was displayed correctly. Changing the time by 4 hours when switching OS should not be necessary. I have reverted to 14.04 LTS as it appears to be a better, more configurable OS (from a normal user way) and the time works correctly. I have all settings on Eastern Time for Canada. Just a suggestion that new releases showed be checked a little more carefully. -- David Corkrey Sr. London, Ontario Canada eh? Sent from my Kubuntu 14.04 LTS Desktop From valorie.zimmerman at gmail.com Mon Oct 24 04:43:38 2016 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Sun, 23 Oct 2016 21:43:38 -0700 Subject: Vision for Kubuntu Message-ID: To me, what has always set Kubuntu apart is the slogan JR set long ago: Friendly computing. I found our software friendly in that it was tested, and worked. And the team was friendly -- not just with one another, but actively welcoming newcomers. And I've seen those newcomers become trusted members of the team over the years. How do we best continue to demonstrate our vision of what Kubuntu is? * How we in the team treat one another. Mutual respect involves honesty and kindness in equal measure, by which I mean (for example) warning others when you will be making changes that affect their work, and looking out for one another. It is delightful to see people fixing bugs, making helpful comments in Trello, checking over our docs for completeness, writing informative blog posts, and offering to do the boring jobs along with the flashier stuff. * Developers paying attention to users in #kubuntu, the forums and the Kubuntu-user mail list is friendly and inspiring. You never know how much a kindly, helpful word will spread. * Reaching out, by attending meetings, cons, festivals and so forth. Not everyone feels comfortable in doing this, but if you can, do it -- it's fun. Round up a friend to help out, and enjoy yourself. Funding is available if needed. Another way of reaching out is writing documentation, blog posts, Dot stories, doing youtube demonstrations, and the great Kubuntu Podcast. Everybody can help. Given all that, how can we best work with one another and get our goals accomplished together? I'd like to hear some other ideas about our vision for Kubuntu. We're having a meeting soon, so put your preferred time on the doodle poll if you want to attend: http://doodle.com/poll/eq59t2bu5g7428ey If you can't or don't want to attend, discussing here is fine. Aaron has started a page for agenda and notes: https://community.kde.org/Kubuntu/Vision All the best, Valorie -- http://about.me/valoriez From ovidiu.b13 at gmail.com Mon Oct 24 05:59:01 2016 From: ovidiu.b13 at gmail.com (Ovidiu-Florin BOGDAN) Date: Mon, 24 Oct 2016 08:59:01 +0300 Subject: [ANN] CVE-2016-7787 In-Reply-To: <57EDEA86.4020000@ubuntu.com> References: <57EDEA86.4020000@ubuntu.com> Message-ID: We don't ship "kdesu" bu default. We only ship "kdesudo", which currently is at Qt: 4.8.7; KDE Development Platform: 4.14.22; KdeSudo: 3.4.2.3 in Yakety. AFAIK "kdesu" != "kdesudo". Ovidiu - Florin BOGDAN GeekAliens.com Kubuntu România 2016-09-30 7:31 GMT+03:00 Simon Quigley : > Hello everyone, > > In case you don't know me, my name is Simon, and I'm a Kubuntu Ninja. > > About 5 hours ago, someone pasted a link to the CVE report for > CVE-2016-7787 on the KDE website[1]. Here is the vulnerability: > > Overview > ======== > > A maliciously crafted command line for kdesu can result in the user > only seeing part of the commands that will actually get executed as > super user. > > Impact > ====== > > Users can unwillingly run commands as root. > > Workaround > ========== > > Users should be careful when running kdesu with a command line they have > not written themselves. > > Solution > ======== > > kde-cli-tools 5.7.5, released as part of KDE Plasma does not allow the > execution of commands with such characters. > > Alternatively, commit 5eda179a099ba68a20dc21dc0da63e85a565a171 in > kde-cli-tools.git > can be applied to previous releases. > > Thanks to Fabian Vogt for reporting this issue. > Thanks to Martin Sandsmark for fixing this issue. > > Since, I've filed a bug[2] and worked with a member of the Ubuntu > Security team to get the bug fixed and the aforementioned commit backported. > > This security vulnerability has been fixed in Xenial (and is in > xenial-security now) and the Backports PPA (only for Xenial as Wily is > not supported any more). We're waiting on kde-cli-tools to migrate from > proposed in Yakkety, and that will happen within the next few days. > > You should update your computer as soon as possible to get this patch. > > Let me know if you have any questions. > > [1] https://www.kde.org/info/security/advisory-20160930-1.txt > [2] https://pad.lv/1629145 > > -- > Simon Quigley > tsimonq2 at ubuntu.com > tsimonq2 on freenode and OFTC > 5C7A BEA2 0F86 3045 9CC8 > C8B5 E27F 2CF8 458C 2FA4 > > -- > kubuntu-devel mailing list > kubuntu-devel at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel From kassube at gmx.net Mon Oct 24 10:20:03 2016 From: kassube at gmx.net (Nils Kassube) Date: Mon, 24 Oct 2016 12:20:03 +0200 Subject: Time Problems in Kubuntu 16.04 and 16.10 In-Reply-To: References: Message-ID: <1583056.ZHuvTeCjMm@p5915> David Corkrey Sr. wrote: > I have a dual boot Lenovo Flex 3 with Windows 10 and a flavor of > Kubuntu. When I had 16.04 and later 16.10 installed (both from clean > installs), the time displayed in the status and elsewhere appeared to > be correct. After a reboot into Windows 10, the time displayed in > Windows was 4 hours off (later). This did not occur with Kubuntu > 14.04 LTS. > I have all settings on Eastern Time for Canada. I think your time zone has a difference of 4 hours to UTC. Windows expects the hardware clock to be set to your local time and i think Kubuntu now defaults to the hardware clock using UTC. You can check the file "/etc/default/rcS" - if there is a line UTC=yes the hardware clock is set to UTC. If you change it to UTC=no Kubuntu will use local time like Windows does and there shouldn't be a difference between the operating systems. Only at the start and end of daylight saving time probably both OSes will change the hardware clock once. Nils From list at xenhideout.nl Mon Oct 24 13:05:02 2016 From: list at xenhideout.nl (Xen) Date: Mon, 24 Oct 2016 15:05:02 +0200 Subject: Vision for Kubuntu In-Reply-To: References: Message-ID: <180741608635cd95c29c7505c5da6885@dds.nl> Valorie Zimmerman schreef op 24-10-2016 6:43: > All the best, > > Valorie I think you know my opinion. One thing that should be an indication is that there are hardly any users participating in this mailing list. I don't mean to sound rough and I think your goals are wonderful. Yet sometimes what people do and what people say are different things. If you are going to oust dissidents in whatever way while at the same time claiming you want more users to come in, you are doing contradictory things. If you become hostile to contributors or people that mean well, because they use the wrong words or are critical of what you do, don't use the correct path to entry or whatever there is wrong with them, And I have seen this on the Gnome mailing list in the past as well. And you can put me on moderation again for writing this message of course as I am still on moderation on devel-. On the ubuntu-gnome mailing list I had tried to provide some feedback that was met with hostility, as it usually is. I was never banned there but just left. The next message someone writes is "How can we better promote <...> in order to draw in more users?" First you kick someone out or become hostile to someone's contribution, and then you wonder how you can draw in more people. How ironic. The way you treat people is the best publicity you can have, or the worst, depending on what you do. You must first practice what you preach, and you are not doing that. This is not exclusive to Kubuntu and in fact it is rampant across the Linux ecosphere although there are some more established places that are more tolerant. Saying this is reason enough to be put on moderation. Ubuntu practices a policy of don't let anyone know that there are people who don't like us. Hide the dissent. Project an image of overall happiness by hiding any contrary voices. Organisations are typically not democratic structures. Decisions are final. Dissent is squashed. This is true across the globe, from Google to Quora to here. Private organisations have taken over public discourse and if Google decides to ban your account based on nothing at all, you are left without a voice. There is no way to appeal. There is no one independently looking at it. The corporation that runs the platform has the final say, and the only say, and often their image is more important than your freedom. And no matter how .... corrosive.... this message might be (I hope you know what I mean) I just mean to say: you must practice what you preach. If your image of being nice and friendly is more important than being nice and friendly, you will be not-nice and not-friendly in order to protect that image of being nice and friendly, and that is the irony. I have had moderators on IRC tell me they are God. I say you are not god, they say you are wrong about that. If dictatorship is the vision you want to spread, you are doing a good job. I don't disagree with your goals but I notice you are clinging to the past. You can't spread an image by enforcing it in lieu of something real, or quenching disagreeing voices about it. A lot of Linux is invested in not ever letting the truth about Linux come out, because they want to sell it to people. And those Linux people want to sell it using promotion. They are not content with letting the product sell it self, they will say so. So they engage in partial reporting. Politicians do so also. They will say what is good, but not what is bad. They will say the pretty, but not the ugly. And they communicate a half-truth, or a quarter-truth, as Putin once called it, very recently I believe, in fact not more than 3 days ago. If you study the elections currently you will see that both parties, but particularly the media, do nothing other than that, and mostly also consistently from the Hillary-supporting side, since the Trump side has not much to misrepresent. And if you ask people why they are doing that they say they do it because they love their country. They consciously lie and smear other people because they love their country. And so people lie about Linux and smear other people or other systems because they love Linux... It's their duty to promote Linux in that way, they feel.... I have seen people promote or reveal the superiority of the Vi editor by saying that it is a better editor because its copy-paste operations are more logical to the mind because "p" means "put" and "y" means yank. Which obviously only holds true in the English language. People will come up with *anything* to claim that theirs is the better product but this is not an honest way of doing business and leads you to try to control the communications of other people that try to say a different thing. Now it becomes a matter of who controls the communication channels and this is what I see happening a lot. And if you think you can create a bright new future by controlling the communication channels such that competing voices are not heard, and that this is an acceptable sacrifice for the greater good, I think you are deeply mistaken. I mean that if your goal is "openness and fairness" but you feel that being "closed and unfair" is a proper sacrifice for achieving that goal, I think you are mistaken. You cannot achieve open and fair by being controlling and dictatorial. You cannot achieve a better tomorrow by doing more of the same. And I think a lot of people believe that they can. You see in the presidential elections of the United States of America currently that all principles are going out the window in order to _save_ the principles that they are throwing away in order to save them. And it doesn't work. It is a moral bankrupt. From stein-schoellkrippen at t-online.de Mon Oct 24 17:10:06 2016 From: stein-schoellkrippen at t-online.de (Arno Stein) Date: Mon, 24 Oct 2016 19:10:06 +0200 Subject: Vision for Kubuntu In-Reply-To: <180741608635cd95c29c7505c5da6885@dds.nl> References: <180741608635cd95c29c7505c5da6885@dds.nl> Message-ID: <3262760.ahAjEo3OYm@arnodesktop> Am Montag, 24. Oktober 2016, 15:05:02 CEST schrieb Xen: > Valorie Zimmerman schreef op 24-10-2016 6:43: > > All the best, > > > > Valorie > > I think you know my opinion. > > One thing that should be an indication is that there are hardly any > users participating in this mailing list. > > I don't mean to sound rough and I think your goals are wonderful. Yet > sometimes what people do and what people say are different things. > . , , > > And it doesn't work. It is a moral bankrupt. Hi, I'm new here. And I think Xen discribes real problems and Valorie's vision is worth to think about. Arno. From tommy.trussell at gmail.com Mon Oct 24 17:10:37 2016 From: tommy.trussell at gmail.com (Tommy Trussell) Date: Mon, 24 Oct 2016 12:10:37 -0500 Subject: Low-End Laptop Likes L... ... Kubuntu ?!?! Message-ID: TL;DR For various reasons I've kept Ubuntu blinders on and I haven't run KDE much in several years. I was surprised at how well Kubuntu 16.10 "Yakkety-Yak" runs on a low-end laptop I own. Is Kubuntu considered a great choice for low-end laptops nowadays? What bugaboos should I be watching for in KDE on a low-spec laptop? BACKGROUND INFORMATION: I have an Acer Aspire One D260 netbook purchased at Wal-Mart a few years back. (I saw a recent posting on the Kubuntu list regarding a similar laptop, so I know there's at least one other out there.) We originally bought this one because it's very small and spouse and I thought it would be good for travel. Sadly its 2-core Atom N260 1.66Ghz processor and its maxxed-out 2Gb RAM are huge limitations. (That and its disappointingly low-spec battery, and smaller-than-most screen, but we'll ignore those for now.) I've never used Windows on it, though I left it installed for warranty reasons. I haven't run anything on it but Ubuntu flavors in years. Because I wasn't the primary user of the netbook, I merely kept it updated on versions of "straight" Ubuntu, following the upgrades through the development of Unity etc. I also have been installing the Mate and LXDE environments as alternatives for testing, and I sometimes switch among those. In years past my experience was that LXDE has sometimes been more usable for low-end systems. I also assumed MATE might presumably look like the older Ubuntu releases spouse has been used to. Unfortunately (in my opinion) Lubuntu has some quirks that make it a bit harder to support, and neither it nor MATE have seemed as "polished" OR as RAM efficient as I hoped for. SO I am again looking at KDE...! WHAT I DID TODAY I keep LTS releases on most of my systems, but I try them all on the netbook. I saw the Yakkety releases had come out, so I downloaded ISOs of Ubuntu, Lubuntu, and Kubuntu. (I haven't yet downloaded any other Ubuntu "spins," nor have I tried Mint lately.) This morning, I tried all three (booting from a USB stick). The clear winner (based on my limited testing) was Kubuntu! Wow! I was surprised... This is based on a short (15 minute) test of each environment... My test procedure: 1) burn iso to USB stick (using my primary Ubuntu LTS system) 2) boot netbook from stick 3) click "Try _buntu" button (doesn't exist in Lubuntu) 4) connect to network 5) open system monitor 6) open Firefox 7) connect to a couple of resource-intensive web sites 8) watch processor and RAM figures as I connect (yes the CPU stays maxxed out) 9) open a LibreOffice writer document and type a few words 10) watch RAM figures as I close everything (to see how much RAM gets released) ... 11) pick another ISO and start over at step 1 WHAT DID I MISS? It occurs to me that maybe I am missing something -- For instance, I am watching the RAM figures in the system monitor because that seems to be the big bugaboo on this system -- in "straight" Ubuntu, by the time you open LibreOffice and a few web sites, the RAM usage is higher, and once it gets maxxed-out, presumably things start going to swap. Ubuntu does noticeably poorly with low RAM -- presumably Unity uses a lot of RAM compared to other environments. HOWEVER it occurs to me that maybe the KDE System monitor MIGHT be measuring RAM differently from the other system monitors. For instance, does the RAM total include system RAM? I presume it does, because it doesn't drop to zero, but it surprised me that it starts out noticeably lower, its maximum is lower, and it releases pretty much everything when I close documents. Also it's likely Ubuntu starts up more stuff as you login, and maybe KDE will start some things later. Do I need to turn something off as I use it more? I just found a Reddit thread saying KDE works great on low-spec systems as long as you avoid akonadi. Maybe that's outdated info, but I'll watch for it. In the past we have seen a few weird random crashes on the netbook when spouse is working hard on something, which may be due to hardware issues when everything has been churning away for minutes at a time. SO ultimately it may be time to retire the old laptop... but I hate to give up too soon. NEXT STEP I haven't installed it yet.... I'll be doing a "clean" install (overwriting the OS but preserving/restoring the user accounts, which takes awhile). I have never done this with Kubuntu but I presume the procedure is the same as regular Ubuntu. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmarsh at bmarsh.com Mon Oct 24 19:06:59 2016 From: bmarsh at bmarsh.com (bmarsh at bmarsh.com) Date: Mon, 24 Oct 2016 15:06:59 -0400 Subject: Low-End Laptop Likes L... ... Kubuntu ?!?! In-Reply-To: References: Message-ID: <8FBD855D-C164-4641-9431-0F22972D3567@bmarsh.com> > On Oct 24, 2016, at 1:10 PM, Tommy Trussell wrote: > > TL;DR > > For various reasons I've kept Ubuntu blinders on and I haven't run KDE much in several years. I was surprised at how well Kubuntu 16.10 "Yakkety-Yak" runs on a low-end laptop I own. > > Is Kubuntu considered a great choice for low-end laptops nowadays? If Kubuntu ever appears to run out of steam on your laptop, give XFCE a try. Works well for me - - I don't need all the glitz of KDE... > > What bugaboos should I be watching for in KDE on a low-spec laptop? > > BACKGROUND INFORMATION: > > I have an Acer Aspire One D260 netbook purchased at Wal-Mart a few years back. (I saw a recent posting on the Kubuntu list regarding a similar laptop, so I know there's at least one other out there.) We originally bought this one because it's very small and spouse and I thought it would be good for travel. Sadly its 2-core Atom N260 1.66Ghz processor and its maxxed-out 2Gb RAM are huge limitations. (That and its disappointingly low-spec battery, and smaller-than-most screen, but we'll ignore those for now.) I've never used Windows on it, though I left it installed for warranty reasons. I haven't run anything on it but Ubuntu flavors in years. > > Because I wasn't the primary user of the netbook, I merely kept it updated on versions of "straight" Ubuntu, following the upgrades through the development of Unity etc. I also have been installing the Mate and LXDE environments as alternatives for testing, and I sometimes switch among those. > > In years past my experience was that LXDE has sometimes been more usable for low-end systems. I also assumed MATE might presumably look like the older Ubuntu releases spouse has been used to. Unfortunately (in my opinion) Lubuntu has some quirks that make it a bit harder to support, and neither it nor MATE have seemed as "polished" OR as RAM efficient as I hoped for. > > SO I am again looking at KDE...! > > WHAT I DID TODAY > > I keep LTS releases on most of my systems, but I try them all on the netbook. I saw the Yakkety releases had come out, so I downloaded ISOs of Ubuntu, Lubuntu, and Kubuntu. (I haven't yet downloaded any other Ubuntu "spins," nor have I tried Mint lately.) > > This morning, I tried all three (booting from a USB stick). The clear winner (based on my limited testing) was Kubuntu! Wow! I was surprised... > > This is based on a short (15 minute) test of each environment... > > My test procedure: > 1) burn iso to USB stick (using my primary Ubuntu LTS system) > 2) boot netbook from stick > 3) click "Try _buntu" button (doesn't exist in Lubuntu) > 4) connect to network > 5) open system monitor > 6) open Firefox > 7) connect to a couple of resource-intensive web sites > 8) watch processor and RAM figures as I connect (yes the CPU stays maxxed out) > 9) open a LibreOffice writer document and type a few words > 10) watch RAM figures as I close everything (to see how much RAM gets released) > ... > 11) pick another ISO and start over at step 1 > > WHAT DID I MISS? > > It occurs to me that maybe I am missing something -- > > For instance, I am watching the RAM figures in the system monitor because that seems to be the big bugaboo on this system -- in "straight" Ubuntu, by the time you open LibreOffice and a few web sites, the RAM usage is higher, and once it gets maxxed-out, presumably things start going to swap. Ubuntu does noticeably poorly with low RAM -- presumably Unity uses a lot of RAM compared to other environments. > > HOWEVER it occurs to me that maybe the KDE System monitor MIGHT be measuring RAM differently from the other system monitors. For instance, does the RAM total include system RAM? I presume it does, because it doesn't drop to zero, but it surprised me that it starts out noticeably lower, its maximum is lower, and it releases pretty much everything when I close documents. > > Also it's likely Ubuntu starts up more stuff as you login, and maybe KDE will start some things later. Do I need to turn something off as I use it more? > > I just found a Reddit thread saying KDE works great on low-spec systems as long as you avoid akonadi. Maybe that's outdated info, but I'll watch for it. > > In the past we have seen a few weird random crashes on the netbook when spouse is working hard on something, which may be due to hardware issues when everything has been churning away for minutes at a time. SO ultimately it may be time to retire the old laptop... but I hate to give up too soon. > > NEXT STEP > > I haven't installed it yet.... I'll be doing a "clean" install (overwriting the OS but preserving/restoring the user accounts, which takes awhile). I have never done this with Kubuntu but I presume the procedure is the same as regular Ubuntu. > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users From valorie.zimmerman at gmail.com Mon Oct 24 19:30:31 2016 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Mon, 24 Oct 2016 12:30:31 -0700 Subject: Vision for Kubuntu In-Reply-To: <3262760.ahAjEo3OYm@arnodesktop> References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> Message-ID: On Mon, Oct 24, 2016 at 10:10 AM, Arno Stein wrote: > Am Montag, 24. Oktober 2016, 15:05:02 CEST schrieb Xen: >> Valorie Zimmerman schreef op 24-10-2016 6:43: >> > All the best, >> > >> > Valorie >> >> I think you know my opinion. >> >> One thing that should be an indication is that there are hardly any >> users participating in this mailing list. >> >> I don't mean to sound rough and I think your goals are wonderful. Yet >> sometimes what people do and what people say are different things. .... >> And it doesn't work. It is a moral bankrupt. > > Hi, > I'm new here. > And I think Xen discribes real problems > and Valorie's vision is worth to think about. > Arno. Hi Arno. Xen's rant is echoed by many linux users, but not by those who actually do the work. Linux all over the place is a do-ocracy, where those who do the work design the systems, and guide the direction. I'm not asking for words; there are plenty of words. I'm asking for people to show up, and not only express their opinion, but also promise to do some important jobs, and *then do those jobs*. That is the nature of a healthy team. Help us get stuff done. Valorie From samorris at netspace.net.au Mon Oct 24 20:11:45 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Tue, 25 Oct 2016 07:11:45 +1100 Subject: Kubuntu 16.10 is out! In-Reply-To: <1c9e23c5a67f46d8ce8188bf74544581@dds.nl> References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> <722de724-f0ea-1cae-946a-a61b9c053eff@netspace.net.au> <8b74858c-601c-b4f1-5a0b-65d89b3a1139@netspace.net.au> <1c9e23c5a67f46d8ce8188bf74544581@dds.nl> Message-ID: On 24/10/16 09:41, Xen wrote: > Stephen Morris schreef op 23-10-2016 23:10: > >> Thanks Valorie. I had to reinstall Ubuntu 16.04 as 'sudo apt install >> -f' did nothing, and, 'sudo dpkg-reconfigure' did not support the '-a' >> parameter and without the parameter did nothing. > > For what it's worth, I get confused with that too, but it is "dpkg > --configure -a" instead of "dpkg-reconfigure -a". Thanks Xen, I had no idea what the command was, I was following instructions. regards, Steve From accessys at smart.net Mon Oct 24 20:49:59 2016 From: accessys at smart.net (accessys at smart.net) Date: Mon, 24 Oct 2016 16:49:59 -0400 (EDT) Subject: Vision for Kubuntu In-Reply-To: References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> Message-ID: hmmm I'm getting a "file is locked by pid 25555 thanks Bob On Mon, 24 Oct 2016, Valorie Zimmerman wrote: > Date: Mon, 24 Oct 2016 12:30:31 -0700 > From: Valorie Zimmerman > Reply-To: Kubuntu user technical support > To: Kubuntu user technical support > Subject: Re: Vision for Kubuntu > > On Mon, Oct 24, 2016 at 10:10 AM, Arno Stein > wrote: >> Am Montag, 24. Oktober 2016, 15:05:02 CEST schrieb Xen: >>> Valorie Zimmerman schreef op 24-10-2016 6:43: >>>> All the best, >>>> >>>> Valorie >>> >>> I think you know my opinion. >>> >>> One thing that should be an indication is that there are hardly any >>> users participating in this mailing list. >>> >>> I don't mean to sound rough and I think your goals are wonderful. Yet >>> sometimes what people do and what people say are different things. > .... > >>> And it doesn't work. It is a moral bankrupt. >> >> Hi, >> I'm new here. >> And I think Xen discribes real problems >> and Valorie's vision is worth to think about. >> Arno. > > Hi Arno. Xen's rant is echoed by many linux users, but not by those > who actually do the work. Linux all over the place is a do-ocracy, > where those who do the work design the systems, and guide the > direction. I'm not asking for words; there are plenty of words. > > I'm asking for people to show up, and not only express their opinion, > but also promise to do some important jobs, and *then do those jobs*. > That is the nature of a healthy team. > > Help us get stuff done. > > Valorie > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > From list at xenhideout.nl Mon Oct 24 21:41:54 2016 From: list at xenhideout.nl (Xen) Date: Mon, 24 Oct 2016 23:41:54 +0200 Subject: Vision for Kubuntu In-Reply-To: References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> Message-ID: <4aa43ba25037b62a6cd8319e57602660@dds.nl> Valorie Zimmerman schreef op 24-10-2016 21:30: > Hi Arno. Xen's rant is echoed by many linux users, but not by those > who actually do the work. Linux all over the place is a do-ocracy, > where those who do the work design the systems, and guide the > direction. I'm not asking for words; there are plenty of words. You are actually creating a class system where only certain people are even allowed to do the work; namely those with certain opinions and who want to work in the political agenda of the entire system. If you disagree with these viewpoints you are not even given a job, because you cannot work within the system, you are pushed out. So it's not a do-ocracy... it's a political do-ocracy where the only ones who are allowed to do any work are the ones who subscribe to the ideology and nothing else (no one else). Simply because the other ones are pushed out before they have even gotten to the place where they can do any work. You cannot do any work out of the blue; you have to first go through the stages of deployment, so to speak. In a job, that means applying for the job (solliciation). Only after given, can you do any. For Linux, that means expressing what you want to do. If you express the wrong interest, you are turned down. In a sense this is only logical because a corporate employer would do the same. But a corporate employer would not blame the sollicitant who was turned down, for not doing any work. However because Linux has an ideology they often do not recognise that they behave exactly like employers, only less overtly, or perhaps less recognisably. Still the same dynamics play a role and even though you suggest many things you can do or many things you would be interested in, all of them are turned down if they do not comply with the wishes the "employers" have for their system. This is only natural. What is not natural is then blaming the applicant for not trying hard enough or not having any intentions to do anything. You turn down suggestions for what someone wants to do, then it's you to blame for that person not doing any work, and no one else. > I'm asking for people to show up, and not only express their opinion, > but also promise to do some important jobs, and *then do those jobs*. > That is the nature of a healthy team. They show up and you push them out. Because what they want to do doesn't agree with what you want from them. They come up with idea after idea after idea of what they want to do, what they think they can do to improve the system, or to yield something valuable or worthwhile. But you do not recognise the worth of it so you turn it down, even not knowing what was intended, or what the proposed system actually was, because you did not listen to it for more than 5 seconds, usually. You want employees that do exactly what *you* want. But all others fall by the wayside, you can't use them. And, moreover, you try to get them to shut up as well! For fear someone else might get enthused by their ideas!!! No miss Valorie, you behave just like a corporation and you control your communication channels. It is all out in the open, but you can still shut people up, if you want. > Help us get stuff done. That's not your job as an employer. Your job as an employer is to help your employees get stuff done. But you only want "slaves to the wage" like a regular corporate one. This is not how an open source community works, but you don't understand open source. I wish you would stop blaming the people you turn down for not doing any work. If you only have a limited perception of what can be done, that is your fault, not mine. If you only have fixed, well described, perfectly delimited positions to give out, good luck filling those slots. But the general idea of open source is that people do what they want to do, and you do not allow them to. Moreoever, you quench and subject any dissenting or alternative thought, because it would distract from your core mission. You don't even want people talking about it. But your core mission is something so few enthuse about, that most 90% of what people could do for Kubuntu is left out of the equation. And consequently you have a hard time filling those slots. Because you won't allow people to do what *they* want to do, for fear it would distract too much from what *you* need to do. You run it like a boss, I wanted to say before. You run it like a company. Like an employer. You are simply trying to run it like a company and this is your corporate communication channel, it is your corporate user support channel. This is not your "where users talk to each other" channel. That doesn't fit in with a company. Also this is the reason why IRC is also not free to chat either and users are directed to other channels constantly if they want to talk about anything that doesn't comply with the missive. Same for other systems and organisations as well (distributions, you might say). So yeah what can I say. You are hobbying to run a company using free resources, for the most part. Corporation Kubuntu. But people are not welcome unless they are "customers". It's playing house. You are hobbying a company and everything has to agree with that. What can I say. From ofv at wanadoo.es Mon Oct 24 22:50:53 2016 From: ofv at wanadoo.es (=?utf-8?Q?=C3=93scar_Fuentes?=) Date: Tue, 25 Oct 2016 00:50:53 +0200 Subject: Vision for Kubuntu References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> <4aa43ba25037b62a6cd8319e57602660@dds.nl> Message-ID: <87mvhtcqeq.fsf@wanadoo.es> Xen writes: [snip] > But the general idea of open source is that people do what they want > to do, True. But the project administrator has no obligation whatsoever to incorporate your work into the project. You can keep your changes to yourself or publish a forked project. It seems to me that you are upset because Kubuntu's admins are not interested on some of your ideas. But you fail to realize that this is also part of how projects are run. In fact, it is a fundamental duty of the admins to encourage work that advances the project's mission and reject the rest. [snip] From list at xenhideout.nl Mon Oct 24 23:40:55 2016 From: list at xenhideout.nl (Xen) Date: Tue, 25 Oct 2016 01:40:55 +0200 Subject: Vision for Kubuntu In-Reply-To: <4aa43ba25037b62a6cd8319e57602660@dds.nl> References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> <4aa43ba25037b62a6cd8319e57602660@dds.nl> Message-ID: <4975d313d16334355d1aa366353ecf4e@dds.nl> I am not receiving messages currently So I am responding from copy paste currently. Óscar Fuentes wrote on Mon Oct 24 22:50:53 UTC 2016: > [snip] >> But the general idea of open source is that people do what they want >> to do, > True. But the project administrator has no obligation whatsoever to > incorporate your work into the project. You can keep your changes to > yourself or publish a forked project. The point is more that not only work is not accepted (which could be reasonable) but also that discourse is disrespected. They abuse public venues some of which are free resources for a company objective, effectively. On those public venues, which are supposed -- at least that's what you would think -- to be places where people can freely talk, free talk is actually not allowed and all messages are continually monitored to comply with the mission. The project and many projects broadcast an idea of community and it is not about community and there is no community, other than perhaps that a company like Logitech or Synology can have community. It is virtually impossible for Kubuntu to become involved as e.g. a documentator, because there are no freely available places where you can document. Free spots for "little work" are not available, and hence only "bigger positions" are up for offer, that require real commitment and big tasks to perform, effectively. This means that the bar to entry is extremely high -- not that I would be wanting to fill any of those bigger spots, nor could I, but just saying. And what's more important even is that instead of creating community a ripe field for creativity is shut down and spontaneous actions are frowned upon. One is not allowed to use even this "space" (where one can talk, with other people, for instance, as would be the case if this really was community) for their own projects, the space itself is guarded as being part only of the core project here. So where do people go that want to do anything? They can't do anything here, because their communication is disrupted. So they must indeed, completely, create their own project and create their own space in which to do these things. But this is hardly possible if you cannot talk to anyone *also* using the systems that you yourself use. How do you get in touch with e.g. other Kubuntu users if the Kubuntu channels themselves are not allowed for doing that? What if you get kicked out of the forums if you are trying to do these things? So the problem is basically that there are no communication channels one could use. Namely, if you were to really create a fork, it would seem evident that it would be a competition, a competing product. One would never allow a competing product to take root on its own floor. And if the only way to agree with and comply with the main project as it exists today, is by creating a totally new project (or fork), then it is completely black and white; there is in fact then no cooperation. There is then no blending. This is what you propose: no blending. This is what is actually true: you cannot use the channels of this project to start anything new or anything that could grow on top of the current project. There is no room for manouvring here. Therefore it is not a fertile ground where you can work with... other people, or reach other people, because if you pitch your ideas here, you get attacked, or at least deeply criticized of what you do. And simply put: communication precedes activity. Talk precedes doing. Design precedes implementation. So by blocking that first step, the 2nd step also never arises and you are left without recourse, or, as is said in Spanish "sin remedio". And Valorie asked about communication but she uses this only as a project management channel. I thought it was a user channel (this one) but... not really. The very simple fact is that there is no way to get in touch with other Kubuntu users. Equally so the same is true for the main Ubuntu product. If you start to _do your own thing_ on e.g. the Ubuntu Forums, they shut you down. They want to hear nothing of it. They are selling _their product_, they have no need for yours. And so of course it is correct that a project management is allowed to do these things. But that is *not* an open source community. The whole idea of open source is that you *are* allowed to do with it what you want, and this *actively fights that*. This just *completely* breaks the social contract of open source: that you can do with it whatever you like. You are not allowed to do with it whatever you like. Yeah, if you first create your own platform and then become a competitor. And then they will probably shut people up if they talk about your product... Then they will say "This is not a xxx forum". "If you want to talk xxx, go elsewhere". Usually as a person you are not seeking the support of the main project. You are usually just seeking a place to talk. But even if you just as a user you have criticism of the product (as a "customer", to keep falling in line with this company model) you are also dissuaded from speaking, but oh! then they send you to the "appropriate channels", they want you to use their "user support system" that they call "bugzilla" or something. Since this is a public channel, bug reports reflect negatively on the product. So they want you to stop talking here and only talk on the bug report system where no other user will readily hear it; such is also what a normal company would do. So effectively, this public channel disagrees with the notion of running a company. Regular companies do not have public channels, they have dedicated systems for this (for individual users, privately) however recently such public channels have been created, often Facebook. And on those channels they do their _utmost best_ to help people -- because it reflects on their image! People often take to those channels because it is the only place they will be taken for real. Some companies then back away from those channels (e.g. forums) because they don't want to be associated with all the complaining ;-). But in general a mailing list is public but it still can be moderated just like a forum. So you can still kick people out who try to do their own thing. > It seems to me that you are upset because Kubuntu's admins are not > interested on some of your ideas. It is not only a lack of interest, it is being actively fought in the interests you are trying to convey to other people by using this as a channel for your own good (and that of Kubuntu, in your opinion, of course). > But you fail to realize that this is also part of how projects are > run. In fact, it is a fundamental duty of the admins to encourage > work that advances the project's mission and reject the rest. I don't disagree with that. Not "exclusively". That is to say, I do not agree with it entirely, but I do also not disagree with it entirely. The point is that they want to "own" their product like a company does. And we all shy away from companies because they are evil, right? Well, not so, because they are doing exactly the same here (and elsewhere). So we have a company, that's a given. It is not a financial or economical company, but it is still a company, even if it is just Kubuntu here (and the people that obviously run it). A regular company will also not allow you to influence the direction of the product. Also not here, even though that is supposed to be the whole intent (that you can contribute, etc.). Anyway, all of this is nice and philosophical, but it doesn't really help much. The point remains that this is not a community. This is not a collaborative project (except within the company itself). Ubuntu is also not a community. Debian is a community, yes, but Ubuntu isn't. Debian has a constitution. Ubuntu doesn't have a constitution. It has a code of conduct, but that is not the same. You can't influence Kubuntu, you cannot add to Kubuntu, you cannot do anything for Kubuntu. Perhaps you can find a vocation (vacation) if you can do some website work, but again, talk precedes doing, and if they don't like your work, you are done. What else can I say? I can't say anything, and that was the whole intent, probably. Sorry about that. See ya. > [snip] From list at xenhideout.nl Tue Oct 25 00:08:54 2016 From: list at xenhideout.nl (Xen) Date: Tue, 25 Oct 2016 02:08:54 +0200 Subject: Vision for Kubuntu In-Reply-To: <4975d313d16334355d1aa366353ecf4e@dds.nl> References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> <4aa43ba25037b62a6cd8319e57602660@dds.nl> <4975d313d16334355d1aa366353ecf4e@dds.nl> Message-ID: Oh, one thing I wanted to say, that I forgot: Xen schreef op 25-10-2016 1:40: >> But you fail to realize that this is also part of how projects are >> run. In fact, it is a fundamental duty of the admins to encourage >> work that advances the project's mission and reject the rest. > > I don't disagree with that. Not "exclusively". That is to say, I do > not agree with it entirely, but I do also not disagree with it > entirely. > > The point is that they want to "own" their product like a company does. It is understandable that people are not interested in ideas they do not understand or have no interest in. Part of selling a product (or an idea) is pitching a product (or an idea). Pitching means getting someone interested in something they don't yet know. However because these are corporate channels we are in they have a specific purpose: - the dev channel is for development purposes from within the company, not for outsiders - the user channel is for user support, not for anything else, really. At least that is the purpose within the missive. So in fact these are not actually channels you can use to pitch an idea. Where then? It is an "open company" where a number of channels are public discourse. Yet they are still dedicated channels for specific purposes so they jealously guard their channels for fear someone abuses it. You are not supposed to talk "openly" in these channels: it is for a specific purpose and this is not it. How else are you going to reach the project? You can't. There are no other channels you can use for that. Where is the place users can freely talk? It doesn't exist. Even the Ubuntu forums are dedicated for "support". One is actually allowed to say much more on a real corporate forum. So since any idea you would pitch would be something new and would take away (or add to, but at least, differ from) the current offering, it kinda bites when you try to pitch a product in a PUBLIC channel that everyone can see and that is SUPPOSED to be about the MAIN product. In private it wouldn't have mattered much -- idealy, at least. But en publique it is not a wanted thing. I can't help that, but it is not a wanted thing. This is a hobby company, and it is not a wanted thing. It is like pitching a new idea on someone's facebook channel -- some corporation, some large corporation's Facebook. They won't like that, you know. Then why do you do that? I don't do that on a company's Facebook. I cannot influence a company, that is their own thing. A company usually also owns their product, I can't change that. However if I had business proposals I would do it in private. That won't work here, there is no one with that job description. We are "left without recourse" (sin remedio). And this is a reason why it is principally impossible to get anyone interested in a new idea here. That means -- it is also simply because the mind blocks new ideas in these channels -- the ego won't have it. These channels are not meant for new idea, so we won't hear it. Logical. So that means it becomes impossible in the Ubuntu world to give any new idea life. It can't be done. Because the public channels that you will need to use are hostile to it. And the channels that wouldn't be hostile don't exist. It's all logical and perhaps you can't blame anyone but it is all the result of this hobbying while pretending to be an open source community, you know. Debian also does it, by the way, to some extent, pretty much. I only wanted to write this additional mail to explain how difficult it is to even make people understand what it is you are trying to do or to enthuse people for that. You get *no* enthusiasm whatsoever, no matter what you do. Even if you say that something doesn't work and you suggest perhaps an alternative ---> hostility. Always the same. Always hostility. You can't suggest anything. Always hostility. There is no way to make a creative inroad. It is like a forest floor where every falling seed is removed. Ardently. Consistently. Conscientiously, you might say. But also, you could say "Sterilely". To me that means the whole model of Ubuntu is bankrupt, but yeah. Take from it what you will. > > And we all shy away from companies because they are evil, right? Well, > not so, because they are doing exactly the same here (and elsewhere). > So we have a company, that's a given. It is not a financial or > economical company, but it is still a company, even if it is just > Kubuntu here (and the people that obviously run it). > > A regular company will also not allow you to influence the direction > of the product. Also not here, even though that is supposed to be the > whole intent (that you can contribute, etc.). > > Anyway, all of this is nice and philosophical, but it doesn't really > help much. > > The point remains that this is not a community. This is not a > collaborative project (except within the company itself). > > Ubuntu is also not a community. Debian is a community, yes, but Ubuntu > isn't. > > Debian has a constitution. Ubuntu doesn't have a constitution. It has > a code of conduct, but that is not the same. > > You can't influence Kubuntu, you cannot add to Kubuntu, you cannot do > anything for Kubuntu. Perhaps you can find a vocation (vacation) if > you can do some website work, but again, talk precedes doing, and if > they don't like your work, you are done. > > What else can I say? I can't say anything, and that was the whole > intent, probably. > > Sorry about that. See ya. > > > > > >> [snip] From demme at pobox.com Tue Oct 25 00:11:29 2016 From: demme at pobox.com (David Emme) Date: Mon, 24 Oct 2016 17:11:29 -0700 Subject: Vision for Kubuntu In-Reply-To: <4975d313d16334355d1aa366353ecf4e@dds.nl> References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> <4aa43ba25037b62a6cd8319e57602660@dds.nl> <4975d313d16334355d1aa366353ecf4e@dds.nl> Message-ID: On 10/24/2016 04:40 PM, Xen wrote (along with much ranting): > You can't influence Kubuntu, you cannot add to Kubuntu, you cannot do > anything for Kubuntu. Oh come on, tell us how you *really* feel! From list at xenhideout.nl Tue Oct 25 00:14:29 2016 From: list at xenhideout.nl (Xen) Date: Tue, 25 Oct 2016 02:14:29 +0200 Subject: Vision for Kubuntu In-Reply-To: References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> <4aa43ba25037b62a6cd8319e57602660@dds.nl> <4975d313d16334355d1aa366353ecf4e@dds.nl> Message-ID: <6a5f31e9bbc3b23447db01b21cb9a857@dds.nl> David Emme schreef op 25-10-2016 2:11: > On 10/24/2016 04:40 PM, Xen wrote (along with much ranting): >> You can't influence Kubuntu, you cannot add to Kubuntu, you cannot do >> anything for Kubuntu. > > > Oh come on, tell us how you *really* feel! Is this some kind of joke? (I haven't heard about you either, but yeah). From ofv at wanadoo.es Tue Oct 25 00:29:58 2016 From: ofv at wanadoo.es (=?utf-8?Q?=C3=93scar_Fuentes?=) Date: Tue, 25 Oct 2016 02:29:58 +0200 Subject: Vision for Kubuntu References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> <4aa43ba25037b62a6cd8319e57602660@dds.nl> <4975d313d16334355d1aa366353ecf4e@dds.nl> Message-ID: <87inshcltl.fsf@wanadoo.es> Xen writes: [snip] > On those public venues, which are supposed -- at least that's what you > would think -- to be places where people can freely talk, free talk is > actually not allowed and all messages are continually monitored to > comply with the mission. This is expected and reasonable. It is what I see on most, if not all, projects that I follow, unless the admins are asleep at the wheel (or simply too busy to do their duty.) [snip] > It is virtually impossible for Kubuntu to become involved as e.g. a > documentator, because there are no freely available places where you > can document. Free spots for "little work" are not available, and > hence only "bigger positions" are up for offer, that require real > commitment and big tasks to perform, effectively. Do you mean that if you submit a patch adding a small piece of documentation or simply correcting some typos, it will be rejected/ignored? [snip] > So they must indeed, completely, create their own project and create > their own space in which to do these things. But this is hardly > possible if you cannot talk to anyone *also* using the systems that > you yourself use. How do you get in touch with e.g. other Kubuntu > users if the Kubuntu channels themselves are not allowed for doing > that? What people do is to post *at* *most* one message on the mailing list saying "I'm starting a new project blah blah blah, follow-ups to X". But it is unacceptable to use the original project's communication channels for promoting your own project or to use them as if they were your own. [snip] > And simply put: communication precedes activity. > > Talk precedes doing. > > Design precedes implementation. So by blocking that first step, the > 2nd step also never arises and you are left without recourse, or, as > is said in Spanish "sin remedio". I know that, in theory, it should be that way, but that's not my experience about how things work. Every now and then someone appears with a significant contribution and *then* it is discussed. Sometimes it is rejected outright, sometimes changes are required but those are never implemented and the work is lost... Project maintainers are not prone to enter on lengthy discussions because they know that most of the time it is a waste of time. They very much prefer facts instead of words. Moreover, while refusing to enter on a philosophical discussion says nothing wrong about the maintainer (although the would-be interlocutor may think otherwise) ignoring a patch without proper review will seriously damage her image on the community. [snip] > And so of course it is correct that a project management is allowed to > do these things. But that is *not* an open source community. The whole > idea of open source is that you *are* allowed to do with it what you > want, and this *actively fights that*. The communication channels are not different from other project resources (web hosting, version control systems, bug tracking, etc.) Taking measures for ensuring that those resources are being used according to the project's goals is reasonable. If they think that an user is either mounting a revolt, recruiting people for a competing project or simply creating noise, it is their duty to stop that user's activity. I'm afraid that you have the wrong idea about what an Open Source project is. Catch phrases like "everybody is welcomed", "we are a community", etc. have not the broad meaning that you seem to attach to them. [snip] From errol at tzora.co.il Tue Oct 25 04:35:24 2016 From: errol at tzora.co.il (Errol Sapir) Date: Tue, 25 Oct 2016 07:35:24 +0300 Subject: sound in 16.10 Message-ID: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> An HTML attachment was scrubbed... URL: From ovidiu.b13 at gmail.com Tue Oct 25 05:59:56 2016 From: ovidiu.b13 at gmail.com (Ovidiu-Florin BOGDAN) Date: Tue, 25 Oct 2016 08:59:56 +0300 Subject: sound in 16.10 In-Reply-To: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> References: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> Message-ID: ALSA is a sound engine. Pulse Audio is a sound server, which is needed to separate the audio from different applications. Without it, all your sounds are merged into one, or you hear just one app at a time. Skype is known to cause audio problems. Mainly because is runs only in 32 bit mode. For me, a few reboots and Skype restarts fixed the issue every time. Pe 25 oct. 2016 07:36, "Errol Sapir" a scris: > Hi > I upgraded to 16.10 from 16.04. I now have sound problems. It started when > I installed Skype and the microphone didn't work (for skype or anything). > My sound system was operating pulse audio and I could hear through the > speaker output(with skype as well). > After googling solutions the main suggestion was to delete pulse audio and > install ALSA. I uninstalled pulse audio and tried installing ALSA but > obviously I did something wrong becuse nothing happened. I now have no > sound output or input at all. > Help please. > TIA > Errol > > -- > 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 o.sinclair at gmail.com Tue Oct 25 07:55:39 2016 From: o.sinclair at gmail.com (O. Sinclair) Date: Tue, 25 Oct 2016 09:55:39 +0200 Subject: sound in 16.10 In-Reply-To: References: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> Message-ID: <5e2692c7-b9c7-74ad-9c8b-eb2f736c9533@gmail.com> On 10/25/16 07:59, Ovidiu-Florin BOGDAN wrote: > ALSA is a sound engine. Pulse Audio is a sound server, which is needed > to separate the audio from different applications. Without it, all your > sounds are merged into one, or you hear just one app at a time. > > Skype is known to cause audio problems. Mainly because is runs only in > 32 bit mode. > > For me, a few reboots and Skype restarts fixed the issue every time. > > > Pe 25 oct. 2016 07:36, "Errol Sapir" > a scris: > > Hi > I upgraded to 16.10 from 16.04. I now have sound problems. It > started when I installed Skype and the microphone didn't work (for > skype or anything). My sound system was operating pulse audio and I > could hear through the speaker output(with skype as well). > After googling solutions the main suggestion was to delete pulse > audio and install ALSA. I uninstalled pulse audio and tried > installing ALSA but obviously I did something wrong becuse nothing > happened. I now have no sound output or input at all. > Help please. > TIA > Errol I don't know if this will help you but scout around for Skype Linux Alpha for Linux. It is, unlike the one in partner repo, under active development From chris at bvhg.freeserve.co.uk Tue Oct 25 10:47:16 2016 From: chris at bvhg.freeserve.co.uk (Chris Luck) Date: Tue, 25 Oct 2016 11:47:16 +0100 Subject: sound in 16.10 In-Reply-To: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> References: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> Message-ID: On 25/10/16 05:35, Errol Sapir wrote: > Hi I upgraded to 16.10 from 16.04. I now have sound problems. It > started when I installed Skype and the microphone didn't work (for > skype or anything). My sound system was operating pulse audio and I > could hear through the speaker output(with skype as well). [snip] This page may give you some idea of the general sound set up, issues to be considered and how to approach sound problems:- http://www.troubleshooters.com/linux/sound/sound_troubleshooting.htm Whether it helps in your case is something only you can determine. -- Regards, Chris Luck From list at xenhideout.nl Tue Oct 25 12:32:51 2016 From: list at xenhideout.nl (Xen) Date: Tue, 25 Oct 2016 14:32:51 +0200 Subject: Vision for Kubuntu In-Reply-To: <87inshcltl.fsf@wanadoo.es> References: <180741608635cd95c29c7505c5da6885@dds.nl> <3262760.ahAjEo3OYm@arnodesktop> <4aa43ba25037b62a6cd8319e57602660@dds.nl> <4975d313d16334355d1aa366353ecf4e@dds.nl> <87inshcltl.fsf@wanadoo.es> Message-ID: Óscar Fuentes schreef op 25-10-2016 2:29: > Xen writes: > > [snip] > >> On those public venues, which are supposed -- at least that's what you >> would think -- to be places where people can freely talk, free talk is >> actually not allowed and all messages are continually monitored to >> comply with the mission. > > This is expected and reasonable. It is what I see on most, if not all, > projects that I follow, unless the admins are asleep at the wheel (or > simply too busy to do their duty.) > > [snip] > >> It is virtually impossible for Kubuntu to become involved as e.g. a >> documentator, because there are no freely available places where you >> can document. Free spots for "little work" are not available, and >> hence only "bigger positions" are up for offer, that require real >> commitment and big tasks to perform, effectively. > > Do you mean that if you submit a patch adding a small piece of > documentation or simply correcting some typos, it will be > rejected/ignored? Kubuntu itself is not a source of a great amount of documentation in that sense, because it derives most from upstream. Naturally if you go directly to upstream, you won't have to deal with the whole Kubuntu situation at all. I am sure that if there was Kubuntu documentation they would allow small patches against it. I mean more that the best way to get involved with any community project is to start to perform small duties. The most agreeable duty anyone can fulfill is extending e.g. wiki documentation. That is something that is "free to do". This opportunity however barely exists. If I look at it again, they now point you to a "Trello" board that is filled with rather difficult tasks or for which you really need to be "part of the team" -- again, a clear separation between "internal" and "external" authority or space, the company vs. its clients, you might say. If you read on you realize the wiki is only about the Kubuntu _project_ but not about using the system in any kind. For that is apparently the separate documenation site. Which is not a wiki at all but a fixed documentation page/site which you can't readily edit unless, probably, you become part of a dedicated documentation team. This documentation however is so simple that it's practically worthless; it's the type of manual that people don't read (who reads a manual?) and just skip and start using the product regardless. I guess for some who are completely new it would give a quick overview, but the same quick overview (of software, for instance!) could be had by just checking out your application menu!!! There is no place whatsoever where you could insert personal remarkts, or stuff that doesn't currently yet work, it is too polished for that! So the raw, random, arbitrary nature of community content has no place there. It's a polished thing and ... by that nature, practically irrelevant (in this case) but the information *I* would be looking for is not there, and, I can also not insert. There is simply no community presence, anywhere. The system is not designed like that. The system is designed to be the product of a company and you generally do not change Microsoft Windows documentation either (but you go elsewhere to promote your fixes). Besides, why would they even want to accept patches if you are not part of the team? They want you to become part of the team first before you can submit any patches. That's the model of operation, because if you don't, they will see you as that outsider that has no business changing things (or something like that). > What people do is to post *at* *most* one message on the mailing list > saying "I'm starting a new project blah blah blah, follow-ups to X". > But > it is unacceptable to use the original project's communication channels > for promoting your own project or to use them as if they were your own. Most of what I would do personally is to talk about the (a) lack of the current system and then conjecture how the lack could be filled or the gap could be resolved. If it is not to do with Kubuntu, why would you talk here, right ? (Including the forums). So it's not about taking a pine forest and then planting a one year old oak tree there. It's usually about dropping a seed for some shrub. If you say "Use them as if they were your own" then apparently I am not part of it. This again, indicates, that there is no community. You are either part of the in-group or part of the out-group but there is nothing else. There are no shades of gray. There is no blending. Apparently, I can not call it "my own" even in the smallest part. There is only this aggressiveness that they don't want you to intrude on their territory, so to speak. That is called "hostile" and "putting up fences". Generally the way you get into a line of work or anything is that you end up chatting to the people who do it and they invite you in. I was offered a job the other day on the street. Not because I applied, but because we were talking about computer software and engineering. There was a "space" where chat was "free". Not that I could accept readily, my health is too bad to take up any positions and I cannot even travel at this point. I cannot ensure food in the fridge, let alone take on a job for which I need to travel each day, know what I'm saying? These people here blame me for not "doing any work" when "doing any work" requires you to hold a job here to begin with. It requires you to become an employee first. It requires you to take on responsibilities. It requires you to promise a certain presence and availability. I cannot even promise any continued existence, and this icks them, I don't know. I am not healthy enough to do the sort of thing they require or I would probably long since be working for that employer (or any other). And the thing I *am* capable of, is not accepted. What can I do about it? I do not have the health to get the smallest thing done currently, and they only want, they do not give. They give you nothing (in terms of allowance, friendliness) but constantly want your labour. Basically they have no understanding at all for what a lesser priviledged person may be in. They judge a rich western person with food in his belly the same as a poor African who has internet access once a week, as a matter of saying. They think everyone is the same, has the same abilities, the same capabilities, the same circumstances. It's a moral deficiency, what can I say. They think it is "ill will" when I cannot even make it to the freaking hospital to get an operation done, because if I have been operated I won't be able to take care for myself even more even though the current impediment is the biggest problem in my life. After operation I can't make it out of my house, cannot even make it INTO my house, so I suffer without recourse BUT I am to do their work for them. It's about as petty as it can get. They think their concerns and trepidations are so important. Someone else has no food. Someone else is dying. But, of course, Kubuntu's rules and regulations are more important than anything else. I guess it is an affliction of the complacent west, where people shield each other off from the misery of others and live in their own bubble so much that they cannot even *fathom* what another person may be going through. It does not even occur to them that, in fact, another person may in fact not be capable of performing the duties due to circumstances. But their project is of course more important than that person. The great little hobby company... Whereas in the street even I am offered more, as we have seen. A guy who sees how bad I can walk and he offers me some .NET programming job, well, whatever. I don't need a job although I would love to have one, but that's not what it's about. Your vision is friendliness, well you are not friendly. Period. Friendly computing but we mouth everyone off. Great. And I don't need anyone's pity all of a sudden but a little understanding (for whomever it is) would be great. Insults all those Linux people who use Linux and who run into those problems while she's at it. Because they "don't get their hands dirty" or however you want to frame it (I'm not reading back to see the exact quote). This insults their intent, insults their goodwill, when it is the people themselves who refuse to offer jobs (in that sense) and who even refuse patches when they are sent!!! Have you never seen how hard it is to get a patch accepted if you are part of the out-group? So it's not enough to "do the job", you must also be a teammember, you must be an employee. "It's the people who do the work that get to design the systems". Well I thought designing systems was work! You think design is some kind of free exercise that comes flying to you on clouds of dismay and ease? You snap your fingers and it's there? Or that it's the "reward" for having been a good employee for 3 years? No wonder design in Linux is so terrible then, if it is relegated to the shadows. Design is frowned upon. It is a do-ocracy, but not a think-ocracy. You are supposed to do before you think. No wonder then, that you can never find any design documents anywhere. There is hardly any design being done in the first place. Scarcely will you ever find some architectural overview about anything. It is certainly not at the fore-front of people's attention. >> Design precedes implementation. So by blocking that first step, the >> 2nd step also never arises and you are left without recourse, or, as >> is said in Spanish "sin remedio". > > I know that, in theory, it should be that way, but that's not my > experience about how things work. Every now and then someone appears > with a significant contribution and *then* it is discussed. Sometimes > it > is rejected outright, sometimes changes are required but those are > never > implemented and the work is lost... That would be fine if the platform should not be the community from which the changes arise. If you can completely stay away from the project (community) and can get your work perfectly done without any interaction whatsoever... sure that would be great.... In practice people need interaction, at least with someone. So perhaps if you have a healthy work environment, you have a job in which you can also do these things, and then you can offer your results in one go, then you don't need the "community". But I say again: you are thrown out of forums if you do this thing. If you discuss anything. And of course a picture says more than a 1000 words. And a completed project says more still. Where is this mighty "community" of us now? The only person I have ever met in Kubuntu was on IRC and our communication was shut down _very_ rapidly. > Project maintainers are not prone to > enter on lengthy discussions because they know that most of the time it > is a waste of time. They very much prefer facts instead of words. This basically implies that you have to do all of the work and implementation yourself without aid from the developers, you realize? > Moreover, while refusing to enter on a philosophical discussion says > nothing wrong about the maintainer (although the would-be interlocutor > may think otherwise) ignoring a patch without proper review will > seriously damage her image on the community. Maintainer and developer are different roles. For a maintainer it makes sense not to do that, it is not a development role. When people engage in debate they are trying to reach developers, not maintainers, in that sense. In essence, the "maintainer" only has to deal with completed projects, things that are ready for submission, that can then be rejected or accepted or rejected with comments, that sort of stuff. However many times we are looking for help and we are also looking to submit something in stages: first the idea, then the design, then the implementation, and so on. Why? Because otherwise WE would be wasting our time on someone that doesn't want it anyway. So this strategy doesn't actually "work" in the sense of creating good software. I mean the strategy of the maintainers that don't want to do any development work. What it basically means is that the interest of even cooperating or interoperating with the maintainer becomes less and less because the maintainer (or developer) doesn't want to be part of the activity that results IN the product. They then do not become a shareholder, a stakeholder. This results in MORE forks because interoperation with the original project is scarcely possible and if someone is not willing to humour you on the way towards the end product, you kinda lose the interest of even sharing your result with them. I originally simply wanted to say that they may not ignore your patch but they don't actually have to give it a good consideration. This is a façade to simply comply with expected behaviour without giving the submitter any leeway. What I mean is that it reminds me of the debates between Bohr and Einstein on Bohr's model of the atom. Bohr "submitted" his model at some convention and Einstein "gave him hell" or at least refused to accept the model and came up with rebuttal after rebuttal. In the end Bohr was able to refute them all and Einstein had to admit he had no arguments left. This is the same process you see with those patches: - the maintainer tries to prove that your patch has any flaws - your task is to rebute all of that and prove that the accusations do not hold. Basically your task is to withstand the "heat" you are given. But this is not a cooperative environment, of course. Bohr could not "go to Einstein" and ask him "help me to develop my model". No, he had to do that in his own time. But that's not community, and that's the whole point I am making. > The communication channels are not different from other project > resources (web hosting, version control systems, bug tracking, etc.) > Taking measures for ensuring that those resources are being used > according to the project's goals is reasonable. If they think that an > user is either mounting a revolt, recruiting people for a competing > project or simply creating noise, it is their duty to stop that user's > activity. And that is not community, is what I'm saying. > I'm afraid that you have the wrong idea about what an Open Source > project is. Catch phrases like "everybody is welcomed", "we are a > community", etc. have not the broad meaning that you seem to attach to > them. And that is my point. This is not any more community than e.g. on Synology's forums, even less so, I would add. "Kubuntu is a community of ..." no, not any more than that "Synology is a community of ...". I usually do not have an issue with what is. I have an issue with proclaiming falsehoods about what is. Because they lead to false attributions. "You do not want to do any work". Pardon me? Can you go insult someone else please? If you refuse to give someone a job or allow him to do any work, and as a consequence he does no work for you, that is your issue, not mine. In the real world that does not pose as "enlightened" or "of higher ethical standards" (such as around "open source" and "free software") these issues do not arise, you see. Well in a sense, they do. People desperately try to get a job and then they are still insulted for not doing any. Because the people do not see how they are getting insulted and treated, rejected and thrown out, at their prospective employers. And perhaps we are all responsible for our level of success in the world. Yet if "competition" is basically the hall-mark of "open source", then "open source" is not any more enlightened than the rest of the corporate world. If "mine not yours" is the hall-mark and credit of open source, then it is not any more enlightened than the rest of the corporate world. If "you are only welcome if you help us sell more, and you are basically just a tool for us selling our products" then there is not any more community here than anywhere else in the corporate world. If image marketing is just as important here as in the corporate world. If people lie just as much about what their product is and what flaws it doesn't have. Then that is the moral bankrupt of the whole idea of "free software" or "open source is a better way of doing things". Because in practice it means you are just as ill-equipped to change Kubuntu as you are in changing Microsoft Windows. Or any other open source project out there. Not all of them!!! I have certainly had debates with developers. You know which ones are the most amenable to influence? The most agreeable to welcoming you? It's the ones hosted at kernel.org. One at least two occasions they have said "Sure, I will fix this issue for you." Or "you are right that this needs to be fixed, but it is difficult ...". Perhaps because they have rejected GPL3, and stick to GPL2, I don't know. The kernel and its associated projects have more community than I have found elsewhere in the Linux world. They are more welcoming. They are happy to see you. And you know what, I have an issue with the mechanisms of the corporate world, and that's why I don't like it here so much, I guess. I mean the broader landscape of people who do not even understand what Linux actually is and what the opinions of Torvalds actually are. You will find time and time again, that the "Linux fanboys" are actually in disagreement with Linus Torvalds! It's also the only project that accepts a wicked number of patches. But anyway. Most Linux projects are just corporate projects using free resources, or something of the kind. Some 80% of real Linux development is probably done using paid employees. The rest are just fighting among eachother. From tommy.trussell at gmail.com Tue Oct 25 14:10:35 2016 From: tommy.trussell at gmail.com (Tommy Trussell) Date: Tue, 25 Oct 2016 09:10:35 -0500 Subject: Low-End Laptop Likes L... ... Kubuntu ?!?! In-Reply-To: <8FBD855D-C164-4641-9431-0F22972D3567@bmarsh.com> References: <8FBD855D-C164-4641-9431-0F22972D3567@bmarsh.com> Message-ID: On Mon, Oct 24, 2016 at 2:06 PM, bmarsh at bmarsh.com wrote: > > > On Oct 24, 2016, at 1:10 PM, Tommy Trussell > wrote: > > > > TL;DR > > > > For various reasons I've kept Ubuntu blinders on and I haven't run KDE > much in several years. I was surprised at how well Kubuntu 16.10 > "Yakkety-Yak" runs on a low-end laptop I own. > > > > Is Kubuntu considered a great choice for low-end laptops nowadays? > If Kubuntu ever appears to run out of steam on your laptop, give XFCE a > try. > > Works well for me - - I don't need all the glitz of KDE... > > I used to run XFCE on a 200 Mhz pentium system with several hundred K of RAM, but I haven't even tried Xubuntu in a long time. Thanks for the reminder! -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmarsh at bmarsh.com Tue Oct 25 14:34:00 2016 From: bmarsh at bmarsh.com (bmarsh at bmarsh.com) Date: Tue, 25 Oct 2016 10:34:00 -0400 Subject: Low-End Laptop Likes L... ... Kubuntu ?!?! In-Reply-To: References: <8FBD855D-C164-4641-9431-0F22972D3567@bmarsh.com> Message-ID: > On Oct 25, 2016, at 10:10 AM, Tommy Trussell wrote: > >> On Mon, Oct 24, 2016 at 2:06 PM, bmarsh at bmarsh.com wrote: >> >> > On Oct 24, 2016, at 1:10 PM, Tommy Trussell wrote: >> > >> > TL;DR >> > >> > For various reasons I've kept Ubuntu blinders on and I haven't run KDE much in several years. I was surprised at how well Kubuntu 16.10 "Yakkety-Yak" runs on a low-end laptop I own. >> > >> > Is Kubuntu considered a great choice for low-end laptops nowadays? >> If Kubuntu ever appears to run out of steam on your laptop, give XFCE a try. >> >> Works well for me - - I don't need all the glitz of KDE... >> > > I used to run XFCE on a 200 Mhz pentium system with several hundred K of RAM, but I haven't even tried Xubuntu in a long time. Thanks for the reminder! > I usually load Kubuntu first to get all the programs, and then add in XFCE. > -- > 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 valorie.zimmerman at gmail.com Tue Oct 25 19:01:25 2016 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Tue, 25 Oct 2016 12:01:25 -0700 Subject: Low-End Laptop Likes L... ... Kubuntu ?!?! In-Reply-To: References: Message-ID: Hi Tommy, I had a little travel netbook I didn't need anymore, so I gave it to my nephew who reallly wanted it. I put the 16.04 LTS on it, and set aside time to help him use it. When I stopped by their house, he said, Hi Auntie Val, no I don't need any help. Everything is great! That poor little atom-processor computer is 6 years old! Vaorie On Mon, Oct 24, 2016 at 10:10 AM, Tommy Trussell wrote: > TL;DR > > For various reasons I've kept Ubuntu blinders on and I haven't run KDE much > in several years. I was surprised at how well Kubuntu 16.10 "Yakkety-Yak" > runs on a low-end laptop I own. > > Is Kubuntu considered a great choice for low-end laptops nowadays? > > What bugaboos should I be watching for in KDE on a low-spec laptop? > > BACKGROUND INFORMATION: > > I have an Acer Aspire One D260 netbook purchased at Wal-Mart a few years > back. (I saw a recent posting on the Kubuntu list regarding a similar > laptop, so I know there's at least one other out there.) We originally > bought this one because it's very small and spouse and I thought it would be > good for travel. Sadly its 2-core Atom N260 1.66Ghz processor and its > maxxed-out 2Gb RAM are huge limitations. (That and its disappointingly > low-spec battery, and smaller-than-most screen, but we'll ignore those for > now.) I've never used Windows on it, though I left it installed for warranty > reasons. I haven't run anything on it but Ubuntu flavors in years. > > Because I wasn't the primary user of the netbook, I merely kept it updated > on versions of "straight" Ubuntu, following the upgrades through the > development of Unity etc. I also have been installing the Mate and LXDE > environments as alternatives for testing, and I sometimes switch among > those. > > In years past my experience was that LXDE has sometimes been more usable for > low-end systems. I also assumed MATE might presumably look like the older > Ubuntu releases spouse has been used to. Unfortunately (in my opinion) > Lubuntu has some quirks that make it a bit harder to support, and neither it > nor MATE have seemed as "polished" OR as RAM efficient as I hoped for. > > SO I am again looking at KDE...! > > WHAT I DID TODAY > > I keep LTS releases on most of my systems, but I try them all on the > netbook. I saw the Yakkety releases had come out, so I downloaded ISOs of > Ubuntu, Lubuntu, and Kubuntu. (I haven't yet downloaded any other Ubuntu > "spins," nor have I tried Mint lately.) > > This morning, I tried all three (booting from a USB stick). The clear winner > (based on my limited testing) was Kubuntu! Wow! I was surprised... > > This is based on a short (15 minute) test of each environment... > > My test procedure: > 1) burn iso to USB stick (using my primary Ubuntu LTS system) > 2) boot netbook from stick > 3) click "Try _buntu" button (doesn't exist in Lubuntu) > 4) connect to network > 5) open system monitor > 6) open Firefox > 7) connect to a couple of resource-intensive web sites > 8) watch processor and RAM figures as I connect (yes the CPU stays maxxed > out) > 9) open a LibreOffice writer document and type a few words > 10) watch RAM figures as I close everything (to see how much RAM gets > released) > ... > 11) pick another ISO and start over at step 1 > > WHAT DID I MISS? > > It occurs to me that maybe I am missing something -- > > For instance, I am watching the RAM figures in the system monitor because > that seems to be the big bugaboo on this system -- in "straight" Ubuntu, by > the time you open LibreOffice and a few web sites, the RAM usage is higher, > and once it gets maxxed-out, presumably things start going to swap. Ubuntu > does noticeably poorly with low RAM -- presumably Unity uses a lot of RAM > compared to other environments. > > HOWEVER it occurs to me that maybe the KDE System monitor MIGHT be measuring > RAM differently from the other system monitors. For instance, does the RAM > total include system RAM? I presume it does, because it doesn't drop to > zero, but it surprised me that it starts out noticeably lower, its maximum > is lower, and it releases pretty much everything when I close documents. > > Also it's likely Ubuntu starts up more stuff as you login, and maybe KDE > will start some things later. Do I need to turn something off as I use it > more? > > I just found a Reddit thread saying KDE works great on low-spec systems as > long as you avoid akonadi. Maybe that's outdated info, but I'll watch for > it. > > In the past we have seen a few weird random crashes on the netbook when > spouse is working hard on something, which may be due to hardware issues > when everything has been churning away for minutes at a time. SO ultimately > it may be time to retire the old laptop... but I hate to give up too soon. > > NEXT STEP > > I haven't installed it yet.... I'll be doing a "clean" install (overwriting > the OS but preserving/restoring the user accounts, which takes awhile). I > have never done this with Kubuntu but I presume the procedure is the same as > regular Ubuntu. > > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > -- http://about.me/valoriez From basroufs at gmail.com Tue Oct 25 21:13:47 2016 From: basroufs at gmail.com (Bas Roufs) Date: Tue, 25 Oct 2016 23:13:47 +0200 Subject: Fwd: Urgently help needed to get restarted with Kontact @ Kubuntu 14.04/ KDE 4.13.3. In-Reply-To: References: Message-ID: Hello Everybody. Kontact worked quite well till a few hours ago; at that moment, a big update seemed to mess everything up. As usual, I restarted the system after such an update. After that restart, I tried to restart Kontact: both via Kontact itself and via SYSTEM SETTINGS > personal information. However, nothing works any more. All I get, is the an error report starting with the phrase "The Akonadi personal information system is not running.....". The detailed error report, you can find below. My trouble shooting routine does not help neither. Several restarts did not help. I also have renamed a few times /home/.kde via mc in the terminal - midnight commander. After each renaming action, I quickly rebooted the system, with a view to getting a fresh version of .kde. This method worked often; no result now. I have also copied a few times backup versions of some essential files and folders into fresh version of /home/.kde. From .kde/share/apps, I have copied a few times /akregator and /emailidenties. From .kde/share/config, I have copied a few times some files: emaildefaults, emailidentities, kmail2rc, kmailrc. Such methods have been effective until recently; but not now. One time, I copied the whole .kde/share/config folder into the new version of .kde: no result neither. Is there any option left for getting restarted with Kontact?! One issue I really urgently need help for, is to get the local draft mail folder back; one draft mail I have been intensely working on the past few days, is only there. Is or are there any files in /.kde/share/config that can help me to get it back? I have a back-up of the .kde configuration of this afternoon. Also if I need to reinstall a whole 14.04 system, i absolutely want to migrate those local draft mails. To other things I want to migrate or get back, are: Akregator feeds; Email identities. Thanks! Yours. Bas G. Roufs. Akonadi Server Self-Test Report =============================== Test 1: SUCCESS -------- Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/bas/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/tmp/akonadi-bas.TsJGw2/mysql.socket" ServerPath=/usr/sbin/mysqld-akonadi StartServer=true [Debug] Tracer=null Test 2: SUCCESS -------- Akonadi is not running as root Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system. Test 3: SUCCESS -------- MySQL server found. Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld-akonadi'. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution. Test 4: SUCCESS -------- MySQL server is executable. Details: MySQL server found: 161025 21:59:55 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. /usr/sbin/mysqld Ver 5.5.53-0ubuntu0.14.04.1 for debian-linux-gnu on i686 ((Ubuntu)) Test 5: SUCCESS -------- No current MySQL error log found. Details: The MySQL server did not report any errors during this startup. The log can be found in '/home/bas/.local/share/akonadi/db_data/mysql.err'. Test 6: SUCCESS -------- MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at /etc/akonadi/mysql-global.conf. File content of '/etc/akonadi/mysql-global.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp # [mysqld] # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled # sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat # sql_mode=strict_trans_tables # DEBUGGING: # log all queries, useful for debugging but generates an enormous amount of data # log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) # log_slow_queries=mysql.slow # long_query_time=1 # log queries not using indices, debug only, disable for production use # log_queries_not_using_indexes=1 # # mesure database size and adjust innodb_buffer_pool_size # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) # Deprecated in MySQL >= 5.6.3 innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # The two options below make no sense with prepared statements and/or transactions # (make sense when having the same query multiple times) # Memory allocated for caching query results (default:0 (disabled)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_open_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K [client] default-character-set=utf8 Test 7: SKIP -------- MySQL server custom configuration not available. Details: The custom configuration for the MySQL server was not found but is optional. Test 8: SUCCESS -------- MySQL server configuration is usable. Details: The MySQL server configuration was found at /home/bas/.local/share/akonadi/mysql.conf and is readable. File content of '/home/bas/.local/share/akonadi/mysql.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp # [mysqld] # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled # sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat # sql_mode=strict_trans_tables # DEBUGGING: # log all queries, useful for debugging but generates an enormous amount of data # log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) # log_slow_queries=mysql.slow # long_query_time=1 # log queries not using indices, debug only, disable for production use # log_queries_not_using_indexes=1 # # mesure database size and adjust innodb_buffer_pool_size # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) # Deprecated in MySQL >= 5.6.3 innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # The two options below make no sense with prepared statements and/or transactions # (make sense when having the same query multiple times) # Memory allocated for caching query results (default:0 (disabled)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_open_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K [client] default-character-set=utf8 Test 9: SUCCESS -------- akonadictl found and usable Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully. Result: Akonadi 1.12.1 Test 10: ERROR -------- Akonadi control process not registered at D-Bus. Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 11: ERROR -------- Akonadi server process not registered at D-Bus. Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 12: SKIP -------- Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 13: ERROR -------- No resource agents found. Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed. Directory listing of '/usr/share/akonadi/agents': akonadibalooindexingagent.desktop akonadinepomukfeederagent.desktop akonotesresource.desktop archivemailagent.desktop birthdaysresource.desktop contactsresource.desktop davgroupwareresource.desktop facebookresource.desktop folderarchiveagent.desktop googlecalendarresource.desktop googlecontactsresource.desktop icaldirresource.desktop icalresource.desktop imapresource.desktop invitationsagent.desktop kabcresource.desktop kalarmdirresource.desktop kalarmresource.desktop kcalresource.desktop kdeaccountsresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mailfilteragent.desktop mboxresource.desktop migrationagent.desktop mixedmaildirresource.desktop mtdummyresource.desktop newmailnotifieragent.desktop nntpresource.desktop notesagent.desktop notesresource.desktop openxchangeresource.desktop pop3resource.desktop sendlateragent.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/' Test 14: ERROR -------- Current Akonadi server error log found. Details: The Akonadi server reported errors during its current startup. The log can be found in /home/bas/.local/share/akonadi/akonadiserver.error. File content of '/home/bas/.local/share/akonadi/akonadiserver.error': Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/bas/.local/share/akonadi/mysql.conf", "--datadir=/home/bas/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-bas.TsJGw2/mysql.socket") stdout: "" stderr: "/usr/sbin/mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2) 161025 21:59:53 [ERROR] Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : /var/lib/mysql-files 161025 21:59:53 [ERROR] Aborting " exit code: 1 process error: "Unknown error" "[ 0: akonadiserver() [0x805d445] 1: akonadiserver() [0x805d6ce] 2: [0xb7799404] 3: [0xb7799428] 4: /lib/i386-linux-gnu/libc.so.6(gsignal+0x47) [0xb6e43687] 5: /lib/i386-linux-gnu/libc.so.6(abort+0x143) [0xb6e46ab3] 6: /usr/lib/i386-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x123) [0xb74ecd73] 7: akonadiserver() [0x805f514] 8: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xc8) [0xb7591488] 9: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x11083e) [0xb75a183e] 10: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x35) [0xb75aaf35] 11: akonadiserver() [0x805877a] 12: akonadiserver() [0x80fcc72] 13: akonadiserver() [0x80600c9] 14: akonadiserver() [0x80627fe] 15: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN14QMetaCallEvent13placeMetaCallEP7QObject+0x3a) [0xb761b8aa] 16: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x20b) [0xb76236fb] 17: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x60) [0xb760a040] 18: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication6notifyEP7QObjectP6QEvent+0x54) [0xb760a0a4] 19: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x7a) [0xb7609e4a] 20: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1dd) [0xb760d70d] 21: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2c) [0xb760dc1c] 22: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x1a923e) [0xb763a23e] 23: /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x273) [0xb6d141e3] 24: /lib/i386-linux-gnu/libglib-2.0.so.0(+0x47468) [0xb6d14468] 25: /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x38) [0xb6d14528] 26: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6b) [0xb763993b] 27: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x43) [0xb7608823] 28: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x179) [0xb7608b49] 29: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8e) [0xb760e8fe] 30: akonadiserver() [0x8057849] 31: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb6e2eaf3] 32: akonadiserver() [0x8058372] ] " Test 15: ERROR -------- Previous Akonadi server error log found. Details: The Akonadi server reported errors during its previous startup. The log can be found in /home/bas/.local/share/akonadi/akonadiserver.error.old. File content of '/home/bas/.local/share/akonadi/akonadiserver.error.old': Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/bas/.local/share/akonadi/mysql.conf", "--datadir=/home/bas/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-bas.TsJGw2/mysql.socket") stdout: "" stderr: "/usr/sbin/mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2) 161025 21:59:53 [ERROR] Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : /var/lib/mysql-files 161025 21:59:53 [ERROR] Aborting " exit code: 1 process error: "Unknown error" "[ 0: akonadiserver() [0x805d445] 1: akonadiserver() [0x805d6ce] 2: [0xb7768404] 3: [0xb7768428] 4: /lib/i386-linux-gnu/libc.so.6(gsignal+0x47) [0xb6e12687] 5: /lib/i386-linux-gnu/libc.so.6(abort+0x143) [0xb6e15ab3] 6: /usr/lib/i386-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x123) [0xb74bbd73] 7: akonadiserver() [0x805f514] 8: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xc8) [0xb7560488] 9: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x11083e) [0xb757083e] 10: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x35) [0xb7579f35] 11: akonadiserver() [0x805877a] 12: akonadiserver() [0x80fcc72] 13: akonadiserver() [0x80600c9] 14: akonadiserver() [0x80627fe] 15: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN14QMetaCallEvent13placeMetaCallEP7QObject+0x3a) [0xb75ea8aa] 16: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x20b) [0xb75f26fb] 17: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x60) [0xb75d9040] 18: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication6notifyEP7QObjectP6QEvent+0x54) [0xb75d90a4] 19: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x7a) [0xb75d8e4a] 20: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1dd) [0xb75dc70d] 21: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2c) [0xb75dcc1c] 22: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x1a923e) [0xb760923e] 23: /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x273) [0xb6ce31e3] 24: /lib/i386-linux-gnu/libglib-2.0.so.0(+0x47468) [0xb6ce3468] 25: /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x38) [0xb6ce3528] 26: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6b) [0xb760893b] 27: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x43) [0xb75d7823] 28: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x179) [0xb75d7b49] 29: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8e) [0xb75dd8fe] 30: akonadiserver() [0x8057849] 31: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb6dfdaf3] 32: akonadiserver() [0x8058372] ] " Test 16: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 17: SUCCESS -------- No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup. -- Bas G. Roufs Utrecht, NL, E. BasRoufs at gmail.com; Mob. +31 6 446 835 10; From henry.linux.1973 at gmail.com Wed Oct 26 01:48:43 2016 From: henry.linux.1973 at gmail.com (Henry Linux) Date: Tue, 25 Oct 2016 22:48:43 -0300 Subject: sound in 16.10 In-Reply-To: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> References: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> Message-ID: 2016-10-25 1:35 GMT-03:00 Errol Sapir : > Hi > I upgraded to 16.10 from 16.04. I now have sound problems. It started when I > installed Skype and the microphone didn't work (for skype or anything). My > sound system was operating pulse audio and I could hear through the speaker > output(with skype as well). > After googling solutions the main suggestion was to delete pulse audio and > install ALSA. I uninstalled pulse audio and tried installing ALSA but > obviously I did something wrong becuse nothing happened. I now have no sound > output or input at all. > Help please. > TIA > Errol > > -- try pavucontrol and configure the outputs and the inputs from pavucontrol Henry. > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > From errol at tzora.co.il Wed Oct 26 02:56:33 2016 From: errol at tzora.co.il (Errol Sapir) Date: Wed, 26 Oct 2016 05:56:33 +0300 Subject: sound in 16.10 In-Reply-To: References: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> Message-ID: <166fcc25-bd4e-9bd0-af6c-f0cc555138c7@tzora.co.il> An HTML attachment was scrubbed... URL: From kassube at gmx.net Wed Oct 26 05:06:40 2016 From: kassube at gmx.net (Nils Kassube) Date: Wed, 26 Oct 2016 07:06:40 +0200 Subject: Fwd: Urgently help needed to get restarted with Kontact @ Kubuntu 14.04/ KDE 4.13.3. In-Reply-To: References: Message-ID: <2043359.XMaaoI8KsB@p5915> Bas Roufs wrote: > Kontact worked quite well till a few hours ago; at that moment, a big > update seemed to mess everything up. As usual, I restarted the system > after such an update. After that restart, I tried to restart Kontact: > both via Kontact itself and via SYSTEM SETTINGS > personal > information. However, nothing works any more. All I get, is the an > error report starting with the phrase "The Akonadi personal > information system is not running.....". The detailed error report, > you can find below. Same here - the update of mysql is the culprit. I installed the previous version and Kmail started again. These are the packages I installed: libmysqlclient18_5.5.52-0ubuntu0.14.04.1_amd64.deb mysql-client-5.5_5.5.52-0ubuntu0.14.04.1_amd64.deb mysql-client-core-5.5_5.5.52-0ubuntu0.14.04.1_amd64.deb mysql-common_5.5.52-0ubuntu0.14.04.1_all.deb mysql-server-core-5.5_5.5.52-0ubuntu0.14.04.1_amd64.deb I still found them in "/var/cache/apt/archives/" - if you can't find them there, you will have to search on the net (archive.ubuntu.com should have them). Nils From basroufs at gmail.com Wed Oct 26 13:35:39 2016 From: basroufs at gmail.com (Bas G. Roufs) Date: Wed, 26 Oct 2016 15:35:39 +0200 Subject: Fwd: Urgently help needed to get restarted with Kontact @ Kubuntu 14.04/ KDE 4.13.3. In-Reply-To: <2043359.XMaaoI8KsB@p5915> References: <2043359.XMaaoI8KsB@p5915> Message-ID: <2344490.IGUkd3JSUF@viaconsensus-camino> Hello Nils and Everybody. Thanks Nils for your suggestions after my message of yesterday: > > Kontact worked quite well till a few hours ago; at that moment, a big > > update seemed to mess everything up...... > > However, nothing works any more. All I get, is the an > > error report starting with the phrase "The Akonadi personal > > information system is not running.....". ... With one phrase from you, Nils, I agree wholeheartedly..... > Same here - the update of mysql is the culprit. No doubt, such a solution may work for now: > I installed the previous version and Kmail started again. However, I am not sure whether such a downgrade is structural solution you can keep relying on. On the other hand, when Googling this morning the phrase "The Akonadi personal information system is not running....." , I stumbled upon two bug reports that together brought more clarity in the issue. Look at this report: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1448345 It's also worth looking at this "duplicate": https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1445383 They key issue is that "mysql" has to be replaced by a "fork": "mariadb". I have done this as follows. I checked first which version I had from "mysql-server-core" and "mysql-client- core"; it was version 5.5. in my case. A second step was this command line command: sudo apt-get purge mysql-server-core-5.5 mysql-client-core-5.5 After hitting the enter-button, I got a whole bunch of technical texts, amongst which this: The following extra packages will be installed: libmariadbclient18 mariadb-client-core-5.5 mariadb-common mariadb-server-core-5.5 The following packages will be REMOVED: mysql-client-core-5.5* mysql-server-core-5.5* The following NEW packages will be installed: libmariadbclient18 mariadb-client-core-5.5 mariadb-common mariadb-server-core-5.5 The following NEW packages will be installed: libmariadbclient18 mariadb-client-core-5.5 mariadb-common mariadb-server-core-5.5 0 upgraded, 4 newly installed, 2 to remove and 0 not upgraded. Need to get 4,884 kB of archives. After this operation, 1,672 kB disk space will be freed. Do you want to continue? [Y/n] y Of course, I have entered "y", to confirm this action. Now, I can access again KMail and most of the other parts of Kontact. I can access again the draft mail I talked about yesterday. One part of Kontact is still a problem: "Akregator", the feeds. This issue I will deal with in another thread. Thanks, yours, Bas. -- Bas G. Roufs Utrecht, NL, EU. E.: BasRoufs at gmail.com; M./SMS: +31 6 446 835 10. From basroufs at gmail.com Wed Oct 26 16:50:54 2016 From: basroufs at gmail.com (Bas G. Roufs) Date: Wed, 26 Oct 2016 18:50:54 +0200 Subject: MySQL en alternatief In-Reply-To: <2043359.XMaaoI8KsB@p5915> References: <2043359.XMaaoI8KsB@p5915> Message-ID: <2537293.Tm1lO9fd8K@viaconsensus-camino> */Re: Fwd: Urgently help needed to get restarted with Kontact @ Kubuntu 14.04/ KDE 4.13.3./* Hello Nils and Everybody. Thanks Nils for your suggestions after my message of yesterday: > > Kontact worked quite well till a few hours ago; at that moment, a big > > update seemed to mess everything up...... > > However, nothing works any more. All I get, is the an > > error report starting with the phrase "The Akonadi personal > > information system is not running.....". ... With one phrase from you, Nils, I agree wholeheartedly..... > Same here - the update of mysql is the culprit. No doubt, such a solution may work for now: > I installed the previous version and Kmail started again. However, I am not sure whether such a downgrade is structural solution you can keep relying on. On the other hand, when Googling this morning the phrase "The Akonadi personal information system is not running....." , I stumbled upon two bug reports that together brought more clarity in the issue. Look at this report: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1448345 It's also worth looking at this "duplicate": https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1445383 They key issue is that "mysql" has to be replaced by a "fork": "mariadb". I have done this as follows. I checked first which version I had from "mysql-server-core" and "mysql-client- core"; it was version 5.5. in my case. A second step was this command line command: sudo apt-get purge mysql-server-core-5.5 mysql-client-core-5.5 After hitting the enter-button, I got a whole bunch of technical texts, amongst which this: The following extra packages will be installed: libmariadbclient18 mariadb-client-core-5.5 mariadb-common mariadb-server-core-5.5 The following packages will be REMOVED: mysql-client-core-5.5* mysql-server-core-5.5* The following NEW packages will be installed: libmariadbclient18 mariadb-client-core-5.5 mariadb-common mariadb-server-core-5.5 The following NEW packages will be installed: libmariadbclient18 mariadb-client-core-5.5 mariadb-common mariadb-server-core-5.5 0 upgraded, 4 newly installed, 2 to remove and 0 not upgraded. Need to get 4,884 kB of archives. After this operation, 1,672 kB disk space will be freed. Do you want to continue? [Y/n] y Of course, I have entered "y", to confirm this action. Now, I can access again KMail and most of the other parts of Kontact. I can access again the draft mail I talked about yesterday. One part of Kontact is still a problem: "Akregator", the feeds. This issue I will deal with in another thread. Thanks, yours, Bas. -- Bas G. Roufs Utrecht, NL, EU. E.: BasRoufs at gmail.com; M./SMS: +31 6 446 835 10. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kassube at gmx.net Wed Oct 26 20:17:54 2016 From: kassube at gmx.net (Nils Kassube) Date: Wed, 26 Oct 2016 22:17:54 +0200 Subject: Fwd: Urgently help needed to get restarted with Kontact @ Kubuntu 14.04/ KDE 4.13.3. In-Reply-To: <2344490.IGUkd3JSUF@viaconsensus-camino> References: <2043359.XMaaoI8KsB@p5915> <2344490.IGUkd3JSUF@viaconsensus-camino> Message-ID: <2202246.jeCQaCnK6M@p5915> Bas G. Roufs wrote: > No doubt, such a solution may work for now: > > I installed the previous version and Kmail started again. > > However, I am not sure whether such a downgrade is structural solution > you can keep relying on. It is certainly not the best solution, especially if we consider that the msql upgrade included security fixes. Unfortunately the Ubuntu Security Notice USN-3109-1 also included this paragraph: | In addition to security fixes, the updated packages contain bug fixes, | new features, and possibly incompatible changes. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I always thought that upgrades to LTS releases wouldn't break the installed system, but obviously that's not the case. > They key issue is that "mysql" has to be replaced by a "fork": > "mariadb". [...] > Now, I can access again KMail and most of the other parts of Kontact. > I can access again the draft mail I talked about yesterday. Thanks for the instructions to switch to mariadb. That saves me some time to search how to do it. :) Nils From errol at tzora.co.il Thu Oct 27 03:51:21 2016 From: errol at tzora.co.il (Errol Sapir) Date: Thu, 27 Oct 2016 06:51:21 +0300 Subject: sound in 16.10 In-Reply-To: References: <5225c477-4be2-e417-15f6-a9c2b3f35f5b@tzora.co.il> Message-ID: <992c056e-6286-faee-96d3-e0c603280d52@tzora.co.il> An HTML attachment was scrubbed... URL: From owlman.lists at gmail.com Fri Oct 28 00:31:58 2016 From: owlman.lists at gmail.com (John Reid) Date: Fri, 28 Oct 2016 11:31:58 +1100 Subject: kernel problem with 16.10 Message-ID: <00027acd-0a7a-4415-b233-b573a7d6e740@gmail.com> Hi all, What is the appropriate channel to report problems with the new kernel? My laptop keyboard is not recognised by the shipped kernel (4.8.0), however works fine using the 4.8.4 kernel from the mainline kernel ppa repository. Cheers, John From kassube at gmx.net Fri Oct 28 05:27:19 2016 From: kassube at gmx.net (Nils Kassube) Date: Fri, 28 Oct 2016 07:27:19 +0200 Subject: kernel problem with 16.10 In-Reply-To: <00027acd-0a7a-4415-b233-b573a7d6e740@gmail.com> References: <00027acd-0a7a-4415-b233-b573a7d6e740@gmail.com> Message-ID: <2662018.M11vWoenUj@p5915> John Reid wrote: > What is the appropriate channel to report problems with the new > kernel? My laptop keyboard is not recognised by the shipped kernel > (4.8.0), however works fine using the 4.8.4 kernel from the mainline > kernel ppa repository. You should file a bug report at . The easiest way to do this is probably the command ubuntu-bug linux which will automatically collect information about your system and attach it to the bug report. Nils From cody.smith at ubuntu.com Fri Oct 28 21:32:01 2016 From: cody.smith at ubuntu.com (Cody Smith) Date: Fri, 28 Oct 2016 14:32:01 -0700 Subject: kernel problem with 16.10 In-Reply-To: References: <00027acd-0a7a-4415-b233-b573a7d6e740@gmail.com> <2662018.M11vWoenUj@p5915> Message-ID: Also, it should be noted that reporting kernel bugs requires a bit more info than most other software, there but reporting software usually does a good job of gathering and adding it, but be prepared to get your hands dirty in the terminal in case it's required. --c_smith On Oct 27, 2016 10:28 PM, "Nils Kassube" wrote: John Reid wrote: > What is the appropriate channel to report problems with the new > kernel? My laptop keyboard is not recognised by the shipped kernel > (4.8.0), however works fine using the 4.8.4 kernel from the mainline > kernel ppa repository. You should file a bug report at . The easiest way to do this is probably the command ubuntu-bug linux which will automatically collect information about your system and attach it to the bug report. Nils -- 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 chris at bvhg.freeserve.co.uk Sat Oct 29 22:30:25 2016 From: chris at bvhg.freeserve.co.uk (Chris Luck) Date: Sat, 29 Oct 2016 23:30:25 +0100 Subject: Time Problems in Kubuntu 16.04 and 16.10 In-Reply-To: <1583056.ZHuvTeCjMm@p5915> References: <1583056.ZHuvTeCjMm@p5915> Message-ID: On 24/10/16 11:20, Nils Kassube wrote: > David Corkrey Sr. wrote: >> After a reboot into Windows 10, the time displayed in Windows was 4 >> hours off (later). This did not occur with Kubuntu 14.04 LTS. > > Windows expects the hardware clock to be set to your local time and i > think Kubuntu now defaults to the hardware clock using UTC. You can > check the file "/etc/default/rcS" - if there is a line > > UTC=yes > > the hardware clock is set to UTC. If you change it to > > UTC=no > > Kubuntu will use local time like Windows does and there shouldn't be > a difference between the operating systems. In my case it was just 1 hour difference (UTC -> British Summer Time). A minor niggle that only shows for 6 months each year - but puzzling. With 16.04 the file "/etc/default/rcS" is still there though the line UTC was not. In 16.10 the file is entirely absent. I added the line UTC=no in 16.04, and created the file in 16.10. This had the desired effect in each case, the only additional change required being to manually reset the Windows setting. After that, swapping between the two OS's gives consistent times. I'm typing this at 11.30pm on the last Saturday in October - which means the clocks go back 1 hour at 2.00am (BST) tomorrow morning. A timely opportunity to test the automatic time setting. Thanks for the info. -- Regards, Chris Luck From Sascha.Manns at mailbox.org Sun Oct 30 12:13:15 2016 From: Sascha.Manns at mailbox.org (Sascha Manns) Date: Sun, 30 Oct 2016 13:13:15 +0100 Subject: kde-telepathy can't load module Message-ID: <5027290.tQ99XX5CDL@sascha-desktop> Hello list, i'm trying to add a jabber account to my instant messaging telepathy. But after clicking on the add button i'm getting: "The module ktpaccountskcm_plugin_kaccounts can't be loaded. Please check your installation." Does anyone knows how to fix this? Greetings Sascha -- Sincerly yours Sascha Manns Maifeldstraße 10 56727 Mayen Phone: +49-1573-9242730 (mobile) Phone: +49-2651-4014045 (home) Email: Sascha.Manns at mailbox.org Jabber: saigkill at jabber.org Web: http://saigkill.github.io Linkedin/Twitter: saigkill Facebook: sascha.manns / Xing: Sascha_Manns2 GPG: 645A18FC6B573A7BE6E95150752763E8BFA83A2C @ hkp://keys.gnupg.net S/MIME: C57921ED8F7535B08DC6D14BF11CD19BF9E8ED5C @ cacert.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: This is a digitally signed message part. URL: From post at volker-wysk.de Sun Oct 30 12:18:55 2016 From: post at volker-wysk.de (Volker Wysk) Date: Sun, 30 Oct 2016 13:18:55 +0100 Subject: kde-telepathy can't load module In-Reply-To: <5027290.tQ99XX5CDL@sascha-desktop> References: <5027290.tQ99XX5CDL@sascha-desktop> Message-ID: <2706644.jm36VbfzSd@desktop> Am Sonntag, 30. Oktober 2016, 13:13:15 CET schrieb Sascha Manns: > Hello list, > > i'm trying to add a jabber account to my instant messaging telepathy. But > after clicking on the add button i'm getting: "The module > ktpaccountskcm_plugin_kaccounts can't be loaded. Please check your > installation." ~ $ apt-file search ktpaccountskcm_plugin_kaccounts kde-config-telepathy-accounts: /usr/lib/x86_64-linux-gnu/qt5/plugins/kaccounts/ ui/ktpaccountskcm_plugin_kaccounts.so Seems like you need to install kde-config-telepathy-accounts. Cheers Volker From Sascha.Manns at mailbox.org Sun Oct 30 12:59:35 2016 From: Sascha.Manns at mailbox.org (Sascha Manns) Date: Sun, 30 Oct 2016 13:59:35 +0100 Subject: kde-telepathy can't load module In-Reply-To: <2706644.jm36VbfzSd@desktop> References: <5027290.tQ99XX5CDL@sascha-desktop> <2706644.jm36VbfzSd@desktop> Message-ID: <3708128.cFTC4AT9tW@sascha-desktop> Hi Volker, Am Sonntag, 30. Oktober 2016, 13:18:55 CET schrieb Volker Wysk: > Am Sonntag, 30. Oktober 2016, 13:13:15 CET schrieb Sascha Manns: > > Hello list, > > > > i'm trying to add a jabber account to my instant messaging telepathy. But > > after clicking on the add button i'm getting: "The module > > ktpaccountskcm_plugin_kaccounts can't be loaded. Please check your > > installation." > > ~ $ apt-file search ktpaccountskcm_plugin_kaccounts > kde-config-telepathy-accounts: > /usr/lib/x86_64-linux-gnu/qt5/plugins/kaccounts/ > ui/ktpaccountskcm_plugin_kaccounts.so > > Seems like you need to install kde-config-telepathy-accounts. That one works. Thank you very much :-) -- Sincerly yours Sascha Manns Maifeldstraße 10 56727 Mayen Phone: +49-1573-9242730 (mobile) Phone: +49-2651-4014045 (home) Email: Sascha.Manns at mailbox.org Jabber: saigkill at jabber.org Web: http://saigkill.github.io Linkedin/Twitter: saigkill Facebook: sascha.manns / Xing: Sascha_Manns2 GPG: 645A18FC6B573A7BE6E95150752763E8BFA83A2C @ hkp://keys.gnupg.net S/MIME: C57921ED8F7535B08DC6D14BF11CD19BF9E8ED5C @ cacert.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: This is a digitally signed message part. URL: From chris at bvhg.freeserve.co.uk Sun Oct 30 20:42:14 2016 From: chris at bvhg.freeserve.co.uk (Chris Luck) Date: Sun, 30 Oct 2016 20:42:14 +0000 Subject: Time Problems in Kubuntu 16.04 and 16.10 In-Reply-To: References: <1583056.ZHuvTeCjMm@p5915> Message-ID: On 29/10/16 23:30, Chris Luck wrote: > A timely opportunity to test the automatic time setting. Well, it seemed to work - initially. Monitoring in Kubuntu, the clocks on both systems jumped back an hour at 2.00am. One system is a Dell desktop dual-booting between Kubuntu 16.04 and WinXP, the other an Asus laptop running Kubuntu 16.10 and Win10. When I switched to XP on the Dell the boot-up screen hung while showing the WindowsXP logo - an uncommon event. A power-button reset was needed to get it running again but it was now showing the same time as 16.04. The laptop showed no such quirks and Win10 also showed the same time as 16.10. There I put both systems (and myself) to bed. This morning I found that both Kubuntu systems still showed the correct time but both Windows systems were running 1 hour behind time! I disabled the mods. and both Windows systems got back in step with the rest of the world. I am hoping, before long, to entirely dispense with MS intrusion-ware so I don't expect to be pursuing the topic, though I understand why others might. -- Regards, Chris Luck From post at volker-wysk.de Mon Oct 31 15:10:33 2016 From: post at volker-wysk.de (Volker Wysk) Date: Mon, 31 Oct 2016 16:10:33 +0100 Subject: Kubuntu PPA doesn't work Message-ID: <1976356.oz5nkb5pk6@desktop> Hello! Of the two Kununtu PPAs, one doesn't work for me: ~ % apt update OK:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Holen:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease [95,7 kB] OK:3 http://security.ubuntu.com/ubuntu xenial-security InRelease OK:4 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial InRelease Ign:5 http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial InRelease OK:6 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease Fehl:7 http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial Release 404 Not Found Paketlisten werden gelesen... Fertig E: The repository 'http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. The culprit is the second one: kubuntu-ppa-ubuntu-ppa-xenial.list ~ % cat /etc/apt/sources.list.d/kubuntu-ppa-ubuntu-ppa-xenial.list deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial main I have followed the instructions on https://community.kde.org/Kubuntu/PPAs in order to add the "Kubuntu Updates" PPA. What am I doing wrong..? Bye V.W. From clay at claydoh.com Mon Oct 31 17:20:29 2016 From: clay at claydoh.com (Clay Weber) Date: Mon, 31 Oct 2016 13:20:29 -0400 Subject: Kubuntu PPA doesn't work In-Reply-To: <1976356.oz5nkb5pk6@desktop> References: <1976356.oz5nkb5pk6@desktop> Message-ID: <3045685.CBHk1E9FT3@jake-latitude-e6420> On Monday, October 31, 2016 4:10:33 PM EDT Volker Wysk wrote: > Hello! > > Of the two Kununtu PPAs, one doesn't work for me: > > ~ % apt update > OK:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease > Holen:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease [95,7 > kB] OK:3 http://security.ubuntu.com/ubuntu xenial-security InRelease > OK:4 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial InRelease > Ign:5 http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial InRelease > OK:6 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease > Fehl:7 http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial Release > 404 Not Found > Paketlisten werden gelesen... Fertig > E: The repository 'http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial > Release' does not have a Release file. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > > The culprit is the second one: kubuntu-ppa-ubuntu-ppa-xenial.list > > ~ % cat /etc/apt/sources.list.d/kubuntu-ppa-ubuntu-ppa-xenial.list > deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu xenial main > > I have followed the instructions on https://community.kde.org/Kubuntu/PPAs > in order to add the "Kubuntu Updates" PPA. > > What am I doing wrong..? > > > Bye > V.W. There simply are no Xenial packages in that ppa; they will all be in the kubuntu- backports one. The Updates PPA ia only relevant to 12.04 and 14.04 systems. https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/ppa Someone needs to update the wiki page to reflect this until or unless there are plans to use this ppa in the future. -- Clay Weber From post at volker-wysk.de Mon Oct 31 18:21:41 2016 From: post at volker-wysk.de (Volker Wysk) Date: Mon, 31 Oct 2016 19:21:41 +0100 Subject: Kubuntu PPA doesn't work In-Reply-To: <3045685.CBHk1E9FT3@jake-latitude-e6420> References: <1976356.oz5nkb5pk6@desktop> <3045685.CBHk1E9FT3@jake-latitude-e6420> Message-ID: <2154100.XOA77oEyQk@desktop> Hi Am Montag, 31. Oktober 2016, 13:20:29 CET schrieb Clay Weber: > There simply are no Xenial packages in that ppa; they will all be in the > kubuntu- backports one. The Updates PPA ia only relevant to 12.04 and 14.04 > systems. > > https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/ppa > > Someone needs to update the wiki page to reflect this until or unless there > are plans to use this ppa in the future. I tried to file a bug report with ubuntu-bug. I've done this before. It shouldn't produce an error in the client, when a PPA simply is empty. But now, this doesn't work at all. I don't know which package this is in, so I started "ubuntu-bug" without any arguments. I chose "dist-upgrade" for the question "which kind of problem do you want do report". Then it asks me, for what hardware I want to report a problem (??). I chose "It's not listed here". Then it asks me for sound problems - I have chosen nothing related to sound! Then it wants to perform a speaker test. Then it asks me no question, but only the text "test". Then I cancel this thing. At the end, it produces a segmenation fault. Nevertheless, thanks for the help! Volker From clay at claydoh.com Mon Oct 31 18:52:32 2016 From: clay at claydoh.com (Clay Weber) Date: Mon, 31 Oct 2016 14:52:32 -0400 Subject: Kubuntu PPA doesn't work In-Reply-To: <2154100.XOA77oEyQk@desktop> References: <1976356.oz5nkb5pk6@desktop> <3045685.CBHk1E9FT3@jake-latitude-e6420> <2154100.XOA77oEyQk@desktop> Message-ID: <6512202.mMhzORsmHF@jake-latitude-e6420> On Monday, October 31, 2016 7:21:41 PM EDT Volker Wysk wrote: > Hi > > Am Montag, 31. Oktober 2016, 13:20:29 CET schrieb Clay Weber: > > There simply are no Xenial packages in that ppa; they will all be in the > > kubuntu- backports one. The Updates PPA ia only relevant to 12.04 and > > 14.04 systems. > > > > https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/ppa > > > > Someone needs to update the wiki page to reflect this until or unless > > there > > are plans to use this ppa in the future. > > I tried to file a bug report with ubuntu-bug. I've done this before. It > shouldn't produce an error in the client, when a PPA simply is empty. > > But now, this doesn't work at all. I don't know which package this is in, so > I started "ubuntu-bug" without any arguments. I chose "dist-upgrade" for > the question "which kind of problem do you want do report". Then it asks > me, for what hardware I want to report a problem (??). I chose "It's not > listed here". Then it asks me for sound problems - I have chosen nothing > related to sound! Then it wants to perform a speaker test. Then it asks me > no question, but only the text "test". Then I cancel this thing. At the > end, it produces a segmenation fault. > > Nevertheless, thanks for the help! > > Volker The ppa is not empty, it does not provide packages for each and every Ubuntu release. Many PPAs do not. Probably the place to add the bug, or rather a feature request, on the script would be to file it against software-properties-common, which is the package that provides the add-apt-repository script. All this script does is take the ppa url, grabs the description of the ppa, converts the the url to a sources.list entry, and asks for confirmation before writing the file. so it is not much different from manually editing one's sources.list. -- Clay Weber From samorris at netspace.net.au Mon Oct 31 21:06:14 2016 From: samorris at netspace.net.au (Stephen Morris) Date: Tue, 1 Nov 2016 08:06:14 +1100 Subject: Kubuntu 16.10 is out! In-Reply-To: <8b74858c-601c-b4f1-5a0b-65d89b3a1139@netspace.net.au> References: <79d3eaa6-b590-b3fe-fca3-26079af4e660@netspace.net.au> <722de724-f0ea-1cae-946a-a61b9c053eff@netspace.net.au> <8b74858c-601c-b4f1-5a0b-65d89b3a1139@netspace.net.au> Message-ID: <0274e881-e502-ed2c-a20b-464a3bf24f97@netspace.net.au> On 24/10/16 08:10, Stephen Morris wrote: > On 23/10/16 10:39, Valorie Zimmerman wrote: >> Reply inline. >> >> On Fri, Oct 21, 2016 at 6:13 PM, Stephen Morris >> wrote: >>> On 21/10/16 09:34, Valorie Zimmerman wrote: >>>> Removing the -devel list since this is a support question. >>>> >>>> On Tue, Oct 18, 2016 at 3:12 PM, Stephen Morris >>>> wrote: >>>>> On 14/10/16 15:29, Valorie Zimmerman wrote: >>>>>> Hi folks, I'm sure most of you have heard by now, but just in case: >>>>>> Kubuntu 16.10 has been released, along with all flavors of Ubuntu. >>>>>> >>>>>> The official announcement: >>>>>> >>>>>> >>>>>> http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html >>>>>> >>>>>> >>>>>> We've got an announcement on the website as well: >>>>>> https://kubuntu.org/news/kubuntu-16-10-released/ >>>>>> >>>>>> Our step-by-step about installing and upgrading lacks some >>>>>> screenshots. Please feel free to help out there if you can: >>>>>> https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu >>>>>> >>>>>> If you want to seed the torrents, the easiest way is to start here: >>>>>> http://torrent.ubuntu.com:6969/ >>>>>> >>>>>> Remember as always to report your bugs. The easiest way is in the >>>>>> commandline: `ubuntu-bug packagename` >>>>>> >>>>>> All the best, >>>>>> >>>>>> Valorie >>>>>> >>>>> Hi, >>>>> I have Kubuntu 16.04 LTS installed (that was installed from >>>>> scratch >>>>> on a >>>>> new system) and tried to upgrade using the instructions in your third >>>>> link >>>>> above. The problem I have is that neither Muon nor >>>>> Plasma-Discovery have >>>>> the >>>>> options specified in the screen shots to invoke the configuration >>>>> settings. >>>>> The only way I could find on my system to change the update >>>>> settings back >>>>> to >>>>> "normal" was to use the update setting options in Synaptic and to set >>>>> those >>>>> to "Any version". Having done this Plasma-Discovery then prompted >>>>> to do >>>>> an >>>>> upgrade, but when I clicked on the upgrade button it did nothing. The >>>>> only >>>>> way I could find to actually upgrade was to issue a 'sudo >>>>> do-release-upgrade' from a shell, which then proceeded to >>>>> undertake the >>>>> upgrade (before switching to "Any Version" in Synaptic this command >>>>> returned >>>>> the message that there were No Releases Available). >>>> That should work, yes. >>>> >>>>> Having done the upgrade the system quite happily booted to the >>>>> Lightdm >>>>> display manager, but was then not able to start Unity, Plasma or >>>>> Gnome. >>>>> Gnome and Unity both produced a garbled graphic display and >>>>> immediately >>>>> dropped back to Lightdm. Plasma produced 'Internal System Error' >>>>> messages >>>>> and when I clicked on 'Details' it said that it was >>>>> /user/bin/Kwin_X11 >>>>> that >>>>> was failing, and, if I click on 'Ignore all future messages of this >>>>> type', >>>>> used ctrl+alt+delete to drop back to Lightdm, and restarted Plasma it >>>>> produced the same failure message, but this time is was in >>>>> /usr/bin/compiz. >>>>> I'm probably not surprised that Compiz had issues as I thought it >>>>> required >>>>> an accelerated video driver, and, from the display I was getting it >>>>> looked >>>>> like the Nvidia proprietary driver I had installed in 16.04 had been >>>>> removed >>>>> by the upgrade and it could not be reinstalled as it appeared that >>>>> the >>>>> repositories did not have the necessary component to allow a >>>>> reinstall. >>>>> How do I now downgrade to 16.04, or do I need to wipe the >>>>> root, boot >>>>> and >>>>> home partitions and re-install 16.04 from scratch, or can I >>>>> download a >>>>> 16.10 >>>>> ISO that I can burn to DVD and do a fresh/clean install from that? >>>>> >>>>> regards, >>>>> Steve >>>> Hi Steve, >>>> >>>> First, downgrade isn't supported. >>>> >>>> We haven't used Lightdm for a long time, perhaps two years? We've used >>>> SDDM since then, and that should support booting into both Unity and >>>> GNOME desktops, as well as the Plasma session. >>>> >>>> So my advice is: first try removing lightdm and installing sddm, if it >>>> is not installed. From the commandline, you can always check to see >>>> what you have installed with the command apt-cache. Like: `apt-cache >>>> policy lightdm` or `apt-cache policy sddm`. Notice that sudo is not >>>> used with this command, since it only looks up what you have >>>> installed. >>>> >>>> Then I would do `sudo apt remove lightdm && sudo apt install sddm`. If >>>> you find that sddm is already installed, instead do: `sudo apt remove >>>> lightdm && sudo dpkg-reconfigure sddm` >>>> >>>> The reason you want to chain those commands together with "&&" is so >>>> that they work sequentially, and you aren't left with no manager at >>>> all. >>>> >>>> When you run into problems, the most useful command is `sudo apt >>>> install -f`. The -f flag stands for fix, and that's what apt will >>>> attempt to do. If you have misconfiguration problems, `sudo >>>> dpkg-reconfigure -a` will try to reconfigure all, and then you can >>>> again try install -f. >>> Thanks Valorie, I'll try the fix commands and see what happens. I would >>> prefer not to use SDDM because in Ubuntu and the other distribution >>> I use I >>> have found that it doesn't work properly and I've always used >>> LightDM for >>> years, ever since Ubuntu standardised on that in preference to KDM >>> and GDM. >> It did work well in the few years we used it, yes. >> >>> In my view the KDE foundation should never have replaced KDM with >>> SDDM as, >>> in my view, SDDM does not compete, KDM is a significantly better >>> product. >> The KDE e.V. has no say in software choice, or programming decisions. >> What happened is that KDM stopped being developed. LightDM is owned by >> Canonical, rather than being entirely Free Software. KDE devels were >> not willing to sign the required documents to be allowed to work on >> LightDM, which left SDDM as the only alternative. >> >>> If the fixes don't rectify the issue (some of my problems could that >>> there >>> were file conflicts in a number of packages being upgrade in the >>> process, >>> for example, I think one of the issues was with Plasma-Amity which >>> wanted to >>> install Amity along with it but there was a file conflict between >>> the two, >>> so I think Plasma-Amity didn't get installed because Amity was always >>> installed first) I could always erase the partitions and reinstall >>> 16.04 LTS >>> from scratch and attempt the upgrade again after installing synaptic >>> so that >>> I can change the update options, because the version of >>> Plasma-Discovery in >>> 16.04 LTS (and the version of Plasma-Discovery in the other >>> distribution i >>> use) does not provide the dialog boxes shown in your screenshots. >>> The only >>> product I could find that provided the tabbed dialog (with the >>> Update tab) >>> was Synaptic, but its version setting was different. >> I have no clue what Plasma-Amity is, but I'm glad you found a way to >> do what you want. > Thanks Valorie. I had to reinstall Ubuntu 16.04 as 'sudo apt install > -f' did nothing, and, 'sudo dpkg-reconfigure' did not support the '-a' > parameter and without the parameter did nothing. > Having reinstalled 16.04, which only installed Unity, I upgraded to > 16.10, which seemed to upgrade fine with Unity still working. I then > proceeded to install Gnome using the gnome package which the > description said was the full Gnome (doing this was the starting point > to get my system back, after getting Gnome installed as set up I will > then install Plasma). > The subsequent boot of Gnome is showing that I may not have all the > necessary packages installed. When I start the Gnome desktop, the Top > Bar has an Activities Menu entry instead of the Applications entry I > am expecting. Clicking on the Activities Menu entry brings up the same > screen as pressing 'Left-super', where from the side bar on the left > of the display I can click on an applicatons button to bring up a > 'list' of the applications installed, but this 'list' is all > applications not a categorized list like the Applications Menu or the > Plasma/KDE Launcher does. Am I missing some packages or is this the > way Gnome is meant to function in Ubuntu? > Once I get the Gnome issues sorted out I'll then install Plasma via > the Plasma package as a starting point to getting Plasma back. I'll > query the multiple entries for Plasma in the Display Manager Options > at a later date if the reinstall puts both back again. Just one question relative to Gnome if you are able to answer it. Having installed the gnome package I now have entries in the Display Manager menu on the login screen of Gnome, Gnome Classic, Gnome Flashback (Compiz) and Gnome Flashback (Metacity) all which seem to boot into Gnome now. Originally Gnome Flashback (Compiz) crashed on first start. If I boot into any of the last 4 Gnome entries, they all have menu entries of Applications and Places in the title bar at the top of the screen, but if I boot with the Gnome entry the title bar at the top of the screen has the entry Activities, why is this (under Fedora 24 the Gnome system has Applications in the title bar at the top of the screen)? Having appearing to have Gnome working I have also installed the Plasma package which appears to have installed a working version of Plasma (hence I'm not sure why the upgrade from 16.04 to 16.10 destroyed my system) and that install has only placed one Plasma entry in the DM login screen selections. I'll have to monitor what packages I subsequently install introduces the additional entry. One gripe I have with Plasma in 16.10 is that the icons on the bottom of the KDE Launcher, and the icons on the options displayed when selecting Leave, are all wireframe icons which I don't like. These icons are the main reason I am looking at moving away from KDE under Fedora, as I could not find any way of changing them by changing the system theme or icon theme. Is there no way to get back the nice coloured icons that were there in 16.04? regards, Steve > > regards, > Steve > >> >>> regards, >>> Steve >>> >>>> It is certainly possible to download the 16.10 ISO and reinstall, but >>>> you will lose your unity and gnome sessions. >>>> https://kubuntu.org/alternative-downloads/ >>>> >>>> As for the nvidia driver: others will have to answer. >>>> >>>> Valorie > >