Re: `Filter failed' no print error message

On Mon 27 Mar 2017 at 07:42:35 +0100, Rodolfo Medina wrote: > Brian writes: > > > > Your best strategy is to download the latest package from Samsung > > instead of using something ancient. > > From Samsung web site I don't find that package... I suppose this is the

Re: `Filter failed' no print error message

Brian writes: >> > "UnifiedLinuxDriver" indicates a package downloaded from >> > >> > http://www.bchemnet.com/suldr/ >> > >> > But there is no version 1.02 offered by this site, See here >> > >> > http://www.bchemnet.com/suldr/suld.html >> > >> > Copying the PPD and

Re: `Filter failed' no print error message

On Sun 26 Mar 2017 at 22:02:44 +0100, Rodolfo Medina wrote: > Brian writes: > > > On Sun 26 Mar 2017 at 17:58:28 +0100, Rodolfo Medina wrote: > > > >> Brian writes: > >> > >> > > From where did you get the necessary drivers? > >> > > Is there any

Re: `Filter failed' no print error message

Brian writes: > On Sun 26 Mar 2017 at 17:58:28 +0100, Rodolfo Medina wrote: > >> Brian writes: >> >> > > From where did you get the necessary drivers? >> > > Is there any sign of "gstoraster" in your error_log? >> >> No, no gstoraster in

Re: `Filter failed' no print error message

On Sun 26 Mar 2017 at 17:58:28 +0100, Rodolfo Medina wrote: > Brian writes: > > > There are two other questions in the mail you are responding to. You > > have not dealt with them. I'll repeat them for reference: > > > > > From where did you get the necessary drivers? >

Re: `Filter failed' no print error message

Teemu Likonen writes: > Rodolfo Medina [2017-03-07 15:41:54Z] wrote: > >> Thanks, `cups' alone was enough. Now the printer seems to be >> configured. But it does not print, and, when I get into `jobs', I see >> they are stopped with "Filter failed" claim. What can I do? Please

Re: `Filter failed' no print error message

Brian writes: > There are two other questions in the mail you are responding to. You > have not dealt with them. I'll repeat them for reference: > > > From where did you get the necessary drivers? > > Is there any sign of "gstoraster" in your error_log? Sorry... No, no

Re: `Filter failed' no print error message

Rodolfo Medina [2017-03-07 15:41:54Z] wrote: > Thanks, `cups' alone was enough. Now the printer seems to be > configured. But it does not print, and, when I get into `jobs', I see > they are stopped with "Filter failed" claim. What can I do? Please > help. Thanks. I had a "filter failed" problem

Re: `Filter failed' no print error message

On Mon 20 Mar 2017 at 18:29:01 +, Rodolfo Medina wrote: > Brian writes: > > > Post the output of 'ls -l /usr/lib/cups/filter'. > > Here it is: > > $ ls -l /usr/lib/cups/filter > total 1332 > -rwxr-xr-x 1 root root 43168 Jan 19 13:44 bannertopdf > -rwxr-xr-x 1 root

Re: `Filter failed' no print error message

Brian writes: > Post the output of 'ls -l /usr/lib/cups/filter'. Here it is: $ ls -l /usr/lib/cups/filter total 1332 -rwxr-xr-x 1 root root 43168 Jan 19 13:44 bannertopdf -rwxr-xr-x 1 root root 1907 Jan 19 13:44 brftoembosser -rwxr-xr-x 1 root root 10480 Feb 16 2016

Re: `Filter failed' no print error message

On Mon 13 Mar 2017 at 16:27:30 +, Rodolfo Medina wrote: > Brian writes: > > > There are seven instructions in the advice given. You haven't provided a > > response to any of them. If there is a problem with following what is > > required, please ask. > > As the wiki

Re: `Filter failed' no print error message

On Mon 13 Mar 2017 at 16:27:30 +, Rodolfo Medina wrote: > Brian writes:

Re: `Filter failed' no print error message

Hi there On 13/03/17 17:27, Rodolfo Medina wrote: Brian writes: On Sat 11 Mar 2017 at 21:06:23 +, Rodolfo Medina wrote: Brian writes: On Tue 07 Mar 2017 at 15:41:54 +, Rodolfo Medina wrote: Thanks, `cups' alone was enough. Now

Re: `Filter failed' no print error message

Brian writes: > On Sat 11 Mar 2017 at 21:06:23 +, Rodolfo Medina wrote: > >> Brian writes: >> >> > On Tue 07 Mar 2017 at 15:41:54 +, Rodolfo Medina wrote: >> > >> >> >> >> Thanks, `cups' alone was enough. Now the printer seems to be

Re: `Filter failed' no print error message

On Sat 11 Mar 2017 at 21:06:23 +, Rodolfo Medina wrote: > Brian writes: > > > On Tue 07 Mar 2017 at 15:41:54 +, Rodolfo Medina wrote: > > > >> > >> Thanks, `cups' alone was enough. Now the printer seems to be configured. > >> But it does not print, and, when I

Re: `Filter failed' no print error message

Brian writes: > On Tue 07 Mar 2017 at 15:41:54 +, Rodolfo Medina wrote: > >> >> Thanks, `cups' alone was enough. Now the printer seems to be configured. >> But it does not print, and, when I get into `jobs', I see they are stopped >> with "Filter failed" claim. What

Re: `Filter failed' no print error message (was: Printing packages)

On Tue 07 Mar 2017 at 15:41:54 +, Rodolfo Medina wrote: > Brian writes: > > > On Sun 05 Mar 2017 at 20:07:22 +, Rodolfo Medina wrote: > > > >> Rodolfo Medina writes: > >> > >> > >> I installed: > >> > >> cups cups-bsd cups-client

`Filter failed' no print error message (was: Printing packages)

Brian writes: > On Sun 05 Mar 2017 at 20:07:22 +, Rodolfo Medina wrote: > >> Rodolfo Medina writes: >> >> >> I installed: >> >> cups cups-bsd cups-client libcupsimage2 printer-driver-gutenprint > > For what purpose do you need cups-bsd? >

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Thu, Feb 02, 2017 at 05:59:57PM +, Lisi Reisz wrote: > [redacted]'s rudeness and unpleasantness to anyone and everyone who tries to > help > him does get a bit wearing. Speaking of which, I'll share the solution I came up with to implement a mailing list killfile (ignore list), but I

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Friday 27 January 2017 21:13:35 Ryan Cunningham wrote: > This includes the message that you sent, and any other message of a similar > type. If this continues, and we cannot reasonably reach a compromise, I > will send a message to the list owner requesting that you be forcefully >

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

Dear Greg Wooledge, The Debian mailing list code of conduct says: "The mailing lists exist to foster the development and use of Debian. Non-constructive or off-topic messages, along with other abuses, are not welcome." This includes the message that you sent, and any other message of a

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Fri, Jan 27, 2017 at 02:50:40PM -0600, Richard Owlett wrote: > Abysmal failure. I have had enough of this bullshit. Richard, you are a toxic person. You give the human race a bad name. Every HONEST effort to help you has been met with insults. You suck the time and energy from those who had

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On 01/27/2017 01:36 PM, Brian wrote: On Fri 27 Jan 2017 at 12:41:00 -0600, Richard Owlett wrote: On 01/27/2017 09:40 AM, Brian wrote: On Fri 27 Jan 2017 at 07:42:27 -0600, Richard Owlett wrote: [...Lots of snipping...] The underlying condition that triggered all the "observables" is that

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Fri 27 Jan 2017 at 12:41:00 -0600, Richard Owlett wrote: > On 01/27/2017 09:40 AM, Brian wrote: > >On Fri 27 Jan 2017 at 07:42:27 -0600, Richard Owlett wrote: > > > >[...Lots of snipping...] > > > >>The underlying condition that triggered all the "observables" is that the > >>.deb in [2] is

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On 01/27/2017 09:40 AM, Brian wrote: On Fri 27 Jan 2017 at 07:42:27 -0600, Richard Owlett wrote: [...Lots of snipping...] The underlying condition that triggered all the "observables" is that the .deb in [2] is not compatible with Mate delivered on Debian 8.6.0 DVDs. [2] is

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Fri 27 Jan 2017 at 07:42:27 -0600, Richard Owlett wrote: [...Lots of snipping...] > The underlying condition that triggered all the "observables" is that the > .deb in [2] is not compatible with Mate delivered on Debian 8.6.0 DVDs. [2] is

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On 01/26/2017 10:12 AM, Darac Marjal wrote: On Thu, Jan 26, 2017 at 08:00:03AM -0600, Richard Owlett wrote: On 12/20/2016 09:10 AM, Sven Joachim wrote: On 2016-12-20 08:34 -0600, Richard Owlett wrote: When I right click on the top panel and then chose "Help" I receive "Could not display help

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Thu 26 Jan 2017 at 08:50:00 -0600, Richard Owlett wrote: > On 01/26/2017 08:06 AM, Brian wrote: > >On Thu 26 Jan 2017 at 08:00:03 -0600, Richard Owlett wrote: > > > >>On 12/20/2016 09:10 AM, Sven Joachim wrote: > >>>On 2016-12-20 08:34 -0600, Richard Owlett wrote: > >>> > When I right

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Thu, Jan 26, 2017 at 08:00:03AM -0600, Richard Owlett wrote: On 12/20/2016 09:10 AM, Sven Joachim wrote: On 2016-12-20 08:34 -0600, Richard Owlett wrote: When I right click on the top panel and then chose "Help" I receive "Could not display help document 'mate-user-guide'. The specified

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On 01/26/2017 08:06 AM, Brian wrote: On Thu 26 Jan 2017 at 08:00:03 -0600, Richard Owlett wrote: On 12/20/2016 09:10 AM, Sven Joachim wrote: On 2016-12-20 08:34 -0600, Richard Owlett wrote: When I right click on the top panel and then chose "Help" I receive "Could not display help document

Re: Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On Thu 26 Jan 2017 at 08:00:03 -0600, Richard Owlett wrote: > On 12/20/2016 09:10 AM, Sven Joachim wrote: > >On 2016-12-20 08:34 -0600, Richard Owlett wrote: > > > >>When I right click on the top panel and then chose "Help" I receive > >>"Could not display help document 'mate-user-guide'. The

Installing a package downloaded from snapshot - was [Re: Mate error message under Debian 8.6.0]

On 12/20/2016 09:10 AM, Sven Joachim wrote: On 2016-12-20 08:34 -0600, Richard Owlett wrote: When I right click on the top panel and then chose "Help" I receive "Could not display help document 'mate-user-guide'. The specified location is not supported." As I do not have adequate bandwidth

Re: Mate error message under Debian 8.6.0

On 2016-12-20 08:34 -0600, Richard Owlett wrote: > When I right click on the top panel and then chose "Help" I receive > "Could not display help document 'mate-user-guide'. The specified > location is not supported." > > As I do not have adequate bandwidth for install from internet I use >

Mate error message under Debian 8.6.0

When I right click on the top panel and then chose "Help" I receive "Could not display help document 'mate-user-guide'. The specified location is not supported." As I do not have adequate bandwidth for install from internet I use purchased sets of DVDs. I assumed the document had not been on

Re: before first use of a brand new flash drive (was: Error message from GParted...)

Richard Owlett composed on 2016-11-27 07:02 (UTC-0500): ... It may be an interesting exercise, before first use of a brand new flash drive, to examine it via Gparted and "wipefs /dev/sdX"... I first test that the claimed capacity is valid:

Re: Error message from GParted, means what?

On 11/27/2016 3:15 AM, Pascal Hambourg wrote: Le 26/11/2016 à 23:42, Richard Owlett a écrit : I've been getting a strange error messages when looking at some 8 GB flash drives from different manufacturers purchased months apart. There is a title bar at top saying "Libparted Warning (as

Re: Error message from GParted, means what?

Le 26/11/2016 à 23:42, Richard Owlett a écrit : I've been getting a strange error messages when looking at some 8 GB flash drives from different manufacturers purchased months apart. There is a title bar at top saying "Libparted Warning (as superuser). The body of the message box has: 1. an

Error message from GParted, means what?

I've been getting a strange error messages when looking at some 8 GB flash drives from different manufacturers purchased months apart. There is a title bar at top saying "Libparted Warning (as superuser). The body of the message box has: 1. an Exclamation point surrounded by orange and yellow

Re: error message after apt-get update

On Sat, November 28, 2015 8:50 pm, Charles Kroeger wrote: > I was hoping someone might know what this message means after running > apt-get update: ... > Reading package lists... Done > W: Problem unlinking the file q - Clean (21: Is a directory) Now and then something gets corrupted with apt. A

Re: error message after apt-get update

On Sun, 29 Nov 2015 05:20:01 +0100 rlhar...@oplink.net wrote: > On Sat, November 28, 2015 8:50 pm, Charles Kroeger wrote: > > I was hoping someone might know what this message means after running > > apt-get update: > ... > > Reading package lists... Done > > W: Problem unlinking the file q -

Re: error message after apt-get update

On Sat, November 28, 2015 11:18 pm, Charles Kroeger wrote: > Ah, thanks so much..the offending q directory was in there (///lists) so > I just deleted that instead, but all is now well. If you delete the entire directory, it is rebuilt automatically as soon as you execute "apt-get update". If I

error message after apt-get update

I was hoping someone might know what this message means after running apt-get update: Reading package lists... Done W: Problem unlinking the file q - Clean (21: Is a directory) I cannot find any directory named 21 or Clean. A search with dpkg -l | grep q Clean or 21 turns

Re: Error message at the login prompt

August Karlstrom: > > Today when I started my computer running Debian 8.2 the following error > message was displayed at the login prompt (where the user name go): > > macmini login: [ 1615.712744] usb 3-3: 1:1: cannot get freq at ep 0x1 > > My question is not so

Re: Error message at the login prompt

On 2015-09-27 14:40, Jochen Spieker wrote: August Karlstrom: Today when I started my computer running Debian 8.2 the following error message was displayed at the login prompt (where the user name go): macmini login: [ 1615.712744] usb 3-3: 1:1: cannot get freq at ep 0x1 My question

Error message at the login prompt

Hi, Today when I started my computer running Debian 8.2 the following error message was displayed at the login prompt (where the user name go): macmini login: [ 1615.712744] usb 3-3: 1:1: cannot get freq at ep 0x1 My question is not so much about the error message but rather why

Re: Error message at the login prompt

Quoting August Karlstrom (fusionf...@gmail.com): > On 2015-09-27 14:40, Jochen Spieker wrote: > >August Karlstrom: > >>Today when I started my computer running Debian 8.2 the following error > >>message was displayed at the login prompt (where the user name

Re: Error message at the login prompt

August Karlstrom: > On 2015-09-27 14:40, Jochen Spieker wrote: >> >> That's a kernel message that is apparently considered important enough >> to print it on all VTs, irrespective of their current content. > > OK, I see. Thanks for the info, Jochen. Still, I think it looks like a mess. Sure,

squeeze error message

One of the servers I admin is giving error messages I don't understand. From logwatch: > Errors when running cron: >grandchild #10246 failed with exit status 1: 1 Time(s) >grandchild #10255 failed with exit status 1: 1 Time(s) >grandchild #10335 failed with exit status 1: 1 Time(s)

One Error Message Down, One to GO

Kept getting warnings about mdir files being changed so copied. Got .lock in procmailrc so maybe this one is done. At least, the error message suggested using lock files (which I thought I had). Now for the expiring/disconnecting/reconnecting eth0. This is operating off a router. I went

Re: CUPS error message, device already exists

On 06/27/2015 01:16 AM, bri...@aracnet.com wrote: On Fri, 26 Jun 2015 03:46:48 -0400 Gary Dale garyd...@torfree.net wrote: On 26/06/15 01:37 AM, bri...@aracnet.com wrote: I'm not sure if this is meaningful, but it would be nice to fix it. failed to CreateDevice:

Re: CUPS error message, device already exists

On Fri 26 Jun 2015 at 22:22:25 -0700, bri...@aracnet.com wrote: meanwhile i'm getting this too: Failed to update TXT record for DCP8110DN @ server: -2 I think i figured that one out. it can't get a hostname for the printer perhaps ? Sort of. Avahi is trying to get a TXT record for a

Re: CUPS error message, device already exists

On 27/06/15 06:16, bri...@aracnet.com wrote: My complaint is that CUPS is complaining. if it doesn't matter - then why is it complaining ? Some programs complain about things that *might* matter where if they do matter then the humans they matter to will be very upset to not be notified.

Re: CUPS error message, device already exists

On 26/06/15 01:37 AM, bri...@aracnet.com wrote: I'm not sure if this is meaningful, but it would be nice to fix it. failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-DCP8110DN' already exists Googling turns up lots of hits, not a one of which has

Re: CUPS error message, device already exists

On Fri 26 Jun 2015 at 03:46:48 -0400, Gary Dale wrote: On 26/06/15 01:37 AM, bri...@aracnet.com wrote: I'm not sure if this is meaningful, but it would be nice to fix it. failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-DCP8110DN' already exists

Re: CUPS error message, device already exists

On 26/06/15 09:51 AM, Brian wrote: On Fri 26 Jun 2015 at 03:46:48 -0400, Gary Dale wrote: On 26/06/15 01:37 AM, bri...@aracnet.com wrote: I'm not sure if this is meaningful, but it would be nice to fix it. failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id

Re: CUPS error message, device already exists

On Fri, 26 Jun 2015 03:46:48 -0400 Gary Dale garyd...@torfree.net wrote: On 26/06/15 01:37 AM, bri...@aracnet.com wrote: I'm not sure if this is meaningful, but it would be nice to fix it. failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id

Re: CUPS error message, device already exists

On Fri, 26 Jun 2015 14:51:54 +0100 Brian a...@cityscape.co.uk wrote: It's a warning - not an error - and can be ignored. It will appear when a printer is installed. It's a dbus thing. ok. Did you try purging the cups install then reinstalling and adding the printer back in? Not

CUPS error message, device already exists

I'm not sure if this is meaningful, but it would be nice to fix it. failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-DCP8110DN' already exists Googling turns up lots of hits, not a one of which has been helpful so far. Brian -- To UNSUBSCRIBE,

[solved] Re: Error message on console at logging in

, but the error message disturbs the logging in. With previous Debian versions, such kernel messages were avoided simply appending to /etc/init.d/rc.local the line: dmesg -n 1 , but now this does not help any more. Apparently, the message does not seem to correspond to any effective problem, so I wish

[solved] Re: Error message on console at logging in

complaining: usb 2-1: device descriptor read/64, error -71 . No usb device is inserted in the machine, but the error message disturbs the logging in. With previous Debian versions, such kernel messages were avoided simply appending to /etc/init.d/rc.local the line: Check lsusb. Some

Re: Error message on console at logging in

. No usb device is inserted in the machine, but the error message disturbs the logging in. With previous Debian versions, such kernel messages were avoided simply appending to /etc/init.d/rc.local the line: dmesg -n 1 , but now this does not help any more. Apparently, the message does

Re: Error message on console at logging in

, error -71 . No usb device is inserted in the machine, but the error message disturbs the logging in. With previous Debian versions, such kernel messages were avoided simply appending to /etc/init.d/rc.local the line: Check lsusb. Some machines have internally connected USB devices. See

Error message on console at logging in

Hi all. With Debian 8: on my Acer netbook, when logging in, if I rotate the screen, many undesired lines appear on the console complaining: usb 2-1: device descriptor read/64, error -71 . No usb device is inserted in the machine, but the error message disturbs the logging in. With previous

Re: Error message on console at logging in

in the machine, but the error message disturbs the logging in. With previous Debian versions, such kernel messages were avoided simply appending to /etc/init.d/rc.local the line: Check lsusb. Some machines have internally connected USB devices. See if you have anything connected at Bus 002 Device 001

Unexpected inconsistency error message after rebooting a newly installed debian wheezy with preseed (lvm partitioning) - Any idea how to auto run fsck after installation, slipstreamed to preseed.cfg

Hi all, Below is my preseed.cfg file. What's wrong with it? Why am I getting unexpected inconsistency and forced to run fsck after a fresh installation? d-i debian-installer/locale string en_US d-i keyboard-configuration/xkb-keymap select us d-i console-keymaps-at/keymap

meaning of an error message

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, When I try to user acroread on debian wheezy, I get this error message: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: relocation error: /lib/i386-linux-gnu/i686/cmov/libc.so.6: symbol _dl_find_dso_for_object, version GLIBC_PRIVATE

Re: meaning of an error message

On 2014-06-21 10:32 +0200, François Patte wrote: When I try to user acroread on debian wheezy, I get this error message: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: relocation error: /lib/i386-linux-gnu/i686/cmov/libc.so.6: symbol _dl_find_dso_for_object, version GLIBC_PRIVATE

Re: meaning of an error message

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 21/06/2014 10:54, Sven Joachim a écrit : On 2014-06-21 10:32 +0200, François Patte wrote: When I try to user acroread on debian wheezy, I get this error message: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: relocation error: /lib

Re: meaning of an error message

On 2014-06-21 11:02 +0200, François Patte wrote: Le 21/06/2014 10:54, Sven Joachim a écrit : On 2014-06-21 10:32 +0200, François Patte wrote: When I try to user acroread on debian wheezy, I get this error message: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: relocation error: /lib

Re: meaning of an error message

this error message: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: relocation error: /lib/i386-linux-gnu/i686/cmov/libc.so.6: symbol _dl_find_dso_for_object, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference This symbol does not exist in wheezy's libc6, FWIW

Re: Error message: Possible missing firmware during linux-image upgrade

On Ma, 27 mai 14, 18:33:45, Reco wrote: On Tue, 27 May 2014 10:06:07 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: lscpi, dmidecode, hwinfo. typo: that should be 'lspci' My mistake. First one comes out of the box in Debian. For usual values of out of the box (i.e.

Re: Error message: Possible missing firmware during linux-image upgrade

On Ma, 27 mai 14, 09:25:04, Reco wrote: On Mon, 26 May 2014 18:05:34 -0700 (PDT) Horatio Leragon hlera...@yahoo.com wrote: How does one find out if the Realtek Gigabit card is 8168B, 8168A, 8168E? lscpi, dmidecode, hwinfo. typo: that should be 'lspci' First one comes out of the

Re: Error message: Possible missing firmware during linux-image upgrade

On Mon, May 26, 2014 at 06:05:34PM -0700, Horatio Leragon wrote: I happen to have Realtek RTL8111/8168B Gigabit card which works flawlessly with any Debian kernel starting with Squeeze's backported 3.1. How does one find out if the Realtek Gigabit card is 8168B, 8168A, 8168E? man

Re: Error message: Possible missing firmware during linux-image upgrade

On Tue, 27 May 2014 10:06:07 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: lscpi, dmidecode, hwinfo. typo: that should be 'lspci' My mistake. First one comes out of the box in Debian. For usual values of out of the box (i.e. it's in Standard, which can be deselected during

Error message: Possible missing firmware during linux-image upgrade

My Debian OS (7.5) has the default linux-image-3.2.0.4-amd64 installed. Using Synaptic, I installed the non-free firmware-realtek. What I did next was to upgrade the default linux-image to 3.14-0.bpo.1-amd64 using its equivalent Wheezy backport. During the upgrading process, the same error

Re: Error message: Possible missing firmware during linux-image upgrade

Hi. On Mon, 26 May 2014 04:53:03 -0700 (PDT) Horatio Leragon hlera...@yahoo.com wrote: Is this a bug? A fixed one (see below). What should I have done under the above circumstances? Install firmware-realtek from the backports. Or, if network connectivity isn't lost after the upgrade -

Re: Error message: Possible missing firmware during linux-image upgrade

On 2014-05-26 17:03 +0200, Reco wrote: On Mon, 26 May 2014 04:53:03 -0700 (PDT) Horatio Leragon hlera...@yahoo.com wrote: Is this a bug? A fixed one (see below). What should I have done under the above circumstances? Install firmware-realtek from the backports. This would get rid of

Re: Error message: Possible missing firmware during linux-image upgrade

Hi. This is probably not recommended, his device likely needs some other firmware already included in the wheezy version of the package. I happen to have Realtek RTL8111/8168B Gigabit card which works flawlessly with any Debian kernel starting with Squeeze's backported 3.1. Every time the

Re: Error message: Possible missing firmware during linux-image upgrade

On Mon, 5/26/14, Reco recovery...@gmail.com wrote: Subject: Re: Error message: Possible missing firmware during linux-image upgrade To: debian-user@lists.debian.org Date: Monday, May 26, 2014, 8:03 AM Install firmware-realtek from the backports

Re: Error message: Possible missing firmware during linux-image upgrade

On Mon, 5/26/14, Sven Joachim svenj...@gmx.de wrote: Subject: Re: Error message: Possible missing firmware during linux-image upgrade To: debian-user@lists.debian.org Date: Monday, May 26, 2014, 8:16 AM This would get rid of the message since

Re: Error message: Possible missing firmware during linux-image upgrade

On Mon, 5/26/14, Reco recovery...@gmail.com wrote: Subject: Re: Error message: Possible missing firmware during linux-image upgrade To: debian-user@lists.debian.org Date: Monday, May 26, 2014, 8:30 AM I happen to have Realtek RTL8111/8168B

Re: Error message: Possible missing firmware during linux-image upgrade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/26/2014 09:05 PM, Horatio Leragon wrote: On Mon, 5/26/14, Reco recovery...@gmail.com wrote: I happen to have Realtek RTL8111/8168B Gigabit card which works flawlessly with any Debian kernel starting with Squeeze's backported 3.1. How

Re: Error message: Possible missing firmware during linux-image upgrade

On Mon, 26 May 2014 17:55:11 -0700 (PDT) Horatio Leragon hlera...@yahoo.com wrote: What should I do to install firmware-realtek (0.41~bpo70+1) which is in Wheezy backports? apt-get install firmware-realtek=0.47~bpo70+1 And you can always use Synaptic to do the same thing (should be called

Re: Error message: Possible missing firmware during linux-image upgrade

On Mon, 26 May 2014 18:05:34 -0700 (PDT) Horatio Leragon hlera...@yahoo.com wrote: How does one find out if the Realtek Gigabit card is 8168B, 8168A, 8168E? lscpi, dmidecode, hwinfo. First one comes out of the box in Debian. Every time the kernel boots it complains about missing

Re: Netselect-Apt is showing error message

On Thu, Jan 09, 2014 at 01:05:25AM +0600, Muntasim-Ul-Haque wrote: Hi, I've faced some problems while using the Netselect-Apt. While giving the command  sudo netselect-apt I get the following errors: Did not find any valid hosts (you requested 10) netselect was unable to find a

Netselect-Apt is showing error message

Hi, I've faced some problems while using the Netselect-Apt. While giving the command */sudo netselect-apt/* I get the following errors: */Did not find any valid hosts (you requested 10)/**/ /**/netselect was unable to find a mirror, this probably means that/**/ /**/you are behind a firewall and

Re: key error message from squeeze-updates repository

Hi, Kailash Thank you for your reply. It is much appreciated. On Tuesday 03 December 2013 05:05:38 Kailash wrote: On Monday 02 December 2013 11:06 PM, Lisi Reisz wrote: I am getting the following error message when I run aptitude update: W: GPG error: http://mirror.ox.ac.uk squeeze

key error message from squeeze-updates repository

I am getting the following error message when I run aptitude update: W: GPG error: http://mirror.ox.ac.uk squeeze-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 The debian-archive-keyring package is installed

Re: key error message from squeeze-updates repository

On Monday 02 December 2013 11:06 PM, Lisi Reisz wrote: I am getting the following error message when I run aptitude update: W: GPG error: http://mirror.ox.ac.uk squeeze-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY

Re: Php5 error message

On Thu, Sep 12, 2013 at 06:12:52PM -0500, John W. Foster wrote: I want to get rid of these messages: HOW! In the files mentioned, replace the # with ;. PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cli/conf.d/ming.ini on line 1 in Unknown on line 0 PHP

Re: Php5 error message

On Fri, 2013-09-13 at 10:15 +0100, Darac Marjal wrote: On Thu, Sep 12, 2013 at 06:12:52PM -0500, John W. Foster wrote: I want to get rid of these messages: HOW! In the files mentioned, replace the # with ;. PHP Deprecated: Comments starting with '#' are deprecated in

Php5 error message

I want to get rid of these messages: HOW! PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cli/conf.d/ming.ini on line 1 in Unknown on line 0 PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cli/conf.d/ming.ini on line 1 in Unknown on line 0 PHP

Re: Evolution error message

On Wed, 2013-07-03 at 19:59 +0200, alberto fuentes wrote: Does /home/myuser/.local/share/evolution/mail/local exist? what permissions does the folder have? do you have free space in your partition? I dont use evolution, but there must be in the configuration of your account somewhere that

Evolution error message

I posted this a week or so back, or tried to. I am getting the error message below every time I send an email. I wish to fix this but really don't know what or how to do it. The reported error was Failed to append to mbox:///home/myuser/.local/share/evolution/mail/local#Sent: Invalid folder URI

Re: Evolution error message

Does /home/myuser/.local/share/evolution/mail/local exist? what permissions does the folder have? do you have free space in your partition? I dont use evolution, but there must be in the configuration of your account somewhere that tells you the path where your mails is trying to get saved. check

Evolution error message

I am getting this message since I did a dist-upgrade to Wheezy on my evolution set up. Your message was sent, but an error occurred during post-processing. The reported error was Failed to append to mbox:///home/frosty/.local/share/evolution/mail/local#Sent: Invalid folder URI

What does this error message mean?

insserv: Script ETH1START is broken: incomplete LSB comment. insserv: missing `Default-Stop:' entry: please add even if empty. insserv: Script ETH1START is broken: incomplete LSB comment. insserv: missing `Default-Stop:' entry: please add even if empty. insserv: Script ETH1START is

Re: What does this error message mean?

John W. Foster wrote: insserv: Script ETH1START is broken: incomplete LSB comment. insserv: missing `Default-Stop:' entry: please add even if empty. insserv: Script ETH1START is broken: incomplete LSB comment. insserv: missing `Default-Stop:' entry: please add even if empty. insserv:

Re: What does this error message mean?

On Mon 24 Jun 2013 at 15:51:35 -0500, John W. Foster wrote: insserv: Script ETH1START is broken: incomplete LSB comment. insserv: missing `Default-Stop:' entry: please add even if empty. insserv: Script ETH1START is broken: incomplete LSB comment. insserv: missing `Default-Stop:'

Re: Error message; cannot fetch install sources

On Sun, 23 Sep 2012 15:28:15 -0400, Edward C. Jones wrote: I use up-to-date Debian testing, amd64 architecture. For the last few days, the following message is sometimes displayed, for a few seconds: cannot fetch install sources. Then it says something like ftp.us.debian.org wheezy

<    1   2   3   4   5   6   7   >