Re: [Parrot Community] Unable to locate kcmshell5

udo apt install x it says E: > Unable to locate package X. > And this happens with everything I want to download via apt install. > > https://community.parrotsec.org/t/unable-to-locate-packages/28238 Aleix, ParrotOS is not Debian Linux. It is based on Debian Linux but is not Debian

[Parrot Community] Unable to locate kcmshell5

Please Write here your help request, – i can't download kcmshell5 at Parrot-security-6.1_amd64.iso maybe it's the latest distro and it's not finished.. I was trying to download something, executing sudo apt install x it says E: Unable to locate package X. And this happens with every

Re: locate question

On Wed, Nov 08, 2023 at 05:16:26PM +0100, to...@tuxteam.de wrote: > On Wed, Nov 08, 2023 at 11:45:30AM -0400, Roy J. Tellason, Sr. wrote: > > On Tuesday 07 November 2023 11:32:21 am gene heskett wrote: > > > so locate isn't working as I think it should. > > > tr

Re: locate question

On Wed, Nov 08, 2023 at 11:45:30AM -0400, Roy J. Tellason, Sr. wrote: > On Tuesday 07 November 2023 11:32:21 am gene heskett wrote: > > so locate isn't working as I think it should. > > try find but it finds the whole my whole local net: > > gene@coyote:~$ find .scad

Re: locate question

On Tuesday 07 November 2023 11:32:21 am gene heskett wrote: > so locate isn't working as I think it should. > try find but it finds the whole my whole local net: > gene@coyote:~$ find .scad .  |wc -l > find: ‘.scad’: No such file or directory Try putting a * before the period in

Re: locate question

If you just want to see files in /home/gene try locate -r 'home/gene/.*\.scad' In that way, regex syntax can be used to narrow down the search. Regards, Jörg.

Re: locate question

On 11/7/23 14:38, to...@tuxteam.de wrote: On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote: Greetings all; [...] gene@coyote:~$ locate *.scad /home/gene/vac_ctrl_box.scad /home/gene/xhome_cable.scad Markus and The Wanderer were spot on. As a reminder to all: this "

Re: locate question

d all its subs with assorted names ending in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an x

Re: locate question

ctory and all its subs with assorted names ending in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued fr

Re: locate question

On Tue, Nov 07, 2023 at 08:38:51PM +0100, to...@tuxteam.de wrote: > On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote: > > gene@coyote:~$ locate *.scad > > /home/gene/vac_ctrl_box.scad > > /home/gene/xhome_cable.scad > > Markus and The Wanderer were spot on

Re: locate question

On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote: > Greetings all; [...] > gene@coyote:~$ locate *.scad > /home/gene/vac_ctrl_box.scad > /home/gene/xhome_cable.scad Markus and The Wanderer were spot on. As a reminder to all: this "naked" *.scad gets already

Re: locate question

ng in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an xfce terminal but I get: gene@coyote:~$ locate

Re: locate question

its subs with assorted names ending in ".scad", made by OpenSCAD > Fact: I just ran "sudo updatedb" and generated a new date just now, > /var/cache/locate/locatedb.n > so that s/b uptodate. > Al of those files should be spit out by: > "locate *.scad&quo

Re: locate question

its subs with assorted names ending in ".scad", made by OpenSCAD > Fact: I just ran "sudo updatedb" and generated a new date just now, > /var/cache/locate/locatedb.n > so that s/b uptodate. > Al of those files should be spit out by: > "locate *.scad" issu

Re: locate question

nding in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an xfce terminal but I get: gene

locate question

enSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an xfce terminal but I get: gene@coyote:~$ locate *.scad /home/gene/vac_ctrl_box.scad

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

On Sun, Aug 27, 2023 at 02:17:06PM -0400, Jeffrey Walton wrote: [...] > The symlink tool works great, too: > > symlink -r / | grep dangling > > You can also delete them, once you verify they are dangling: > > symlink -r -d / > > In fact, it is a recommended post-upgrade step for Fedor

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

On Sun, Aug 27, 2023 at 1:10 PM Jörg-Volker Peetz wrote: > > to...@tuxteam.de wrote on 24/08/2023 14:00: > > > > A couple of days ago I was searching for dangling symlinks. > > > >find . -follow -lname "*" > > > How about > find -L . -type l The symlink tool works great, too: symlink

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

On Sun, Aug 27, 2023 at 07:09:36PM +0200, Jörg-Volker Peetz wrote: > to...@tuxteam.de wrote on 24/08/2023 14:00: > > > > A couple of days ago I was searching for dangling symlinks. > > > >find . -follow -lname "*" > > > How about >find -L . -type l Should work, too. Cheers -- t sign

dangling symlinks [ was: Re: "locate" easier to use than "find"]

to...@tuxteam.de wrote on 24/08/2023 14:00: A couple of days ago I was searching for dangling symlinks. find . -follow -lname "*" How about find -L . -type l Regards, Jörg.

Re: "locate" easier to use than "find"

> > to...@tuxteam.de (12023-08-24): > > > Dunno. I use find nearly every day. Seeing it as "just a recursive > > > grep" doesn't cover a fraction of its usefulness. > > > > > > A couple of days ago I was searching for dangling symlinks. > > > > > > find . -follow -lname "*" Wow... what a cryptic

Re: "locate" easier to use than "find"

Stanislav Vlasov (12023-08-24): > Sometimes it's unexpected :-) Then the shell prints an error and I try again. Still less time wasted than these two mails. Regards, -- Nicolas George

Re: "locate" easier to use than "find"

чт, 24 авг. 2023 г. в 18:17, Nicolas George : > > With a really large amount of files there will be overflow of process > > environment (or too large cmdline). > If I expect a very large amount of files, I can use it another way. Sometimes it's unexpected :-) -- Stanislav

Re: "locate" easier to use than "find"

ago I was searching for dangling symlinks. > > > > find . -follow -lname "*" > > ls **/*(N@-@) > > Zsh rulz. Definitely. My point was rather to illustrate the kind of things find can do that locate can't. There is more than one way to do it (TM). Cheers -- t signature.asc Description: PGP signature

Re: "locate" easier to use than "find"

Stanislav Vlasov (12023-08-24): > With a really large amount of files there will be overflow of process > environment (or too large cmdline). If I expect a very large amount of files, I can use it another way. -- Nicolas George

Re: "locate" easier to use than "find"

arching for dangling symlinks. > > > > find . -follow -lname "*" > > ls **/*(N@-@) With a really large amount of files there will be overflow of process environment (or too large cmdline). locate and find does not store filenames in memory. -- Stanislav

Re: "locate" easier to use than "find"

to...@tuxteam.de (12023-08-24): > Dunno. I use find nearly every day. Seeing it as "just a recursive > grep" doesn't cover a fraction of its usefulness. > > A couple of days ago I was searching for dangling symlinks. > > find . -follow -lname "*" ls **/*(N@-@) Zsh rulz. Regards, -- Nicol

Re: "locate" easier to use than "find"

On Thu, Aug 24, 2023 at 01:52:28PM +0200, Oliver Schoede wrote: [...] > Have basically stopped using traditional 'find' outside of scripts, as > always thought I was about the last one [...] Dunno. I use find nearly every day. Seeing it as "just a recursive grep" doesn't cover a fraction of its

Re: "locate" easier to use than "find"

ug >> > 21 13:29 .mozilla/firefox/gs0gkgv2.default/favicons.sqlite 1515049 >> >    260 -rw-r--r--   1 myusername myusername   262144 Aug 18 22:36 >> > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite >> >> For me command "locate" is easier t

Re: "locate" easier to use than "find"

On Mon, Aug 21, 2023 at 06:45:16PM +0100, Brian wrote: [...] > plocate-updatedb.service and plocate-updatedb.timer take care of > that for me. :) I admit to accepting some help from trusty cron :) > > Tools, jobs and that :) > > Indeed. Cheers -- t signature.asc Description: PGP signature

Re: "locate" easier to use than "find"

On 2023-08-21 17:21, to...@tuxteam.de wrote: On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote: On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de: >> For me command "locate" is easier to use than "find": > > They do different things. Locate i

Re: "locate" easier to use than "find"

On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote: > On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de: > >> For me command "locate" is easier to use than "find": > > > > They do different things. Locate is much faster, but it only l

Re: "locate" easier to use than "find"

On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de: >> For me command "locate" is easier to use than "find": > > They do different things. Locate is much faster, but it only looks > into file names. Find can do nearly everything, like looking into > file met

Re: "locate" easier to use than "find"

lite > >  1515049    260 -rw-r--r--   1 myusername myusername   262144 Aug 18 22:36 > > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite > > For me command "locate" is easier to use than "find": They do different things. Locate is much faster, bu

"locate" easier to use than "find"

/th3dv2jy.default-1461749950404/favicons.sqlite For me command "locate" is easier to use than "find": rprice@titan ~ locate favicons.sqlite /mnt/home/rprice/.mozilla/firefox/60mahk24.default-esr/favicons.sqlite /mnt/home/rprice/.mozilla/firefox/60mahk24.default-esr/favicons.

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On Fri, Jul 08, 2022 at 08:37:19AM -0500, Albretch Mueller wrote: > [...] that bash utils needed to be declared in > the PATH in order for you to access them. Noticing it and opening > another windows was all it took. Ah, oh. You overwrote your PATH. Makes sense now :) > it amazes me also how a

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On Fri, 2022-07-08 at 08:37 -0500, Albretch Mueller wrote: > it seemed to have been somehow > blanketed by my "unconscious" that bash utils needed to be declared in > the PATH in order for you to access them. 'which' isn't a 'bash util' whatever that is (presumably you mean a shell built-in). As y

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

after reading through all your suggestions and still wondering about what exactly was the mistake that I had made, I realized that it was a simple and stupid "type in a rush and let 'the compiler' (sorry!) find the mistake for you" kind of error: it seemed to have been somehow blanketed by my "unc

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On 2022-07-08 12:48, Greg Wooledge wrote: https://wiki.debian.org/DebianAlternatives thanks mick

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

Give us all the additional details you have. * The problem happens in all terminals I've tried -- xterm, rxvt-unicode, gnome-terminal and konsole. * If I type 'zsh' the problem goes away. But I really want it to work in bash too. * I did a 'locate cat' and I can see that it's in /usr/bin, or at least locate thinks it is. Here is the output of 'ls -l /usr/bin/cat'.

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On 2022-07-08 at 07:48, Greg Wooledge wrote: > On Fri, Jul 08, 2022 at 12:47:19PM +0100, mick crane wrote: > >> here on bookworm >> mick@pumpkin:~$ ls -la /usr/bin |grep which >> lrwxrwxrwx 1 root root 23 Jan 23 18:05 which -> >> /etc/alternatives/which >> -rwxr-xr-x 1 root root

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On Fri, Jul 08, 2022 at 12:47:19PM +0100, mick crane wrote: > here on bookworm > mick@pumpkin:~$ ls -la /usr/bin |grep which > lrwxrwxrwx 1 root root 23 Jan 23 18:05 which -> > /etc/alternatives/which > -rwxr-xr-x 1 root root 946 May 1 17:47 which.debianutils > mick@pumpkin:~$ >

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On 2022-07-08 11:30, to...@tuxteam.de wrote: Not every binary is contained in a package called like it. That's what "apt-file" is for (in the same named package): tomas@trotzki:~$ apt-file search bin/which debian-goodies: /usr/bin/which-pkg-broke debian-goodies: /usr/bin/which-pkg-b

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

e what that has to do with anything else that's in this message. > export _GRAALVM_HOME=.../graalvm-ce-java17-22.1.0 > export PATH=${PATH}:${_GRAALVM_HOME}/bin > which javac > which java > $ > > bash: which: command not found > > # apt-get install which > Reading packa

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

d not found So, did you check what $PATH contains? (e.g. echo $PATH) It seems likely it's corrupted or missing the right directory (/usr/bin see below). > > # apt-get install which > Reading package lists... Done > Building dependency tree... Done > Reading state information

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

Done > Building dependency tree... Done > Reading state information... Done > E: Unable to locate package which > # > > > > # cat /etc/apt/sources.list > # deb cdrom:[Official Debian GNU/Linux Live 11.2.0 lxde > 2021-12-18T12:41]/ bullseye main > #d

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

graalvm-ce-java17-22.1.0 > export PATH=${PATH}:${_GRAALVM_HOME}/bin > which javac > which java > $ > > bash: which: command not found > > # apt-get install which > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done &g

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

which has been deprecated. Use command -v. If you need which -a, you are out of luck... Please find an attached which if you are interested. # apt-get install which > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > E: Unabl

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

Hi, Albretch Mueller wrote: > # apt-get install which > E: Unable to locate package which Try apt-get install debianutils I got the proposal from $ apt-file search which | grep 'which$' | less which still finds 18 lines which end by "which". Number two looks lik

bash: which: command not found? + (E: Unable to locate package which? ...)

ATH}:${_GRAALVM_HOME}/bin which javac which java $ bash: which: command not found # apt-get install which Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package which # # cat /etc/apt/sources.list # deb cdrom:[Official Deb

Re: Help with --regex in locate

cutable: > > $ chmod -v u+x show_args.bash > mode of 'show_args.bash' changed from 0640 (rw-r-) to 0740 (rwxr-) > > Now we have created a command that just > displays the arguments that it receives from > the shell. > > The command is in the curren

Re: Help with --regex in locate

x27;show_args.bash' changed from 0640 (rw-r-) to 0740 (rwxr-) Now we have created a command that just displays the arguments that it receives from the shell. The command is in the current directory and not in the PATH, so we need to specify its location when invoking it: ./show_arg

Re: Metavariable [was: Help with --regex in locate]

On Tue, Dec 03, 2019 at 10:18:59AM -0500, Stefan Monnier wrote: > > I think the canonical name is "metasyntactic variable" [1]. I've > > seen also just "metavariable", although Wikipedia would say that > > the latter belongs in the realm of logic [2], not programming. > > AFAICT those two usages a

Re: Metavariable [was: Help with --regex in locate]

> I think the canonical name is "metasyntactic variable" [1]. I've > seen also just "metavariable", although Wikipedia would say that > the latter belongs in the realm of logic [2], not programming. AFAICT those two usages are one and the same: when you see "foo" it's because the code is actually

Re: Help with --regex in locate

On Ma, 03 dec 19, 15:09:45, Jonas Smedegaard wrote: > > What I have so far settled on is to distinguish "variables" in capital > letters, and explicitly hint that it should be changed, like this: > > With 'find' instead of 'locate' (adapt dir):

Metavariable [was: Help with --regex in locate]

On Tue, Dec 03, 2019 at 08:07:16AM -0500, rhkra...@gmail.com wrote: [...] > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > With 'find' instead of 'locate'. [...] > It took me a minute (well, a trial) to realize that dir_with_repos is a >

Re: Help with --regex in locate

On Tuesday, December 03, 2019 09:01:16 AM Greg Wooledge wrote: > On Tue, Dec 03, 2019 at 05:54:33AM -0500, Rh Kramer wrote: > > locate --regex \/\.gitignore > > Your quoting is all wrong here. What you want is: > > locate --regex '/\.gitignore' > > The / d

Re: Help with --regex in locate

On Tuesday, December 03, 2019 09:09:45 AM Jonas Smedegaard wrote: > With 'find' instead of 'locate' (adapt dir): > > find DIR_WITH_REPOS -type d -name .git That helps, also, especially with the note "adapt dir" (or maybe "adjust dir", or

Re: Help with --regex in locate

On Tuesday, December 03, 2019 08:39:28 AM Brian wrote: > On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote: > > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > > With 'find' instead of 'locate'. > > > &

Re: Help with --regex in locate

Quoting Brian (2019-12-03 14:39:28) > On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote: > > > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > > With 'find' instead of 'locate'. > > > > > >

Re: Help with --regex in locate

On Tue, Dec 03, 2019 at 05:54:33AM -0500, Rh Kramer wrote: > locate --regex \/\.gitignore Your quoting is all wrong here. What you want is: locate --regex '/\.gitignore' The / does not need to be quoted, either for the shell, or for the regex. It's just a regular old charact

Re: Help with --regex in locate

On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote: > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > With 'find' instead of 'locate'. > > > > find dir_with_repos -type d -name .git > > > > or > > &g

Re: Help with --regex in locate

Andrei, Thanks very much! (Please forgive the nitpicky comment below.) On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > With 'find' instead of 'locate'. > > find dir_with_repos -type d -name .git > > or > > find dir_with_rep

Re: Help with --regex in locate

't mind other approaches, especially if they are simpler, I > would like to learn what I'm doing wrong with locate --regex. With 'find' instead of 'locate'. find dir_with_repos -type d -name .git or find dir_with_repos -type d -name "*.git"

Resolved: Re: Help with --regex in locate

specially if they are simpler, I > would like to learn what I'm doing wrong with locate --regex. > > Overall objective: > > I have several .git repositories on this computer. I want to get a list of > those repositories without getting a listing of all the files in each

Help with --regex in locate

what I'm doing wrong with locate --regex. Overall objective: I have several .git repositories on this computer. I want to get a list of those repositories without getting a listing of all the files in each repository. Each repository is in a different subdirectory, and with varying pa

Re: Problem to locate bug

Hi Julian, Quoting sj...@uranus.uni-freiburg.de (2019-11-21 11:39:14) > if it (from around June 28th) still matters for somebody: I > re-installed my whole system and I couldn't re-recognise the behaviour > described. I also can't remember having changed anything in the > "deeper settings of th

Re: Problem to locate bug

Hi, if it (from around June 28th) still matters for somebody: I re-installed my whole system and I couldn't re-recognise the behaviour described. I also can't remember having changed anything in the "deeper settings of the system"… However, best regards, Julian Schreck -- > Hi, > > Julian Schr

Re: Problem to locate bug

Hi, I tried to shut down the pc with ctrl + alt + 1 -> [login] -> sudo poweroff -> no reaction. I had some music file playing. A snippet (< 1 s) was repeated roughly between 5 and 10 times before I didn't hear anything further on. Ctrl + SysRq + k normally reboot immediately. In my case, no react

Re: Problem to locate bug

Hi, Julian Schreck wrote: > I could narrow it down to lxterminal (autostarted), You could start another terminal program from the lxterminal and then end the lxterminal. (I use "xterm", the old and sparse one.) You could also check whether the lxterm menus give you an opportunity to disable any f

Re: Problem to locate bug

Hi, I could narrow it down to lxterminal (autostarted), openbox or an automatically started process. Any other advice than changing the window manager (in case that was suggested/your intention)? - A rough description of the kind of computer: ”# lshw“ gives debian descr

Re: Problem to locate bug

On 6/24/19 6:52 AM, sj...@uranus.uni-freiburg.de wrote: Dear all, for some weeks (or months perhaps already), my screen freezes suddenly and once in a while without any chance to de-freeze it again. I don't know wether my input is recognized after such a freeze, but I don't think so. (I should'

Re: Problem to locate bug

Hi, sj...@uranus.uni-freiburg.de wrote: > As far as I can see, this behaviour may only be > caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution, > openbox. Consider to use alternatives for a few days until it is clear whether avoiding one or more of the suspects makes the freeze

Problem to locate bug

Dear all, for some weeks (or months perhaps already), my screen freezes suddenly and once in a while without any chance to de-freeze it again. I don't know wether my input is recognized after such a freeze, but I don't think so. (I should've tested this before writing to you…) The thing is that

Re: E: Unable to locate package zimlib . . .

On 25.01.2019 1:15, Albretch Mueller wrote: > I installed the package, but could not make sense of it. > > "zim" is the extension used by compressed wikipedia pages. You find > such files here: > > https://wiki.kiwix.org/wiki/Content > http://download.kiwix.org/zim/wikipedia_en_all_nopic.zim >

Re: E: Unable to locate package zimlib . . .

On 1/16/19, Tom Bachreier wrote: > I don't know what zimlib is but you mean maybe libzim? In stretch is > libzim0v5: > I installed the package, but could not make sense of it. "zim" is the extension used by compressed wikipedia pages. You find su

Re: E: Unable to locate package zimlib . . .

Hi! Jan 16, 2019, 8:00 AM by lbrt...@gmail.com: > Why is it I can't install zimlib? > I don't know what zimlib is but you mean maybe libzim? In stretch is libzim0v5: Tom

Re: E: Unable to locate package zimlib . . .

https://packages.debian.org/sid/xz-utils seems to be what I actually needed in order to decompress zim files

Re: E: Unable to locate package zimlib . . .

> Why is it I can't install zimlib? Because there is no package named zimlib available: https://packages.debian.org/search?keywords=zimlib You probably want libzim-dev, which does exist: https://packages.debian.org/search?keywords=libzim Note that libzim 2.x is only available fo

E: Unable to locate package zimlib . . .

Why is it I can't install zimlib? # apt-get install zimlib Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package zimlib # apt-get update Get:1 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB] Ign:2

Fwd: E : unable to locate package

I using Debian jessie 8.2.I use # DEBIAN # Debian Experimental deb http://ftp.de.debian.org/debian experimental main contrib non-free deb-src http://ftp.de.debian.org/debian experimental main contrib # Debian Sid # CURRENT UNSTABLE deb http://ftp.de.debian.org/debian sid main

cups Unable to locate printer

following error Unable to locate printer "maybel.local File: /etc/cups/cupsd.conf this the cupsd.conf on the printclient and the printserver LogLevel warn MaxLogSize 0 Listen *:631 Listen /var/run/cups/cups.sock Browsing On BrowseLocalProtocols

Re: Fwd: Unable to locate Bug's package

On 06/27/2015 at 08:35 PM, Nile Aagard wrote: > To whom it may concern, > > At present, I'm experiencing a nasty bug somewhere in my desktop > environment. I recently upgraded to Debian 8 which has given me a > myriad of problems, the latest of which being an intermittent issue > where all new w

Fwd: Unable to locate Bug's package

To whom it may concern, At present, I'm experiencing a nasty bug somewhere in my desktop environment. I recently upgraded to Debian 8 which has given me a myriad of problems, the latest of which being an intermittent issue where all new windows and menus are rendered as a black box on the screen.

Re: how do I locate all the pictures on an Android phone?

On Thu, Dec 11, 2014 at 02:32:18PM -0200, Andre N Batista wrote: > On Wed, Dec 10, 2014 at 06:05:13PM -0500, Gary Dale wrote: > > I'm running Jessie on an AMD64 system. > > > > Last night I took some pictures and tried my usual method of > > downloading - I plugged in the phone through USB and sel

Re: how do I locate all the pictures on an Android phone?

On Wed, Dec 10, 2014 at 06:05:13PM -0500, Gary Dale wrote: > I'm running Jessie on an AMD64 system. > > Last night I took some pictures and tried my usual method of > downloading - I plugged in the phone through USB and selecting File > Manager when the notification window popped up. Navigating to

Re: how do I locate all the pictures on an Android phone?

On 12/10/2014 03:05 PM, Gary Dale wrote: I'm running Jessie on an AMD64 system. Last night I took some pictures and tried my usual method of downloading - I plugged in the phone through USB and selecting File Manager when the notification window popped up. Navigating to /store_00010001/DCIM/Camer

how do I locate all the pictures on an Android phone?

I'm running Jessie on an AMD64 system. Last night I took some pictures and tried my usual method of downloading - I plugged in the phone through USB and selecting File Manager when the notification window popped up. Navigating to /store_00010001/DCIM/Camera, I found a lot of pictures but not t

Re: Unable to locate theme engine in module_path: "xfce"

On Wed, Jun 11, 2014 at 3:38 PM, Brian wrote: > On Tue 10 Jun 2014 at 21:34:49 -0700, Rusi Mody wrote: > > > Running the dialog for the printer -- captstatusui -- > > gives me the message > > Proprietiary software. > > > Gtk-WARNING **: Unable to locate t

Re: Unable to locate theme engine in module_path: "xfce"

On Tue 10 Jun 2014 at 21:34:49 -0700, Rusi Mody wrote: > Running the dialog for the printer -- captstatusui -- > gives me the message Proprietiary software. > Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", Any use? https://packages.debian.org/s

Unable to locate theme engine in module_path: "xfce"

ning the dialog for the printer -- captstatusui -- gives me the message Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", in hundreds takes a long while to start and slows my machine down. My vague guess is that many i386 packages had to be installed and at least two a

Re: E: Unable to locate package libpngwriter0-dev

don magnify wrote: > now that have sorted out the sources.list i get this: > E: Unable to locate package libpngwriter0-dev > for # apt-get install libpngwriter0-dev > > although http://packages.debian.org/squeeze/libpngwriter0-dev > > my guess is one is squeezing the other

Re: E: Unable to locate package libpngwriter0-dev

don magnify writes: > http://packages.debian.org/squeeze/libpngwriter0-dev > > do i create a separate sources.list for squeeze? No. I would recommend you to read sources.list(5) accurately, and then add squeeze repository into it. pgpuB6F9Kl7qe.pgp Description: PGP signature

E: Unable to locate package libpngwriter0-dev

hi... now that have sorted out the sources.list i get this: E: Unable to locate package libpngwriter0-dev for # apt-get install libpngwriter0-dev although http://packages.debian.org/squeeze/libpngwriter0-dev my guess is one is squeezing the other is weezing. so how do i force it in? do i

Re: Unable to locate mail spool file.

Unable > to locate Mail spool file. It is a UNIX Movemail account. What am I > doing wrong? > > I just want to get my local linux account email in IMAP in Thunderbird.. > /var/log/exim4/mainlog shows Completed, so it is doing it's job, so I > guess I am missing something in the

Unable to locate mail spool file.

ok, I have exim4 setup as internet site, using Maildir. my /home/user/Maildir is there. I sent a test message and a new message shows up in /home/user/Maildir/new . in Thunderbird when I try to check mail in that account is says Unable to locate Mail spool file. It is a UNIX Movemail account. What

Re: Unable to locate mail spool file.-SOLVED

Unable > to locate Mail spool file. It is a UNIX Movemail account. What am I > doing wrong? > > I just want to get my local linux account email in IMAP in Thunderbird.. > /var/log/exim4/mainlog shows Completed, so it is doing it's job, so I > guess I am missing something in the

Locate-like tool but which indexes files metadata as well (and allows you to search)

Hi. I'm dealing with millions and millions of small files in a directory structure and finding something with 'find' takes ages. So I was wandering if there is a locate-like tool which periodically indexes the files, but instead of storing only the path names, it also stores the

Re: "Segmentation faults" and "could not locate so-and-so library or plugin" ...

On Tue, 18 Sep 2012 02:21:51 +, Albretch Mueller wrote: > I am trying to install an application (huludesktop), but I either get a > "Segmentation fault" or "Hulu Desktop could not locate the Flash plugin" > message. (...) The error messages you get are similar t

"Segmentation faults" and "could not locate so-and-so library or plugin" ...

I am trying to install an application (huludesktop), but I either get a "Segmentation fault" or "Hulu Desktop could not locate the Flash plugin" message. You may easily spot the mistake or have suggestions based on the steps I followed or you could let me know about either

  1   2   3   4   5   >