[opensuse] Leap 15.0 woes -- fresh install
I'll try to be polite for this ;) why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast? why am I denied permission to run a shell script **even as the admin user**? what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management") and would someone please remind me how to get tab completion of filenames at the command line? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 4 juni 2018 02:40:13 CEST schreef Darryl Gregorash:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast?
Had no issues with the default proposals by the installer
why am I denied permission to run a shell script **even as the admin user**?
What is the exact output, and of which script?
what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management")
How would anybody know if you don't provide us with error messages, which printer driver, from where?
and would someone please remind me how to get tab completion of filenames at the command line?
Tab completion works fine on my openSUSE systems. You really have to provide more info, before any of us could reply with much more than questions. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Knurpht @ openSUSE wrote:
and would someone please remind me how to get tab completion of filenames at the command line?
Tab completion works fine on my openSUSE systems.
Semi OT, but there are some caveats. bash application dependent autocomplete has its pitfalls. E.g., tar has one, that will autocomplete only archives with known extentions. If you have an archive without proper extention, TAB will not autocomplete it. You get the impression there is no file starting with what you typed so far. Has annoyed me several times already :o -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 4 Jun 2018 11:17:34 +0100 Peter Suetterlin <pit@astro.su.se> wrote:
Knurpht @ openSUSE wrote:
and would someone please remind me how to get tab completion of filenames at the command line?
Tab completion works fine on my openSUSE systems.
Semi OT, but there are some caveats. bash application dependent autocomplete has its pitfalls. E.g., tar has one, that will autocomplete only archives with known extentions. If you have an archive without proper extention, TAB will not autocomplete it. You get the impression there is no file starting with what you typed so far.
Has annoyed me several times already :o
Yeah, I've been caught a few times like this. When did this start, instead of just tab-completing with all and any available files? Is it customisable? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 14:01, Dave Howorth wrote:
On Mon, 4 Jun 2018 11:17:34 +0100 Peter Suetterlin <> wrote:
Knurpht @ openSUSE wrote:
and would someone please remind me how to get tab completion of filenames at the command line?
Tab completion works fine on my openSUSE systems.
Semi OT, but there are some caveats. bash application dependent autocomplete has its pitfalls. E.g., tar has one, that will autocomplete only archives with known extentions. If you have an archive without proper extention, TAB will not autocomplete it. You get the impression there is no file starting with what you typed so far.
Has annoyed me several times already :o
Yeah, I've been caught a few times like this. When did this start, instead of just tab-completing with all and any available files? Is it customisable?
Yes. See /usr/share/bash-completion/*, and in this case, "/usr/share/bash-completion/completions/tar". Once bash knows that the command is "tar" it applies that configuration, and only looks for tar files. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
On 06/04/2018 07:47 AM, Carlos E. R. wrote:
Yeah, I've been caught a few times like this. When did this start, instead of just tab-completing with all and any available files? Is it customisable? Yes.
See /usr/share/bash-completion/*, and in this case, "/usr/share/bash-completion/completions/tar". Once bash knows that the command is "tar" it applies that configuration, and only looks for tar files.
So much for tab-completion just working... It seems to me it would make a whole lot more sense just to default to traditional "all" tab-completion. Then if some power-user wants to tweak the tab-completion to his liking, the feature is there. That would seem to make more sense than defaulting to some custom tab-completion config that doesn't actually do tab-completion unless you have the DOS type extension right. This reliance on file "extensions" seems to fly in the face of Linux simply having "files". A decade or so ago there was a thorough discussion of why Linux tools don't rely on file extensions for functionality. This was touted as being superior to the myriad of 'file-associations' used by windows. So if I have this straight now, our tab-completion now rejects that mindset and has reverted to using the DOS type extensions to govern whether completions are provided? That's a head-scratcher, but..., umm... OK. -- David C. Rankin, J.D.,P.E.
On 06/04/2018 04:38 PM, David C. Rankin wrote:
On 06/04/2018 07:47 AM, Carlos E. R. wrote:
Yeah, I've been caught a few times like this. When did this start, instead of just tab-completing with all and any available files? Is it customisable? Yes.
See /usr/share/bash-completion/*, and in this case, "/usr/share/bash-completion/completions/tar". Once bash knows that the command is "tar" it applies that configuration, and only looks for tar files.
So much for tab-completion just working...
It seems to me it would make a whole lot more sense just to default to traditional "all" tab-completion. Then if some power-user wants to tweak the tab-completion to his liking, the feature is there.
That would seem to make more sense than defaulting to some custom tab-completion config that doesn't actually do tab-completion unless you have the DOS type extension right.
This reliance on file "extensions" seems to fly in the face of Linux simply having "files". A decade or so ago there was a thorough discussion of why Linux tools don't rely on file extensions for functionality. This was touted as being superior to the myriad of 'file-associations' used by windows.
So if I have this straight now, our tab-completion now rejects that mindset and has reverted to using the DOS type extensions to govern whether completions are provided?
That's a head-scratcher, but..., umm... OK.
systemd-bash-completion is one of the first things I remove and make taboo. I much prefer the old behavior. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 4 Jun 2018 15:38:41 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
On 06/04/2018 07:47 AM, Carlos E. R. wrote:
Yeah, I've been caught a few times like this. When did this start, instead of just tab-completing with all and any available files? Is it customisable? Yes.
See /usr/share/bash-completion/*, and in this case, "/usr/share/bash-completion/completions/tar". Once bash knows that the command is "tar" it applies that configuration, and only looks for tar files.
So much for tab-completion just working...
Yeah, looks like too much magic to me.
It seems to me it would make a whole lot more sense just to default to traditional "all" tab-completion. Then if some power-user wants to tweak the tab-completion to his liking, the feature is there.
How do we turn it off? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 22:51, Dave Howorth wrote:
How do we turn it off?
Maybe remove the package? cer@minas-tirith:~> rpm -qf /usr/share/bash-completion/completions/tar bash-completion-2.1-16.3.noarch cer@minas-tirith:~> Or, perhaps there is a key that disables it while typing. Just guessing, but if I were the programmer I would have added it, so the real me would instead read docs to find out. The documentation file /usr/share/doc/packages/bash-completion/README says the feature can be disabled on a per user basis. There is a FAQ, and there is indeed a key that disables it. Q. The bash completion code inhibits some commands from completing on files with extensions that are legitimate in my environment. Do I have to disable completion for that command in order to complete on the files that I need to? A. No. Use M-/ to (in the words of the man page) attempt file name completion on the text to the left of the cursor. This will circumvent any file type restrictions put in place by the bash completion code. Now, find out which is the meta key. There is also a Q on tar. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
On 2018-06-04 22:38, David C. Rankin wrote:
On 06/04/2018 07:47 AM, Carlos E. R. wrote:
Yeah, I've been caught a few times like this. When did this start, instead of just tab-completing with all and any available files? Is it customisable? Yes.
See /usr/share/bash-completion/*, and in this case, "/usr/share/bash-completion/completions/tar". Once bash knows that the command is "tar" it applies that configuration, and only looks for tar files.
So much for tab-completion just working...
It seems to me it would make a whole lot more sense just to default to traditional "all" tab-completion. Then if some power-user wants to tweak the tab-completion to his liking, the feature is there.
That would seem to make more sense than defaulting to some custom tab-completion config that doesn't actually do tab-completion unless you have the DOS type extension right.
/I/ do use extension on my file names. It helps. :-) And in the case of tab completion, it would be impossible to do it without them, analysing files. Many Linux tools do use extensions, specially file browsers. Even Midnight Commander. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
On 2018-06-04 02:40, Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast?
I don't see why you can't install another one.
why am I denied permission to run a shell script **even as the admin user**?
where? which one? How? I asked my crystal ball about details of what do you mean, but it broke down and I had to sent it out for repairs. These things are very expensive, you know. So, will you instead tell us what exactly you are doing in full detail? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/03/2018 07:09 PM, Carlos E. R. wrote:> I asked my crystal ball about details of what do you mean, but it broke> down and I had to sent it out for repairs. These things are very> expensive, you know. Sorry for the delay, Carlos. It should be ready for pickup by Thursday morning. -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast?
You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp.
why am I denied permission to run a shell script **even as the admin user**?
You'll have to provide some more information. Where and how? Fyi, I have no such problem.
what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management")
YaST was rewritten in ruby, maybe that is what you're seeing.
and would someone please remind me how to get tab completion of filenames at the command line?
Works fine here. -- Per Jessen, Zürich (18.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast? You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp. Chrony is quick and dirty, emphasis on the dirty. We should at least have the option of selecting NTP, and being able to configure it in Yast. I don't mind chrony being the default, though -- that is fine for most users, I imagine, especially those who aren't experienced and might not be able to configure/use NTP to its maximum benefit. For example, can chrony connect to a local clock, eg. GPS? I don't recall that it can. why am I denied permission to run a shell script **even as the admin user**? You'll have to provide some more information. Where and how? Fyi, I have no such problem. See Jeffrey Taylor's reply, and my reply to that <mega-blush> what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management") YaST was rewritten in ruby, maybe that is what you're seeing. Yes, that was it. I must have had Yast minimized on the first try -- is
On 2018-06-03 11:32 PM, Per Jessen wrote: there any way to locate a .rpm file on disk directly from within Yast? If so, I've never found out how to do so. Now my printer/scanner drivers are installed successfully, and after a bit of hassle, the scanner function is working OK (requiredunplugging/replugging the USB cable), but the printer is still notworking. The log files show that print jobs are being sent"successfully", but they never seem to reach the printer. I've had this same issue in the past with various installs of opensuse (way back to 9.x, IIRC), and always managed to resolve them -- but I cannot recall just what I did to fix it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 4 juni 2018 18:07:09 CEST schreef Darryl Gregorash:
On 2018-06-03 11:32 PM, Per Jessen wrote:
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast?
You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp.
Chrony is quick and dirty, emphasis on the dirty. We should at least have the option of selecting NTP, and being able to configure it in Yast. I don't mind chrony being the default, though -- that is fine for most users, I imagine, especially those who aren't experienced and might not be able to configure/use NTP to its maximum benefit. For example, can chrony connect to a local clock, eg. GPS? I don't recall that it can.
why am I denied permission to run a shell script **even as the admin user**?
You'll have to provide some more information. Where and how? Fyi, I have no such problem.
See Jeffrey Taylor's reply, and my reply to that <mega-blush>
what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management")
YaST was rewritten in ruby, maybe that is what you're seeing.
Yes, that was it. I must have had Yast minimized on the first try -- is there any way to locate a .rpm file on disk directly from within Yast? If so, I've never found out how to do so. Now my printer/scanner drivers are installed successfully, and after a bit of hassle, the scanner function is working OK (requiredunplugging/replugging the USB cable), but the printer is still notworking. The log files show that print jobs are being sent"successfully", but they never seem to reach the printer. I've had this same issue in the past with various installs of opensuse (way back to 9.x, IIRC), and always managed to resolve them -- but I cannot recall just what I did to fix it.
Show us the output of lpstat -t -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 4 juni 2018 18:27:34 CEST schreef Knurpht @ openSUSE:
Op maandag 4 juni 2018 18:07:09 CEST schreef Darryl Gregorash:
On 2018-06-03 11:32 PM, Per Jessen wrote:
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast?
You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp.
Chrony is quick and dirty, emphasis on the dirty. We should at least have the option of selecting NTP, and being able to configure it in Yast. I don't mind chrony being the default, though -- that is fine for most users, I imagine, especially those who aren't experienced and might not be able to configure/use NTP to its maximum benefit. For example, can chrony connect to a local clock, eg. GPS? I don't recall that it can.
why am I denied permission to run a shell script **even as the admin user**?
You'll have to provide some more information. Where and how? Fyi, I have no such problem.
See Jeffrey Taylor's reply, and my reply to that <mega-blush>
what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management")
YaST was rewritten in ruby, maybe that is what you're seeing.
Yes, that was it. I must have had Yast minimized on the first try -- is there any way to locate a .rpm file on disk directly from within Yast? If so, I've never found out how to do so. Now my printer/scanner drivers are installed successfully, and after a bit of hassle, the scanner function is working OK (requiredunplugging/replugging the USB cable), but the printer is still notworking. The log files show that print jobs are being sent"successfully", but they never seem to reach the printer. I've had this same issue in the past with various installs of opensuse (way back to 9.x, IIRC), and always managed to resolve them -- but I cannot recall just what I did to fix it.
Show us the output of lpstat -t Also, what downloaded driver rpm is installed ?
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 10:29 AM, Knurpht @ openSUSE wrote:
Op maandag 4 juni 2018 18:27:34 CEST schreef Knurpht @ openSUSE:
Op maandag 4 juni 2018 18:07:09 CEST schreef Darryl Gregorash:
On 2018-06-03 11:32 PM, Per Jessen wrote:
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast? You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp. Chrony is quick and dirty, emphasis on the dirty. We should at least have the option of selecting NTP, and being able to configure it in Yast. I don't mind chrony being the default, though -- that is fine for most users, I imagine, especially those who aren't experienced and might not be able to configure/use NTP to its maximum benefit. For example, can chrony connect to a local clock, eg. GPS? I don't recall that it can.
why am I denied permission to run a shell script **even as the admin user**? You'll have to provide some more information. Where and how? Fyi, I have no such problem. See Jeffrey Taylor's reply, and my reply to that <mega-blush>
what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management") YaST was rewritten in ruby, maybe that is what you're seeing. Yes, that was it. I must have had Yast minimized on the first try -- is there any way to locate a .rpm file on disk directly from within Yast? If so, I've never found out how to do so. Now my printer/scanner drivers are installed successfully, and after a bit of hassle, the scanner function is working OK (requiredunplugging/replugging the USB cable), but the printer is still notworking. The log files show that print jobs are being sent"successfully", but they never seem to reach the printer. I've had this same issue in the past with various installs of opensuse (way back to 9.x, IIRC), and always managed to resolve them -- but I cannot recall just what I did to fix it. Show us the output of lpstat -t Also, what downloaded driver rpm is installed ?
Driver is from Brother, latest for DCP-7040 printer:brdcp7040lpr-2.0.2-1.i386 Installation also requires this rpm: cupswrapperDCP7040-2.0.2-1.i386 Output of lpstat: ~ # lpstat -t scheduler is running system default destination: DCP7040 device for DCP7040: usb://Brother/DCP-7040?serial=000F9N210911 DCP7040 accepting requests since Mon Jun 4 09:11:56 2018 printer DCP7040 is idle. enabled since Mon Jun 4 09:11:56 2018 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 4 juni 2018 19:02:39 CEST schreef Darryl Gregorash:
On 2018-06-04 10:29 AM, Knurpht @ openSUSE wrote:
Op maandag 4 juni 2018 18:27:34 CEST schreef Knurpht @ openSUSE:
Op maandag 4 juni 2018 18:07:09 CEST schreef Darryl Gregorash:
On 2018-06-03 11:32 PM, Per Jessen wrote:
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast?
You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp.
Chrony is quick and dirty, emphasis on the dirty. We should at least have the option of selecting NTP, and being able to configure it in Yast. I don't mind chrony being the default, though -- that is fine for most users, I imagine, especially those who aren't experienced and might not be able to configure/use NTP to its maximum benefit. For example, can chrony connect to a local clock, eg. GPS? I don't recall that it can.
why am I denied permission to run a shell script **even as the admin user**?
You'll have to provide some more information. Where and how? Fyi, I have no such problem.
See Jeffrey Taylor's reply, and my reply to that <mega-blush>
what is ruby doing that is so important that it blocks me from installing a rpm that I have downloaded (drivers for my printer)? (popup appears yammering something about "system management")
YaST was rewritten in ruby, maybe that is what you're seeing.
Yes, that was it. I must have had Yast minimized on the first try -- is there any way to locate a .rpm file on disk directly from within Yast? If so, I've never found out how to do so. Now my printer/scanner drivers are installed successfully, and after a bit of hassle, the scanner function is working OK (requiredunplugging/replugging the USB cable), but the printer is still notworking. The log files show that print jobs are being sent"successfully", but they never seem to reach the printer. I've had this same issue in the past with various installs of opensuse (way back to 9.x, IIRC), and always managed to resolve them -- but I cannot recall just what I did to fix it.
Show us the output of lpstat -t
Also, what downloaded driver rpm is installed ?
Driver is from Brother, latest for DCP-7040 printer:brdcp7040lpr-2.0.2-1.i386
Installation also requires this rpm: cupswrapperDCP7040-2.0.2-1.i386
Output of lpstat: ~ # lpstat -t
h
scheduler is running
system default destination: DCP7040
device for DCP7040: usb://Brother/DCP-7040?serial=000F9N210911
DCP7040 accepting requests since Mon Jun 4 09:11:56 2018
printer DCP7040 is idle. enabled since Mon Jun 4 09:11:56 2018
Apart from the driver package and the cupswrapper package being 32bit, the output looks normal. What does lpstat -W all give? Anything in the dmesg output ? -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 12:27 PM, Knurpht @ openSUSE wrote:
Op maandag 4 juni 2018 19:02:39 CEST schreef Darryl Gregorash:
Op maandag 4 juni 2018 18:27:34 CEST schreef Knurpht @ openSUSE:
Op maandag 4 juni 2018 18:07:09 CEST schreef Darryl Gregorash:
On 2018-06-03 11:32 PM, Per Jessen wrote:
Darryl Gregorash wrote: > I'll try to be polite for this ;) > > why do I have to run chrony? why can I not use a decent NTP client, > and be able to configure it in Yast? You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp. Chrony is quick and dirty, emphasis on the dirty. We should at least have the option of selecting NTP, and being able to configure it in Yast. I don't mind chrony being the default, though -- that is fine for most users, I imagine, especially those who aren't experienced and might not be able to configure/use NTP to its maximum benefit. For example, can chrony connect to a local clock, eg. GPS? I don't recall that it can.
> why am I denied permission to run a shell script **even as the admin > user**? You'll have to provide some more information. Where and how? Fyi, I have no such problem. See Jeffrey Taylor's reply, and my reply to that <mega-blush>
> what is ruby doing that is so important that it blocks me from > installing a rpm that I have downloaded (drivers for my printer)? > (popup appears yammering something about "system management") YaST was rewritten in ruby, maybe that is what you're seeing. Yes, that was it. I must have had Yast minimized on the first try -- is there any way to locate a .rpm file on disk directly from within Yast? If so, I've never found out how to do so. Now my printer/scanner drivers are installed successfully, and after a bit of hassle, the scanner function is working OK (requiredunplugging/replugging the USB cable), but the printer is still notworking. The log files show that print jobs are being sent"successfully", but they never seem to reach the printer. I've had this same issue in the past with various installs of opensuse (way back to 9.x, IIRC), and always managed to resolve them -- but I cannot recall just what I did to fix it. Show us the output of lpstat -t Also, what downloaded driver rpm is installed ? Driver is from Brother, latest for DCP-7040
On 2018-06-04 10:29 AM, Knurpht @ openSUSE wrote: printer:brdcp7040lpr-2.0.2-1.i386
Installation also requires this rpm: cupswrapperDCP7040-2.0.2-1.i386
Output of lpstat: ~ # lpstat -t
h
scheduler is running
system default destination: DCP7040
device for DCP7040: usb://Brother/DCP-7040?serial=000F9N210911
DCP7040 accepting requests since Mon Jun 4 09:11:56 2018
printer DCP7040 is idle. enabled since Mon Jun 4 09:11:56 2018
Apart from the driver package and the cupswrapper package being 32bit, the output looks normal. What does lpstat -W all give? ~ # lpstat -W all DCP7040-1 root 17408 Mon Jun 4 08:15:45 2018 DCP7040-2 root 17408 Mon Jun 4 08:18:36 2018 DCP7040-6 root 17408 Mon Jun 4 09:06:30 2018
Anything in the dmesg output ? Nothing that I can see. There are lots of references to the printer. I believe this is everything after, and including, the point where I unplugged/replugged the USB cable:
[ 7124.948792] usb 9-3: USB disconnect, device number 3 [ 7124.949101] usblp0: removed [ 7134.521917] usb 9-3: new full-speed USB device number 6 using ohci-pci [ 7134.723450] usb 9-3: New USB device found, idVendor=04f9, idProduct=01e9 [ 7134.723460] usb 9-3: New USB device strings: Mfr=0, Product=0, SerialNumber=3 [ 7134.723464] usb 9-3: SerialNumber: 000F9N210911 [ 7134.730610] usblp 9-3:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 0 proto 2 vid 0x04F9 pid 0x01E9 [ 7139.823004] usblp0: removed [ 7139.838567] usblp 9-3:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 0 proto 2 vid 0x04F9 pid 0x01E9 [ 7194.670789] usb 9-3: usbfs: interface 0 claimed by usblp while 'xsane' sets config #1 [ 7194.670798] usb 9-3: usbfs: process 6205 (xsane) did not claim interface 1 before use [ 7200.115042] usb 9-3: usbfs: interface 0 claimed by usblp while 'xsane' sets config #1 [ 7200.115046] usb 9-3: usbfs: process 6205 (xsane) did not claim interface 1 before use [ 7256.137329] usb 9-3: usbfs: interface 0 claimed by usblp while 'xsane' sets config #1 [ 7256.137334] usb 9-3: usbfs: process 6205 (xsane) did not claim interface 1 before use [ 7312.529218] usblp0: removed [ 7315.042766] usblp 9-3:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 0 proto 2 vid 0x04F9 pid 0x01E9 [ 7521.520307] usblp0: removed [ 7521.536867] usblp 9-3:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 0 proto 2 vid 0x04F9 pid 0x01E9 [ 7849.189819] usblp0: removed [ 7849.453198] usblp 9-3:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 0 proto 2 vid 0x04F9 pid 0x01E9 [ 8173.419237] usblp0: removed [ 8175.932487] usblp 9-3:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 0 proto 2 vid 0x04F9 pid 0x01E9 Before that point, the printer shows up frequently as USB dev 3, but I am fairly sure that is before I managed to install the drivers. Maybe I should reboot this thing to see if that does anything? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
DCP7040: A friend used this "http://support.brother.com/g/b/downloadend.aspx? c=us&lang=en&prod=dcp7040_us_as&os=127&dlid=dlf006893_000&flang=4&type3=625" installer and has the printer working on Leap 42.3 . It might be something in
Op maandag 4 juni 2018 21:57:49 CEST schreef Darryl Gregorash: the 32bit rpms. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 02:11 PM, Knurpht @ openSUSE wrote:
http://support.brother.com/g/b/downloadend.aspx? c=us&lang=en&prod=dcp7040_us_as&os=127&dlid=dlf006893_000&flang=4&type3=625" OK, thanks. I'll give it a try -- probably not until tomorrow, though. I'm thinking it's likely best to run it on a clean install (meaning remove the driver rpms first, and maybe also unplug the printer cable) so as to avoid creating any more issues.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 4 juni 2018 22:38:42 CEST schreef Darryl Gregorash:
On 2018-06-04 02:11 PM, Knurpht @ openSUSE wrote:
http://support.brother.com/g/b/downloadend.aspx? c=us&lang=en&prod=dcp7040_us_as&os=127&dlid=dlf006893_000&flang=4&type3=62 5" OK, thanks. I'll give it a try -- probably not until tomorrow, though. I'm thinking it's likely best to run it on a clean install (meaning remove the driver rpms first, and maybe also unplug the printer cable) so as to avoid creating any more issues. That would be my strategy too.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 03:31 PM, Knurpht @ openSUSE wrote:
Op maandag 4 juni 2018 22:38:42 CEST schreef Darryl Gregorash:
On 2018-06-04 02:11 PM, Knurpht @ openSUSE wrote:
http://support.brother.com/g/b/downloadend.aspx? c=us&lang=en&prod=dcp7040_us_as&os=127&dlid=dlf006893_000&flang=4&type3=62 5" OK, thanks. I'll give it a try -- probably not until tomorrow, though. I'm thinking it's likely best to run it on a clean install (meaning remove the driver rpms first, and maybe also unplug the printer cable) so as to avoid creating any more issues. That would be my strategy too.
(Should I start a new thread on this?) I've run the script after deleting the rpms in Yast and disconnecting the printer. Here are the outputs of lpstat as per your previous messages: ~ # lpstat -t scheduler is running no system default destination device for DCP7040: usb:/dev/usb/lp0 DCP7040 accepting requests since Tue Jun 5 08:08:27 2018 printer DCP7040 is idle. enabled since Tue Jun 5 08:08:27 2018 static24-72-0-229:~ # lpstat -W all DCP7040-8 root 17408 Tue Jun 5 08:02:04 2018 static24-72-0-229:~ # No significant differences from before, except now there is no system default, and lpstat -W only shows one instance of the printer (previously there were 3). A test print from Yast went successfully to the print queue, but CUPS (browser interface) showed that the job was waiting for the printer to become available. I cancelled the print job, powered down the printer, then after turning it back down, tried a job in CUPS. That too sat waiting for the printer to become available. dmesg output shows pretty much the same as my previous message. The script seemed to run OK, except for one thing: at one point it asked for a device URI. The default response was "yes", but with a disconnected printer, how could there be a URI? Besides which, even if the printer had been connected to the system, I have no idea what its URI might be. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
ISP mail servers were down for awhile today, and I did (despite what they promised) lose a few emails here, including the most recent one on this thread, and Carlos's and jdd's replies to that. So (thank <insert deity name here> for the list archives)... for Carlos: su won't work if you're trying to use the web interface.. logging in as root in a separate X session is out for philosophical/political reasons ;) for jdd: that did it, thanks.. and it's "root", not the user. You get one crack at it, and that is all -- I think that may be per session, but not really too sure. I booted up in the old OS installation to check the printer there, to be sure it's not a hardware error.. printer works. I'm in the process of comparing all the old vs. new config files to see what, if any, changes I might have had to make in 42.x to get this thing working. Nothing so far. I'll get back to this later, for now I have other things to deal with. Just as an aside (this was one of those "other things").. I used to have a APC UPS for my system, and was using the apcupsd package. Now I have a CyberPower unit, so I wanted to switch to NUT... what a nightmare trying to configure that so I could get any info out of it. On that reboot into 42.1 (yes, I was still running that old thing), I discovered quite by accident that apcupsd is quite happy talking to the CyberPower UPS, though the power usage seems to have gone up quite a bit. No idea why that is, but at least I have a working UPS monitor again. So it would seem that apcupsd is a viable solution for quite a few UPSes, even if APC didn't build them. Just a FWIW for anyone else who's a bit intimidated by NUT. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Trying to get this printer working became too frustrating, so I went looking for alternative solutions. It didn't take too long to find one at http://www.openprinting.org/drivers -- the brlasers driver package (rpm package printer-driver-brlaser included in Leap 15.0 distribution) contains at least 2 drivers that I have now verified to work with the DCP7040. The drivers in the package are written for 4 different printers, but I have verified the DCP1510 and DCP7030 drivers work acceptably well with the 7040. For anyone with this printer choosing to go this route, selecting these drivers in Yast is a little cumbersome; it is probably far easier to make the selection in the CUPS web interface -- but remember, when prompted, you will need to log into CUPS as /root/ and not as your user account. There are quite a few alternatives also available in Yast itself, for example several of the gutenberg drivers. These are a lot easier to install on this printer, but I didn't try them. Perhaps I'll test them out sometime (or maybe not). Thanks to all for all the help, and sorry for the short-tempered opening post of this thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
PS, could someone please remind me how I add myself as an administrator in CUPS so I can do meaningful work in that? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 05/06/2018 à 16:52, Carlos E. R. a écrit :
On 2018-06-05 16:38, Darryl Gregorash wrote:
PS, could someone please remind me how I add myself as an administrator in CUPS so I can do meaningful work in that?
Su to root first?
no, simply give root pass (or user pass, I don't remember) when cups ask jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Darryl Gregorash wrote:
On 2018-06-03 11:32 PM, Per Jessen wrote:
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast? You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp.
Chrony is quick and dirty, emphasis on the dirty. We should at least have the option of selecting NTP, and being able to configure it in Yast.
I don't mind having to configure ntp myself, it's not a big deal. I can understand the YaST team not wanting to spend the effort on maintaining two different sets of code.
might not be able to configure/use NTP to its maximum benefit. For example, can chrony connect to a local clock, eg. GPS? I don't recall that it can.
No, I don't think so. It doesn't do ipv6 multicast either. The reasons for using chrony are mostly to do with security, I believe. In a closed environment with a local reference clock I don't think chrony is the right thing. -- Per Jessen, Zürich (19.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 05 Jun 2018, Per Jessen wrote:
No, I don't think so. It doesn't do ipv6 multicast either. The reasons for using chrony are mostly to do with security, I believe. In a closed environment with a local reference clock I don't think chrony is the right thing.
In the past I've used chrony for machines that are only intermittently online. Ntpd didn't copy too well when the offline clocks drifted too far from the reference clock. When connectivity is restored, chrony is able to smoothly bring the clocks back into sync. So chrony would also be a good default if the connectivity of the box is unknown. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Michael Hamilton wrote:
On Tue, 05 Jun 2018, Per Jessen wrote:
No, I don't think so. It doesn't do ipv6 multicast either. The reasons for using chrony are mostly to do with security, I believe. In a closed environment with a local reference clock I don't think chrony is the right thing.
In the past I've used chrony for machines that are only intermittently online. Ntpd didn't copy too well when the offline clocks drifted too far from the reference clock. When connectivity is restored, chrony is able to smoothly bring the clocks back into sync. So chrony would also be a good default if the connectivity of the box is unknown.
s/unknown/unreliable/ ? Yes, I believe that is one significant advantage of chrony. -- Per Jessen, Zürich (17.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 05 Jun 2018, Per Jessen wrote:
Michael Hamilton wrote:
On Tue, 05 Jun 2018, Per Jessen wrote:
No, I don't think so. It doesn't do ipv6 multicast either. The reasons for using chrony are mostly to do with security, I believe. In a closed environment with a local reference clock I don't think chrony is the right thing.
In the past I've used chrony for machines that are only intermittently online. Ntpd didn't copy too well when the offline clocks drifted too far from the reference clock. When connectivity is restored, chrony is able to smoothly bring the clocks back into sync. So chrony would also be a good default if the connectivity of the box is unknown.
s/unknown/unreliable/ ?
Yes, I believe that is one significant advantage of chrony.
-- Per Jessen, Zürich (17.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
Sorry I should have been clearer - I meant that the reliability of the link is unknown to the installer. It seems safer to have the installer assume the worst in this instance. I guess a well annotated tick box in the installer would be another possible solution. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 18:07, Darryl Gregorash wrote:
On 2018-06-03 11:32 PM, Per Jessen wrote:
Darryl Gregorash wrote:
YaST was rewritten in ruby, maybe that is what you're seeing. Yes, that was it. I must have had Yast minimized on the first try -- is there any way to locate a .rpm file on disk directly from within Yast? If so, I've never found out how to do so.
You can call sw_single and tell it to install a given rpm, but I have not used this syntax in several years so I don't know if it still works. --help doesn't mention it. What I do is create a directory and put rpms inside, then use YaST module to configure repositories to tell it that "that" directory is a repository. From that point, that directory is another repo, and both yast and zypper will consider it automatically, handling also updates. If you do not do that, yast will show that rpm in red as orphaned. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
On 4 June 2018 at 07:32, Per Jessen <per@computer.org> wrote:
Darryl Gregorash wrote:
I'll try to be polite for this ;)
why do I have to run chrony? why can I not use a decent NTP client, and be able to configure it in Yast?
You don't have to, just deselect chrony and select ntp, but you'll have to configure your ntp manually. I don't know the reasoning for the switch to Chrony. I'm also sticking to ntp.
Chrony is infinitely more flexible and reliable in real world scenarios where network connectivity is not always guaranteed Laptops, cluster nodes, containers, VMs, systems with software defined networks, all benefit from chrony and all risk serious disruption with ntpd when networks go wrong and ntpd fails to handle it gracefully Nothing wrong with sticking with ntpd as an informed choice but a good default works in more scenarios in the real-world than the alternatives That is something which is unquestionably true with chrony vs ntpd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Quoting Darryl Gregorash <raven@accesscomm.ca>:
I'll try to be polite for this ;)
[snip]
why am I denied permission to run a shell script **even as the admin user**?
Is the execute bit set? What is the exact error message? Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 08:43 AM, Jeffrey L. Taylor wrote:
Quoting Darryl Gregorash <raven@accesscomm.ca>:
I'll try to be polite for this ;)
[snip]
why am I denied permission to run a shell script **even as the admin user**?
Is the execute bit set? What is the exact error message?
Jeffrey
DOH! I am ***so*** embarrassed! I downloaded this thing ages ago and forget to set that bit.. then yesterday, forgot all about checking it. That has also taken care of the tab completion problem, TYVM for the reminder. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (13)
-
Carlos E. R. -
Darryl Gregorash -
Dave Howorth -
David C. Rankin -
Fraser_Bell -
jdd＠dodin.org -
Jeffrey L. Taylor -
Knurpht ＠ openSUSE -
Mark Hounschell -
Michael Hamilton -
Per Jessen -
Peter Suetterlin -
Richard Brown