From fluca1978 at infinito.it Wed Oct 1 07:01:10 2014 From: fluca1978 at infinito.it (Luca Ferrari) Date: Wed, 1 Oct 2014 09:01:10 +0200 Subject: cannot update from 13.10 to 14.04 In-Reply-To: <5584844.8UF5gaIvXp@rachael> References: <1412070335.842.2.camel@yahoo.com> <5584844.8UF5gaIvXp@rachael> Message-ID: On Tue, Sep 30, 2014 at 8:51 PM, Mark Fraser wrote: > One last suggestion, are you using a proxy? I've had times when using squid- > deb-proxy that I have been unable to upgrade to a newer version. I'm behind a proxy that I cannot manage. This can be the problem after all. Luca From fluca1978 at infinito.it Wed Oct 1 10:00:54 2014 From: fluca1978 at infinito.it (Luca Ferrari) Date: Wed, 1 Oct 2014 12:00:54 +0200 Subject: cannot update from 13.10 to 14.04 In-Reply-To: References: <1412070335.842.2.camel@yahoo.com> <5584844.8UF5gaIvXp@rachael> Message-ID: In the end using the -d option seems to work: % sudo do-release-upgrade -d and a new release is found. I don't understand why the -d switch is required. Luca From girardhenri at free.fr Wed Oct 1 18:16:52 2014 From: girardhenri at free.fr (GH) Date: Wed, 01 Oct 2014 20:16:52 +0200 Subject: cannot update from 13.10 to 14.04 In-Reply-To: References: <1412070335.842.2.camel@yahoo.com> <5584844.8UF5gaIvXp@rachael> Message-ID: <542C4514.4000908@free.fr> Means develop Le 01/10/2014 12:00, Luca Ferrari a écrit : > In the end using the -d option seems to work: > % sudo do-release-upgrade -d > > and a new release is found. I don't understand why the -d switch is required. > > Luca > From kbun at xpresso.seaslug.org Thu Oct 2 07:41:54 2014 From: kbun at xpresso.seaslug.org (Bill Vance) Date: Thu, 2 Oct 2014 00:41:54 -0700 (PDT) Subject: apt-get wonder..... In-Reply-To: <542B3B98.3060402@linux.com> References: <5426E691.6010306@linux.com> <542998F9.8050300@linux.com> <542B3B98.3060402@linux.com> Message-ID: On Tue, 30 Sep 2014, Scott DuBois wrote: > On 09/30/2014 02:53 AM, Bill Vance wrote: >> >> Been there, done all that, worked in the past, but not anymore. >> >> I've even spent most of yesterday and today, seeing if I could >> get something working by way of building mplayer from source. >> Amazing how you can forget something like going way above and >> beyond fighting the battle of searching for, and building the >> seventh dependency of the seventh dependency of the seventh >> dependency..... >> >> It didn't work either. >> >> Bill >> >> > > You're trying with more than just one DVD too right? > > "Just in case"? Weider things have happened to me. =| > > ...and what version of Kubuntu are you on for reference so I can help > you dig around (time permitting)? > > Multimedia used to be kind of a PITA 3 or 4 years ago but I haven't had > any issues in the last couple years (not even with BluRay) so I feel for > your frustrations. I finally decided to bite the bullet, made some essential backups, and re-installed the OS, (12.04). Smplayer works, but only if I dissable dvd menuing, which is odd, as I've never before had a problem with it. Vlc still likes to do it's vanishing act. K3b is still a pain, as I have two working dvd drives, (one inherited from a now defunct machine), and could, if k3b allowed me to, copy directly from one drive to the other. Bill From kbun at xpresso.seaslug.org Thu Oct 2 07:47:49 2014 From: kbun at xpresso.seaslug.org (Bill Vance) Date: Thu, 2 Oct 2014 00:47:49 -0700 (PDT) Subject: cannot update from 13.10 to 14.04 In-Reply-To: References: <5743341.tMW9GboNCC@lark-latitude-d630> <1412070034.842.1.camel@yahoo.com> <1412070335.842.2.camel@yahoo.com> Message-ID: What kind of motherboard are you using? AMD owners have been seeing a number of problems upgrading/installing 14.04, some of them, (like mine), pretty nasty ones. Bill On Tue, 30 Sep 2014, Luca Ferrari wrote: > On Tue, Sep 30, 2014 at 11:45 AM, Ralf Mardorf wrote: >>>> Yes, I've tried doing it directly from root as well as via sudo, and >>>> nothing changed. ^^^^^^^^^ >> perhaps I just misunderstood this >> > > Ok, to make it clear I ran do-release-upgrade with the SAME results: > - as normal user > - via sudo > - into a root shell > > Luca > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > From girardhenri at free.fr Thu Oct 2 08:56:49 2014 From: girardhenri at free.fr (GH) Date: Thu, 02 Oct 2014 10:56:49 +0200 Subject: cannot update from 13.10 to 14.04 In-Reply-To: References: <5743341.tMW9GboNCC@lark-latitude-d630> <1412070034.842.1.camel@yahoo.com> <1412070335.842.2.camel@yahoo.com> Message-ID: <542D1351.4050007@free.fr> I have an AMD x8 with nvidia works fine (now I upgraded to 14.10) Le 02/10/2014 09:47, Bill Vance a écrit : > > What kind of motherboard are you using? AMD owners have been seeing > a number of problems upgrading/installing 14.04, some of them, (like > mine), pretty nasty ones. > > Bill > > > On Tue, 30 Sep 2014, Luca Ferrari wrote: > >> On Tue, Sep 30, 2014 at 11:45 AM, Ralf Mardorf >> wrote: >>>>> Yes, I've tried doing it directly from root as well as via sudo, and >>>>> nothing changed. ^^^^^^^^^ >>> perhaps I just misunderstood this >>> >> >> Ok, to make it clear I ran do-release-upgrade with the SAME results: >> - as normal user >> - via sudo >> - into a root shell >> >> Luca >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users >> > From o.sinclair at gmail.com Fri Oct 3 03:39:06 2014 From: o.sinclair at gmail.com (O. Sinclair) Date: Fri, 03 Oct 2014 05:39:06 +0200 Subject: KDE 4.14.1?? In-Reply-To: <5429005E.5050702@gmail.com> References: <5429005E.5050702@gmail.com> Message-ID: <542E1A5A.3080301@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/09/2014 08:46, O. Sinclair wrote: > Dear devs/packagers, > > I know you are hard at work with 14.10 and KDE5 - but given the > rather serious bug with Courier IMAP in 4.14.0 I was expecting > 4.14.1 to be packaged for those releases that now have 4.14 > > Any chance we might see this soon? > Just a note that it was released for Trusty 14.04 yesterday via the Kubuntu backports ppa. regards Sinclair -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQuGloACgkQdVb2AWQj/7YL6gCfebEke9vzCKwhq6FC3/S/GQP6 mNEAnRZLhLsqSOrrCxtnBuOsjigQ9V0r =Il/W -----END PGP SIGNATURE----- From basroufs at gmail.com Fri Oct 3 09:36:18 2014 From: basroufs at gmail.com (Bas Roufs) Date: Fri, 3 Oct 2014 11:36:18 +0200 Subject: Kubuntu 14.04: no access any more to Skype from Telepathy? Message-ID: Hello Everybody, until and including Kubuntu 13.10, I managed to access Skype via Telepathy, via the intermediary package 'pidgin-skype'. Also here in Kubuntu 14.04, I have installed the 3 packages managed above. When trying to access Skype from Telepathy, I need now to manually fill in my 'Skype path', which was not necessary in previous Kubuntu versions. The path is my case /home/bas/Skype/basroufs/. As far as I can see, this path must be correct - however I still do not get access from Telepathy after giving it in. Also when skipping the final slash - '~/basroufs' instead of '~/basroufs/' , I do not have success. They only way I manage to Skype now is using the stand-alone Skype package for Linux which is still in the repository. Do I overlook anything? Thanks for your feedback. Respectfully Yours, Bas G. Roufs, in Vienna. -- Bas G. Roufs Utrecht, NL, E. BasRoufs at gmail.com; Mob. +31 6 446 835 10; -------------- next part -------------- An HTML attachment was scrubbed... URL: From o.sinclair at gmail.com Fri Oct 3 10:39:24 2014 From: o.sinclair at gmail.com (O. Sinclair) Date: Fri, 03 Oct 2014 12:39:24 +0200 Subject: Kubuntu 14.04: no access any more to Skype from Telepathy? In-Reply-To: References: Message-ID: <542E7CDC.7090707@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/10/2014 11:36, Bas Roufs wrote: > Hello Everybody, until and including Kubuntu 13.10, I managed to > access Skype via Telepathy, via the intermediary package > 'pidgin-skype'. > > Also here in Kubuntu 14.04, I have installed the 3 packages > managed above. When trying to access Skype from Telepathy, I need > now to manually fill in my 'Skype path', which was not necessary in > previous Kubuntu versions. The path is my case > /home/bas/Skype/basroufs/. As far as I can see, this path must be > correct - however I still do not get access from Telepathy after > giving it in. Also when skipping the final slash - '~/basroufs' > instead of '~/basroufs/' , I do not have success. They only way I > manage to Skype now is using the stand-alone Skype package for > Linux which is still in the repository. Do I overlook anything? > > Thanks for your feedback. Respectfully Yours, > > Bas G. Roufs, in Vienna. I got 2 options after installing the packages: skype-dbus skype-X11 I opted for skype-dbus. After giving my skype path as /home/sinclair/.Skype/myskypeid it works as expected. did you by mistake leave out the dot in .Skype ?? Sinclair -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQufNwACgkQdVb2AWQj/7aBTwCfRaeLTP8Q+N9fHHty5Y09Pt5l vRkAniQByE9ih2GNKaZlC8Fr3YNKRqga =v11b -----END PGP SIGNATURE----- From kbun at xpresso.seaslug.org Fri Oct 3 10:50:36 2014 From: kbun at xpresso.seaslug.org (Bill Vance) Date: Fri, 3 Oct 2014 03:50:36 -0700 (PDT) Subject: cannot update from 13.10 to 14.04 In-Reply-To: <542D1351.4050007@free.fr> References: <5743341.tMW9GboNCC@lark-latitude-d630> <1412070034.842.1.camel@yahoo.com> <1412070335.842.2.camel@yahoo.com> <542D1351.4050007@free.fr> Message-ID: Mine is an AMD Sempron 2800+, and 14.04 wouldn't boot after upgrading with apt-get, Muon updater, or installing from DVD. 14.04.01, Using whichever method, locks the machine into an unacceptable screen resolution, requiring an electron microscope just to read the text. On top of that, nothing, (that I've tried), in system settings works. Phonon doesn't work, it wont give me the number of desktops I want, and trying to adjust the screen resolution just results in a blank screen, rendering all that upgrade/install work useless. The install disk software locks me into the same above mentioned useless screen resolution, so the process sucks from start to finish. My luck, it'll be about 50 years before they get 14.04 whipped into useful shape. :-/ Bill On Thu, 2 Oct 2014, GH wrote: > I have an AMD x8 with nvidia works fine (now I upgraded to 14.10) > Le 02/10/2014 09:47, Bill Vance a écrit : >> >> What kind of motherboard are you using? AMD owners have been seeing >> a number of problems upgrading/installing 14.04, some of them, (like >> mine), pretty nasty ones. >> >> Bill >> >> >> On Tue, 30 Sep 2014, Luca Ferrari wrote: >> >>> On Tue, Sep 30, 2014 at 11:45 AM, Ralf Mardorf >>> wrote: >>>>>> Yes, I've tried doing it directly from root as well as via sudo, >>>>>> and >>>>>> nothing changed. ^^^^^^^^^ >>>> perhaps I just misunderstood >>>> this >>>> >>> >>> Ok, to make it clear I ran do-release-upgrade with the SAME results: >>> - as normal user >>> - via sudo >>> - into a root shell >>> >>> Luca >>> >>> -- >>> 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 wajdlee at gmail.com Sat Oct 4 14:54:10 2014 From: wajdlee at gmail.com (Wajdlee Harfouch) Date: Sat, 4 Oct 2014 17:54:10 +0300 Subject: email Message-ID: wajdlee at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sandcastlebob at gmail.com Sun Oct 5 11:33:28 2014 From: sandcastlebob at gmail.com (Bob Scott) Date: Sun, 5 Oct 2014 07:33:28 -0400 Subject: not getting the right response to vulnerability test Message-ID: I used "env x='() { :;}; echo vulnerable' bash -c 'echo hello'", discovered I was vulnerable then performed upgrade. The subsequent test results in the response "hello" without the bash statements: bash: warning: x: ignoring function definition attempt bash: error importing function definition for `x' Does the absence of "vulnerable" mean the updating was successful? I am using Kubuntu 14.04 Thanks, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbun at xpresso.seaslug.org Mon Oct 6 18:10:59 2014 From: kbun at xpresso.seaslug.org (Bill Vance) Date: Mon, 6 Oct 2014 11:10:59 -0700 (PDT) Subject: dwww question Message-ID: Well, it was working, but now is not. I type in, "dwww progname", and instead of a bunch of info options, I get: Forbidden You don't have permission to access /cgi-bin/dwww/ on this server. Apache/2.2.22 (Ubuntu) Server at xpresso.com Port 80 Don't you just hate it when you're locked out of your own machine? I've done a, "locate cgi-bin|less", and tried changing the perms on each one, but no luck. Anybody know what's going on here? Bill From kassube at gmx.net Mon Oct 6 18:54:50 2014 From: kassube at gmx.net (Nils Kassube) Date: Mon, 06 Oct 2014 20:54:50 +0200 Subject: not getting the right response to vulnerability test In-Reply-To: References: Message-ID: <4912065.OcPVqr1yu1@p5915> Bob Scott wrote: > I used "env x='() { :;}; echo vulnerable' bash -c 'echo hello'", > discovered I was vulnerable then performed upgrade. The subsequent > test results in the response "hello" without the bash statements: > > bash: warning: x: ignoring function definition attempt > bash: error importing function definition for `x' > > Does the absence of "vulnerable" mean the updating was successful? It seems that nobody who knows the details has an answer - and I don't claim to really _know_ the answer. But the original problem of the shellshock vulnerability was that bash would allow to define a function as part of the call parameters which could be executed later to be used for exploits. The update for this original vulnerability resulted in an error message if such a function was defined, like you expected. And it also printed the text "hello". However there were other vulnerabilities found later which resulted in another update. Obviously that later update simultaneously removed the error message for the test you posted. Again, the original shellshock vulnerability would allow a function definition by call parameters. Your test would execute that function and print the message "vulnerable". Now after the second update the message is "hello" which means that bash is not vulnerable. IMHO it doesn't matter that there is no error message. It is only important that the exploit code would not be executed. So I would say that your bash version is not vulnerable for the shellshock problem. And BTW I don't see the error message either on those machines which have the second update installed. Nils From Christo.Larsen at bytes.co.za Mon Oct 6 21:26:37 2014 From: Christo.Larsen at bytes.co.za (Christo Larsen) Date: Mon, 6 Oct 2014 21:26:37 +0000 Subject: not getting the right response to vulnerability test In-Reply-To: <4912065.OcPVqr1yu1@p5915> References: <4912065.OcPVqr1yu1@p5915> Message-ID: <5433094C.2060000@bytes.co.za> Hi Just as info. Also update my systems, and I just get the "this is a test" message. No other errors. Regards Christo ________________________________ From: Nils Kassube Sent: Monday, October 06, 2014 8:54PM To: Kubuntu-users Subject: Re: not getting the right response to vulnerability test Bob Scott wrote: I used "env x='() { :;}; echo vulnerable' bash -c 'echo hello'", discovered I was vulnerable then performed upgrade. The subsequent test results in the response "hello" without the bash statements: bash: warning: x: ignoring function definition attempt bash: error importing function definition for `x' Does the absence of "vulnerable" mean the updating was successful? It seems that nobody who knows the details has an answer - and I don't claim to really _know_ the answer. But the original problem of the shellshock vulnerability was that bash would allow to define a function as part of the call parameters which could be executed later to be used for exploits. The update for this original vulnerability resulted in an error message if such a function was defined, like you expected. And it also printed the text "hello". However there were other vulnerabilities found later which resulted in another update. Obviously that later update simultaneously removed the error message for the test you posted. Again, the original shellshock vulnerability would allow a function definition by call parameters. Your test would execute that function and print the message "vulnerable". Now after the second update the message is "hello" which means that bash is not vulnerable. IMHO it doesn't matter that there is no error message. It is only important that the exploit code would not be executed. So I would say that your bash version is not vulnerable for the shellshock problem. And BTW I don't see the error message either on those machines which have the second update installed. Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdubois at linux.com Fri Oct 10 01:40:22 2014 From: sdubois at linux.com (Scott DuBois) Date: Thu, 09 Oct 2014 18:40:22 -0700 Subject: dwww question In-Reply-To: References: Message-ID: <54373906.3010509@linux.com> On 10/06/2014 11:10 AM, Bill Vance wrote: > > Well, it was working, but now is not. I type in, "dwww progname", > and instead of a bunch of info options, I get: > > > Forbidden > > You don't have permission to access /cgi-bin/dwww/ on > this server. Apache/2.2.22 (Ubuntu) Server at xpresso.com > Port 80 > > Don't you just hate it when you're locked out of your > own machine? I've done a, "locate cgi-bin|less", and > tried changing the perms on each one, but no luck. > > Anybody know what's going on here? > > Bill > Try this link: https://www.digitalocean.com/community/tutorials/how-to-configure-the-apache-web-server-on-an-ubuntu-or-debian-vps When I was playing around with this a few months back I had to tweak this file for anything to work. Also check with the server guide. https://help.ubuntu.com/12.04/serverguide/serverguide.pdf -- Scott DuBois President EBLUG BSIT Software Engineering Freenode: Roguehorse From kbun at xpresso.seaslug.org Fri Oct 10 08:22:28 2014 From: kbun at xpresso.seaslug.org (Bill Vance) Date: Fri, 10 Oct 2014 01:22:28 -0700 (PDT) Subject: dwww question In-Reply-To: <54373906.3010509@linux.com> References: <54373906.3010509@linux.com> Message-ID: On Thu, 9 Oct 2014, Scott DuBois wrote: > On 10/06/2014 11:10 AM, Bill Vance wrote: >> >> Well, it was working, but now is not. I type in, "dwww progname", >> and instead of a bunch of info options, I get: >> >> >> 403 Forbidden >> >> You don't have permission to access /cgi-bin/dwww/ on >> this server. Apache/2.2.22 (Ubuntu) Server at xpresso.com >> Port 80 >> >> Don't you just hate it when you're locked out of your >> own machine? I've done a, "locate cgi-bin|less", and >> tried changing the perms on each one, but no luck. >> >> Anybody know what's going on here? >> >> Bill >> > > Try this link: > https://www.digitalocean.com/community/tutorials/how-to-configure-the-apache-web-server-on-an-ubuntu-or-debian-vps > > When I was playing around with this a few months back I had to tweak > this file for anything to work. Also check with the server guide. > > https://help.ubuntu.com/12.04/serverguide/serverguide.pdf Thanks Scott. Been pouring over the abv refs for the last couple hours, and still haven't solved it. Time to go crash and burn. One weird thing though; The error.log file says I'm missing a whole bunch of files. /var/www/admin /var/www/favicon.ico /var/www/phpMyAdmin /var/www/phpmyadmin /var/www/pma /var/www/wp-login.php /var/www/blog /var/www/wordpress /var/www/wp /usr/lib/cgi-bin/php /var/www/tmUnblock.cgi /var/www/zc /var/www/etc /var/www/currentsetting.htm /var/www/manager /var/www/webdav Baring a couple of these, I have no idea whats being looked for. Bill From sboyce at blueyonder.co.uk Sun Oct 12 14:54:44 2014 From: sboyce at blueyonder.co.uk (Sid Boyce) Date: Sun, 12 Oct 2014 15:54:44 +0100 Subject: kubuntu login fails Message-ID: <543A9634.6080709@blueyonder.co.uk> None of the suggested fixes in bug 1304805 work. I even tried root at sdrbox:~# ln -s /usr/lib/x86_64-linux-gnu/qt4/bin /usr/lib/i386-linux-gnu/qt4/ root at sdrbox:~# l /usr/lib/i386-linux-gnu/qt4 total 4 lrwxrwxrwx 1 root root 33 Oct 12 15:47 bin -> /usr/lib/x86_64-linux-gnu/qt4/bin drwxr-xr-x 3 root root 4096 Oct 5 02:03 plugins This is a big puzzle. I am fully updated on 14.04 and none of the workarounds fixes the problem. My post 2014-10-05 is the last entry in bug 1304805. root at sdrbox:~# ls -l /usr/lib/i386-linux-gnu/qt4/bin/qdbus ls: cannot access /usr/lib/i386-linux-gnu/qt4/bin/qdbus: No such file or directory root at sdrbox:~# ls -l /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus -rwxr-xr-x 1 root root 64920 Mar 12 2014 /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus root at sdrbox:~# root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 root at sdrbox:~# There is no /usr/lib/i386-linux-gnu/qt4/bin directory ii qdbus 4:4.8.5+git192-g085f851+dfsg-2ubunt amd64 Qt 4 D-Bus tool root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 ii libqtcore4:i386 4:4.8.5+git192-g085f851+dfsg-2ubunt i386 Qt 4 core module Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -------------- next part -------------- An HTML attachment was scrubbed... URL: From sboyce at blueyonder.co.uk Sun Oct 12 15:04:01 2014 From: sboyce at blueyonder.co.uk (Sid Boyce) Date: Sun, 12 Oct 2014 16:04:01 +0100 Subject: kubuntu login fails In-Reply-To: <543A9634.6080709@blueyonder.co.uk> References: <543A9634.6080709@blueyonder.co.uk> Message-ID: <543A9861.1090004@blueyonder.co.uk> Just selected "KDE Plasma Workspace" at the login prompt and that fixed it. Regards Sid. On 12/10/14 15:54, Sid Boyce wrote: > None of the suggested fixes in bug 1304805 work. > I even tried > root at sdrbox:~# ln -s /usr/lib/x86_64-linux-gnu/qt4/bin > /usr/lib/i386-linux-gnu/qt4/ > root at sdrbox:~# l /usr/lib/i386-linux-gnu/qt4 > total 4 > lrwxrwxrwx 1 root root 33 Oct 12 15:47 bin -> > /usr/lib/x86_64-linux-gnu/qt4/bin > drwxr-xr-x 3 root root 4096 Oct 5 02:03 plugins > > This is a big puzzle. I am fully updated on 14.04 and none of the > workarounds fixes the problem. > My post 2014-10-05 is the last entry in bug 1304805. > > root at sdrbox:~# ls -l /usr/lib/i386-linux-gnu/qt4/bin/qdbus > ls: cannot access /usr/lib/i386-linux-gnu/qt4/bin/qdbus: No such file > or directory > root at sdrbox:~# ls -l /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus > -rwxr-xr-x 1 root root 64920 Mar 12 2014 > /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus > root at sdrbox:~# > > root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 > libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 > root at sdrbox:~# > > There is no /usr/lib/i386-linux-gnu/qt4/bin directory > > ii qdbus 4:4.8.5+git192-g085f851+dfsg-2ubunt amd64 Qt 4 D-Bus tool > > root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 > libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 > > ii libqtcore4:i386 4:4.8.5+git192-g085f851+dfsg-2ubunt i386 Qt 4 core > module > > Regards > Sid. > -- > Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot > Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support > Senior Staff Specialist, Cricket Coach > Microsoft Windows Free Zone - Linux used for all Computing Tasks -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukovszkil at gmail.com Mon Oct 13 19:08:30 2014 From: lukovszkil at gmail.com (=?UTF-8?B?TMOhc3psw7MgTHVrb3Zzemtp?=) Date: Tue, 14 Oct 2014 08:08:30 +1300 Subject: Logout issue - Re: kubuntu-users Digest, Vol 117, Issue 7 Message-ID: I have not been able to log out but from shell. Solution was to remove gnome packages I was trying out. On 14/10/2014 1:00 am, wrote: > Send kubuntu-users mailing list submissions to > kubuntu-users at lists.ubuntu.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > or, via email, send a message with subject or body 'help' to > kubuntu-users-request at lists.ubuntu.com > > You can reach the person managing the list at > kubuntu-users-owner at lists.ubuntu.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of kubuntu-users digest..." > > > Today's Topics: > > 1. kubuntu login fails (Sid Boyce) > 2. Re: kubuntu login fails (Sid Boyce) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 12 Oct 2014 15:54:44 +0100 > From: Sid Boyce > To: kubuntu-users at lists.ubuntu.com > Subject: kubuntu login fails > Message-ID: <543A9634.6080709 at blueyonder.co.uk> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > None of the suggested fixes in bug 1304805 work. > I even tried > root at sdrbox:~# ln -s /usr/lib/x86_64-linux-gnu/qt4/bin > /usr/lib/i386-linux-gnu/qt4/ > root at sdrbox:~# l /usr/lib/i386-linux-gnu/qt4 > total 4 > lrwxrwxrwx 1 root root 33 Oct 12 15:47 bin -> > /usr/lib/x86_64-linux-gnu/qt4/bin > drwxr-xr-x 3 root root 4096 Oct 5 02:03 plugins > > This is a big puzzle. I am fully updated on 14.04 and none of the > workarounds fixes the problem. > My post 2014-10-05 is the last entry in bug 1304805. > > root at sdrbox:~# ls -l /usr/lib/i386-linux-gnu/qt4/bin/qdbus > ls: cannot access /usr/lib/i386-linux-gnu/qt4/bin/qdbus: No such file or > directory > root at sdrbox:~# ls -l /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus > -rwxr-xr-x 1 root root 64920 Mar 12 2014 > /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus > root at sdrbox:~# > > root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 > libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 > root at sdrbox:~# > > There is no /usr/lib/i386-linux-gnu/qt4/bin directory > > ii qdbus 4:4.8.5+git192-g085f851+dfsg-2ubunt amd64 Qt 4 D-Bus tool > > root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 > libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 > > ii libqtcore4:i386 4:4.8.5+git192-g085f851+dfsg-2ubunt i386 Qt 4 core > module > > Regards > Sid. > > -- > Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot > Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support > Senior Staff Specialist, Cricket Coach > Microsoft Windows Free Zone - Linux used for all Computing Tasks > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.ubuntu.com/archives/kubuntu-users/attachments/20141012/236e14b1/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Sun, 12 Oct 2014 16:04:01 +0100 > From: Sid Boyce > To: kubuntu user technical support > Subject: Re: kubuntu login fails > Message-ID: <543A9861.1090004 at blueyonder.co.uk> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Just selected "KDE Plasma Workspace" at the login prompt and that fixed it. > Regards > Sid. > > On 12/10/14 15:54, Sid Boyce wrote: > > None of the suggested fixes in bug 1304805 work. > > I even tried > > root at sdrbox:~# ln -s /usr/lib/x86_64-linux-gnu/qt4/bin > > /usr/lib/i386-linux-gnu/qt4/ > > root at sdrbox:~# l /usr/lib/i386-linux-gnu/qt4 > > total 4 > > lrwxrwxrwx 1 root root 33 Oct 12 15:47 bin -> > > /usr/lib/x86_64-linux-gnu/qt4/bin > > drwxr-xr-x 3 root root 4096 Oct 5 02:03 plugins > > > > This is a big puzzle. I am fully updated on 14.04 and none of the > > workarounds fixes the problem. > > My post 2014-10-05 is the last entry in bug 1304805. > > > > root at sdrbox:~# ls -l /usr/lib/i386-linux-gnu/qt4/bin/qdbus > > ls: cannot access /usr/lib/i386-linux-gnu/qt4/bin/qdbus: No such file > > or directory > > root at sdrbox:~# ls -l /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus > > -rwxr-xr-x 1 root root 64920 Mar 12 2014 > > /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus > > root at sdrbox:~# > > > > root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 > > libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 > > root at sdrbox:~# > > > > There is no /usr/lib/i386-linux-gnu/qt4/bin directory > > > > ii qdbus 4:4.8.5+git192-g085f851+dfsg-2ubunt amd64 Qt 4 D-Bus tool > > > > root at sdrbox:~# dpkg -S /usr/lib/i386-linux-gnu/qt4 > > libqtcore4:i386: /usr/lib/i386-linux-gnu/qt4 > > > > ii libqtcore4:i386 4:4.8.5+git192-g085f851+dfsg-2ubunt i386 Qt 4 core > > module > > > > Regards > > Sid. > > -- > > Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot > > Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support > > Senior Staff Specialist, Cricket Coach > > Microsoft Windows Free Zone - Linux used for all Computing Tasks > > > -- > Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot > Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support > Senior Staff Specialist, Cricket Coach > Microsoft Windows Free Zone - Linux used for all Computing Tasks > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.ubuntu.com/archives/kubuntu-users/attachments/20141012/206a9089/attachment-0001.html > > > > ------------------------------ > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > > End of kubuntu-users Digest, Vol 117, Issue 7 > ********************************************* > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kapeka at bering-uclibc.de Thu Oct 16 15:21:03 2014 From: kapeka at bering-uclibc.de (KP.Kirchdoerfer) Date: Thu, 16 Oct 2014 17:21:03 +0200 Subject: kmail: filtering does not work with 4.14.2 Message-ID: <4737393.rOdFQ9YnKA@stalker> Hi all; as the subject says: After updating to kde 4.14.2 kmail filters refuse to work. Any hints tia kp From o.sinclair at gmail.com Thu Oct 16 19:46:20 2014 From: o.sinclair at gmail.com (O. Sinclair) Date: Thu, 16 Oct 2014 21:46:20 +0200 Subject: kmail: filtering does not work with 4.14.2 In-Reply-To: <4737393.rOdFQ9YnKA@stalker> References: <4737393.rOdFQ9YnKA@stalker> Message-ID: <5440208C.8040806@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 16/10/2014 17:21, KP.Kirchdoerfer wrote: > Hi all; > > as the subject says: > > After updating to kde 4.14.2 kmail filters refuse to work. > > Any hints > > tia kp > Hi, I use KDE 4.14.2 on 14.04 and for me Kmail filters work just fine. Not much help but hints to it being a local problem in your setup? Kind regards, Sinclair -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRAIIsACgkQdVb2AWQj/7ZCMACff/uH1xFuLPaHDE7B9YSFPA3f WqgAoOdT8Y50op18lTUeNuqqnpXBKuoo =kgY3 -----END PGP SIGNATURE----- From reb at barmannsbar.com Fri Oct 24 15:22:05 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Fri, 24 Oct 2014 11:22:05 -0400 Subject: How to change Screen Size in Ver, 14.10 Message-ID: <544A6E9D.9020106@barmannsbar.com> I have installed the new release of 14.010 and now my screen size is smaller than it was. I thought I could change that in System Settings but it does not change it. Thanks for any help. From mrmazda at earthlink.net Fri Oct 24 16:09:31 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Fri, 24 Oct 2014 12:09:31 -0400 Subject: How to change Screen Size in Ver, 14.10 In-Reply-To: <544A6E9D.9020106@barmannsbar.com> References: <544A6E9D.9020106@barmannsbar.com> Message-ID: <544A79BB.40301@earthlink.net> Richard Barmann composed on 2014-10-24 11:22 (UTC-0400): > I have installed the new release of 14.010 and now my screen size is > smaller than it was. I thought I could change that in System Settings > but it does not change it. Please describe "smaller than it was". Does it mean fewer but larger objects fit on the screen? Does it mean some of your display is displaying only black? Please upload /var/log/Xorg.0.log to http://paste.ubuntu.com/ or other web space and provide a URL so people can evaluate what's happening on your system. Please share output from terminal: 'lspci | grep VGA'. I'm guessing you have Intel video, as it's very common. 14.10 if I'm reading right is using xserver-xorg-video-intel-2.99.914, which could be as broken as the latest release version, 2.99.916. If this is correct, you may need a manual X server configuration workaround, via /etc/X11/xorg.conf, that at a minimum includes as follows: Section "Device" Identifier "Default Device" Option "AccelMethod" "UXA" EndSection -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From phil_lor at bigpond.com Fri Oct 24 22:46:34 2014 From: phil_lor at bigpond.com (Phil) Date: Sat, 25 Oct 2014 08:46:34 +1000 Subject: Muon Update Manager Message-ID: <544AD6CA.6030303@bigpond.com> Thank you for reading this. I have Muon Update Manager's "Release upgrade" set to Normal Releases" yet I'm not notified of the new release. Xubuntu's updater (not on the same laptop) is similar to Muon Update Manager and it did show that 14.10 was available. I suspect that I have a conflicting configuration somewhere. Is there a way of forcing the upgrade or at least forcing the notification? -- Regards, Phil From kde.lists at yahoo.com Fri Oct 24 23:03:00 2014 From: kde.lists at yahoo.com (Ralf Mardorf) Date: Sat, 25 Oct 2014 01:03:00 +0200 Subject: Muon Update Manager In-Reply-To: <544AD6CA.6030303@bigpond.com> References: <544AD6CA.6030303@bigpond.com> Message-ID: <1414191780.1876.42.camel@yahoo.com> On Sat, 2014-10-25 at 08:46 +1000, Phil wrote: > Thank you for reading this. > > I have Muon Update Manager's "Release upgrade" set to Normal Releases" > yet I'm not notified of the new release. Xubuntu's updater (not on the > same laptop) is similar to Muon Update Manager and it did show that > 14.10 was available. > > I suspect that I have a conflicting configuration somewhere. Is there a > way of forcing the upgrade or at least forcing the notification? "Forcing" a relase upgrade could be done by command line: https://help.ubuntu.com/lts/serverguide/installing-upgrading.html Notification about what kind of upgrade ever are a silly custom. That makes people upgrade without at least reading the news of their distro's homepage, let alone that they never ever will read release notes. A notification "hello, here are upgrades" is insane, a self-responsible user is aware about needed upgrades and about things that need attention when doing an upgrade. Just upgrading, while there is a notification easily could end up disastrous. *buntu made a big step into the wrong direction with this Windows/iOS like approach. JFTR the Ubuntu Studio team compared release upgrades with installing a new release and *buntu rlease upgrades tend to cause issues, you better stay with your release or do a plain new install. From clay at claydoh.com Fri Oct 24 23:52:33 2014 From: clay at claydoh.com (Clay Weber) Date: Fri, 24 Oct 2014 19:52:33 -0400 Subject: Muon Update Manager In-Reply-To: <1414191780.1876.42.camel@yahoo.com> References: <544AD6CA.6030303@bigpond.com> <1414191780.1876.42.camel@yahoo.com> Message-ID: <3195394.FDaVITKlDn@lark-latitude-d630> On Saturday, October 25, 2014 01:03:00 AM Ralf Mardorf wrote: > On Sat, 2014-10-25 at 08:46 +1000, Phil wrote: > > Thank you for reading this. > > > > I have Muon Update Manager's "Release upgrade" set to Normal Releases" > > yet I'm not notified of the new release. Xubuntu's updater (not on the > > same laptop) is similar to Muon Update Manager and it did show that > > 14.10 was available. > > > > I suspect that I have a conflicting configuration somewhere. Is there a > > way of forcing the upgrade or at least forcing the notification? > > "Forcing" a relase upgrade could be done by command line: > https://help.ubuntu.com/lts/serverguide/installing-upgrading.html > > Notification about what kind of upgrade ever are a silly custom. That > makes people upgrade without at least reading the news of their distro's > homepage, let alone that they never ever will read release notes. A > notification "hello, here are upgrades" is insane, a self-responsible > user is aware about needed upgrades and about things that need attention > when doing an upgrade. Just upgrading, while there is a notification > easily could end up disastrous. *buntu made a big step into the wrong > direction with this Windows/iOS like approach. > Meh. I guess we should do everything your way :) Some people like, appreciate, and want such things. I do. It can be turned off if one does not want them to happen. > JFTR the Ubuntu Studio team compared release upgrades with installing a > new release and *buntu rlease upgrades tend to cause issues, you better > stay with your release or do a plain new install. I am not noticing any significant upgrade issues, based on the overall low level of reports of them in irc and in kubuntuforums. I am sure many have not upgraded yet, so that may change as the weekend comes around and more folks do the deed. Anecdotally, my 2 upgrades were 100 percent flawless. My PC is on its third upgrade in a row without flaw. *My* suggestion is to do what you want. -- Clay Weber (claydoh) http://kubuntuforums.net http://claydoh.com From reb at barmannsbar.com Sat Oct 25 01:02:26 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Fri, 24 Oct 2014 21:02:26 -0400 Subject: No subject In-Reply-To: <544AF1E7.7070304@barmannsbar.com> References: <544AF1E7.7070304@barmannsbar.com> Message-ID: <544AF6A2.1080004@barmannsbar.com> On 10/24/2014 08:42 PM, Richard Barmann wrote: > Correction: I am using version 14.10. I have 2" of black on the left > and right of my screen. The top and bottom seem to be correct. > I have pasted the contents of the Xorg.0.log to http://paste.ubuntu.com/ lspci | grep VGA Gives me this 01:00.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) I have a 22" monitor and before I upgraded the screen was completely covered . I thought I could adjust that in settings/monitor but it will not work. Thank you for any help. I am a novice and appreciate the help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrmazda at earthlink.net Sat Oct 25 01:16:39 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Fri, 24 Oct 2014 21:16:39 -0400 Subject: How to change Screen Size in Ver, 14.10 In-Reply-To: <544AF6A2.1080004@barmannsbar.com> References: <544AF1E7.7070304@barmannsbar.com> <544AF6A2.1080004@barmannsbar.com> Message-ID: <544AF9F7.5000404@earthlink.net> Richard Barmann composed on 2014-10-24 21:02 (UTC-0400): > I have pasted the contents of the Xorg.0.log to > http://paste.ubuntu.com/ That URL doesn't have your paste. Please try again. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From reb at barmannsbar.com Sat Oct 25 01:42:15 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Fri, 24 Oct 2014 21:42:15 -0400 Subject: Screen Size/Richard Barmann Message-ID: <544AFFF7.4030004@barmannsbar.com> The URL http://paste.ubuntu.com/8663860/ From phil_lor at bigpond.com Sat Oct 25 02:23:41 2014 From: phil_lor at bigpond.com (Phil) Date: Sat, 25 Oct 2014 12:23:41 +1000 Subject: Muon Update Manager In-Reply-To: <1414191780.1876.42.camel@yahoo.com> References: <544AD6CA.6030303@bigpond.com> <1414191780.1876.42.camel@yahoo.com> Message-ID: <544B09AD.2080102@bigpond.com> On 25/10/14 09:03, Ralf Mardorf wrote: > On Sat, 2014-10-25 at 08:46 +1000, Phil wrote: >> Thank you for reading this. >> >> I have Muon Update Manager's "Release upgrade" set to Normal Releases" >> yet I'm not notified of the new release. Xubuntu's updater (not on the >> same laptop) is similar to Muon Update Manager and it did show that >> 14.10 was available. >> >> I suspect that I have a conflicting configuration somewhere. Is there a >> way of forcing the upgrade or at least forcing the notification? > > "Forcing" a relase upgrade could be done by command line: > https://help.ubuntu.com/lts/serverguide/installing-upgrading.html > Thank you Ralf and Clay for your replies. I'd forgotten about "do-release-upgrade". Anyway, it worked - took around about 4 hours. No problems so far and several improvements. -- Regards, Phil From mrmazda at earthlink.net Sat Oct 25 02:24:04 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Fri, 24 Oct 2014 22:24:04 -0400 Subject: How to change Screen Size in Ver, 14.10 In-Reply-To: <544AFFF7.4030004@barmannsbar.com> References: <544AFFF7.4030004@barmannsbar.com> Message-ID: <544B09C4.2070703@earthlink.net> Richard Barmann composed on 2014-10-24 21:42 (UTC-0400): > The URL http://paste.ubuntu.com/8663860/ Look in that file and you see many instances of VESA That means your system is using the VESA driver, a generic driver that doesn't understand widescreen modes, which results in the black bars. In most cases VESA is a fallback used because the driver specific to the gfxchip is not available or the gfxchip is not supported by the available driver. Instead of VESA what GeForce users want to see is either NOUVEAU or NVIDIA. NVIDIA is a proprietary driver, usually the better performer, and required for gfxchips to new to have support in the NOUVEAU driver. To install the proprietary driver, the easier route to try, one would normally follow the instructions on: http://www.howtoinstall.co/en/ubuntu/utopic/restricted/nvidia-331/ Before trying, you need to find out whether support for your chip in that driver is included. Periodically, support for older chips gets dropped. To troubleshoot getting the open source NOUVEAU driver to work, start here: https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection http://tinyurl.com/k6l4dn3 may help you find if there is a more specific solution for your NV44A found by users of releases prior to 14.10. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From mrmazda at earthlink.net Sat Oct 25 02:31:05 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Fri, 24 Oct 2014 22:31:05 -0400 Subject: How to change Screen Size in Ver, 14.10 In-Reply-To: <544AFFF7.4030004@barmannsbar.com> References: <544AFFF7.4030004@barmannsbar.com> Message-ID: <544B0B69.4070700@earthlink.net> Richard Barmann composed on 2014-10-24 21:42 (UTC-0400): > The URL http://paste.ubuntu.com/8663860/ Another clue: (EE) [drm] KMS not enabled KMS needs to be enabled for either Nouveau or Nvidia drivers to be used, so one, maybe primary, focus in your search should be why KMS is reported to not be enabled. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From mattjcliffe at gmail.com Sat Oct 25 10:40:45 2014 From: mattjcliffe at gmail.com (mattjcliffe at gmail.com) Date: Sat, 25 Oct 2014 10:40:45 +0000 Subject: =?utf-8?Q?Re:_Screen_Size/Richard_Barmann?= In-Reply-To: <544AFFF7.4030004@barmannsbar.com> References: <544AFFF7.4030004@barmannsbar.com> Message-ID: <544b7e9a.c166b40a.037d.ffffa5f2@mx.google.com> I’ve had that problem before with ati cards, when using the proprietary drivers. To fix the ati problem I adjusted the underscan / overscan setting ; aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0 would fix it is there a comparable setting in the NVidia driver? Matt From: Richard Barmann Sent: ‎Saturday‎, ‎25‎ ‎October‎ ‎2014 ‎02‎:‎42 To: kubuntu-users at lists.ubuntu.com The URL http://paste.ubuntu.com/8663860/ -- 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 mrmazda at earthlink.net Sat Oct 25 15:59:38 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 11:59:38 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <544b7e9a.c166b40a.037d.ffffa5f2@mx.google.com> References: <544AFFF7.4030004@barmannsbar.com> <544b7e9a.c166b40a.037d.ffffa5f2@mx.google.com> Message-ID: <544BC8EA.20703@earthlink.net> mattjcliffe at gmail.com composed on 2014-10-25 10:40 (UTC): > I’ve had that problem before with ati cards, when using the proprietary > drivers. To fix the ati problem I adjusted the underscan / overscan > setting ; Overscan isn't OP's problem of 2" of black on both sides. His Xorg.0.log tells he's using the VESA driver, which does not support his 22" BTC LE2262 display's native/preferred 1680x1050 mode. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From reb at barmannsbar.com Sat Oct 25 19:12:46 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 15:12:46 -0400 Subject: Screen Size/Richard Barmann Message-ID: <544BF62E.6090507@barmannsbar.com> I installed the the driver that you suggested with no difference. The screen seems to be closing to the Status bar and I have to reopen it as I work or type. Also I had a small window constantly open in the middle of the page and I would have to hit enter to remove it. That window would be a miniature of the Firefox page I have open. I do not understand about "KMS" not being enabled. From reb at barmannsbar.com Sat Oct 25 19:17:26 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 15:17:26 -0400 Subject: Screen Size/Richard Barmann Message-ID: <544BF746.6020604@barmannsbar.com> This all started when I did the upgrade from Ver 14.04 to 14.10 in Kubuntu if that is any help. From mrmazda at earthlink.net Sat Oct 25 19:32:05 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 15:32:05 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <544BF62E.6090507@barmannsbar.com> References: <544BF62E.6090507@barmannsbar.com> Message-ID: <544BFAB5.6040208@earthlink.net> Richard Barmann composed on 2014-10-25 15:12 (UTC-0400): > I installed the the driver that you suggested with no difference. The Upload /var/log/Xorg.0.log again. It changes each time you boot or restart the X server, and will necessarily be different if a different video driver gets used. That log has clues to tell what problems are occurring. When your display works right, most or all lines containing (EE) will no longer appear in it. The (EE) lines are the main clues. > screen seems to be closing to the Status bar and I have to reopen it as > I work or type. Also I had a small window constantly open in the middle > of the page and I would have to hit enter to remove it. That window > would be a miniature of the Firefox page I have open. What you find on the desktop would better be left to deal with after the X configuration is correct for your display's native 1680x1050, after the black bars are gone. > I do not understand about "KMS" not being enabled. KMS means kernel mode setting. KMS is a function introduced several years ago. It is required to be disabled for some drivers (e.g. Nvidia), and enabled for others (e.g. Nouveau). With most kernels since it was introduced, it is enabled automatically unless the system is booted with nomodeset or equivalent on the kernel cmdline. It can be added on the fly from the boot menu if needed and not present. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From reb at barmannsbar.com Sat Oct 25 19:49:57 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 15:49:57 -0400 Subject: Screen Size/Richard Barmann Message-ID: <544BFEE5.50407@barmannsbar.com> I have uploaded the file in paste.ubuntu.com From mrmazda at earthlink.net Sat Oct 25 19:58:40 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 15:58:40 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <544BFEE5.50407@barmannsbar.com> References: <544BFEE5.50407@barmannsbar.com> Message-ID: <544C00F0.6040004@earthlink.net> Richard Barmann composed on 2014-10-25 15:49 (UTC-0400): > I have uploaded the file in paste.ubuntu.com What is the URL to find it? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From reb at barmannsbar.com Sat Oct 25 20:15:03 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 16:15:03 -0400 Subject: Fwd: Screen Size/Richard Barmann In-Reply-To: <544BF746.6020604@barmannsbar.com> References: <544BF746.6020604@barmannsbar.com> Message-ID: <544C04C7.7000508@barmannsbar.com> The URL Is http://paste.ubuntu.com/8676499/ Sorry about that. I am 82 and trying to stay up with this. I appreciate the help you are giving me. From kassube at gmx.net Sat Oct 25 20:36:38 2014 From: kassube at gmx.net (Nils Kassube) Date: Sat, 25 Oct 2014 22:36:38 +0200 Subject: Screen Size/Richard Barmann In-Reply-To: <544BFAB5.6040208@earthlink.net> References: <544BF62E.6090507@barmannsbar.com> <544BFAB5.6040208@earthlink.net> Message-ID: <1484061.DBIDOQqIm2@p5915> Felix Miata wrote: > KMS means kernel mode setting. KMS is a function introduced several > years ago. It is required to be disabled for some drivers (e.g. > Nvidia), I can't believe that - I haven't disabled KMS and the nvidia driver works without problems on my machine. Maybe it depends on the individual nvidia card? Nils From mrmazda at earthlink.net Sat Oct 25 20:38:14 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 16:38:14 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <544C04C7.7000508@barmannsbar.com> References: <544BF746.6020604@barmannsbar.com> <544C04C7.7000508@barmannsbar.com> Message-ID: <544C0A36.6080701@earthlink.net> Richard Barmann composed on 2014-10-25 16:15 (UTC-0400): > The URL Is http://paste.ubuntu.com/8676499/ That says the Nvidia driver was found, and yet the VESA driver is still being used. > Sorry about that. I am 82 and trying to stay up with this. I appreciate > the help you are giving me. You may have installed the wrong Nvidia package. Which did you install? The log seems to say you have 311 but need 304. Is it possible your installation is incomplete? According to https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia you need to do 'sudo nvidia-xconfig' in a terminal and then restart. It might be useful for troubleshooting to eliminate the following from the kernel cmdline in Grub: splash quiet You should pastebin also /etc/X11/xorg.conf and the latest Xorg.0.log on your next reply here. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From reb at barmannsbar.com Sat Oct 25 20:38:44 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 16:38:44 -0400 Subject: Screen Size/Richard Barmann Message-ID: <544C0A54.1000407@barmannsbar.com> It still shows a lot of VESA in the file. Line 251 shows VEAS with a 1680 x 1050 Size. From mrmazda at earthlink.net Sat Oct 25 20:44:30 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 16:44:30 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <1484061.DBIDOQqIm2@p5915> References: <544BF62E.6090507@barmannsbar.com> <544BFAB5.6040208@earthlink.net> <1484061.DBIDOQqIm2@p5915> Message-ID: <544C0BAE.9020400@earthlink.net> Nils Kassube composed on 2014-10-25 2:36 (UTC+0200): > Felix Miata wrote: >> KMS means kernel mode setting. KMS is a function introduced several >> years ago. It is required to be disabled for some drivers (e.g. >> Nvidia), > I can't believe that - I haven't disabled KMS and the nvidia driver > works without problems on my machine. Maybe it depends on the individual > nvidia card? The need to disable KMS may have become obsolete, or depend on chip as you suggest, but it has been a requirement in the past. ISTR kernel devs mentioning something about automatic disabling whenever a gfxchip lacking a KMS driver was found. Last machine I installed Nvidia on was not mine, so I don't have it here to check. I only use FOSS drivers here, and last I checked have needed to disable KMS via nomodeset only for MGA and SIS drivers. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From mrmazda at earthlink.net Sat Oct 25 20:56:20 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 16:56:20 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <544C0A54.1000407@barmannsbar.com> References: <544C0A54.1000407@barmannsbar.com> Message-ID: <544C0E74.4090100@earthlink.net> Richard Barmann composed on 2014-10-25 16:38 (UTC-0400): > It still shows a lot of VESA in the file. Line 251 shows VEAS with a > 1680 x 1050 Size. Line with "Modeline" tell what your display supports, not what the video BIOS supports. Last I checked, there were no video BIOS supporting 1680x1050. That's why you need a Nouveau or Nvidia driver instead of VESA. If it still has VESA(0): Setting up VESA Mode 0x11B (1280x1024) then you're not done yet. You need to see NVIDIA lines after the last VESA lines. Getting Nvidia to work is not normally specific to Kubuntu, so asking also in the ubuntu-users mailing list might get you better or faster help getting through this. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From reb at barmannsbar.com Sat Oct 25 21:29:28 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 17:29:28 -0400 Subject: Screen Size/Richard Barmann Message-ID: <544C1638.4050204@barmannsbar.com> URL is http://paste.ubuntu.com/8677674/ From reb at barmannsbar.com Sat Oct 25 21:38:21 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 17:38:21 -0400 Subject: Screen Size Richard Barmann Message-ID: <544C184D.80502@barmannsbar.com> http://paste.ubuntu.com/8677793/ Last URL From mrmazda at earthlink.net Sat Oct 25 21:40:37 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 17:40:37 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <544C1638.4050204@barmannsbar.com> References: <544C1638.4050204@barmannsbar.com> Message-ID: <544C18D5.7020302@earthlink.net> Richard Barmann composed on 2014-10-25 17:29 (UTC-0400): > URL is http://paste.ubuntu.com/8677674/ Still VESA is used. Still it reports you have Nvidia version 311 but need version 304. The following lines in xorg.conf do not match your display specifications: HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Try changing them with a text editor thus: HorizSync 30.0 - 82.0 VertRefresh 56.0 - 76.0 I don't expect it will help making Nvidia take over from VESA, but leaving it like it is could be a problem even with Nvidia in use. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From reb at barmannsbar.com Sat Oct 25 21:57:09 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 17:57:09 -0400 Subject: Screen Size/Richard Barmann Message-ID: <544C1CB5.3070707@barmannsbar.com> Now I have 1.5 Inches on each side and the Icons and type in the message is so large that It is hard to send this message. This took up 4 line From reb at barmannsbar.com Sat Oct 25 22:01:44 2014 From: reb at barmannsbar.com (Richard Barmann) Date: Sat, 25 Oct 2014 18:01:44 -0400 Subject: Screen Size Richard Barmann Message-ID: <544C1DC8.9040006@barmannsbar.com> In system settings/display monitor there is only one size shown. 640x420 I think. It is not clear. From mrmazda at earthlink.net Sat Oct 25 22:37:54 2014 From: mrmazda at earthlink.net (Felix Miata) Date: Sat, 25 Oct 2014 18:37:54 -0400 Subject: Screen Size/Richard Barmann In-Reply-To: <544C1CB5.3070707@barmannsbar.com> References: <544C1CB5.3070707@barmannsbar.com> Message-ID: <544C2642.9050802@earthlink.net> Richard Barmann composed on 2014-10-25 17:57 (UTC-0400): > Now I have 1.5 Inches on each side and the Icons and type in the message > is so large that It is hard to send this message. This took up 4 line Don't expect it to get better until you get it to stop using VESA. Did you try replacing the 311 driver with 304 yet? If you have done that and did not get 1680x1050 as a result, maybe it would be better to try uninstalling Nvidia and trying to get Nouveau to work. Here's what Xorg.0.log looks like on 14.10 here using Nouveau (and a moderately newer than your NV44A [GeForce 6200], G84 [GeForce 8600 GT] gfxchip): http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big41-buntu1410-1600x1200nouveauDVI Note that it contains no instances of the string "VESA(0)", and many of "NOUVEAU(0)". Something else to try if you can is to switch cable types. If now VGA, try DVI. If now DVI, try VGA. Try to borrow the other type if you don't have it, just to test. Even though in 14.04 it worked for you, regressions do sometimes happen with support for older hardware. Richard Barmann composed on 2014-10-25 18:01 (UTC-0400): > In system settings/display monitor there is only one size shown. 640x420 > I think. It is not clear. As long as VESA is in use, you cannot expect 1680x1050. After this finally is fixed, consider not "upgrading" next time a new version is released. Instead, create a multiboot installation, where you can keep using what works until you can get the bugs out of what's new, and have the old to fall back on easier than live media if something breaks. You can have more than two installations, using extras e.g. to participate in testing betas, and finding problems like this before they are unleashed via GA on the unsuspecting. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From phb at hbsys.plus.com Sun Oct 26 22:20:36 2014 From: phb at hbsys.plus.com (Peter Hillier-Brook) Date: Sun, 26 Oct 2014 22:20:36 +0000 Subject: Loss of bootable disk after dist-upgrade Message-ID: <544D73B4.6070706@hbsys.plus.com> Just a heads-up in case anyone else hits this problem. I upgraded my laptop from 14.04 to 14.10 today and ended up with "no bootable disc" at the restart. I suspect an EFI/secure boot issue that I'll diagnose and fix sometime soon, but I thought I ought to flag it up in case any other upgraders are troubled by it. Fore warned is fore armed! Peter HB -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jimmckenzie at earthlink.net Mon Oct 27 05:44:20 2014 From: jimmckenzie at earthlink.net (James R McKenzie) Date: Mon, 27 Oct 2014 01:44:20 -0400 (GMT-04:00) Subject: Password required to mount External Drives, Thumb Drives & SD Chips after upgrading to Kubuntu 14.10 Message-ID: <16283350.1414388660811.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net> I just rebooted my system for the first time since doing a command line upgrade of Kubuntu 14.04 to Kubuntu 14.10 and when I tried to open one of the External Drives I was presented with a system needs authorization screen (basically it asked me to type in the administrative password in order to allow the drive(s) to mount) I played a hunch and discovered that I have to so this in order to open "ANY" external drive of any kind. Is there a setting I can change to do away with this and if so exactly where is it? I load my preferred wallpaper from an external drive (none of the provided images are of any interest at all, they are all too boring) and it can't load with this setting. I already went into the control center and set all external drives to auto-mount on start-up but that apparently didn't have the desired effect. Am I over-looking something? Any/All help will be appreciated. Thank You In Advance. From grokit at ajinfosearch.com Mon Oct 27 20:52:52 2014 From: grokit at ajinfosearch.com (Alan Dacey (grokit)) Date: Mon, 27 Oct 2014 16:52:52 -0400 Subject: Password required to mount External Drives, Thumb Drives & SD Chips after upgrading to Kubuntu 14.10 In-Reply-To: <16283350.1414388660811.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net> References: <16283350.1414388660811.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net> Message-ID: <3692286.EG9arr38I0@kirk> On Monday, October 27, 2014 1:44:20 AM James R McKenzie wrote: > I just rebooted my system for the first time since doing a command line upgrade of Kubuntu 14.04 to Kubuntu 14.10 and when I tried to open one of the External Drives I was presented with a system needs authorization screen (basically it asked me to type in the administrative password in order to allow the drive(s) to mount) I played a hunch and discovered that I have to so this in order to open "ANY" external drive of any kind. Is there a setting I can change to do away with this and if so exactly where is it? I load my preferred wallpaper from an external drive (none of the provided images are of any interest at all, they are all too boring) and it can't load with this setting. I already went into the control center and set all external drives to auto-mount on start-up but that apparently didn't have the desired effect. Am I over-looking something? Any/All help will be appreciated. > > Thank You In Advance. > What are the permissions on the folder(s) that the disks are auto-mounting to? Also what in your /etc/fstab file? If you are going to have a setup with auto-mounted disks on startup then that would be the preferred way to do it (in my opinion of course). -- Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From cody.smith9202 at gmail.com Mon Oct 27 20:59:46 2014 From: cody.smith9202 at gmail.com (Cody Smith) Date: Mon, 27 Oct 2014 13:59:46 -0700 Subject: Password required to mount External Drives, Thumb Drives & SD Chips after upgrading to Kubuntu 14.10 In-Reply-To: <3692286.EG9arr38I0@kirk> References: <16283350.1414388660811.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net> <3692286.EG9arr38I0@kirk> Message-ID: As was suggested, this looks like a permission issue. Have you tried "sudo chown -R : /path/to/drive" without quotes and replacing the two instances with your username and /path/to/drive with the path (under the / directory) to the drive? That'll put your user as the owner of the drive and its contents. On Monday, October 27, 2014, Alan Dacey (grokit) wrote: > On Monday, October 27, 2014 1:44:20 AM James R McKenzie wrote: > > > I just rebooted my system for the first time since doing a command line > upgrade of Kubuntu 14.04 to Kubuntu 14.10 and when I tried to open one of > the External Drives I was presented with a system needs authorization > screen (basically it asked me to type in the administrative password in > order to allow the drive(s) to mount) I played a hunch and discovered that > I have to so this in order to open "ANY" external drive of any kind. Is > there a setting I can change to do away with this and if so exactly where > is it? I load my preferred wallpaper from an external drive (none of the > provided images are of any interest at all, they are all too boring) and it > can't load with this setting. I already went into the control center and > set all external drives to auto-mount on start-up but that apparently > didn't have the desired effect. Am I over-looking something? Any/All help > will be appreciated. > > > > > > Thank You In Advance. > > > > > > > What are the permissions on the folder(s) that the disks are auto-mounting > to? > > > > Also what in your /etc/fstab file? If you are going to have a setup with > auto-mounted disks on startup then that would be the preferred way to do it > (in my opinion of course). > > > > -- > > Alan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From d.kuntadi at gmail.com Tue Oct 28 01:19:31 2014 From: d.kuntadi at gmail.com (David Kuntadi) Date: Tue, 28 Oct 2014 08:19:31 +0700 Subject: Password required to mount External Drives, Thumb Drives & SD Chips after upgrading to Kubuntu 14.10 In-Reply-To: References: <16283350.1414388660811.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net> <3692286.EG9arr38I0@kirk> Message-ID: On Tue, Oct 28, 2014 at 3:59 AM, Cody Smith wrote: > > As was suggested, this looks like a permission issue. It should not be permission issue. Please check: System Settings > Startup & Shutdown > Service Manager, is "Removable Device Automounter" enabled? DK From sdubois at linux.com Tue Oct 28 17:50:31 2014 From: sdubois at linux.com (Scott DuBois) Date: Tue, 28 Oct 2014 10:50:31 -0700 Subject: Password required to mount External Drives, Thumb Drives & SD Chips after upgrading to Kubuntu 14.10 In-Reply-To: <16283350.1414388660811.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net> References: <16283350.1414388660811.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net> Message-ID: <544FD767.8080303@linux.com> On 10/26/2014 10:44 PM, James R McKenzie wrote: > I just rebooted my system for the first time since doing a command line upgrade of Kubuntu 14.04 to Kubuntu 14.10 and when I tried to open one of the External Drives I was presented with a system needs authorization screen (basically it asked me to type in the administrative password in order to allow the drive(s) to mount) I played a hunch and discovered that I have to so this in order to open "ANY" external drive of any kind. Is there a setting I can change to do away with this and if so exactly where is it? I load my preferred wallpaper from an external drive (none of the provided images are of any interest at all, they are all too boring) and it can't load with this setting. I already went into the control center and set all external drives to auto-mount on start-up but that apparently didn't have the desired effect. Am I over-looking something? Any/All help will be appreciated. > > Thank You In Advance. > > > > Yeah, I have a similar situation whereas I have an external eSATA drive that I can simply find it in the left panel of Dolphin and click then it will mount but, if I'm only working in Konsole without performing the previous in Dolphin, I can't get to it. As I've recently installed a new internal drive, my suspicion is that one needs to follow the same procedure of creating a mount point based on the UUID and edit fstab to reflect: sudo blkid (find your device in the list) sudo vim /etc/fstab UUID= defaults 0 2 http://ubuntuforums.org/showthread.php?t=1432413 -- Scott DuBois BSIT President EBLUG Freenode: Roguehorse