Re: Howto?
On 1/26/20 2:25 AM, Gene Heskett wrote: I think that last statement needs a grin.;-) Any way I made a tarball, then xz'd it, saveing a nominal gigabyte to DL. I'd still like to make a deb out of it. I might see if I can do a dummy install and tar.xz that. When I'm awake again.:) Gene will this help? http://www.noah.org/wiki/DEB_package_notes_-_dpkg,_apt,_aptitude,_and_friends#Creating_DEB_packages -- Jimmy Johnson Slackware64 11.19.KDE5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: looking for a replacement for debian since systemd
On 12/15/19 11:45 PM, Jonas Smedegaard wrote: Quoting Jimmy Johnson (2019-12-16 02:13:08) On 12/14/19 5:29 AM, Jonas Smedegaard wrote: Hi Alessandro, Quoting Alessandro Vesely (2019-12-14 13:23:14) On Sat 14/Dec/2019 03:18:39 +0100 Kenneth Parker wrote: I use Devuan, especially on older hardware. Works well. Good to know. For the time being, I see SysV is working. I'm on old-stable Debian. As, in a few months, it will be time to migrate, I'll have to decide on Devuan (current) vs. Buster. Any recommendation on that? Will the voted resolution shred any light on migration strategies? Since this is a Debian list, I recommend to discuss Debian here, and consult Devuan mailinglist for details of what they can offer. The vote currently in Debian will affect _future_ releases of Debian, not the current stable release, Buster. For Debian Buster (regardless of the outcome of the vote) SysV is a supported init system: Please do report any flaws you may encounter! Kde5 on buster without systemd don't work, True, and also what I wrote (and even mentioned KDE explicitly): Depends on which kind of system you need and how much of systemd must be gone. In case you missed, here it is again: Beware in discussions here and elsewhere to distinguish between these: a) running a system with SysV as init system b) running a system without systemd installed c) running a system without libsystemd0 installed If you need a), then quite likely Debian Buster is fine for you. If you need b) and don't need a complex¹ X11/Wayland desktop environment, then Debian Buster is likely fine as well. If you need c) and/or a complex¹ X11/Wayland desktop environment, then Debian Buster is most likely no fun for you - might be possible, but you will feel alone and bugreports will be harder to debug due to your complex setup (in particular your suppressing package recommendations). ¹ In this context, "complex" desktop environments include GNOME, KDE, Cinnamon, MATE and more - as a rule of thumb anything which directly or indirectly recommends dbus-user-session. It's nice to see that you agree. blessings, -- Jimmy Johnson Slackware64 11.19.KDE5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: looking for a replacement for debian since systemd
On 12/14/19 5:29 AM, Jonas Smedegaard wrote: Hi Alessandro, Quoting Alessandro Vesely (2019-12-14 13:23:14) On Sat 14/Dec/2019 03:18:39 +0100 Kenneth Parker wrote: I use Devuan, especially on older hardware. Works well. Good to know. For the time being, I see SysV is working. I'm on old-stable Debian. As, in a few months, it will be time to migrate, I'll have to decide on Devuan (current) vs. Buster. Any recommendation on that? Will the voted resolution shred any light on migration strategies? Since this is a Debian list, I recommend to discuss Debian here, and consult Devuan mailinglist for details of what they can offer. The vote currently in Debian will affect _future_ releases of Debian, not the current stable release, Buster. For Debian Buster (regardless of the outcome of the vote) SysV is a supported init system: Please do report any flaws you may encounter! Kde5 on buster without systemd don't work, all kde5 is config for systemd, screen settings and pluseaudio will not save settings, to bad, so sad. Give it a try and see for yourself. -- Jimmy Johnson Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: looking for a replacement for debian since systemd
On 12/13/19 1:55 PM, Britton Kerin wrote: I see from below vote that we're working on dumping other init systems now as expected. Luckily I've given up on debian since systemd in the first place and am in long process of finding a replacement. Some options are slackware it comes with xfce and kde4, slackware live with kde5, another is mxlinux for xfce, it's real nice, probably the best xfce desktop I've seen if you like xfce and it's using debian, and another is pclinuxos it has xfce and kde5. I'm running pclos kde5, slackware 14.2, slackware current and slackware live kde5 and I'm still testing debian but I don't think it's linux anymore than windows10 is, just another mainstream backdoor. Already mentioned are bsd and devuan and devuan has some forks to look at too. -- Jimmy Johnson Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: Bootable USB Buster System
On 10/29/19 12:07 PM, Joe wrote: No, it doesn't do legacy. There is no 'legacy' on any BIOS screen. It's an Aspire ES1-132. But Stretch installed in EFI easily and even gave me a dual-boot with Win10, which didn't interest me at the time, but does now. I'm doing a bit of Access work for the first time in years. Sorry Joe, I retired in 2012 and don't do windows anymore and every time I wipe a new computers win10 I celebrate!
Re: Bootable USB Buster System
On 10/29/19 12:22 PM, Pascal Hambourg wrote: HP UEFI firmwares were among the most broken ones, ignoring EFI boot entries created for GRUB. I swear those new hp's are broken by design just like our main stream(cough) linux. But if you find the right system, using the right kernel you can get around it and I think you already know that.
Re: Bootable USB Buster System
On 10/29/19 9:23 AM, deloptes wrote: Jimmy Johnson wrote: My acer aspire one is not having a problem and another acer with 17 inch screen, hdmi and ddr3 is not having a problem, I can't get at the model right now. You may have to fiddle with your bios, on a samsung I have to go to bios at boot, to boot device where I find what I want is at the top of the list and hit f10 and it then boots what I want. I personally do not see a reason why I should mess up with the bios to switch back and fort to legacy and not legacy - the one HP I have does not support legacy too. Well if you don't tell the computer you want to use legacy then you will get uefi every time. On a new hp using ddr4 you're going to get uefi every time unless you use the bios boot menu no matter what you do. Also the file system you use matters, some file systems only use uefi and will give you no legacy support. Good luck.
Re: Bootable USB Buster System
On 10/29/19 1:56 AM, Joe wrote: On Tue, 29 Oct 2019 01:21:52 -0700 Jimmy Johnson wrote: On 10/27/19 10:38 AM, Peter Ehlert wrote: On 10/26/19 5:41 PM, songbird wrote: Peter Ehlert wrote: I have tried it, several times, but was unable to get Grub properly installed... not able to boot. I too would like such a tool hmm, i have a booting USB stick of stable (before recent release so i'm actually one stable back now :) ). no issues at all booting from it and i don't recall installing GRUB to it. i use UEFI booting most of the time via refind so i don't bios boot often, but it does work. I don't use UEFI, perhaps that is the difference. Keep doing a legacy install it's the best bet, most all computers will do a legacy boot from the bios boot menu, even the new computers built for windows 10. Not mine, Acer netbook about a year old. My acer aspire one is not having a problem and another acer with 17 inch screen, hdmi and ddr3 is not having a problem, I can't get at the model right now. You may have to fiddle with your bios, on a samsung I have to go to bios at boot, to boot device where I find what I want is at the top of the list and hit f10 and it then boots what I want. Good luck.
Re: Bootable USB Buster System
On 10/27/19 10:38 AM, Peter Ehlert wrote: On 10/26/19 5:41 PM, songbird wrote: Peter Ehlert wrote: I have tried it, several times, but was unable to get Grub properly installed... not able to boot. I too would like such a tool hmm, i have a booting USB stick of stable (before recent release so i'm actually one stable back now :) ). no issues at all booting from it and i don't recall installing GRUB to it. i use UEFI booting most of the time via refind so i don't bios boot often, but it does work. I don't use UEFI, perhaps that is the difference. Keep doing a legacy install it's the best bet, most all computers will do a legacy boot from the bios boot menu, even the new computers built for windows 10. I've done this with many systems, having firmware and drivers installed is the only consideration I can think of and installing a usb wireless can help if needed when you get stuck. I have one that looks like a pin drive called 'proster' and seems to work on all kinds of computer systems. Good luck.
Re: Trapped in Gnome
On 9/11/19 8:41 AM, Thomas George wrote: At login after booting up there is a symbol like a gear below the password entry line. I moved the mouse and clicked on this symbol. Several options appeared and I decided to try Classic Gnome. This worked but the next time I booted up the mouse was frozen. The symbol to change desktops is there but there is no way to reach it, the mouse is stuck in the lower right side of the screen How can I escape? I don't like the version of Gnome I an stuck in If you got a new kernel or kernel upgrade, then that is where I would put the blame. I've seen the problem before, reverting back to the old kernel got it going again. -- Jimmy Johnson MX-19-XFCE-4.14 - AMD E2-6110 - EXT4 at sda11 Registered Linux User #380263
Re: Repair Grumb (grub)
On 7/12/19 3:08 AM, Stephen P. Molnar wrote: Plese see responses to questions. . . . . On 07/11/2019 11:16 PM, David wrote: On Fri, 12 Jul 2019 at 05:09, Stephen P. Molnar wrote: I have Stretch installed on sda1 and Buster installed on sdd1 on my 64bit Linux platform. Unfortunately, grub on sdd1 became corrupted and the boot process fails after Buster is selected. Everyone reading this wonders: 1) why are you hiding the most important facts in your question? 2) what exact symptoms cause you to conclude that "grub on sdd1 became corrupted"? After allowing choice of Buster the boot hung with a '>' prompt. AMD computers and complete buster update with wayland cause problems like x not starting or sometimes the user space will freeze with only background service running, input device's stop working. I don't know the fix. -- Jimmy Johnson Slackware 14.2 - KDE 4.14.32 - EXT4 at sda5 Registered Linux User #380263
Re: Giving remaja (teens) group full administrator privileges through sudo - dangerous?
On 06/19/2019 09:56 PM, Bagas Sanjaya wrote: That is almost as bad as having no security restrictions at all. The correct thing to do would be to set permissions on the programs to allow them to be run by group remaja. What I thought that the correct way is to configure sudoers so that remaja group can access programs that they absolutely required via sudo (e.g. mount for mounting USB sticks). I don't say this often. I would immediately fire the person responsible for instituting this policy on a "production" system. (It would be a good policy if the system is intended as an educational environment to allow the teens to ruin things, and learn from experience.) In fact, many television stations have most programs written for teens (age 13 and older), so sysadmins there configure sudoers which allows teens to behave like sysadmins themselves (by giving them full administrator privileges) on their production systems. Also, parental monitoring and guidance can reduce likehood of teens breaking such systems. Maybe because teens are largest marketshare for TVs. Some one mentioned mounting drives, all that and what they need can be configured. There is no reason to give /sudo/root/ to anyone but the admin, unless it's a class on system admin. What are you going to do about it? -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
On 05/28/2019 08:44 AM, Andy Smith wrote: Hello, On Mon, May 27, 2019 at 10:13:12AM -0700, Jimmy Johnson wrote: On 05/26/2019 11:03 PM, Andy Smith wrote: There doesn't seem to be any point in interacting further. Andy that's the most helpful thing you've said, I guess you missed the response where the very first thing I did was to actually show Gene how to disable IPv6, even though I predicted it wasn't his issue, and then he later agreed (in a response to another poster) that it wasn't his issue. You predicted it wasn't his issue, you knew that for sure, like you know what the issue is but your not saying. That's not a question, I'm being a sounding board. you are trolling Gene a longtime Debian Linux User who is having problems adjusting to not having Debian Linux any longer, like so many others who are longtime Debian Users, I'm having trouble making sense of what you're saying there, but what I am doing is taking issue with Gene's insistence that IPv6 is responsible for every problem he encounters. IPv6 just like systemd, kernel modules, programs with added code, etc. and I really can go on, but the point is the mere mention of somethings start arguments and trolling since day one. so please don't troll. Is your definition of trolling "asking someone to back up their statements"? Yes, often it is trolling, it's a deliberate act of discrediting a poster who may often be expressing his personal experience working with technology. If not then I'd be interested to know what it is that I'm doing that you think is trolling. Cheers, Andy So please don't troll. -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
On 05/27/2019 12:54 PM, Brian wrote: On Mon 27 May 2019 at 10:19:45 -0700, Jimmy Johnson wrote: On 05/27/2019 12:46 AM, Curt wrote: On 2019-05-27, wrote: If Network Manager is giving you grief, please go bark up /that/ tree (I can't say much about N-M, because I banned it from my boxes about ten years ago: I was at a customer's, in his LAN via an Ethernet, when N-M suddenly saw a WLAN out there, out the window and said "oh, let's go online over there" and obliterated my network setting in favor of some seedy captive portal. That was when I decided that N-M and me, we aren't made for each other). This is a grave bug. I suppose we can assume from your description that the seedier the wifi portal, the more likely it is to spontaneously occur, despite any and all user configuration or intervention. Would it be possible to post the link to your bug report? To your knowledge has the bug been fixed since you reported it a decade ago? As many users here including myself rely on the N-M app, I'm sure we would all be interested in knowing where we stand. Who needs NetworkManager and why? Curt's query was concise and to the point. You are obviously unable to respond to it in a manner which advances the discusion. Hence your pathetic attempt at topic divergence. Please try to read and respond sympathetically to the posts in -user. No, seriously I would like to get some user feedback to the question. And also why is net-tools being deprecated? -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
On 05/27/2019 01:51 AM, Jonas Smedegaard wrote: Quoting Curt (2019-05-27 09:46:00) On 2019-05-27, wrote: If Network Manager is giving you grief, please go bark up /that/ tree (I can't say much about N-M, because I banned it from my boxes about ten years ago: I was at a customer's, in his LAN via an Ethernet, when N-M suddenly saw a WLAN out there, out the window and said "oh, let's go online over there" and obliterated my network setting in favor of some seedy captive portal. That was when I decided that N-M and me, we aren't made for each other). This is a grave bug. I suppose we can assume from your description that the seedier the wifi portal, the more likely it is to spontaneously occur, despite any and all user configuration or intervention. Would it be possible to post the link to your bug report? To your knowledge has the bug been fixed since you reported it a decade ago? As many users here including myself rely on the N-M app, I'm sure we would all be interested in knowing where we stand. I fully agree, this is a quite scary and severe bug in network-manager that I want to inspect closer as Debian Developer. Please do share information about where it was reported to I can follow up on it. I sincerely hope that it has not gone unfixed through these many years!!! Who needs it and what for? Why is NetworkManager installed? -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
On 05/27/2019 12:46 AM, Curt wrote: On 2019-05-27, wrote: If Network Manager is giving you grief, please go bark up /that/ tree (I can't say much about N-M, because I banned it from my boxes about ten years ago: I was at a customer's, in his LAN via an Ethernet, when N-M suddenly saw a WLAN out there, out the window and said "oh, let's go online over there" and obliterated my network setting in favor of some seedy captive portal. That was when I decided that N-M and me, we aren't made for each other). This is a grave bug. I suppose we can assume from your description that the seedier the wifi portal, the more likely it is to spontaneously occur, despite any and all user configuration or intervention. Would it be possible to post the link to your bug report? To your knowledge has the bug been fixed since you reported it a decade ago? As many users here including myself rely on the N-M app, I'm sure we would all be interested in knowing where we stand. Who needs NetworkManager and why? Thanks, -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
On 05/26/2019 11:03 PM, Andy Smith wrote: There doesn't seem to be any point in interacting further. Andy Andy that's the most helpful thing you've said, you are trolling Gene a longtime Debian Linux User who is having problems adjusting to not having Debian Linux any longer, like so many others who are longtime Debian Users, so please don't troll. Thanks, -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: which mutt?
On 05/03/2019 10:56 AM, David Wright wrote: On Fri 03 May 2019 at 09:40:05 (-0700), Jimmy Johnson wrote: On 05/03/2019 04:43 AM, Francisco M Neto wrote: AFAIK in Stretch Mutt actually means Neomutt. There was a flamewar between the package maintainer and the Mutt guy a while ago about that. It wasn't pretty[1,2]. It's been blogged too. No reference. I think Neo is kind of in your face and it is about the hate Microsoft has for Open Source Linux. No evidence or reference. The idea of a embargo is a good idea. Embargo of what? Debian knows what I'm talking about. Why do you think it's a good idea? MS has taken their Billions and bought into Open Source and now there are more Microsoft Neo-Linux-Developers(That's what they call themselves) than any other single group of developers including google. And along with that comes a declaration of war. I came to Linux to get away from Microsoft where I was a partner, they are bad for my nerves and my high blood pressure. So I personally have found myself other sources until Debian comes around and is no longer playing with Microsoft. After more than 20 years with Debian as my main OS it was not easy, but I am still testing. Or is your post just a troll? David you know better than that and as a matter of fact your post is more Trolling than mine with your put up or shut up attitude. The truth is out there, you have to dig and sometimes read between the lines. This is my last post in this thread. Thanks, -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: which mutt?
On 05/03/2019 04:43 AM, Francisco M Neto wrote: AFAIK in Stretch Mutt actually means Neomutt. There was a flamewar between the package maintainer and the Mutt guy a while ago about that. It wasn't pretty[1,2]. It's been blogged too. I think Neo is kind of in your face and it is about the hate Microsoft has for Open Source Linux. The idea of a embargo is a good idea. In Buster, Mutt means Mutt, and Neomutt means Neomutt. I suppose if you want to use "Vanilla" Mutt in Stretch you need to get it some other way. [1] https://jmtd.net/log/mutt_year_zero [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870635 --Francisco -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: Cannot re-install synaptic on Buster.
On 04/15/2019 01:12 AM, Brad Rogers wrote: On Mon, 15 Apr 2019 17:32:47 +1000 Keith Bainbridge wrote: Hello Keith, I'm more intrigued that synaptic reportedly removed itself. How is this possible, or did some other package force its removal? Removal occurred because of otherwise unresolvable conflicts. In this case, with Wayland. OP apparently didn't notice Synaptic was to be removed, and proceeded with the upgrade. Apt-auto-remove could remove it, me, while upgrading would use synaptic to mark synaptic as not being auto-installed then it would become a local installed package and would not be removed. there's another package in buster repos called "upgrade-system" that needs to be fixed or removed, I use it because it runs deborphan after doing a full/dist-upgrade, I think it may now be dead, also deborphan and gtkorphan cause it uses gksu, I don't think users are allowed that kind of power any longer. I ran one package and it said I needed to be Wheel, so I installed kuser to add me as wheel, while trying to use kuser I got command not found. -- Jimmy Johnson 14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263
Re: Cannot re-install synaptic on Buster.
On 4/14/19 10:24 PM, Kieran Smyth wrote: Hi, For reasons unknown to me, synaptic uninstalled itself about three weeks ago. I am using Buster on the desktop, with MATE as my desktop environment. When i open up a terminal and try to re-install it, i get the following- # apt update Hit:1 http://ftp.us.debian.org/debian buster InRelease Hit:2 http://ftp.us.debian.org/debian buster-updates InRelease Hit:3 http://security.debian.org/debian-security buster/updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. # apt install synaptic Reading package lists... Done Building dependency tree Reading state information... Done Package synaptic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'synaptic' has no installation candidate /etc/apt/sources.list is the following- deb http://ftp.us.debian.org/debian/ buster main contrib non-free deb-src http://ftp.us.debian.org/debian/ buster main contrib non-free deb http://ftp.us.debian.org/debian/ buster-updates main contrib non-free deb-src http://ftp.us.debian.org/debian/ buster-updates main contrib non-free deb http://security.debian.org/debian-security/ buster/updates main contrib non-free deb-src http://security.debian.org/debian-security/ buster/updates main contrib non-free I like using a GUI frontend to apt, and if anyone can help me get it back on my system i'd really appreciate it. Thank you in advance for any help that may be provided. If I was you, I would remove the buster-updates sources, keeping main and security and add stretch main and security sources and install Synaptic. Works great for me. It seems only a few users and even less developers know the power of Synaptic, it's ability's are great and there is no replacement for Synaptic. -- Jimmy Johnson Current - KDE4 - AMD A8-7600 - EXT4 at sda11 Registered Linux User #380263
Re: A call to drop gnome
On 4/17/19 5:57 AM, songbird wrote: what? synaptic is a GUI interface to package installation and removal. why should this block anything? dpkg and apt do those tasks just fine in a terminal. i only used synaptic in the past to get a quick access to lists of files installed and locations which i now get another way. it certainly isn't a requirement... Synaptic is able to install different versions of packages, allowing a Disabled User who is not a keyboard jockey to test Debian release's and a lot more. But I no longer care because it hurts to care, Deb has been raped and will never be mentally or usably the same and Microsoft is happy, I'm glad someone is happy. -- Jimmy Johnson Current - KDE - AMD A8-7600 - EXT4 at sda11 Registered Linux User #380263
Re: Laptop still extremely slow after replacing msata ssd and putting old one back
hdv@gmail wrote: On 05/03/2019 04.28, Paul Ezvan wrote: Le 04/03/2019 à 13:32, deloptes a écrit : double check - I had similar observation when trying to setup USB stick boot for a notebook - it's a company property, so not supposed to do that ;-) Well turned out that I had to modify few bios settings to see the usb working at acceptable speed. First I was thinking the one stick was a problem, but after observing the same with a second one I looked at the bios and it did it. regards What does "top" show when your menu takes a long time to load? What is the CPU temp? Maybe you accidentaly touched the cooling system while replacing the SSD? What I forgot to mention (sloppy, sorry for that) is that the slowness already happens at "grub" time. I presume that rules out trouble with my DE (KDE/Plasma) or systemd or something like that. I am thinking hardware trouble too. Not only because the trouble start before the kernel and DE gets loaded, but also because it happens with two different SSDs. It happens with the new one with a freshly installed system, and with the old one that I never had any trouble with before this and that hasn't been changed (by me that is). In both cases the slowness begins immediately after boot. Possibly after the BIOS has run, but definitely before the kernel gets loaded or otherwise during the earliest stages of loading it. Thanks for the pointer to the cooling. I will check that. Grx HdV Is the bios still showing all the installed ram, are there any test you can run from the bios... -- Jimmy Johnson Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Mirror release file expired
Brian wrote: On Fri 09 Nov 2018 at 08:32:57 -0500, Boyan Penkov wrote: On apt-get update, I see: Reading package lists... Done E: Release file for http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired (invalid since 17h 5min 48s). Updates for this repository will not be applied. What's the best way to communicate this to the folks who manage that particular mirror -- the Columbia one? http://mirror.cc.columbia.edu/ has a contact address. I've seen mirrors expire for one reason or another. Is there anyway to find/get the hits on that address? Thanks. -- Jimmy Johnson Slackware64 Current - Linux 4.19.23 - KDE 4.14.38 - AMD A8-7600 - EXT4 at sda11 Registered Linux User #380263
Re: Swapping Drives - Sanity Check
On 2/22/19 5:54 PM, David Wright wrote: On Fri 22 Feb 2019 at 14:20:05 (-0500), Michael Stone wrote: On Fri, Feb 22, 2019 at 11:36:28AM -0500, Stephen P. Molnar wrote: Before disconnection the power to the drives, I edited out their lines in fstab. I disconnecting the power to sdb and sdc and started the computer. It booted for a few lines until it encountered the line starting with 'start job fgfor device disk by . . .' (at least that what i jotted down). then t\iot Then it through the three HD's, two of which had the power unplugged) for 1 minute and 30 seconds and then went on to tell me that I could log on as root or ctrl-D to continue. Ctrl-D didn't work so I logged oh as root It sounds like you didn't actually comment them out of fstab. Well, that should be easy to check: reconnect the drives and boot up the system "as normal". And while it's up, I would seriously look at those mount point names; I agree, they are awful. Create some nice new ones to use with your future disk(s). I know little to nothing about a raid, but otherwise I would boot with the new drive installed and run "blkid" then make appropriate changes to the "fstab". -- Jimmy Johnson Slackware64 Current - Linux 4.19.23 - KDE 4.14.38 - AMD A8-7600 - EXT4 at sda11 Registered Linux User #380263
Re: Need help making new boot vol
On 01/15/2019 02:56 PM, Dennis Wicks wrote: buster i386 The installer has a repair option, I've used it in the past and it works, it goes like you're doing a install before it gets to the repair part. Use the buster iso and make a boot-disc and then choose the repair option from the menu, I think it's in the advanced menu. -- Jimmy Johnson Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Gparted error report
On 01/01/2019 04:07 AM, Richard Owlett wrote: I am trying to modify the partitioning of a 240GB USB connected SSD. It was originally created on a laptop running Debian 9.1 which is in the shop for cooling problems. I attempted to repartition it on a laptop running Debian 8.6 and received an error message that the installed revision of e2fsck could not analyze the first partition. I then tried to perform the repartitioning on a machine I believe to be running Debian 9.1. I think the version in Jessie is doing check sums and the version in Stretch is not. If you are going to re-partition, then first delete your current partition. If that is not what you want to do, then disable checksums and reformat. To disable checksums on an existing filesystem, ensure that the filesystem will pass fsck. Then turn off metadata_csum via #tune2fs, e.g. tune2fs -O ^metadata_csum /dev/path/to/disk. One other thing is you will need to reformat the partition, but you still may have a problem, the partition maybe one byte off and will not boot your system, so while using gparted add or remove one byte to the partition and then format. You didn't say, but you can check and repair ext4 with #fsck.ext4 -pvcf /dev/sdXX but as above you need to first disable checksum. -- Jimmy Johnson Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: [OT?] home partition vs. home directory
On 11/30/2018 09:22 AM, Hans wrote: Am Freitag, 30. November 2018, 18:14:40 CET schrieb Default User: When you are using a seperate home-partition you can easily install the whole system new - and all user specific content will be saved and will not have to configured by the user(s) again. In case, you have no backup from the users.. Best Hans There is no need to have more than one partition for the reason you suggest. For 15 years or more there is no need to format before install, you only need to delete system files. You can save the files in users /home/user folder and do the install with no format, just use the same user name or change the user name to what you want before install. I do recommend deleting the users system files too before the install. I often see people recommend a separate home partition. But why would (or not) that be better than just a home directory within the root directory? Wouldn't one less partition be simpler, and therefore (all other things being equal) better? Opinions, please. I dislike top posting. -- Jimmy Johnson Debian Wheezy - KDE 4.8.4 - AMD A8-7600 - EXT4 at sda10 Registered Linux User #380263
Re: Reverting firefox-esr upgrade in Buster
On 11/07/2018 09:43 PM, local10 wrote: Hi, Is there a way to revert firefox-esr upgrade to version 60 in Buster and install back firefox v 52.9.0? Thanks Here: https://pkgs.org/download/firefox-esr -- Jimmy Johnson Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Burn Blu-Ray video on Linux
On 10/02/2018 09:02 PM, Bob McGowan wrote: Hi, I have a high def (4K) mp4 video I would like to put on a Blu-Ray disk, to play in a standard Blu-Ray player. So I did the Google search and found several posts, all of which mentioned an application tsMuxeR, which is available for Linux and is in the Debian repos. However, it is a 32 bit application, but hey, no problem, I have multi-arch configured, and I've been able to run some 32 bit apps without issues. Except this one. The ldd command (is it ok to use the 64 bit command on a 32 bit binary?) says the file is "not a dynamic executable", yet when I run it, it complains about libraries not being found (which probably answers the question about ldd): tsMuxeR: error while loading shared libraries: libstdc++.so.6: But: $ find /usr/lib* -name libstdc++\* /usr/lib/gcc/x86_64-linux-gnu/6/libstdc++fs.a /usr/lib/gcc/x86_64-linux-gnu/6/libstdc++.a /usr/lib/gcc/x86_64-linux-gnu/6/libstdc++.so /usr/lib/x86_64-linux-gnu/libstdc++.so.6 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.22 /usr/lib64/libstdc++.so.6.0.22 /usr/lib64/libstdc++.so.6 /usr/libx32/libstdc++.so.6.0.22 /usr/libx32/libstdc++.so.6 Only one directory in the above with 32 bit, so I tried adding it to LD_LIBRARY_PATH: $ LD_LIBRARY_PATH=/usr/libx32 tsMuxeR tsMuxeR: error while loading shared libraries: libstdc++.so.6: No joy. And there is no file matching libstdc++.so.6 in /lib* or /usr/local/lib, either Have I misconfigured something with multi-arch? Is there a bug I couldn't find a reference too? Any help or suggestions on other software to try? Thanks, Bob This package? https://packages.debian.org/sid/libstdc++6 -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD E2-6110 EXT4 at sda1 Registered Linux User #380263
Re: update problem
--# ## Debian Main Repos deb http://deb.debian.org/debian/ unstable main contrib non-free deb-src http://deb.debian.org/debian/ unstable main contrib non-free -- Jimmy Johnson Debian Wheezy - KDE 4.8.4 - AMD A8-7600 - EXT4 at sda10 Registered Linux User #380263
Re: recovering a partition table
On 09/07/2018 02:06 PM, Dominic Knight wrote: On Fri, 2018-09-07 at 13:02 -0700, Jimmy Johnson wrote: On 09/07/2018 12:19 PM, Eike Lantzsch wrote: On Friday, September 7, 2018 5:34:00 PM -04 Dominic Knight wrote: Whilst trying to create one partition out of two (using disks) I appear to have accidentally deleted the partition table of (almost) the whole drive. Then diverse methods for partition table recovery are open to you. All the best E.L. What the Doctor ordered: How to Recover a Disk Partition with TestDisk and GParted Live https://ubuverse.com/recover-a-disk-partition-with-testdisk-and-gparted-live/ It seems the problem was that it wasn't really deleted at all, just 'disks' (the software program) being a bit useless and saying it was. I had wondered what I had done to cause it as I was fairly certain I had double checked what I was doing. I had deleted one partition ready to expand another into it when 'disks' decided to play a trick on me. Slightly worrying when it tells you there is one big empty drive, and then gpart reporting this Warning: more than 4 primary partitions: 6. Partition(Linux swap or Solaris/x86): primary Partition(Linux ext2 filesystem): primary Partition(Linux ext2 filesystem): primary Partition(Linux ext2 filesystem): primary Partition(Linux ext2 filesystem): invalid primary Partition(Linux ext2 filesystem): invalid primary Ok. is a bug in that piece of software? There is actually one primary and one extended all are ext4. gparted reports all is good. Risked a reboot and everything is just fine. Thanks Dom. It looks like the logical partition has been removed, I don't think I've seen that before. And rebooting brought it back, lucky you. :) -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: recovering a partition table
On 09/07/2018 12:19 PM, Eike Lantzsch wrote: On Friday, September 7, 2018 5:34:00 PM -04 Dominic Knight wrote: Whilst trying to create one partition out of two (using disks) I appear to have accidentally deleted the partition table of (almost) the whole drive. It still has the swap partition and an unknown partition of zero size apparently with 2tb of freespace. It was 10gb swap, 1tb, 50 gb, and two at roughly 500gb each at the end. How do I recover the original partition table? testdisk and gparted come to mind. A Google search turns up many HOWTOs for Linux. Before you do anything else first of all make an image of the disk by means of clonezilla-live. Then diverse methods for partition table recovery are open to you. All the best E.L. What the Doctor ordered: How to Recover a Disk Partition with TestDisk and GParted Live https://ubuverse.com/recover-a-disk-partition-with-testdisk-and-gparted-live/ -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: question about memtest86+
On 08/24/2018 12:05 AM, Long Wind wrote: Sorry, Ben, i made mistake, it isn't hp dx5150, it's lenovo motherboard is 865GV-M8, it uses Dual DDR 400 memory i've used it for about 5 years, it's OK except sometimes it's noisy noise must come from fans in case since it's OK, why should i bother with memory or overheat problem? it has 512M x 2, now i want to change one of them to 1G, so that total is 1.5G i want to use memtester to test it, but it doesn't print progress, it seems i have to wait forever. You don't need to run memtest, be careful, install the new memory and start the computer, it does a self test, check the BIOS is the new memory there? Memtest is known to cause heat to the max. Memtest is known to cause budget chips to error. -- Jimmy Johnson Slackware64 14.2 - Just Say No! To SystemD, Plasma5 & Drugs! KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: question about memtest86+
On 08/22/2018 02:58 PM, Long Wind wrote: i install memtest86+ of stretch to test memory i don't see any error msg, but after a few minutes, it shutdown my PC does that mean my memory is bad? i read manual of memtest86+, can't find explaination Maybe system shutdown due to heat.. -- Jimmy Johnson Slackware64 14.2 - Just Say No! To SystemD, Plasma5 & Drugs! KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: painted into a corner
On 08/21/2018 05:29 PM, Gene Heskett wrote: On Tuesday 21 August 2018 18:33:50 Jimmy Johnson wrote: On 08/19/2018 12:40 PM, Gene Heskett wrote: Greetings all; I just installed stretch to a fresh 2T HD. letting it autopartition and format for separate /, swap, /var and /home partitions. But I didn't let it overwrite the grub on the 1st drive it was/is booting wheezy from. I figured I'd mount it to wheezy and copy over my personal stuff, like an email corpus well over 15GB reaching back to 2002. But I can't mount much of the drive, / is all that will actually mount, because the 2 versions of ext4 are incompatible, nearly all the mount and e2tools can't touch the installers ext4 file systems. For instance, its not mounted: gene@coyote:~$ e2fsck /dev/sdb8 e2fsck 1.42.5 (29-Jul-2012) /dev/sdb8 has unsupported feature(s): metadata_csum e2fsck: Get a newer version of e2fsck! And of course whats installed to wheezy is the latest available wheezy version of e2fsck. Whats the recommended way to do these mounts so I can maintain as much continuity as possible? Thanks all. Hi Gene, I've seen this before, a few times. If you run #fdisk -l while in stretch and get error, you need to fix that first, using gparted move the ailing partition '1'byte, just one digit larger or smaller, if you have to shrink another partition, do it '2'bytes. UUID will not change and it will pass fdisk -l no error. Now in wheezy see if you can mount. If not you can disable the checksums. To disable checksums on an existing filesystem, ensure that the filesystem will pass fsck. Then turn off metadata_csum via tune2fs. #tune2fs -O ^metadata_csum /dev/path/to/disk The above is for ext4, for repairing partition I use this with force. #fsck.ext4 -pvcf /dev/sdxx Thanks Jimmy. I haven't gotten that far, as I've done 6 or 7 installs today and it will not install grub on anything but /dev/sda. Run #fdisk -l, only takes a moment...If you have a bad partition-table, formatting will not fix it. -- Jimmy Johnson Slackware64 14.2 - Just Say No! To SystemD, Plasma5 & Drugs! KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: painted into a corner
On 08/21/2018 10:28 AM, David Wright wrote: On Mon 20 Aug 2018 at 18:13:22 (-0700), Jimmy Johnson wrote: On 08/20/2018 01:28 PM, Gene Heskett wrote: On Monday 20 August 2018 11:23:00 Andrew McGlashan wrote: On 20/08/18 05:40, Gene Heskett wrote: Whats the recommended way to do these mounts so I can maintain as much continuity as possible? Those other areas, are they logical volumes perhaps? lvms. No, straight partitions according to gparted. Hi Gene, I've seen this before, a few times. It might be useful for posterity to explain what it is in Gene's extensive posts that you've seen before and which demands such actions as "described" below. Thanks David, I thought I was replaying to the first post, I tried again. If you run #fdisk -l while in stretch and get error, you need to fix that first, using gparted move the ailing partition '1'byte, just one digit larger or smaller, if you have to shrink another partition, do it '2'bytes. UUID will not change and it will pass fdisk -l no error. Now in wheezy see if you can mount. If not you can disable the checksums. To disable checksums on an existing filesystem, ensure that the filesystem will pass fsck. Then turn off metadata_csum via tune2fs. #tune2fs -O ^metadata_csum /dev/path/to/disk The above is for ext4, for repairing partition I use this with force. #fsck.ext4 -pvcf /dev/sdxx Cheers, David. -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: painted into a corner
On 08/19/2018 12:40 PM, Gene Heskett wrote: Greetings all; I just installed stretch to a fresh 2T HD. letting it autopartition and format for separate /, swap, /var and /home partitions. But I didn't let it overwrite the grub on the 1st drive it was/is booting wheezy from. I figured I'd mount it to wheezy and copy over my personal stuff, like an email corpus well over 15GB reaching back to 2002. But I can't mount much of the drive, / is all that will actually mount, because the 2 versions of ext4 are incompatible, nearly all the mount and e2tools can't touch the installers ext4 file systems. For instance, its not mounted: gene@coyote:~$ e2fsck /dev/sdb8 e2fsck 1.42.5 (29-Jul-2012) /dev/sdb8 has unsupported feature(s): metadata_csum e2fsck: Get a newer version of e2fsck! And of course whats installed to wheezy is the latest available wheezy version of e2fsck. Whats the recommended way to do these mounts so I can maintain as much continuity as possible? Thanks all. Hi Gene, I've seen this before, a few times. If you run #fdisk -l while in stretch and get error, you need to fix that first, using gparted move the ailing partition '1'byte, just one digit larger or smaller, if you have to shrink another partition, do it '2'bytes. UUID will not change and it will pass fdisk -l no error. Now in wheezy see if you can mount. If not you can disable the checksums. To disable checksums on an existing filesystem, ensure that the filesystem will pass fsck. Then turn off metadata_csum via tune2fs. #tune2fs -O ^metadata_csum /dev/path/to/disk The above is for ext4, for repairing partition I use this with force. #fsck.ext4 -pvcf /dev/sdxx -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: painted into a corner
On 08/20/2018 01:28 PM, Gene Heskett wrote: On Monday 20 August 2018 11:23:00 Andrew McGlashan wrote: On 20/08/18 05:40, Gene Heskett wrote: Whats the recommended way to do these mounts so I can maintain as much continuity as possible? Those other areas, are they logical volumes perhaps? lvms. No, straight partitions according to gparted. Cheers A. Hi Gene, I've seen this before, a few times. If you run #fdisk -l while in stretch and get error, you need to fix that first, using gparted move the ailing partition '1'byte, just one digit larger or smaller, if you have to shrink another partition, do it '2'bytes. UUID will not change and it will pass fdisk -l no error. Now in wheezy see if you can mount. If not you can disable the checksums. To disable checksums on an existing filesystem, ensure that the filesystem will pass fsck. Then turn off metadata_csum via tune2fs. #tune2fs -O ^metadata_csum /dev/path/to/disk The above is for ext4, for repairing partition I use this with force. #fsck.ext4 -pvcf /dev/sdxx -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: Laptop recommendation
On 07/06/2018 07:47 AM, Charlie Gibbs wrote: On 05/07/18 10:57 PM, Ben Oliver wrote: On 18-07-06 08:43:44, Zenaan Harkness wrote: > Default answer to many folks these days⦂ https://puri.sm/ I think they are in the market for a used ThinkPad. Here's another vote for used ThinkPads. I'm on my second (a T410) and it works quite well. A local shop sells refurbished ones for a good price. > IMHO ThinkPads are the only laptop with a keyboard worth using. (I'm a fast touch typist - YMMV.) Hi Charlie! I have a T430 and a T400 using one or the other they both feel the same, fantastic keyboard, but my old A31 is built like a tank and the keyboard is old school IBM, they don't make them like that any more and even today I enjoy using it. I needed HDMI and found a DELL Latitude E6430, built lake tank with a all metal frame, has the IBM keyboard and pointing stick, low power consumption I7-4 core, 16GB and the HDMI, I paid 250.00 cash for it. All of them look like new, no problems using linux software, firmware or drivers on any of them, all coast less than 300.00 and I got them on the local Craigslist and I see they serve us, canada, europe, asia/pacific/middle east, oceania, latin america and africa. https://www.craigslist.org/about/sites -- Jimmy Johnson Slackware 14.2-64 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: new install of amd64, 9-4 from iso #1
On 06/11/2018 04:42 AM, Gene Heskett wrote: On Monday 11 June 2018 06:40:41 Mirko Parthey wrote: On Sun, Jun 10, 2018 at 04:44:16PM -0400, Gene Heskett wrote: and 3: to treat the grub install as if there are no other drives hooked up. I don't need grub to fill half the boot screen with data from the other drives. Once your Debian installation is finished, put this in /etc/default/grub: GRUB_DISABLE_OS_PROBER=true Then run update-grub to remove the unwanted entries from your grub menu. The Grub info documentation describes it as follows: 'GRUB_DISABLE_OS_PROBER' Normally, 'grub-mkconfig' will try to use the external 'os-prober' program, if installed, to discover other operating systems installed on the same system and generate appropriate menu entries for them. Set this option to 'true' to disable this. Disconnecting disks while installing Debian can help avoid mistakes. However, it does not permanently suppress the boot menu entries referring to other OS installations. Regards, Mirko Thanks Mirko, that will be handy. #3 problem, have you looked to see if you can remove drives in your BIOS, if you can you won't need to crack your case. Cheers, -- Jimmy Johnson Devuan Jessie - TDE Trinity R14.0.4 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: Intermittent blank screen – Stretch
On 06/03/2018 06:29 AM, Gene Heskett wrote: On Sunday 03 June 2018 07:54:22 Mike wrote: On 02/06/18 08:11, floris wrote: Mike schreef op 2018-06-01 01:27: I have just installed Stretch and and randomly getting a 2 second (or so) blank screen. I can go for quite some time without it happening, or it can happen several times over a few minutes. I can dual boot with Jessie and do not have the problem with that – so I think I can rule out a hardware issue. I have an Nvidia GTX1050 video card, HDMI output to a Samsung 49" TV, 4K video. There is no other type of input into the TV for me to be able to test. Here is what I have done 1. Installed Stretch (amd64) with XFCE 2. apt-get install firmware-linux nvidia-driver nvidia-settings nvidia-xconfig 3. run nvidia-xconfig 4. turned off screen blanking in power settings I am quite happy to spend time troubleshooting, but don’t really know where to start. The blanking happens too quickly for me to be able to do anything at the time. Does anyone have any thoughts? Thanks Mike You can try the NVidia driver module from backports [1] and/or run journalctl -f in a terminal and wait for the blank screen. [1] https://packages.debian.org/stretch-backports/nvidia-driver --- Floris Okay, now here is a weird thing. I just unplugged a USB cable that was, in turn, connected to a microcontroller. My screen went blank. When I plugged in back in it went blank again. This happened about 4 times until I could plug and unplug without the blanking. I left it for 30-odd seconds and was able to do the same thing. It did not happen when I unplugged my computer keyboard, or my USB camera. Does this give anyone any ideas? Yes. Unplug it again, and install htop, the run it as root so the kill button, F9 can kill any thing. Plug the cable to the micro-controller back in and see what pops up in the top 10 or so when htop is set to watch cpu. My theory is that the micro-controller is spaming your main box with lots of traffic. But its just a theory. Hi Gene, I want to make sure I understand your instructions. You say install htop and run htop as root, when the screen goes black press f9. Is that correct? Thanks, -- Jimmy Johnson Devuan Jessie - TDE Trinity R14.0.4 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: Intermittent blank screen – Stretch
On 06/01/2018 01:11 PM, floris wrote: Mike schreef op 2018-06-01 01:27: I have just installed Stretch and and randomly getting a 2 second (or so) blank screen. I can go for quite some time without it happening, or it can happen several times over a few minutes. I can dual boot with Jessie and do not have the problem with that – so I think I can rule out a hardware issue. I have an Nvidia GTX1050 video card, HDMI output to a Samsung 49" TV, 4K video. There is no other type of input into the TV for me to be able to test. Here is what I have done 1. Installed Stretch (amd64) with XFCE 2. apt-get install firmware-linux nvidia-driver nvidia-settings nvidia-xconfig 3. run nvidia-xconfig 4. turned off screen blanking in power settings I am quite happy to spend time troubleshooting, but don’t really know where to start. The blanking happens too quickly for me to be able to do anything at the time. Does anyone have any thoughts? Thanks Mike You can try the NVidia driver module from backports [1] and/or run journalctl -f in a terminal and wait for the blank screen. [1] https://packages.debian.org/stretch-backports/nvidia-driver It's a bug and can be reproduced, happens on both Intel and Nvidia. Does not happen on Wheeze or Jessie without systemd. Thanks, -- Jimmy Johnson Devuan Jessie - TDE Trinity R14.0.4 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: Intermittent blank screen – Stretch
On 05/31/2018 04:27 PM, Mike wrote: I have just installed Stretch and and randomly getting a 2 second (or so) blank screen. I can go for quite some time without it happening, or it can happen several times over a few minutes. I can dual boot with Jessie and do not have the problem with that – so I think I can rule out a hardware issue. I have an Nvidia GTX1050 video card, HDMI output to a Samsung 49" TV, 4K video. There is no other type of input into the TV for me to be able to test. Here is what I have done 1. Installed Stretch (amd64) with XFCE 2. apt-get install firmware-linux nvidia-driver nvidia-settings nvidia-xconfig 3. run nvidia-xconfig 4. turned off screen blanking in power settings I am quite happy to spend time troubleshooting, but don’t really know where to start. The blanking happens too quickly for me to be able to do anything at the time. Does anyone have any thoughts? I see the same thing on my smart-tv, while watching movies from my laptop. If you have a smart-tv then you have a tv with a computer in it and it's try to communicate with your computer and your computer is trying to communicate with your tv, not a good thing. Both Wheezy and Jessie with no-systemd do not have this behavior. Maybe the problem can be fixed, maybe. Cheers, -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: messed up release in apt
On 05/01/2018 06:11 AM, Anil Duggirala wrote: If it were my machine (so that if I sank it I would be the only one to go down with the ship), I might run: 'apt-key update' When running that command I am getting : Warning: 'apt-key update' is deprecated and should not be used anymore! Note: In your distribution this command is a no-op and can therefore be removed safely. after removing '/etc/apt/trusted.gpg' When you say removing you mean : rm /etc/apt/trusted.gpg ? I appreciate any other alternative procedure to correct this, thanks, If you have a desktop and Synaptic installed you can do all the things you want to do in Synaptic, like force a different version and reinstalling the keyring or installing distro-info. Cheers, -- Jimmy Johnson Devuan ASCII - TDE Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263
Re: I wish put another Debian, and with its command line.
On 04/24/2018 05:20 AM, Greg Wooledge wrote: On Mon, Apr 23, 2018 at 04:33:00PM -0700, Jimmy Johnson wrote: While installing and you check no boxes to add packages or desktop you get Debian Base install, command line, apt, dpkg and internet. Correct. Package 'net-tools' is installed so you have ifconfig if needed. This is the same for all current Debian releases. Incorrect. net-tools is deprecated, and not installed by default in stretch. iproute2 is installed by default. Of course, if you simply configure your network by editing /etc/network/interfaces and running ifdown/ifup commands (or rebooting), then you wouldn't know or care which network tool package is installed. I was thinking net-tools gave us ifconfig. So Greg what package pulls in the things we need for internet? I know its not network-manager. Thanks, -- Jimmy Johnson Devuan Jessie - TDE Trinity R14.0.5 - Intel Pentium-4-M 1.9GHz - EXT4 at sda2 Registered Linux User #380263
Re: I wish put another Debian, and with its command line.
On 04/23/2018 01:08 PM, Gdsi wrote: Hi all. On my disk is a little free space at which I wish put another Debian, and with its command line. A few times I tried doing it but always there was a excess , as the installer don't say exactly what is into minimal inst-ion, and I'm afraid there's kernel only. If I shall not be setting check marks for additional components, will be there: 'apt', man pages and some editor? Thank. While installing and you check no boxes to add packages or desktop you get Debian Base install, command line, apt, dpkg and internet. Package 'net-tools' is installed so you have ifconfig if needed. This is the same for all current Debian releases. Cheers! -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - Intel 4-M, 1.9GHz - 1G RAM - EXT4 at sda5 Registered Linux User #380263
Re: Install 9.4 on acer V15 Nitro 4K -> black screen after choosing installation method; Kali live running and Ubuntu installation no problem
On 04/23/2018 02:20 AM, Dr. Volker Jaenisch wrote: Dear Jimmy! On 23.04.2018 02:06, Jimmy Johnson wrote: I'm setting here looking at the secs for your laptop and it say's you have an Intel computer with Nvidia Video, but the first thing to do is make sure you have the firmware meta package installed, first you need to add non-free to your sources and 'apt-get update' and then 'apt-get install firmware-linux* xorg' Now reboot and see what happens. Good Luck! Please read my initial post. The problem is that the installer does not boot: Installer grub2 comes up nicely. Then I choose the install method (whichever) then the system get stuck immediately (Some access to the USB-Stick (blinking), HDD is accessed (blinking), Blank screen.). This happens with the Kali linux (Debian based) installer and Debian installers 9.3 (firmware-edition), 9.4 (netinstall or firmware or 1st DVD edition), buster-a2 (netinstall). But an Ubuntu 16.04 installer runs fine. Ubuntu integrates nicely in the UEFI and I have a full functional dual boot system (with win10). Under Ubuntu the 4K video display on NVIDIA 1060 runs OOTB. IMHO this is a problem with the Debian installer kernel, kernel params and/or drivers in the initrd. For Debian install you need to dd to USB or use cd. https://www.ostechnix.com/how-to-create-bootable-usb-drive-using-dd-command/ And I recommend using the net-install with non-free-firmware and I don't recommend using Kali because it's a rolling release and never will be completely stable. Also you need to verify the .iso is a good download first. https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/ These things are not hard to do. Cheers -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: Install 9.4 on acer V15 Nitro 4K -> black screen after choosing installation method; Kali live running and Ubuntu installation no problem
On 04/22/2018 02:28 PM, Dr. Volker Jaenisch wrote: Hi Songbird! On 20.04.2018 17:39, songbird wrote: i'd give the most recent versions of the installer a try to see: https://www.debian.org/devel/debian-installer/ there are the alpha versions and also the daily/weekly versions. Tried the actual debian-buster-DI-alpha2-amd64-netinst.iso some behavior report bugs/issues to debian-boot using reportbug. Will do Cheers, Volker I'm setting here looking at the secs for your laptop and it say's you have an Intel computer with Nvidia Video, but the first thing to do is make sure you have the firmware meta package installed, first you need to add non-free to your sources and 'apt-get update' and then 'apt-get install firmware-linux* xorg' Now reboot and see what happens. Good Luck! Cheer! -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Jessie-backports now has spectre patched kernel
4.9.0-0.bpo.6-amd64 is patched, tested on AMD and Intel - Variant 1,2 and 3 patched. Cheers! -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: Error while upgrading from Wheezy to Stretch
On 04/11/2018 12:31 PM, David Parker wrote: Hello, I am trying to upgrade two test boxes from Wheezy to Stretch (skipping Jessie). The upgrade worked on one of them, although I ran into errors and had to run "apt-get -f install" a few times, but that resolved the issues and it ultimately worked. However, on the second box, I ran into an error about halfway through the upgrade, and I'm not able to get past it. No matter what I do, I keep running into version mismatch issue with libpam-modules. It's preventing the upgrade from finishing. # apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libcfg4 libcib1 libclass-isa-perl libconfdb4 libcoroipcc4 libcoroipcs4 libcrmcluster1 libcrmcommon2 libevs4 liblogsys4 libpe-status3 libpengine3 libpload4 libquorum4 libsam4 libstonithd1 libswitch-perl libsystemd-login0 libtransitioner1 libvotequorum4 Use 'apt autoremove' to remove them. The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 199 not upgraded. 2 not fully installed or removed. Need to get 0 B/308 kB of archives. After this operation, 62.5 kB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... dpkg: dependency problems prevent processing triggers for man-db: man-db depends on bsdmainutils; however: Package bsdmainutils is not configured yet. dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.1.8-3.6_amd64.deb (--unpack): dependency problems - leaving triggers unprocessed Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.1.8-3.6_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Any ideas or suggestions for resolving this will be greatly appreciated. Yes, use aptitude until you get going again. Aptitude will analyze the problem and make suggestions. aptitude update and aptitude -f install. Cheers, -- Jimmy Johnson Devuan ASCII - Trinity TDE-3 version R14.0.5 - Intel P8400 - EXT4 at sda6 Registered Linux User #380263
Re: apt-get update on sid: Hash Sum mismatch
On 04/14/2018 08:24 AM, Felix Natter wrote: > apt-get update on sid: Hash Sum mismatch That means try again later or try a different source. :) Cheers! -- Jimmy Johnson Devuan Beowulf - TDE-Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: Update for i965-va-driver-shaders - Bug -
On 04/13/2018 10:45 AM, Martin Steigerwald wrote: Hi Jimmy. Jimmy Johnson - 13.04.18, 18:04: i965-va-driver-shaders in Sid, Buster and Ubuntu 18.04LTS has an upgrade, if applied will remove the i965-va-driver, the upgrades been there for a week. What's up with this? % apt changelog i965-va-driver-shaders […] [ Sebastian Ramacher ] * New upstream release. * debian/: - Revert the split and switch back to full driver. Thanks to Timo Aaltonen. This package now Conflicts+Replaces i965-va-driver. -- Sebastian Ramacher <[…]> Tue, 20 Mar 2018 21:49:53 +0100 If that's the case then we have a bug. Package details state "depends on 1965-driver" and "enhances i965-driver" Cheers, -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Update for i965-va-driver-shaders
i965-va-driver-shaders in Sid, Buster and Ubuntu 18.04LTS has an upgrade, if applied will remove the i965-va-driver, the upgrades been there for a week. What's up with this? Cheers, -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: Debian 9 sucks really badly
On 03/23/2018 08:31 PM, Chris Anderson wrote: Hello I have been using different flavours of Linux since slackware 96 over 20 years ago. Since then I have installed and used at least a dozen different flavours. By far the most challenging was the X windows system for slackware but I managed to get it installed and running with no problems. Last week I bought a new PC and decided to try debian so I downloaded the DVD version 9 and performed a fresh install besides windows 10. Right from the off, it fucked up, Grubb was a hassle as this was the default boot loader,(I have always used LILO), it would not find the windows partition, I managed to fix this. Then it didn't give me a choice of X windows manager, I was stuck with KDE, which I am familiar with and am aware of its may limitations and given the choice I wouldn't use KDE for installation and configuration. Nearly everything fucked up from the Network install to the gcc make command, what a hassle and after spending nearly a week trying to get it all working I've had enough and am not wasting any more of my time on this awful software. So thanks for wasting my time Debian and for future reference, go and get fucked!!! Chris Anderson Linus! Is that you? -- Jimmy Johnson Debian Sid/Testing - Trinity KDE 3.5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: update bios from debian
On 03/07/2018 07:37 PM, emetib wrote: has anyone tried to update their bios from debian or linux in general? i've looked at these pages -> https://wiki.debian.org/FlashBIOS https://support.lenovo.com/us/en/downloads/DS038945 and have downloaded the packages that they say to get, and have also downloaded the new bios from lenovo's website. don't really want to turn my laptop into a brick, so i'm curious if anyone has done this before, and if so anything that i should worry, not worry about? the lenovo site say to just click on the .exe, yet i don't know if it needs windows to do the install or not. It's easy to do using WindowsXP Live cd, less than 593Mb Zip file download. https://www.hiren.info/pages/bootcd Cheers, -- Jimmy Johnson Debian Sid/Testing - Trinity KDE 3.5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 07:02 PM, rhkra...@gmail.com wrote: On Wednesday, February 21, 2018 03:40:51 PM Jimmy Johnson wrote: On 02/21/2018 10:47 AM, Roberto C. S�nchez wrote: Note that upgrades skipping a release (e.g., wheezy -> stretch instead of wheezy -> jessie -> stretch) are not supported. A fresh install sounds like the better route in this case. I know what I'm talking about and if I can do it anybody can do it, Debian has given us all the tools we need to upgrade any stable release to current stable release or higher for that matter, thank about it. Just start with a simple upgrade first before tackling the other things, it's not rocket science after all. And what if their system has slightly different hardware or some other difference such that your advice doesn't work? (AFAICT, the fact that Debian does not support an upgrade skipping a release means that little or no testing has been done and there is an indeterminate amount of risk.) First off you're quoting something you have read and not from any real experience. I can say this, I run 5 laptops and two desktops, one laptop is reaching it's end of life for kde plasma upstream, it's an older real IBM Thinkpad, while all the others are different makes and models, AMD and Intel, none are the same but they are running Wheezy, Jessie, Stretch, Buster, Sid, 14.04 lts, 16.04 lts, 18.04 lts and I test other systems of interest too and it keeps me busy, these are not virtual installs, they are real hardware installs and I fix my problems, that's how I learn, I've been doing this for more than 20 years, it's called experience, real experience. My main testing desktop has sid on sda15 and its probably broken with every release, been moved to more computers than I care to remember, but I fix it, clean it and keep going, so far this release, knock on wood and thinks to Debian upstream repairs have been minimal. Outside of machine language I'm not a coder, nor do I use machine language any longer. Will you stand behind the upgrade, and fix his system if there is a problem? (Site visits are usually not cheap.) No more or less than anybody else here, I don't know the OP or what his capabilities are and my time is limited, but when I see a post where I can help I will, what else can you ask from a fellow Linux User. Just one other thing, I'm not a joiner and I won't get held back. I'm done discussing this tread, unless the OP has a question for me. Your like a pack of wolf's ready to pounce on anything different than what you have read and some of you have not changed in the 20+ years I've been using Linux, you are bullies and mean to anyone different than you, and I am different than you period. Cheers, -- Jimmy Johnson - The Linux Tester Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 02:10 PM, Karol Augustin wrote: On 2018-02-21 21:42, Jimmy Johnson wrote: On 02/21/2018 01:31 PM, deloptes wrote: Jimmy Johnson wrote: For all the "Na" Sayers here, nothing lost except for sometime and something to gan the system you want and if you can't make it work format and do a new system, but remember there is no "sysvinit" in Stretch. OK, I have a question: Why do you think you are smarter than all Debian developers? I never said that! But I do know what I'm talking about because I do what I'm talking about constantly. I have a question for you. Why do your emails wind up in my spam box where I have to fish them out? I have never black-listed you or marked your email as spam yet you keep going to my spam box, maybe my system knows something about you that I don't know. Its because Deloptes is using an e-mail to news gateway with his gmail address. As you are also using gmail it is marked as spam/phishing as DMARC fails because the mail is sent using third party servers to reach Debian mailing list instead of Google's. I'm using my gmail account's smtp.gmail server. But thanks. Even though gmail DMARC policy is "none" i think they mark messages without DKIM from gmail domain as spam to protect themselves. It might be hard to fix as even if you repeatedly mark Deloptes' emails as not spam it probably won't help. You can try adding him to contacts if you desire. If you are using Android you will also have his e-mail address on your phone for quick access anytime you might need to reach him... k. Cheers, -- Jimmy Johnson Debian Wheezy - KDE 4.8.4 - Intel i7-3540M - EXT4 at sda10 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 02:18 PM, Sven Joachim wrote: On 2018-02-21 16:49 -0500, Greg Wooledge wrote: On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote: Speaking of sysvinit, one problem with a direct upgrade from Wheezy to Stretch is that there is no _package_ named sysvinit in Stretch, so you will be left with the old sysvinit from Wheezy and have to do a manual upgrade, e.g. like this: Moot argument. You don't *DO* a direct upgrade from wheezy to stretch in the first place. You go wheezy->jessie, and then jessie->stretch. Certainly. I only mentioned this because Jimmy had suggested the reckless method of directly upgrading from Wheezy to Stretch, and I was curious how badly it would break. It's sicking the people who talk with authority about things they have never done and I don't care if they read something somewhere, doing is knowing. Cheers, -- Jimmy Johnson Debian Wheezy - KDE 4.8.4 - Intel i7-3540M - EXT4 at sda10 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 01:31 PM, deloptes wrote: Jimmy Johnson wrote: For all the "Na" Sayers here, nothing lost except for sometime and something to gan the system you want and if you can't make it work format and do a new system, but remember there is no "sysvinit" in Stretch. OK, I have a question: Why do you think you are smarter than all Debian developers? I never said that! But I do know what I'm talking about because I do what I'm talking about constantly. I have a question for you. Why do your emails wind up in my spam box where I have to fish them out? I have never black-listed you or marked your email as spam yet you keep going to my spam box, maybe my system knows something about you that I don't know. Cheers, -- Jimmy Johnson - The Linux Tester Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 01:01 PM, Greg Wooledge wrote: On Wed, Feb 21, 2018 at 12:58:11PM -0800, Jimmy Johnson wrote: For all the "Na" Sayers here, nothing lost except for sometime and something to gan the system you want and if you can't make it work format and do a new system, but remember there is no "sysvinit" in Stretch. There is. It's just not the default.\ I had to boot stretch to double check my memory and there is no "sysvinit", you do have sysv-rc, sysv-rc-conf, sysvinit-core and sysvinit-utils and yes I do know that you can run a sysvinit system with those files or so it seems. I'll let the OP choose what he wants to do. Cheers, -- Jimmy Johnson - "The Linux Tester" Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 10:39 AM, Jimmy Johnson wrote: On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote: I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh install of Stretch (v9 = stable) before Wheezy's support runs out on May 31st. I will try the default systemd installation and see how I like it. Okay, but I suggest instead you keep your wheezy system and your wheezy sources and do a upgrade using package upgrade-system, it will clean your system and then add the stretch sources including backports and run apt update & apt-upgrade and then run upgrade-system until your system is upgraded and clean, careful that sysvinit is not removed cause that package is not in stretch. You can also use apt dist-upgrade and deborphan. After the installation, I will want to build my system from my favorite window manager (fvwm). With sysvinit, I would set initdefault to runlevel 3 in /etc/inittab. In /etc/rc3.d, I would rename gdm3 so that I would boot into a terminal interface (command line) instead of Gnome. Then I would quickly install fvwm, call startx, and happily finish building. I know systemd doesn't have inittab. Will the default installation leave me with a terminal interface whenever I boot? If not, how will I accomplish that? I also thought I had read about some problem with window authentication in Stretch, but I can't find any such posts now. I don't know of any current problems in stretch. For all the "Na" Sayers here, nothing lost except for sometime and something to gan the system you want and if you can't make it work format and do a new system, but remember there is no "sysvinit" in Stretch. Cheers, -- Jimmy Johnson - "The Linux-Tester" Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote: I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh install of Stretch (v9 = stable) before Wheezy's support runs out on May 31st. I will try the default systemd installation and see how I like it. Okay, but I suggest instead you keep your wheezy system and your wheezy sources and do a upgrade using package upgrade-system, it will clean your system and then add the stretch sources including backports and run apt update & apt-upgrade and then run upgrade-system until your system is upgraded and clean, careful that sysvinit is not removed cause that package is not in stretch. You can also use apt dist-upgrade and deborphan. After the installation, I will want to build my system from my favorite window manager (fvwm). With sysvinit, I would set initdefault to runlevel 3 in /etc/inittab. In /etc/rc3.d, I would rename gdm3 so that I would boot into a terminal interface (command line) instead of Gnome. Then I would quickly install fvwm, call startx, and happily finish building. I know systemd doesn't have inittab. Will the default installation leave me with a terminal interface whenever I boot? If not, how will I accomplish that? I also thought I had read about some problem with window authentication in Stretch, but I can't find any such posts now. I don't know of any current problems in stretch. Thanks. Cheers, -- Jimmy Johnson Debian Buster - KDE Plasma 5.12.0 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Wheezy to Stretch
On 02/21/2018 10:47 AM, Roberto C. Sánchez wrote: On Wed, Feb 21, 2018 at 10:39:54AM -0800, Jimmy Johnson wrote: On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote: I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh install of Stretch (v9 = stable) before Wheezy's support runs out on May 31st. I will try the default systemd installation and see how I like it. Okay, but I suggest instead you keep your wheezy system and your wheezy sources and do a upgrade using package upgrade-system, it will clean your system and then add the stretch sources including backports and run apt update & apt-upgrade and then run upgrade-system until your system is upgraded and clean, careful that sysvinit is not removed cause that package is not in stretch. You can also use apt dist-upgrade and deborphan. Note that upgrades skipping a release (e.g., wheezy -> stretch instead of wheezy -> jessie -> stretch) are not supported. A fresh install sounds like the better route in this case. Also, adding backports sources for the target version during an upgrade is a terrible idea. Packages in backports have not received upgrade testing, so who knows what sort of a mess it could create. For Steven, the best thing is to read the release notes and/or installation manual and follow the instructions found there. Regards, -Roberto I know what I'm talking about and if I can do it anybody can do it, Debian has given us all the tools we need to upgrade any stable release to current stable release or higher for that matter, thank about it. Just start with a simple upgrade first before tackling the other things, it's not rocket science after all. Cheers, -- Jimmy Johnson Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Debian Sid spectre-meltdown
On 02/21/2018 08:30 AM, Michael Fothergill wrote: On 21 February 2018 at 16:25, Jimmy Johnson <field.engin...@gmail.com> wrote: As reported by Linus kernel 4.15 would have the spectre-meltdown fix, Debian Sid just got 4.15 and I installed it on both AMD and Intel and then I ran the spectre-meltdown-checker and Sid is no longer vulnerable to Spectre-1,2 or 3/meltdown. It should be in Buster soon. Cheers, -- Jimmy Johnson Heroic stuff... Excellent news. Cheers MF Debian Sid/Testing - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda8 Buster, after making sure buster was up to date and clean I added sid sources and installed anything that was a new package or upgrade package with the name linux and then removed the sid sources, clean and upgraded I rebooted to the 4.15 kernel with no problem, ran the spectre-meltdown-checker and was not vulnerable. The AMD A8-7600 needed 12 packages, it has non-free nvidia driver. Not vulnerable. The Intel i7-3540 only needed 5 packages. Not vulnerable. KDE Plasma 5.12 Desktop on both. Cheers, -- Jimmy Johnson Debian Buster - KDE Plasma 5.12.0 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Debian Sid spectre-meltdown
As reported by Linus kernel 4.15 would have the spectre-meltdown fix, Debian Sid just got 4.15 and I installed it on both AMD and Intel and then I ran the spectre-meltdown-checker and Sid is no longer vulnerable to Spectre-1,2 or 3/meltdown. It should be in Buster soon. Cheers, -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.12.0 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: [OT] debian (or debian like) terminal program for android
On 02/10/2018 01:46 PM, Harry Putnam wrote: aside: , | Having such a time trying to google this. It seems google has been | dumbed down to the point where +word or "these words" no longer force | those things to be in the hits. ` Can anyone tell me if there is a serious terminal program for android phones? I mean a full OS and the basic commands. Especially I'd like to have ssh and scp among them. What I've already tried and found lacking: Terminux simple sshd ConnectBot Material Terminal (Supposed to be an improvement over Terminal Emulator for Android so didn't try that one) Best place to look for software https://f-droid.org/en/ Can you get root on your phone? Cheers, -- Jimmy Johnson Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Debian buster & gnucash
On 02/08/2018 03:06 PM, Sven Hartge wrote: Jimmy Johnson <field.engin...@gmail.com> wrote: On 02/08/2018 10:05 AM, Sven Hartge wrote: Donald F. Emery <dem...@vermontel.net> wrote: I am new to debian and was hoping someone could tell me why GNUCASH was not in debian testing. Because of https://tracker.debian.org/news/859896 and https://bugs.debian.org/790204 Make sure you read the part about it being fixed in Sid. No, #790204 has been fixed with 1:2.7.3-1, currently only available in experimental. You're right and they are saying it's RC-buggy, I should have looked further into it than I did before posting, my bad and it's probably not a good idea to be running an app like GNUCash on testing or Sid in the first place. But: | However 2.7.* is still a development branch and upstream NEWS file contains | the following warning: | | | This release is UNSTABLE and SHOULD NOT BE USED in production. | See the KNOWN PROBLEMS list at the bottom of the announcement. So beware when using that version. Grüße, Sven. Cheers, -- Jimmy Johnson Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: I do not want to install Linux
On 02/07/2018 11:37 PM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Feb 08, 2018 at 12:01:57AM +, Michael Fothergill wrote: [...] It sounds like a dietary supplement. MF ;-P Actually Kali Linux [1] is pretty cool and definitely worth a look. To be fare it should be noted that Kali Linux is a rolling release using Debian Testing and is subject to all bugs found in testing, while testing Stretch X and sddm where both broken so I installed Kali only to find that it too was broken and did not fare any better than Debian Testing, not sure but if they are helping fix bugs then they are doing a good thing, but I don't care for a rolling release as I'm already running Buster and Sid. https://docs.kali.org/general-use/kali-linux-sources-list-repositories And, as a Debian derivative, it is a wonderful illustration of the things the Debian culture makes possible (another being Ubuntu, of course). So not *completely* off-topic here. Cheers [1] https://en.wikipedia.org/wiki/Kali_Linux - -- tomás -BEGIN PGP SIGNATURE- Cheers, -- Jimmy Johnson Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: Debian buster & gnucash
On 02/08/2018 10:05 AM, Sven Hartge wrote: Donald F. Emery <dem...@vermontel.net> wrote: I am new to debian and was hoping someone could tell me why GNUCASH was not in debian testing. Because of https://tracker.debian.org/news/859896 and https://bugs.debian.org/790204 Grüße, S° Make sure you read the part about it being fixed in Sid. Cheers, -- Jimmy Johnson Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: Debian buster & gnucash
On 02/08/2018 09:25 AM, Donald F. Emery wrote: I am new to debian and was hoping someone could tell me why GNUCASH was not in debian testing. It's not the only package missing from Buster, you can probably install it from Sid without to much problem. Cheers, -- Jimmy Johnson Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: How to safely hold kernel packages ?
On 02/07/2018 12:27 AM, Stéphane Rivière wrote: Thanks Jimmy for your help, I would use 'apt-mark'. # apt-mark hold 'package-name' and # apt-mark unhold 'package-name' It appears that apt-mark hold and aptitude hold have same effects, you could obtain the same with some tricks with dpkg. If I used apt-get, it should be wise to use apt-mark. When using only aptitude (my choice), it seems I must use aptitude hold to remain consistent (using apt-get or aptitude is an old, and perhaps unclear, war ;))) I love using all the Debian Tools, while using Synaptic to install the meta-package nvidia-driver in Wheezy I found the nvidia-driver package is broken and Synaptic does not give much info on broken packages so I ran # aptitude install nvidia-driver and found that nvidia-settings was not installable and knowing that nvidia-settings is not needed I was able to install the nvidia-driver with no further problem. Thanks to your post I found a new tool> Debian package "dlocate" and now I can run: # dpkg-hold 'package-name' and dpkg-unhold, dpkg-remove, dpkg-purge. Pretty powerful tool don't you think. By the way I've found what is the kaiser patch (inducing performance loss between 5% -mean use- and 30% -a heavy network load-) and why (in my context only, see previous message) I should use nokaiser option (https://lwn.net/Articles/737940) and, thanks to fine people here, the nopti option.network link Well thanks to all the noise about spectre and meltdown some people are now trying to exploit it, now saying that, these problems have been in hardware for more than 5 years(and Intel kept on making them and that seems criminal to me) and with no reports of any exploit, so I let the experts work on the problem and keep my many systems(Ubuntu 14.04, 16.04, 18.04 and Debian Wheezy, Jessie, Stretch, Buster and Sid installed on two desktops and 5 laptops) updated and I feel as the experts do and that is these affected cpu's should be recalled and replaced, Intel trying to fix a hardware problem with software is not acceptable. On an almost idle workstation the effects of using theses options are not really visible (tested). But on a huge Xeon 64Go ram 2x2To raid1/lvm/debian 8/Xen 4 with 1 Gbps network and more than twenty VM, definitly not the same story (some friends has done some tests on their less loaded than mine dedicated servers and the performance loss is really huge). I have some low cost spare dedicated servers and will proceed to some tests too. Sounds like a nice computer, but without the model number, cores, bus speed it's hard to tell just how fast it can work or move a Tb or two of data. Stef All the best from Oleron island, Cool! And blessings to you from sunny California!-- Jimmy Johnson Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: How to safely hold kernel packages ?
On 02/06/2018 09:00 AM, Stéphane Rivière wrote: Hi all, I wanted to avoid kernel updates after the Spectre/Meltdown 'bug', also known as KPTI or kaiser CPU flaw. In my specific context, these patches are useless or even harmful. Before applying an aptitude update/upgrade to all the servers and VMs I'm in charge, I've done a little test on a Debian 9 stable workstation, with the kernel linux-image-4.9.0-4-amd64 release 4.9.51-1 So, after an aptitude search ~i~linux- I hold theses meta-packages : aptitude hold linux-image-amd64 aptitude hold linux-headers-amd64 Then I check the applied holds : aptitude search ~ahold ihA linux-headers-amd64 ih linux-image-amd64 then... aptitude update/upgrade After that... I discover a kernel change : linux-image-4.9.0-4-amd64 release 4.9.65-3 (instead of previously 4.9.51-1) Reading : http://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_4.9.65-3+deb9u2_changelog I discovered I've perfectly applied the patch I wished to avoid. linux (4.9.65-3+deb9u2) stretch-security; urgency=high .../... * [amd64] Implement Kernel Page Table Isolation (KPTI, aka KAISER) (CVE-2017-5754) Hopefully, there is a new "nokaiser" boot option ! (happy end). So it seems I just learn that 'hold' aptitude command is for packet version (i.e 4.9.0-4), not for package security fixes versions (4.9.65-3)... But is there a way to really *freeze* a packet (block all updates) ? Is it the 'keep' aptitude option ? (can't really see the difference with 'hold') Or may be it's better to apply security patches and use the new "nokaiser" boot option... Thanks a lot in advance for your advices ;) All the best from France... I would use 'apt-mark'. # apt-mark hold 'package-name' and # apt-mark unhold 'package-name' Cheers, -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263
Re: Problem using "dpkg -i"
On 01/15/2018 11:17 PM, deloptes wrote: Jimmy Johnson wrote: Instead of using apt, next time use aptitude -f install, reason is if aptitude can not fix the problem it will give you a clue as what you can do. Also if you apt install and run 'upgrade-system' upgrade-system will tell what to do, and clean your system too. I thought aptitude was obsolated - never used it, but I think there was a thread on the list about In my post I should have said: Instead of using apt-get, next time use apt -f install or aptitude -f install because the newer apt is also verbose like aptitude is. Aptitude is old but still verbose. Personally I use all of Debian's tools and when there is a problem, the more verbose the better. Interesting, both aptitude and gdebi got upgrades in the wee hours of my morning. Thank you Debian. :) -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: Problem using "dpkg -i"
On 01/15/2018 01:17 AM, Richard Owlett wrote: On 01/15/2018 02:25 AM, Bernd Gruber wrote: Richard Owlett wrote: Received error message: dpkg: dependency problems prevent configuration of amaya: amaya depends on libssl0.9.8 (>= 0.9.8m-1); however: Package libssl0.9.8 is not installed. try apt-get -f install Bernd I had already tried "fix broken" option in Synaptic. All it did was remove all pieces of Amaya. I repeated dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb followed by apt-get -f install with the same result ;< Instead of using apt, next time use aptitude -f install, reason is if aptitude can not fix the problem it will give you a clue as what you can do. Also if you apt install and run 'upgrade-system' upgrade-system will tell what to do, and clean your system too. Also there is a GUI package that installs downloaded packages called 'gdebi', 'apt install gdebi' and right click on the package you want to install, choose other, check the box to remember so you don't have to do this again and choose '/usr/bin/gdebi-gtk' and install your package, the next time just click on the package you want to install. There is a gdebi-kde version but never seems to work. Cheers, -- Jimmy Johnson Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Kernel problem?
On 01/06/2018 06:58 PM, Rob Hurle wrote: Hi All, I'm running Stretch and yesterday I did my normal: sudo apt-get update sudo apt-get upgrade It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config and image files, etc) in place of 4.9.0-4-686-pae versions. Now the system won't boot at all. I have reverted to 4.9.0-4-686-pae and all is well. My questions are: 1. Does anyone else see this? 2. How can I revert without losing my working 4.9.0-4-686-pae system? Can I just change the soft links for initrd.img and vmlinuz at / to point to the 4.9.0-4-686-pae versions instead of the 4.9.0-5-686-pae ones? Will this break something else for a future upgrade? Any help much appreciated. Thank you. I had a problem with that kernel on first boot, so I booted the old kernel with no problem and then tried the new kernel again to see if I could get a hint at what the problem was and it booted and the desktop started with no problem and again with no problem, go figure..I'm still booting the new kernel(Linux jimmy-1 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux) with no problem. So if you have not tried to reboot with the new kernel, maybe cross your fingers and give it another try or two. Cheers, -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263
Re: Debian iso installation incorrectly sets sources.list
On 01/09/2018 07:54 PM, John Hosack wrote: Hello, This is a bug report. I tried to use the reporting system, but it did not seem to be appropriate. So, I will give a narrative: This is what happened. I decided to install Debian on my small machine (Asus eeePC 900A, 1GB ram, 4GB storage). So I selected debian-9.3.0-i386-xfce-CD-1.iso and put it onto a flash memory stick. Installation went ok, but later on when I did "apt install gcc", the installation program requested the insertion of the installation disk in the drive /media/cdrom. Why? Examination. The /etc/apt/sources.list file had "deb: cdrom:[..." as the first entry, and was not commented out. My installation medium was wrong! John I'm thinking you did not run 'apt update' before 'apt install'? Cheers, -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263
Re: Embarrassing security bug in systemd
On 12/09/2017 08:23 AM, David Wright wrote: On Fri 08 Dec 2017 at 18:30:08 (-0800), Jimmy Johnson wrote: On 12/07/2017 02:31 AM, Jonathan Dowland wrote: On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote: I'm running Jessie (with systemd running but booting with sysvinit) and trying to execute halt/poweroff/reboot/shutdown from a terminal without root privileges gives an error saying I must be superuser. Which has always been my experience in 10 years of using Debian. Be careful to double check what you are testing: in your situation it's not clear whether /sbin/reboot is a symlink to systemctl (part of systemd, so I would expect this not to work if you were not running systemd as the init system) or a separate binary. Jonathan, I started thinking about lost work where someone restarted the computer while I was away from it and thought what if you can lock-screen and lock access to console at the same time. Is that something that could be done? Helpful? I know someone can pull the cord or press the power button, I got past that. I use vlock -a in a VC to lock all the consoles. I've been using it for years so I hadn't noticed the -n switch that allows you to run it in X (with switching to a VC first). You can still ssh into, and scp to, the machine while it's locked. AFAICT Debian's versions allow unlocking with the root password as well as the user's, which is handy if you forget which username you were logged in under when you vlock'd it. https://lists.debian.org/debian-user/2017/11/msg00951.html Thanks David, works great, KDE runs on VC7 I went to VC2 an ran '$ vlock -a' and I was NOT able to switch to any other VC it was locked with the message to press enter with passwd, if you press enter with wrong passwd or no passwd you will be prompted for ROOT passwd. For me that was no problem, but I can see the shock on someones face when they don't know the root passwd and I got a chuckle out of that. After entering the root passwd I was able to switch back to VC7 and all was well. :) Cheers! -- Jimmy Johnson Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Embarrassing security bug in systemd
On 12/07/2017 02:31 AM, Jonathan Dowland wrote: On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote: I'm running Jessie (with systemd running but booting with sysvinit) and trying to execute halt/poweroff/reboot/shutdown from a terminal without root privileges gives an error saying I must be superuser. Which has always been my experience in 10 years of using Debian. Be careful to double check what you are testing: in your situation it's not clear whether /sbin/reboot is a symlink to systemctl (part of systemd, so I would expect this not to work if you were not running systemd as the init system) or a separate binary. Jonathan, I started thinking about lost work where someone restarted the computer while I was away from it and thought what if you can lock-screen and lock access to console at the same time. Is that something that could be done? Helpful? I know someone can pull the cord or press the power button, I got past that. -- Jimmy Johnson Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Upgrading from very-old Debian
On 11/29/2017 01:01 AM, Jonathan Dowland wrote: On Tue, Nov 28, 2017 at 03:42:15PM +, Richard Zimmerman wrote: I'm pretty new to the Debian list here Welcome aboard! but over on the CentOS list I'm on, migrating from init system to systemd isn't for the faint of heart as I understand it. There's more of a culture of upgrade rather than reinstall in Debian than in CentOS and family, in general. The systemd upgrade was handled very well and was seamless for most people; however, someone upgrading from such a long release ago is not something that will have been thoroughly tested and it's quite possible that an old init script that was modified (and therefore won't be replaced by package upgrades) could come along for the ride and cause problems. Hi Jonathan, and that's the reason I would choose Wheezy as the target to upgrade to where the only thing sys.d is login.d and there's not a lot of plasma to deal with. But I'm the weird guy who thinks upgrading is mostly always a fun learning experience where I get to use the tools Debian has given me, synaptic, apt, aptitude, dpkg, upgrade-system, gtkorphan, etc. Cheers! -- Jimmy Johnson KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: Upgrading from very-old Debian
On 11/28/2017 08:58 AM, The Wanderer wrote: On 2017-11-28 at 11:53, Patrick Bartek wrote: On Tue, 28 Nov 2017 10:28:57 -0500 The Wanderer <wande...@fastmail.fm> wrote: I've run across someone who says her machine is running Debian oldoldoldstable or maybe even oldoldoldoldstable, and who consequently can't upgrade to newer Debian. I seem to recall that there *is* a way to do step-wise upgrades of such old systems, i.e. upgrading from oldoldoldoldstable to oldoldoldstable, then to oldoldstable, then to oldstable, then to stable. However, I'm stumped as to how to actually get started on doing that. The last few steps of this are straightforward; oldoldstable is still available in the repos, as far as I'm aware. The first ones are more of a problem; if I understand matters correctly, anything prior to oldoldstable is removed from the live repos, although its .deb files are still maintained on e.g. snapshot.debian.org. (Which doesn't really suffice for the equivalent of a dist-upgrade, because you'd have to manually download all the correct .debs by hand and then install them with dpkg.) Is there in fact a way to manage the first steps of this stepwise upgrade, from one aged-out-of-the-repos release to another? If so, any pointers to information on how to go about it? Save yourself time and lots of problems, back up your data and do a clean install of the current Debian release. A: This isn't me, this is someone I encountered. B: That's not always a viable option, depending on the circumstances. It's probably the easier option when it is viable, but that doesn't mean it should be the only option considered, for cases when something else may be more viable. And all the fun you could have too. is the system running? Can you currently apt-get update? If nothing else you can always delete the system and the system files in home too saving home and do a new install with no format of root. I would go to whezzy for the upgrade and unless you have active repos to your current install all your packages will orphaned, that don't help, but with the whezzy repos make sure you don't lose your internet connection or all will be lost and or make it harder to do the upgrade. Upgrade linux-image, linux-headers and apt, aptitude, net-tools, firmware-linux, xorg, grub, etc. Stay away from meta-packages as much as you can and some applications you may want to start by upgrading the lib-common package first. Installing synaptic after xorg could help and from the command line using package 'upgrade-system' can help, but first thing is to get the base going. And remember to have fun! To do what you want requires dist-upgrading each release, in order, one-at-a-time, then troubleshooting each dist-upgrade once done with no guarantees it will work. Yes, of course. That's established procedure, and it's entirely reasonable to expect people to follow it. (Is there any reason it shouldn't work, when it worked for people at the time when those releases were made?) Be sure to read and explicitly follow the dist-upgrade instructions in the Release Notes for each release. Many times there are special things that must be done. Just dist-upgrading from your current old install to Stretch, skipping all those inbetween is "not recommended," meaning it won't work. Of course. That's exactly why accessible repositories containing those older releases are needed; my question was about how / where to manage those, and that was answered in the first reply. Cheers! -- Jimmy Johnson KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: How to automagically rewrite udev rules files
On 11/19/2017 12:59 PM, J.W. Foster wrote: I was trying to get rid of a crap load of the boot errors that were being generated on my system after I installed a new motherboard... I move drives with multi systems all the time AMD to Intel and back, all I need do is install drivers and firmware, I can do that from command line and reboot to desktop. Have you done that? As for the windows, you can remove all the devices from the device manager and reboot it should reload the new devices. Have you thought about installing legacy grub to one of those drives so you can write them all to menu? regards, -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263
Re: Firefox not displaying text on website(s)
On 11/15/2017 08:58 PM, Sridhar M A wrote: Yesterday when I updated my system, I got firefox 57. It does appear to work faster. But, I noticed that the sites I frequent, do not display the text: distrocwatch.com, slashdot.org, gmail, etc. Removed $HOME/.mozilla and checked again. Same problem :-( The screenshots can be seen here: https://imgur.com/lwjhGGu, https://imgur.com/Jcdo1Wg, https://imgur.com/KPyxmFN Anyone else facing a similar problem? If it matters, except uBlock, I do not have any other extensions. Even with the extension removed, the behaviour is the same. Regards, I would click Customize and then click Restore Defaults, also make sure your addons are up to date. -- Jimmy Johnson Ubuntu 16.04 LTS - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading
On 10/29/2017 01:17 AM, none wrote: So is there an example ocaml code that can trigger the bug ? Debian Linux reveals Intel Skylake and Kaby Lake processors have broken hyper-threading http://www.zdnet.com/article/debian-linux-reveals-intel-skylake-kaby-lake-processors-have-broken-hyper-threading/ -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: X crashes when closing one of two running X sessions
On 10/23/2017 10:40 PM, Robert Arkiletian wrote: On Mon, Oct 23, 2017 at 2:51 PM, The Wanderer <wande...@fastmail.fm> wrote: On 2017-10-23 at 16:21, Robert Arkiletian wrote: Just tried this on a different box running Fedora 25 (64) and it works perfectly, no problem. So I think this is a Debian bug. Although on Fedora I'm not starting the first X session with startx, I can start another X session on tty2 with startx and switch to tty3, log in and log out without issue. Per the description in bug 791342 (linked to from 858073 as being the same issue), "[s]tarting the server on tty[2-6] does not generally appear to lead to the behaviour described above". So I don't think this is enough of a test to conclude that Fedora does not exhibit the same behaviour. My mistake. Confirmed the same behavior on the Debian Stretch box. If I don't use tty1 everything is fine. I can use tty2 (running X) and tty3 logging in and out switching back and forth, no issues. What an odd bug. Well at least I have a workaround now. I will simply avoid using tty1. When I'm trying to work in ttys I avoid tty1 the system will output data there, seems to be logging stuff, firewall, etc., so I use tty2, etc. and then I'm not bothered by the system background noise. -- Jimmy Johnson Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: thinkpad mute button not working since upgrade to stretch
On 10/23/2017 05:24 AM, Paul Seyfert wrote: Assuming I'm not the only thinkpad user, any others around who encountered that problem and have already found a solution? Or tips for how to get the mute button to work hardware-like again? Thanks for checking. I did not have have tpb installed. Installing it didn't help though. I also install firmware-linux* and intel-microcode/amd64-microcode, plus if you search thinkpad you will find some packages too. Hi, firmware-linux* and intel/amd64-microcode were already installed. I tried adding acpitool and tp-smapi-dkms without success. I have 3 Thinkpad's, not you model but I don't have your problem, yes I know that does not help, maybe the problem is the desktop, I don't know, but while googling I found this http://www.thinkwiki.org/wiki/ThinkPad_Button and maybe it will help or maybe someone else will chime in and can get you going. Good luck, -- Jimmy Johnson Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: thinkpad mute button not working since upgrade to stretch
On 10/20/2017 08:43 AM, Paul Seyfert wrote: Hi, On 20.10.2017 06:09, Jimmy Johnson wrote: On 10/19/2017 03:11 PM, Jimmy Johnson wrote: On 10/19/2017 02:48 PM, Paul Seyfert wrote: Hi, Assuming I'm not the only thinkpad user, any others around who encountered that problem and have already found a solution? Or tips for how to get the mute button to work hardware-like again? Paul, do you have "tpb" installed? That's the package to install thinkpad buttons. I have it installed and can mute, etc. My thinkpad is running Buster/Testing now and busy, but will check in Stretch sometime today. I upgraded Jessie on this Thinkpad and the volume buttons are working fine. Thanks for checking. I did not have have tpb installed. Installing it didn't help though. Alexandre's reply makes me wonder if my setup is wrong in another place than the presence/absence of tpb. Cheers, Paul I also install firmware-linux* and intel-microcode/amd64-microcode, plus if you search thinkpad you will find some packages too. -- Jimmy Johnson Ubuntu 16.04 LTS - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: thinkpad mute button not working since upgrade to stretch
On 10/19/2017 03:11 PM, Jimmy Johnson wrote: On 10/19/2017 02:48 PM, Paul Seyfert wrote: Hi, Assuming I'm not the only thinkpad user, any others around who encountered that problem and have already found a solution? Or tips for how to get the mute button to work hardware-like again? Paul, do you have "tpb" installed? That's the package to install thinkpad buttons. I have it installed and can mute, etc. My thinkpad is running Buster/Testing now and busy, but will check in Stretch sometime today. I upgraded Jessie on this Thinkpad and the volume buttons are working fine. -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - Intel Mobile 965 - EXT4 at sda6 Registered Linux User #380263
Re: thinkpad mute button not working since upgrade to stretch
On 10/19/2017 02:48 PM, Paul Seyfert wrote: Hi, Assuming I'm not the only thinkpad user, any others around who encountered that problem and have already found a solution? Or tips for how to get the mute button to work hardware-like again? Paul, do you have "tpb" installed? That's the package to install thinkpad buttons. I have it installed and can mute, etc. My thinkpad is running Buster/Testing now and busy, but will check in Stretch sometime today. -- Jimmy Johnson Ubuntu 16.04 LTS - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: X crashes when closing one of two running X sessions
On 10/19/2017 01:01 PM, David Wright wrote: On Thu 19 Oct 2017 at 08:35:55 (-0700), Jimmy Johnson wrote: On 10/18/2017 09:13 AM, Robert Arkiletian wrote: Using Debian Stretch x86_64. I don't use a greeter like lightdm. I just log in at the virtual terminal, then startx (xfce desktop). I like to use multiple accounts (running X) at the same time on different virtual terminals (eg. ctrl-alt-f1 ctrl-alt-f2) All is fine until I exit (shutdown) one X session, then the other running X session freezes and then after a little while crashes. Any ideas on how to find or diagnose what's causing this issue are much appreciated. I don't know about how you shutdown a terminal, me I just ctrl+d and it logs out. That sounds like you're talking about an xterm, not X. Well if the OP is starting multi-X as the same user, that's not advisable, from what I read, different users are okay and currently there maybe problems if plasma is involved, also from what I read. And yes, I was posting about simple logout and nothing about stopping X. Now I'll just listen and learn. -- Jimmy Johnson Ubuntu 16.04 LTS - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: X crashes when closing one of two running X sessions
On 10/18/2017 09:13 AM, Robert Arkiletian wrote: Using Debian Stretch x86_64. I don't use a greeter like lightdm. I just log in at the virtual terminal, then startx (xfce desktop). I like to use multiple accounts (running X) at the same time on different virtual terminals (eg. ctrl-alt-f1 ctrl-alt-f2) All is fine until I exit (shutdown) one X session, then the other running X session freezes and then after a little while crashes. Any ideas on how to find or diagnose what's causing this issue are much appreciated. I don't know about how you shutdown a terminal, me I just ctrl+d and it logs out. -- Jimmy Johnson Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5
On 10/17/2017 11:42 AM, Brian wrote: On Tue 17 Oct 2017 at 13:56:37 -0400, Greg Wooledge wrote: On Tue, Oct 17, 2017 at 06:42:04PM +0100, Brian wrote: On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote: On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexan:der V. Makartsev wrote: Deprecated doesn't mean it doesn't exist or work anymore at all, it means it isn't supported anymore and should not be used. Look it up, it was deprecated for quite some time. https://forums.mageia.org/en/viewtopic.php?f=8=8737 So it's deprecated in Mageia GNU/Linux? OK. If I were a Mageia user (or had ever heard of it before today) that might carry some weight with me. Just curious, what are Mageia users expected to use instead of startx if they want to start a traditional X session from a console? Or is that no longer a supported configuration at all? (By traditional, I mean a ~/.xsession or ~/.xinitrc file that contains "exec twm" or whatever window manager you prefer.) Did they simply throw every window manager under the bus and say "Nope, sorry, you gotta run a desktop environment now"? That is possible, but I'm not going to invest the time in finding out. The purpose of my post was to point out Alexan:der V. Makartsev's use of a post from elsewhere without acknowledgement and indicate Debian's attitude towards startx (without going into detail). I use startx. My users get xdm because they have poor memories for the names of commands and like pretty pictures. I use startx a lot because I install a lot of systems from a base install and after installing drivers, firmware and desktop I can startx and do my desktop setup before rebooting or logging out. I'm sure there are other ways like starting sddm or start plasma or? But I know and use startx. -- Jimmy Johnson Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5
On 10/17/2017 07:39 AM, Greg Wooledge wrote: On Tue, Oct 17, 2017 at 07:32:11PM +0500, Alexander V. Makartsev wrote: Deprecated doesn't mean it doesn't exist or work anymore at all, it means it isn't supported anymore and should not be used. Look it up, it [startx] was deprecated for quite some time. Quoting from https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html == * Only the gdm3 display manager supports running X as a non-privileged user in stretch. Other display managers will always run X as root. Alternatively, you can also start X manually as a non-root user on a virtual terminal via startx. When run as a regular user, the Xorg log will be available from ~/.local/share/xorg/. == Looks supported to me. +1 -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: D-Bus (Re: systemd process(es) consuming CPU when laptop lid closed)
On 10/17/2017 06:22 AM, Michael Biebl wrote: Am 17.10.2017 um 14:49 schrieb Jimmy Johnson: path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; Michael I found it interesting that I do not have a folder /org/ .hidden or not and that's with kde5 desktop on Stretch. Those are D-Bus path names, not file names. https://dbus.freedesktop.org/doc/dbus-tutorial.html explains the basic concepts. If you want to dig a bit deeper, install d-feet to explore what D-Bus services are running on your system and what API they provide. Michael Michael, this sounds like the background system and what a normal user would not get into. I will explore. Thanks you, -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: systemd process(es) consuming CPU when laptop lid closed
On 10/17/2017 02:27 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 16, 2017 at 10:12:52PM +, Glen B wrote: You’re going to get an e-mail from me in ~10 hours or so saying I fixed it; for some reason, this mailing list is delaying my emails by about 24 hours. So much for speedy technology! It must be something else. I'm seeing my mails arrive whithin minutes. Cheers "rhkramer" time is off, it looks like his post is 12hr in the future. Cheers! -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: systemd process(es) consuming CPU when laptop lid closed
On 10/16/2017 02:33 PM, Michael Biebl wrote: Am 16.10.2017 um 02:56 schrieb Glen B: On 10/15/2017 10:31 AM, Michael Biebl wrote: Am 14.10.2017 um 21:48 schrieb Glen B: 295 root 20 07448 4432 3992 R 41.2 0.9 0:54.81 systemd-logind 298 message+ 20 06260 3636 3268 S 17.6 0.7 0:17.12 dbus-daemon That looks like there is a huge amount of dbus messages sent. Can you run dbus-monitor --system (as root) to see what those messages are? That's an interesting command, lots of information was spat out. Here's an excerpt of what was put out: uint32 0 error time=1508114297.985967 sender=:1.0 -> destination=:1.1 error_name=org.freedesktop.systemd1.UnitMasked reply_serial=26352 string "Unit suspend.target is masked." signal time=1508114297.986032 sender=:1.0 -> destination=(null destination) serial=52814 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitNew string "suspend.target" object path "/org/freedesktop/systemd1/unit/suspend_2etarget" signal time=1508114297.986058 sender=:1.0 -> destination=(null destination) serial=52815 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitRemoved string "suspend.target" object path "/org/freedesktop/systemd1/unit/suspend_2etarget" signal time=1508114297.991185 sender=:1.1 -> destination=(null destination) serial=26353 path=/org/freedesktop/login1; interface=org.freedesktop.login1.Manager; member=PrepareForSleep boolean true method call time=1508114297.992516 sender=:1.1 -> destination=org.freedesktop.systemd1 serial=26354 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=StartUnit string "suspend.target" string "replace-irreversibly" method call time=1508114297.993237 sender=:1.0 -> destination=org.freedesktop.DBus serial=52816 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetConnectionUnixUser string ":1.1" method return time=1508114297.993292 sender=org.freedesktop.DBus -> destination=:1.0 serial=13188 reply_serial=52816 If I'm understanding this correctly, it looks like it's trying to suspend but is somehow getting confused... Not sure about the confused part. We might need a debug log for systemd-logind. That said, is that all? Given the high cpu usage for the dbus-daemon process I was expecting it to be flooded by dbus messages. You could also try stracing dbus-daemon and systemd-logind and see if you get anything interesting. Michael I found it interesting that I do not have a folder /org/ .hidden or not and that's with kde5 desktop on Stretch. -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - Intel G3220 - EXT4 at sda7 Registered Linux User #380263
Re: Plasma and qt apps broken after upgrade in Testing
On 10/17/2017 03:14 AM, devfra wrote: Hi list I upgraded Testing this morning and now Plasma 5 and all the qt applications are broken. Sddm does not work, it just shows me a black screen and the mouse cursor. I am also unable to start Plasma with another display manager (lightdm in my case). I am now in an xfce session, all the qt applications do not work and give me always the same error: kcalc: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current transmission-qt: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current kwrite: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current I tried to downgrade the liblgl1 and libglx0 packages to a previous version from debian snapshot but the problem remains. This [0] is the list of the packages upgraded this morning. Thanks in advance for any help. [0] https://paste.debian.net/hidden/938ee68a/ Thinks for the heads up, plasma-workspace is currently broken and of course that will break the whole kde-plasma-desktop and will get fixed soon, I hope, trust, etc. :) Thanks, -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: non-free firmware not found despite unofficial CD
On 10/13/2017 01:56 PM, Emanuel Berg wrote: Felix Miata wrote: What I would do is remove the HD currently installed, temporarily install some other HD, install Windows on that, install the BIOS update, then reinstall the original HD that has Debian already installed. Why not install XP, apply the upgrade, and install Debian? Isn't that less work than the separate HD idea? There is a Windows XP Live iso(Hiren's Boot CD) on the net with all the tools one would need to upgrade the bios and many other things and it's free and neutered too. -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Recovering accidentally deleted file folder
On 10/16/2017 08:28 AM, Richard Owlett wrote: It wasn't backed up - will have to follow advice advice I've given others ;/ I've not done file recovery since early days of WinXP. On the affected machine I'm running Stretch(9.1) with Mate desktop. The affected folders are on a partition normally mounted by a line in fstab. I immediately shut down. There is another instance of Debian on a separate partition. Logging in as root I edited fstab commenting out the appropriate line. I feel the the data is still valid - there is just no appropriate directory entries for the affected folder and its sub-directories. Guidance please. TIA I've used "testdisk" a couple of times, the last time I recovered a one TB drive and it pulled 1.6TB of stuff off of the drive, how because it will find all the partitions tables that have ever been installed. You may need to run testdisk from a cd or pen drive, you don't want to run it on a mounted drive and you need an external to save back what you want and it will take some time for it to find the stuff and for it to be coped back and of course depending on size of the drive. For me it was worth it and saved my files going back to the mid 90's. -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
bugs.debian.bug=851175
"Debian Bug report logs - #851175 plasma-workspace - All shell packages missing. This is an installation issue, please contact your distribution - missing dependency on plasma-desktop-data" I got hit with this one "All shell packages missing." while updating a Buster install today, it started with dpkg not being able to overwrite package "desktop-profiles" so instead of doing a force install I chose to purge the package and completed the update then reinstalled desktop-profiles, on reboot, after login is when I got hit with "All shell packages missing." and plasma would not start and it seems to be ambiguous from what I get searching the net, in my case the problem was package "desktop-profiles" being installed and purging desktop-profiles solved the problem and Plasma starts fine now. Why would "desktop-profiles" being installed keep plasma from starting? Upgrade-system said the system was completely updated and clean with no orphaned packages before I rebooted. -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
