Re: [opensuse] Three Seconds
On Tue, 2016-11-29 at 07:14 -0500, Mark Misulich wrote:
I have attached four dmesg -w outputs. 1. I disconnected the usb cable last night to be able to shut down the printer overnight. This output is before I reconnected the cable to the printer this morning. The power was shut off last night with the power button after I disconnected the usb cable. 2. After I reconnected the usb cable this morning, the printer started up automatically. This is the output. 3. In the three seconds after I used the power button to shut down the printer, this is the output before the printer restarted automatically. 4. This is the output after the printer restarted automatically.
On 2016-11-29 15:16, Mark Misulich wrote:
On Tue, 2016-11-29 at 07:14 -0500, Mark Misulich wrote:
I have attached four dmesg -w outputs.
1. I disconnected the usb cable last night to be able to shut down the printer overnight. This output is before I reconnected the cable to the printer this morning. The power was shut off last night with the power button after I disconnected the usb cable.
2. After I reconnected the usb cable this morning, the printer started up automatically. This is the output.
3. In the three seconds after I used the power button to shut down the printer, this is the output before the printer restarted automatically.
4. This is the output after the printer restarted automatically.
It is a bit confusing, because you posted the entire dmesg. What is wanted is only the new text that appears after triggering the problem. You can use, in a terminal: dmesg --follow --reltime Then press enter twice to add two empty lines, and do your thing with the printer. Powering it down and waiting the three seconds till it comes up again suffices, I think. Then select with the mouse the new text that appeared after the two empty lines. You can do the same with "journalctl --follow". Output may be different - it is in my machine. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-11-29 15:16, Mark Misulich wrote:
On Tue, 2016-11-29 at 07:14 -0500, Mark Misulich wrote:
I have attached four dmesg -w outputs.
It is a bit confusing, because you posted the entire dmesg. What is wanted is only the new text that appears after triggering the problem.
You can use, in a terminal:
dmesg --follow --reltime
Then press enter twice to add two empty lines, and do your thing with the printer. Powering it down and waiting the three seconds till it comes up again suffices, I think.
Then select with the mouse the new text that appeared after the two empty lines. Here is the output [Nov29 10:23] usb 4-1.4: USB disconnect, device number 4 [ +0.000289] usblp0: removed [Nov29 10:24] usb 4-1.4: new full-speed USB device number 5 using uhci_hcd [ +0.159283] usb 4-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 4-1.4: Product: DeskJet 970C [ +0.000002] usb 4-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 4-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011188] usblp 4-1.4:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.141187] usblp0: removed
You can do the same with "journalctl --follow". Output may be different - it is in my machine. journalctl --follow Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. -- Logs begin at Mon 2016-11-21 12:49:06 EST. -- Nov 29 09:57:13 linux org.a11y.atspi.Registry[2050]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Nov 29 09:57:13 linux org.freedesktop.secrets[1757]: gnome-keyring- daemon: insufficient process capabilities, unsecure memory might get used Nov 29 09:57:13 linux gnome-keyring-daemon[2074]: couldn't access control socket: /run/user/1000/keyring/control: No such file or
On Tue, 2016-11-29 at 16:15 +0100, Carlos E. R. wrote: directory Nov 29 09:57:13 linux org.freedesktop.secrets[1757]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Nov 29 09:57:13 linux org.gnome.OnlineAccounts[1757]: goa-daemon- Message: goa-daemon version 3.20.4 starting Nov 29 09:57:18 linux org.freedesktop.Telepathy.ConnectionManager.sofiasip[1757]: tp-glib- Message: Exiting Nov 29 09:57:18 linux org.freedesktop.Telepathy.ConnectionManager.haze[1757]: tp-glib- Message: Exiting Nov 29 10:21:20 linux gnome-keyring-daemon[2074]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered Nov 29 10:21:20 linux org.freedesktop.secrets[1757]: ** (gnome-keyring- daemon:2074): WARNING **: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered Nov 29 10:22:12 linux systemd-coredump[2987]: Process 2910 (evolution) of user 1000 dumped core. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-29 16:31, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:15 +0100, Carlos E. R. wrote:
Then select with the mouse the new text that appeared after the two empty lines. Here is the output
I'll edit to unwrap.
[Nov29 10:23] usb 4-1.4: USB disconnect, device number 4 [ +0.000289] usblp0: removed [Nov29 10:24] usb 4-1.4: new full-speed USB device number 5 using uhci_hcd [ +0.159283] usb 4-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 4-1.4: Product: DeskJet 970C [ +0.000002] usb 4-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 4-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011188] usblp 4-1.4:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.141187] usblp0: removed
Appears to see the new connection of the USB device. First it disconnect, then it connects again. It is blaming the printer. It also appears to be using the usblp translation ??
You can do the same with "journalctl --follow". Output may be different - it is in my machine.
journalctl --follow Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice.
Huh. You have to do this as root, or add your user to the 'systemd-journal', and log in again.
-- Logs begin at Mon 2016-11-21 12:49:06 EST. -- Nov 29 09:57:13 linux org.a11y.atspi.Registry[2050]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Nov 29 09:57:13 linux org.freedesktop.secrets[1757]: gnome-keyring- daemon: insufficient process capabilities, unsecure memory might get used Nov 29 09:57:13 linux gnome-keyring-daemon[2074]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Nov 29 09:57:13 linux org.freedesktop.secrets[1757]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Nov 29 09:57:13 linux org.gnome.OnlineAccounts[1757]: goa-daemon- Message: goa-daemon version 3.20.4 starting Nov 29 09:57:18 linux org.freedesktop.Telepathy.ConnectionManager.sofiasip[1757]: tp-glib- Message: Exiting Nov 29 09:57:18 linux org.freedesktop.Telepathy.ConnectionManager.haze[1757]: tp-glib- Message: Exiting Nov 29 10:21:20 linux gnome-keyring-daemon[2074]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered Nov 29 10:21:20 linux org.freedesktop.secrets[1757]: ** (gnome-keyring- daemon:2074): WARNING **: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered Nov 29 10:22:12 linux systemd-coredump[2987]: Process 2910 (evolution) of user 1000 dumped core.
The event is not displayed, it happened at 10:23, probably because the warning printed above. You have to "su -" first. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tue, 2016-11-29 at 16:49 +0100, Carlos E. R. wrote:
On 2016-11-29 16:31, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:15 +0100, Carlos E. R. wrote:
Then select with the mouse the new text that appeared after the two empty lines.
Here is the output
I'll edit to unwrap.
[Nov29 10:23] usb 4-1.4: USB disconnect, device number 4 [ +0.000289] usblp0: removed [Nov29 10:24] usb 4-1.4: new full-speed USB device number 5 using uhci_hcd [ +0.159283] usb 4-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 4-1.4: Product: DeskJet 970C [ +0.000002] usb 4-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 4-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011188] usblp 4-1.4:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.141187] usblp0: removed
Appears to see the new connection of the USB device. First it disconnect, then it connects again. It is blaming the printer.
It also appears to be using the usblp translation ??
dmesg --follow --reltime as root [Nov29 12:25] usb 2-1.4: USB disconnect, device number 5 [ +1.869142] usb 2-1.4: new full-speed USB device number 6 using uhci_hcd [ +0.157939] usb 2-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 2-1.4: Product: DeskJet 970C [ +0.000002] usb 2-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 2-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011221] usblp 2-1.4:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.139999] usblp0: removed
You can do the same with "journalctl --follow". Output may be different - it is in my machine.
journalctl --follow Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice.
Huh. You have to do this as root, or add your user to the 'systemd-journal', and log in again.
The event is not displayed, it happened at 10:23, probably because the warning printed above. You have to "su -" first.
journalcntl --follow as root # journalcntl --follow If 'journalcntl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journalcntl # cnf journalcntl journalcntl: command not found
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-29 18:36, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:49 +0100, Carlos E. R. wrote:
On 2016-11-29 16:31, Mark Misulich wrote:
Appears to see the new connection of the USB device. First it disconnect, then it connects again. It is blaming the printer.
It also appears to be using the usblp translation ??
dmesg --follow --reltime as root
[Nov29 12:25] usb 2-1.4: USB disconnect, device number 5 [ +1.869142] usb 2-1.4: new full-speed USB device number 6 using uhci_hcd [ +0.157939] usb 2-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 2-1.4: Product: DeskJet 970C [ +0.000002] usb 2-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 2-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011221] usblp 2-1.4:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.139999] usblp0: removed
Well, nothing new. The printer powers up, then the USB appears and is detected. Does not show what is done to wake it up.
journalctl --follow Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice.
Huh. You have to do this as root, or add your user to the 'systemd-journal', and log in again.
The event is not displayed, it happened at 10:23, probably because the warning printed above. You have to "su -" first.
journalcntl --follow as root
No, notice the extra "n". ctl, not cntl. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tue, 2016-11-29 at 19:40 +0100, Carlos E. R. wrote:
On 2016-11-29 18:36, Mark Misulich wrote: I think that I got the automatic power on problem fixed. I was reading in a configuration file for HP that Leap 42.2 is not supported. So I used yast to remove any program with an HP in the title.
Then I reinstalled the printer using a cups driver for the printer, without using HP Setup. Power button seems to work normally now, no automatic turn on after three seconds. The printer prints normally but must be turned on manually to print, no automatic turn on when the print command is given for a job. Thanks for everyone's help! Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-30 18:30, Mark Misulich wrote:
On Tue, 2016-11-29 at 19:40 +0100, Carlos E. R. wrote:
On 2016-11-29 18:36, Mark Misulich wrote: I think that I got the automatic power on problem fixed. I was reading in a configuration file for HP that Leap 42.2 is not supported. So I used yast to remove any program with an HP in the title.
Then I reinstalled the printer using a cups driver for the printer, without using HP Setup. Power button seems to work normally now, no automatic turn on after three seconds. The printer prints normally but must be turned on manually to print, no automatic turn on when the print command is given for a job.
Well, that's what I told you, that some hp printers can be configured without hplip -- I'm unsure if I got the spelling right ;-) As long as a printer speaks postscript, it can be done without a driver. So, your printer has a function to be turned on from software, and previously you were using that. Now, you have to use the button. Well, it is very probably that HP feature which is broken now in software. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wed, 2016-11-30 at 20:00 +0100, Carlos E. R. wrote:
On 2016-11-30 18:30, Mark Misulich wrote:
On Tue, 2016-11-29 at 19:40 +0100, Carlos E. R. wrote:
On 2016-11-29 18:36, Mark Misulich wrote:
I think that I got the automatic power on problem fixed. I was reading in a configuration file for HP that Leap 42.2 is not supported. So I used yast to remove any program with an HP in the title.
Then I reinstalled the printer using a cups driver for the printer, without using HP Setup. Power button seems to work normally now, no automatic turn on after three seconds. The printer prints normally but must be turned on manually to print, no automatic turn on when the print command is given for a job.
Well, that's what I told you, that some hp printers can be configured without hplip -- I'm unsure if I got the spelling right ;-)
Thanks for bringing that to my attention again. I didn't understand the import of what you were saying when you originally wrote that to me, as I probably still don't. Sorry about my lack of understanding. I don't know what hplip stands for or what it does. I did reply to you originally that I thought that printer installation in Yast pulled in hplip as a dependency. I had originally used an hp driver called something like HP970 hp***, which I don't find in Yast now so I can't provide the correct driver name. During that installation without using HPsetup, it pulled in hplip and other hp*'s as dependencies. Since that driver caused a problem with the power starting, I changed drivers to the CUPS + gutenprint, and later another driver. Neither driver fixed the power issue. So then I ran HPsetup, which also didn't fix the problem, and led to me posting on the mailing list. Thanks again for your help in trying to resolve this, it is much appreciated.
As long as a printer speaks postscript, it can be done without a driver.
So, your printer has a function to be turned on from software, and previously you were using that. Now, you have to use the button. Well, it is very probably that HP feature which is broken now in software.
Agreed. It is just a minor issue to turn on the printer manually to print. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-30 20:57, Mark Misulich wrote:
On Wed, 2016-11-30 at 20:00 +0100, Carlos E. R. wrote:
On 2016-11-30 18:30, Mark Misulich wrote:
On Tue, 2016-11-29 at 19:40 +0100, Carlos E. R. wrote:
On 2016-11-29 18:36, Mark Misulich wrote:
I think that I got the automatic power on problem fixed. I was reading in a configuration file for HP that Leap 42.2 is not supported. So I used yast to remove any program with an HP in the title.
Then I reinstalled the printer using a cups driver for the printer, without using HP Setup. Power button seems to work normally now, no automatic turn on after three seconds. The printer prints normally but must be turned on manually to print, no automatic turn on when the print command is given for a job.
Well, that's what I told you, that some hp printers can be configured without hplip -- I'm unsure if I got the spelling right ;-)
Thanks for bringing that to my attention again. I didn't understand the import of what you were saying when you originally wrote that to me, as I probably still don't. Sorry about my lack of understanding. I don't know what hplip stands for or what it does.
No problem, don't worry :-) hplip is the HP software for handling their printers. It is open source, thus it is included in the distro, and the installation is suggested/done by YaST when you say you are going to configure an HP printer.
I did reply to you originally that I thought that printer installation in Yast pulled in hplip as a dependency. I had originally used an hp driver called something like HP970 hp***, which I don't find in Yast now so I can't provide the correct driver name. During that installation without using HPsetup, it pulled in hplip and other hp*'s as dependencies.
Yes, that is so.
Since that driver caused a problem with the power starting, I changed drivers to the CUPS + gutenprint, and later another driver. Neither driver fixed the power issue. So then I ran HPsetup, which also didn't fix the problem, and led to me posting on the mailing list.
Thanks again for your help in trying to resolve this, it is much appreciated.
Welcome.
As long as a printer speaks postscript, it can be done without a driver.
So, your printer has a function to be turned on from software, and previously you were using that. Now, you have to use the button. Well, it is very probably that HP feature which is broken now in software.
Agreed. It is just a minor issue to turn on the printer manually to print.
You will just have to watch out for things like paper margins and some other things, maybe they are not fully correct. You might report all this in a bugzilla. Or perhaps to the hplip people directly. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tuesday, 29 November 2016 12:36:04 GMT Mark Misulich wrote:
On Tue, 2016-11-29 at 16:49 +0100, Carlos E. R. wrote:
On 2016-11-29 16:31, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:15 +0100, Carlos E. R. wrote:
Then select with the mouse the new text that appeared after the two empty lines.
Here is the output
I'll edit to unwrap.
[Nov29 10:23] usb 4-1.4: USB disconnect, device number 4 [ +0.000289] usblp0: removed [Nov29 10:24] usb 4-1.4: new full-speed USB device number 5 using uhci_hcd [ +0.159283] usb 4-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 4-1.4: Product: DeskJet 970C [ +0.000002] usb 4-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 4-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011188] usblp 4-1.4:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.141187] usblp0: removed
Appears to see the new connection of the USB device. First it disconnect, then it connects again. It is blaming the printer.
It also appears to be using the usblp translation ??
dmesg --follow --reltime as root
[Nov29 12:25] usb 2-1.4: USB disconnect, device number 5 [ +1.869142] usb 2-1.4: new full-speed USB device number 6 using uhci_hcd [ +0.157939] usb 2-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 2-1.4: Product: DeskJet 970C [ +0.000002] usb 2-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 2-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011221] usblp 2-1.4:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.139999] usblp0: removed
You can do the same with "journalctl --follow". Output may be different - it is in my machine.
journalctl --follow Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice.
Huh. You have to do this as root, or add your user to the 'systemd-journal', and log in again.
The event is not displayed, it happened at 10:23, probably because the warning printed above. You have to "su -" first.
journalcntl --follow as root
# journalcntl --follow If 'journalcntl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journalcntl
# cnf journalcntl journalcntl: command not found
Journlactl -- opensuse:tumbleweed:20161125 Qt: 5.7.0 KDE Frameworks: 5.28.0 KDE Plasma: 5.8.4 kwin5-5.8.4-171.1.x86_64 kmail5-16.08.3-1.1.x86_64 Kernel: 4.8.10-1-default Nouveau: 1.0.13_2.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/30/2016 04:27 AM, ianseeks wrote:
# cnf journalcntl journalcntl: command not found
Journlactl
# LOL If 'LOL' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf LOL Mainbox:~ # cnf LOL LOL: command not found -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, 30 November 2016 07:06:55 GMT Anton Aylward wrote:
On 11/30/2016 04:27 AM, ianseeks wrote:
# cnf journalcntl journalcntl: command not found
Journlactl
Oops, i can't spell journalctl either....
# LOL If 'LOL' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf LOL Mainbox:~ # cnf LOL LOL: command not found
> Q: Are you sure? > >> A: Because it reverses the logical flow of conversation. >> >>> Q: Why is top posting frowned upon?
-- opensuse:tumbleweed:20161128 Qt: 5.7.0 KDE Frameworks: 5.28.0 KDE Plasma: 5.8.4 kwin5-5.8.4-171.1.x86_64 kmail5-16.08.3-1.1.x86_64 Kernel: 4.8.10-1-default Nouveau: 1.0.13_2.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/30/2016 06:06 AM, Anton Aylward wrote:
On 11/30/2016 04:27 AM, ianseeks wrote:
# cnf journalcntl journalcntl: command not found Journlactl # LOL If 'LOL' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf LOL Mainbox:~ # cnf LOL LOL: command not found
LOL: Laughing Out Loud -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-12-01 02:06, Doug wrote:
On 11/30/2016 06:06 AM, Anton Aylward wrote:
# cnf journalcntl journalcntl: command not found Journlactl # LOL If 'LOL' is not a typo you can use command-not-found to lookup the
On 11/30/2016 04:27 AM, ianseeks wrote: package that contains it, like this: cnf LOL Mainbox:~ # cnf LOL LOL: command not found
LOL: Laughing Out Loud
cer@Telcontar:~> wtf LOL LOL: laughing out loud cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tue, 2016-11-29 at 16:49 +0100, Carlos E. R. wrote:
On 2016-11-29 16:31, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:15 +0100, Carlos E. R. wrote:
Huh. You have to do this as root, or add your user to the 'systemd-journal', and log in again.
The event is not displayed, it happened at 10:23, probably because the warning printed above. You have to "su -" first.
This journalcntl --follow command isn't working for some reason. I added my user to systemd-journal and did the command in konsole, and it gave an output when I used it as root. I went to do it one more time to get an output to copy to send on in an email, and it isn't working again. Its giving this message: If 'journalcntl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journalcntl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 2016-11-29 at 16:49 +0100, Carlos E. R. wrote:
On 2016-11-29 16:31, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:15 +0100, Carlos E. R. wrote:
Then select with the mouse the new text that appeared after the two empty lines.
Here is the output
I'll edit to unwrap.
[Nov29 10:23] usb 4-1.4: USB disconnect, device number 4 [ +0.000289] usblp0: removed [Nov29 10:24] usb 4-1.4: new full-speed USB device number 5 using uhci_hcd [ +0.159283] usb 4-1.4: New USB device found, idVendor=03f0, idProduct=1004 [ +0.000007] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 4-1.4: Product: DeskJet 970C [ +0.000002] usb 4-1.4: Manufacturer: Hewlett-Packard [ +0.000002] usb 4-1.4: SerialNumber: MY07N1F1JTJQ [ +0.011188] usblp 4-1.4:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 [ +0.141187] usblp0: removed
Appears to see the new connection of the USB device. First it disconnect, then it connects again. It is blaming the printer.
It also appears to be using the usblp translation ??
You can do the same with "journalctl --follow". Output may be different - it is in my machine.
journalctl --follow Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice.
Huh. You have to do this as root, or add your user to the 'systemd-journal', and log in again.
-- Logs begin at Mon 2016-11-21 12:49:06 EST. -- Nov 29 09:57:13 linux org.a11y.atspi.Registry[2050]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Nov 29 09:57:13 linux org.freedesktop.secrets[1757]: gnome-keyring- daemon: insufficient process capabilities, unsecure memory might get used Nov 29 09:57:13 linux gnome-keyring-daemon[2074]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Nov 29 09:57:13 linux org.freedesktop.secrets[1757]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Nov 29 09:57:13 linux org.gnome.OnlineAccounts[1757]: goa-daemon- Message: goa-daemon version 3.20.4 starting Nov 29 09:57:18 linux org.freedesktop.Telepathy.ConnectionManager.sofiasip[1757]: tp- glib- Message: Exiting Nov 29 09:57:18 linux org.freedesktop.Telepathy.ConnectionManager.haze[1757]: tp-glib- Message: Exiting Nov 29 10:21:20 linux gnome-keyring-daemon[2074]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered Nov 29 10:21:20 linux org.freedesktop.secrets[1757]: ** (gnome- keyring- daemon:2074): WARNING **: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered Nov 29 10:22:12 linux systemd-coredump[2987]: Process 2910 (evolution) of user 1000 dumped core.
The event is not displayed, it happened at 10:23, probably because the warning printed above. You have to "su -" first.
Now the journalcntl --follow is working for the moment. Here is the output: # journalctl --follow -- Logs begin at Mon 2016-11-21 12:48:40 EST. -- Nov 29 12:55:44 linux python[5813]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=1 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 535: claimed 7/1/2 interface Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:55:46 linux hp-firmware[5813]: hp-firmware[5813]: error: Device hp:/usb/DeskJet_970C?serial=MY07N1F1JTJQ does not support or require firmware download. Nov 29 12:55:46 linux systemd-udevd[5810]: Process '/usr/bin/hp- firmware -s 002:014' failed with exit code 1. Nov 29 12:55:46 linux systemd[1]: Reached target Printer. Nov 29 12:59:14 linux kernel: usb 2-1.4: USB disconnect, device number 14 Nov 29 12:59:14 linux udev-configure-printer[5849]: remove /devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1.4 Nov 29 12:59:14 linux systemd[1]: printer.target: Unit not needed anymore. Stopping. Nov 29 12:59:14 linux systemd[1]: Stopped target Printer. Nov 29 12:59:16 linux kernel: usb 2-1.4: new full-speed USB device number 15 using uhci_hcd Nov 29 12:59:16 linux kernel: usb 2-1.4: New USB device found, idVendor=03f0, idProduct=1004 Nov 29 12:59:16 linux kernel: usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 29 12:59:16 linux kernel: usb 2-1.4: Product: DeskJet 970C Nov 29 12:59:16 linux kernel: usb 2-1.4: Manufacturer: Hewlett-Packard Nov 29 12:59:16 linux kernel: usb 2-1.4: SerialNumber: MY07N1F1JTJQ Nov 29 12:59:16 linux kernel: usblp 2-1.4:1.0: usblp0: USB Bidirectional printer dev 15 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 Nov 29 12:59:16 linux root[5853]: udev hpmud.rules runs hp-firmware to test if HP device with USB vendor ID 03f0 and USB product ID 1004 at USB bus ID 002 and USB device ID 015 needs firmware and if yes to upload it Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 2179: [5854] hpmud_make_usb_uri() bus=002 dev=015 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 2276: hpmud_make_usb_uri() uri=hp:/usb/DeskJet_970C?serial=MY07N1F1JTJQ bytes_read=40 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=1 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=1 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 393: Detaching kernel driver on interface=0 ret=0 Nov 29 12:59:17 linux kernel: usblp0: removed Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 535: claimed 7/1/2 interface Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=1 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 535: claimed 7/1/2 interface Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:59:19 linux hp-firmware[5854]: hp-firmware[5854]: error: Device hp:/usb/DeskJet_970C?serial=MY07N1F1JTJQ does not support or require firmware download. Nov 29 12:59:19 linux systemd-udevd[5851]: Process '/usr/bin/hp- firmware -s 002:015' failed with exit code 1. Nov 29 12:59:19 linux systemd[1]: Reached target Printer.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-29 19:01, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:49 +0100, Carlos E. R. wrote:
Now the journalcntl --follow is working for the moment. Here is the output:
It is journalctl, not journalcntl :-) I'll edit to unwrap, then I'll analyze.
# journalctl --follow -- Logs begin at Mon 2016-11-21 12:48:40 EST. -- Nov 29 12:55:44 linux python[5813]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=1 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 535: claimed 7/1/2 interface Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:55:46 linux python[5813]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:55:46 linux hp-firmware[5813]: hp-firmware[5813]: error: Device hp:/usb/DeskJet_970C?serial=MY07N1F1JTJQ does not support or require firmware download.
I think it is attempting to upload some firmware to the printer, but fails. Maybe this is not needed.
Nov 29 12:55:46 linux systemd-udevd[5810]: Process '/usr/bin/hp-firmware -s 002:014' failed with exit code 1. Nov 29 12:55:46 linux systemd[1]: Reached target Printer.
Printer is up.
Nov 29 12:59:14 linux kernel: usb 2-1.4: USB disconnect, device number 14 Nov 29 12:59:14 linux udev-configure-printer[5849]: remove /devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1.4 Nov 29 12:59:14 linux systemd[1]: printer.target: Unit not needed anymore. Stopping. Nov 29 12:59:14 linux systemd[1]: Stopped target Printer.
And here printer stops.
Nov 29 12:59:16 linux kernel: usb 2-1.4: new full-speed USB device number 15 using uhci_hcd
But two seconds later it is detecting that there is a new USB device being connected, so the printer has been powered up already.
Nov 29 12:59:16 linux kernel: usb 2-1.4: New USB device found, idVendor=03f0, idProduct=1004 Nov 29 12:59:16 linux kernel: usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 29 12:59:16 linux kernel: usb 2-1.4: Product: DeskJet 970C Nov 29 12:59:16 linux kernel: usb 2-1.4: Manufacturer: Hewlett-Packard Nov 29 12:59:16 linux kernel: usb 2-1.4: SerialNumber: MY07N1F1JTJQ Nov 29 12:59:16 linux kernel: usblp 2-1.4:1.0: usblp0: USB Bidirectional printer dev 15 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1004 Nov 29 12:59:16 linux root[5853]: udev hpmud.rules runs hp-firmware to test if HP device with USB vendor ID 03f0 and USB product ID 1004 at USB bus ID 002 and USB device ID 015 needs firmware and if yes to upload it
The printer is detected. This explains the firmware upload attempt.
Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 2179: [5854] hpmud_make_usb_uri() bus=002 dev=015 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 2276: hpmud_make_usb_uri() uri=hp:/usb/DeskJet_970C?serial=MY07N1F1JTJQ bytes_read=40 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=1 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=1 Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 393: Detaching kernel driver on interface=0 ret=0 Nov 29 12:59:17 linux kernel: usblp0: removed
The usblp0 interface is removed (parallel printer port emulation, I think)
Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 535: claimed 7/1/2 interface Nov 29 12:59:17 linux python[5854]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=1 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 535: claimed 7/1/2 interface Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=220 Nov 29 12:59:19 linux python[5854]: io/hpmud/musb.c 561: released 7/1/2 interface Nov 29 12:59:19 linux hp-firmware[5854]: hp-firmware[5854]: error: Device hp:/usb/DeskJet_970C?serial=MY07N1F1JTJQ does not support or require firmware download.
The printer firmware upload fails, as it should.
Nov 29 12:59:19 linux systemd-udevd[5851]: Process '/usr/bin/hp- firmware -s 002:015' failed with exit code 1. Nov 29 12:59:19 linux systemd[1]: Reached target Printer.
Printer is up. So no, the log does not show why the printer comes up. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tue, 2016-11-29 at 19:55 +0100, Carlos E. R. wrote:
On 2016-11-29 19:01, Mark Misulich wrote:
On Tue, 2016-11-29 at 16:49 +0100, Carlos E. R. wrote:
It is journalctl, not journalcntl :-)
Oops. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anton Aylward -
Carlos E. R. -
Doug -
ianseeks -
Mark Misulich