On 9/2/21 5:37 PM, David Wright wrote:
On Wed 01 Sep 2021 at 16:00:13 (-0700), David Christensen wrote:
[three long posts]
That was very useful. I've condensed it into a file (attached) for
my own use. The footnotes are notes, guesses and queries.
I tried to file a bug report against the deb
On 03/09/2021 01:34, David Wright wrote:
(I use my own customisations for distinct colours on each host,
and inverse colours for root's prompt.)
Can you please share your root prompt invocation? Thanks!
--
With kindest regards, piorunz.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
On Thu, Sep 2, 2021, 7:34 PM David Wright wrote
>
> (I use my own customisations for distinct colours on each host,
> and inverse colours for root's prompt.)
>
Good idea :-)
For some reason putting "root:" there doesn't save me 100% of the time :-)
Cheers,
> David.
>
>
On Wed 01 Sep 2021 at 16:00:13 (-0700), David Christensen wrote:
[three long posts]
That was very useful. I've condensed it into a file (attached) for
my own use. The footnotes are notes, guesses and queries.
My main question is — there are three identical listings taken at
different times; all
On Thu 02 Sep 2021 at 09:46:33 (+), Andrew M.A. Cater wrote:
> On Wed, Sep 01, 2021 at 08:12:06PM +0300, Andrei POPESCU wrote:
> > On Mi, 01 sep 21, 12:32:19, Andrew M.A. Cater wrote:
> > > debian-user is a mailing list provided for support for Debian users,
> > > and to facilitate discussion o
On Fri 03 Sep 2021 at 03:15:13 (+0300), IL Ka wrote:
> .bashrc on bullseye contains following lines
>
> ```
> # set a fancy prompt (non-color, unless we know we "want" color)
> case "$TERM" in
> xterm-color|*-256color) color_prompt=yes;;
> esac
> ```
>
> So we only have colors in the termina
On 2021-09-03 00:21, Brian wrote:
On Fri 03 Sep 2021 at 00:03:08 +0100, mick crane wrote:
On 2021-09-02 23:28, Brian wrote:
[...]
> Please go back and read your very first post. You asked three questions.
> Which one has not been answered?
Please understand you are talking to an idiot, you
Hi
.bashrc on bullseye contains following lines
```
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac
```
So we only have colors in the terminal emulator, but not in virtual
linux console.
This could be fixed by
On Fri 03 Sep 2021 at 00:03:08 +0100, mick crane wrote:
> On 2021-09-02 23:28, Brian wrote:
[...]
> > Please go back and read your very first post. You asked three questions.
> > Which one has not been answered?
>
> Please understand you are talking to an idiot, you have to say things slowly
>
On 2021-09-02 23:28, Brian wrote:
On Thu 02 Sep 2021 at 21:06:59 +0100, mick crane wrote:
On 2021-09-02 17:57, Brian wrote:
> Regarding Greg Wooledge's exhortations to provide information about
> an issue: You were asked explicity to provide some; you never did.
> As it happens, I do not think
On Thu, 02 Sep 2021 16:09:23 -0500
"David Palacio" wrote:
> Hi,
>
> > If you copied a disk image (.qcow2 extension) over, but not the
> > setup files that Virtual Machine Manager (VMM) uses
> > (in /etc/libvirt), then Windows is on a new machine, and can have
> > conniptions over it. Go into Win
On Thu 02 Sep 2021 at 21:06:59 +0100, mick crane wrote:
> On 2021-09-02 17:57, Brian wrote:
>
> > Regarding Greg Wooledge's exhortations to provide information about
> > an issue: You were asked explicity to provide some; you never did.
> > As it happens, I do not think the problems you have enco
On Thu, Sep 2, 2021, at 2:09 PM, Charles Curley wrote:
> On Thu, 02 Sep 2021 12:43:41 -0500
> "David Palacio" wrote:
>
> > Good day,
> >
> > I have recently installed Debian testing around its alpha release
> > state. Previously I had a working Windows 10 QEMU guest with access
> > to the host S
On Thu, Sep 02, 2021 at 10:01:24PM +0100, piorunz wrote:
> On 02/09/2021 21:30, Miguel A. Vallejo wrote:
> > Oh. You Are running UNSTABLE version of Debian. And just installed a
> > program outside of Debian, from third party website. You must know what
> > you are doing.
> >
> > I kno
On 02/09/2021 21:30, Miguel A. Vallejo wrote:
Oh. You Are running UNSTABLE version of Debian. And just installed a
program outside of Debian, from third party website. You must know what
you are doing.
I know what I'm doing, thank you.
That's great.
I know how to report bugs, but
> Oh. You Are running UNSTABLE version of Debian. And just installed a
> program outside of Debian, from third party website. You must know what
> you are doing.
I know what I'm doing, thank you.
> Also you must then know how to report bugs like this, I
> understand. Otherwise you shouldn't be
On 02/09/2021 19:23, Miguel A. Vallejo wrote:
I thought it was clear, but I was wrong.
Telegram from website ( version 3.0.1 ), running in KDE under Unstable.
Oh. You Are running UNSTABLE version of Debian. And just installed a
program outside of Debian, from third party website. You must know
On 2021-09-02 17:57, Brian wrote:
Regarding Greg Wooledge's exhortations to provide information about
an issue: You were asked explicity to provide some; you never did.
As it happens, I do not think the problems you have encountered
have anything to do with saned. You have picked the wrong targe
Thanks to those who chimed in!
My focus today is on those lines in ~/.icewm/preferences that
specify fonts for the task bar. I have in mind such statements
as:
NormalTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"
ActiveTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"
I suspec
On Thu, 02 Sep 2021 12:43:41 -0500
"David Palacio" wrote:
> Good day,
>
> I have recently installed Debian testing around its alpha release
> state. Previously I had a working Windows 10 QEMU guest with access
> to the host Samba shares in a previous Debian testing install. I
> copied the Window
On Thu, Sep 02, 2021 at 08:23:43PM +0200, Miguel A. Vallejo wrote:
> I thought it was clear, but I was wrong.
>
> Telegram from website ( version 3.0.1 ), running in KDE under Unstable.
> Everything was ok until Bullseye came out and a tsunami of new packages
> arrived to Unstable. Since that mome
I thought it was clear, but I was wrong.
Telegram from website ( version 3.0.1 ), running in KDE under Unstable.
Everything was ok until Bullseye came out and a tsunami of new packages
arrived to Unstable. Since that moment the icon disappeared. Everything
seems to work fine, except for that icon.
On 02/09/2021 18:53, Miguel A. Vallejo wrote:
Hello!
Since the new Debian release and after a ton of new packages arrived to
Unstable I noticed the system tray icon for Telegram desktop does not
appear... or at least it appear completely black. See attached image.
Is it a Debian problem or a Te
Hello!
Since the new Debian release and after a ton of new packages arrived to
Unstable I noticed the system tray icon for Telegram desktop does not
appear... or at least it appear completely black. See attached image.
Is it a Debian problem or a Telegram problem? Any ideas?
Thank you
Good day,
I have recently installed Debian testing around its alpha release state.
Previously I had a working Windows 10 QEMU guest with access to the host Samba
shares in a previous Debian testing install. I copied the Windows 10 disk image
over to the new Debian install and set it up to run a
On Thu 02 Sep 2021 at 17:05:10 +0100, mick crane wrote:
> On 2021-09-02 16:22, Greg Wooledge wrote:
> > On Thu, Sep 02, 2021 at 04:13:34PM +0100, mick crane wrote:
> > > I'll just presume you are grumpy because you have had the jab.
> >
> > Please stop.
> >
> > Take a breath. In. Out.
> >
> >
I found at least a workaround: I installed and use xscreensaver for
locking the screen. Unlike light-locker that xfce uses by default,
xscreensaver doesn't seem to mess with the colormap.
I should add: I am using nominally the same installation of debian 10 on
two computers with very different ha
On 2021-09-02 16:22, Greg Wooledge wrote:
On Thu, Sep 02, 2021 at 04:13:34PM +0100, mick crane wrote:
I'll just presume you are grumpy because you have had the jab.
Please stop.
Take a breath. In. Out.
Now: what is the problem you're experiencing? Start with a high level
description: "My
On Thu, Sep 02, 2021 at 04:13:34PM +0100, mick crane wrote:
> I'll just presume you are grumpy because you have had the jab.
Please stop.
Take a breath. In. Out.
Now: what is the problem you're experiencing? Start with a high level
description: "My scanner doesn't work", for example.
After t
On 2021-09-02 10:53, Curt wrote:
On 2021-09-01, mick crane wrote:
On 2021-09-01 16:22, Greg Wooledge wrote:
On Wed, Sep 01, 2021 at 04:06:37PM +0100, mick crane wrote:
On 2021-09-01 15:15, Brian wrote:
> * saned is socket activated.
> * saned@.service manages saned instances.
> * saned.servic
On Thu, Sep 02, 2021 at 05:44:33AM +0200, Thomas Anderson wrote:
> Thanks for the insightful replies.
>
> I think I am getting closer to a solution.
>
> Wouldn't it be possible to bind the "redraw-current-line" to the delete
> (ASCII DEL), i.e. Alt 127??
>
> And, just add that to my user's bash
On 2021-09-01, mick crane wrote:
> On 2021-09-01 16:22, Greg Wooledge wrote:
>> On Wed, Sep 01, 2021 at 04:06:37PM +0100, mick crane wrote:
>>> On 2021-09-01 15:15, Brian wrote:
>>> > * saned is socket activated.
>>> > * saned@.service manages saned instances.
>>> > * saned.service is masked becau
On Wed, Sep 01, 2021 at 08:12:06PM +0300, Andrei POPESCU wrote:
> On Mi, 01 sep 21, 12:32:19, Andrew M.A. Cater wrote:
> > debian-user is a mailing list provided for support for Debian users,
> > and to facilitate discussion on relevant topics.
> >
> > Some guidelines which may help explain how t
33 matches
Mail list logo
