> On Sep 2, 2022, at 8:14 PM, Kevin Price wrote:
>
> Am 03.09.22 um 02:15 schrieb Kevin Price:
>> Let's double check whether our connman is in fact the culprit, and then
>> make arrest. (file bug report)
>
> We got him. :) Casey, you file the bug report, Okay?
Done! https://bugs.debian.org/c
Am 03.09.22 um 02:15 schrieb Kevin Price:
> Let's double check whether our connman is in fact the culprit, and then
> make arrest. (file bug report)
We got him. :) Casey, you file the bug report, Okay?
Blank debian,
apt --no-install-recommends install connman
will break "disable_ipv6" as you
Am 02.09.22 um 22:03 schrieb Casey Deccio:
> Then I ran tasksel and add Debian desktop environment and LXDE and rebooted.
> At that point, disable_ipv6 does *not* work.
>
> Now, this does seem to narrow it down--sort of.
It does. And *now* I can reproduce.
task-lxde-desktop requires lxde,
lxde
> On Fri, 2 Sep 2022 12:09:31 -0400
> Dan Ritter wrote:
>
> > Dave Howorth wrote:
> > >
> > > I'd like to use uvcdynctrl on a bullseye 64-bit system. But
> > > according to
> > > https://packages.debian.org/search?keywords=uvcdynctrl the
> > > package is not available for any flavour of bulls
> On Sep 2, 2022, at 1:05 PM, Kevin Price wrote:
>
> I suspect your "very little customization" (since you're doing
> networking stuff) or the "VBox Guest Additions" (since they mess with
> network interfaces). In order to test this, I used
> debian-11.3.0-amd64-netinst.iso from the archive to
On Fri, 02 Sep 2022 18:43:29 +0200
Sven Joachim wrote:
> On 2022-09-02 16:47 +0100, Dave Howorth wrote:
>
> > I'd like to use uvcdynctrl on a bullseye 64-bit system. But
> > according to https://packages.debian.org/search?keywords=uvcdynctrl
> > the package is not available for any flavour of bu
On Fri, 02 Sep 2022 18:43:29 +0200
Sven Joachim wrote:
> On 2022-09-02 16:47 +0100, Dave Howorth wrote:
>
> > I'd like to use uvcdynctrl on a bullseye 64-bit system. But
> > according to https://packages.debian.org/search?keywords=uvcdynctrl
> > the package is not available for any flavour of bu
On Fri, 2 Sep 2022 12:09:31 -0400
Dan Ritter wrote:
> Dave Howorth wrote:
> >
> > I'd like to use uvcdynctrl on a bullseye 64-bit system. But
> > according to https://packages.debian.org/search?keywords=uvcdynctrl
> > the package is not available for any flavour of bullseye. It is
> > available
On Fri, 2 Sep 2022 12:09:31 -0400
Dan Ritter wrote:
> Dave Howorth wrote:
> >
> > I'd like to use uvcdynctrl on a bullseye 64-bit system. But
> > according to https://packages.debian.org/search?keywords=uvcdynctrl
> > the package is not available for any flavour of bullseye. It is
> > available
Am 02.09.22 um 15:46 schrieb Casey Deccio:
>> On Sep 2, 2022, at 2:51 AM, Kevin Price wrote:
> Thanks for the idea. I took your advice and booted my 5.10.0-17 system
> (problem system) with 5.10.0-13. The problem persisted! Then I updated my
> "old" (non-problem) system from Debian 11.3 to 11
On 2022-09-02 16:47 +0100, Dave Howorth wrote:
> I'd like to use uvcdynctrl on a bullseye 64-bit system. But according
> to https://packages.debian.org/search?keywords=uvcdynctrl the package
> is not available for any flavour of bullseye. It is available for both
> earlier (stretch and buster) and
On 01/09/2022 06:33, David Christensen wrote:
First sentence -- You don't want the OS to access the drive on the next
boot.
I would say that while ddrescue is running any other disk operations,
especially causing seeks, may be undesired. While smartd may be
configured or stopped, udisksd is
Dave Howorth wrote:
>
> I'd like to use uvcdynctrl on a bullseye 64-bit system. But according
> to https://packages.debian.org/search?keywords=uvcdynctrl the package
> is not available for any flavour of bullseye. It is available for both
> earlier (stretch and buster) and later (bookworm and sid
I'd like to use uvcdynctrl on a bullseye 64-bit system. But according
to https://packages.debian.org/search?keywords=uvcdynctrl the package
is not available for any flavour of bullseye. It is available for both
earlier (stretch and buster) and later (bookworm and sid) releases.
So I'm curious wh
On Fri 02 Sep 2022 at 13:44:24 (+0300), Anssi Saari wrote:
>
> I have an LTE module in my Debian router for failover in case my fiber
> goes down. It has this occasional issue that mostly its interface is
> wwan0 but sometimes it's wwx0a697e2d934f.
>
> When that happens I have something like this
> On Sep 2, 2022, at 2:51 AM, Kevin Price wrote:
>
> Am 02.09.22 um 06:33 schrieb Casey Deccio:
>> 1) a sanity check (can others confirm the behavior discrepancy?);
>
> No. My 5.10.0-17 behaves like your 5.10.0-13.
Thanks so much for checking!
> 2) an expectation of *correct* behavior (seem
Tixy writes:
> The number in the name looks like a MAC address and its value is in the
> 'locally administered' range, i.e. not something baked into the device
> by the manufacturer.
It's an LTE device so it doesn't have a MAC address even though it
presents an ethernet-like interface. Or I gues
On Fri, 2022-09-02 at 13:44 +0300, Anssi Saari wrote:
> I have an LTE module in my Debian router for failover in case my fiber
> goes down. It has this occasional issue that mostly its interface is
> wwan0 but sometimes it's wwx0a697e2d934f.
>
> When that happens I have something like this in my s
On Fri 02 Sep 2022 at 13:44:24 +0300, Anssi Saari wrote:
>
> I have an LTE module in my Debian router for failover in case my fiber
> goes down. It has this occasional issue that mostly its interface is
> wwan0 but sometimes it's wwx0a697e2d934f.
>
> When that happens I have something like this
Sven Joachim writes:
> On 2022-08-31 08:47 -0400, Kenneth Parker wrote:
>
>> On Wed, Aug 31, 2022, 5:36 AM riveravaldez
>> Okay. So archivemail hasn't been updated for Python 3 yet.
>
> s/ yet//
>
> Some people have tried, but gave up eventually, therefore the package
> has been removed. See
I have an LTE module in my Debian router for failover in case my fiber
goes down. It has this occasional issue that mostly its interface is
wwan0 but sometimes it's wwx0a697e2d934f.
When that happens I have something like this in my syslog:
Sep 1 08:34:40 animus kernel: [8.150781] qmi_ww
Chuck Zmudzinski writes:
> On 8/31/22 11:03 AM, Jeremy Ardley wrote:
> It also seems to be a ridiculously long time (ten minutes) for your provider
> to configure your interface. I would look for a different provider if they
> can't or won't fix it.
Or maybe just create an overlay for the haprox
On Fri 02 Sep 2022 at 01:03:21 +, jindam, vani wrote:
> hello debian users,
>
> i want to attach files when creating a new issue
> using reportbug. i could not find an option
> to use it.
I rather think adding an attachment is a function of your mail client.
I do it in mutt just before sen
Am 02.09.22 um 06:33 schrieb Casey Deccio:
> 1) a sanity check (can others confirm the behavior discrepancy?);
No. My 5.10.0-17 behaves like your 5.10.0-13.
2) an expectation of *correct* behavior (seems to me like the 5.10.0-13
behavior is "correct");
Yes.
and 3) suggestions for next steps.
F
On 2022-09-02, David Wright wrote:
> On Fri 02 Sep 2022 at 01:02:10 (+), jindam, vani wrote:
>> i am trying to open pdf file from cli:
>> $ /usr/bin/lowriter --inputfilter="*.pdf" /home/user/file.pdf
>
> ↑↑↑
>
>> the above command fails to open pdf file
>>
>> what am
25 matches
Mail list logo
