On Thu, 6 Feb 2025 14:51:17 +
Joe wrote:
>
> > On 2/6/25 8:20 AM, Charles Curley wrote:
> > >
> > > And for those who are wondering, this is going on in trixie.
[...]
> The quick fix in sources.list for debian is to add signed-by into
> existing lines after deb or deb-src:
>
> deb \
> [
On Thu, Feb 06, 2025 at 08:53:49AM -0700, Charles Curley wrote:
On Thu, 6 Feb 2025 10:42:27 -0500
Michael Stone wrote:
>...except that, per the rest of the discussion in that bug, it almost
>certainly won't be able to predict which signer to apply for each
>sources.list entry. That you'll prob
Also, there is https://wiki.debian.org/SourcesList .
Regards,
Jörg.
Hi,
On Thu, Feb 06, 2025 at 08:27:54AM -0500, Dan Ritter wrote:
> Charles Curley wrote:
> > Another option would be to retain all comments, and let the user
> > manually convert commented out entries. Simple, easy to do, and only a
> > little obnoxious for the user.
> >
> > And for those who are
On Thu, 6 Feb 2025 08:53:49 -0700
Charles Curley wrote:
> However, it is not in the man page for apt or apt-get.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094784
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
On Thu, 6 Feb 2025 15:30:02 +
Joe wrote:
> Why in the world bother making your own scripts when you can just do
>
> # apt modernize-sources
> The following files need modernizing:
> - /etc/apt/sources.list.d/google-chrome-beta.list
> - /etc/apt/sources.list.d/google-earth-pro.list
> -
Andy Smith wrote:
> Hi,
>
> On Thu, Feb 06, 2025 at 01:51:49AM -0500, songbird wrote:
>> when doing the upgrade you do have the option of doing
>> a test run to see what changes are made or not making the
>> changes at that time.
>>
>> when goi
On Thu, 6 Feb 2025 10:42:27 -0500
Michael Stone wrote:
> >...except that, per the rest of the discussion in that bug, it almost
> >certainly won't be able to predict which signer to apply for each
> >sources.list entry. That you'll probably have to add on your own.
>
> It even tells you that!
On Thu, Feb 06, 2025 at 10:22:17AM -0500, The Wanderer wrote:
I haven't seen this hit yet (though I probably will next time I
dist-upgrade against testing), but a comment in bug #1094263 leads me to
suspect that there is now supposed to be an 'apt modernize-sources'
sub-command, which looks like
On Thu, 6 Feb 2025 08:09:37 -0700
Charles Curley wrote:
> On Thu, 6 Feb 2025 14:51:17 +
> Joe wrote:
>
> > The long-term fix is a file standard.sources root:root 644 in
> > /etc/sources.list.d containing:
>
> Is there anything that tells one how to make this conversion? Better
> yet, a s
On 2025-02-06 at 10:09, Charles Curley wrote:
> On Thu, 6 Feb 2025 14:51:17 + Joe wrote:
>
>> The long-term fix is a file standard.sources root:root 644 in
>> /etc/sources.list.d containing:
>
> Is there anything that tells one how to make this conversion? Better
> yet, a script or two to d
On Thu, Feb 06, 2025 at 08:09:37AM -0700, Charles Curley wrote:
Is there anything that tells one how to make this conversion? Better
yet, a script or two to do it for us? There will be a lot of people
scrambling to convert at the last minute.
Yes, current version prompts on what to do.
On Thu, 6 Feb 2025 14:51:17 +
Joe wrote:
> The long-term fix is a file standard.sources root:root 644 in
> /etc/sources.list.d containing:
Is there anything that tells one how to make this conversion? Better
yet, a script or two to do it for us? There will be a lot of people
scrambling to co
hem their
own sources.list.d/.sources files e.g. opera-stable.sources,
dmo.sources (deb-multimedia.org).
Note that some upgrades may place/maintain .list files in
sources.list.d, as was formerly customary. This will again cause the
double source error, the new file should be checked and if necessary
an
On Feb 06, 2025, Frank McCormick wrote:
>
>
> On 2/6/25 8:20 AM, Charles Curley wrote:
> > On Thu, 6 Feb 2025 07:53:07 +
> > Andy Smith wrote:
> >
> > > Having said that, I am not sure how the complaint could be addressed
> > > since from what I understand you are basically asking for other
On 2/6/25 8:20 AM, Charles Curley wrote:
On Thu, 6 Feb 2025 07:53:07 +
Andy Smith wrote:
Having said that, I am not sure how the complaint could be addressed
since from what I understand you are basically asking for otherwise
valid but commented-out sources.list lines to be converted in
Charles Curley wrote:
> On Thu, 6 Feb 2025 07:53:07 +
> Andy Smith wrote:
>
> > Having said that, I am not sure how the complaint could be addressed
> > since from what I understand you are basically asking for otherwise
> > valid but commented-out sources.list lines to be converted into
> >
On Thu, 6 Feb 2025 07:53:07 +
Andy Smith wrote:
> Having said that, I am not sure how the complaint could be addressed
> since from what I understand you are basically asking for otherwise
> valid but commented-out sources.list lines to be converted into
> inactive deb822 files, which seems l
Hi,
On Thu, Feb 06, 2025 at 01:51:49AM -0500, songbird wrote:
> when doing the upgrade you do have the option of doing
> a test run to see what changes are made or not making the
> changes at that time.
>
> when going through this process the comments in
> sources.list
when doing the upgrade you do have the option of doing
a test run to see what changes are made or not making the
changes at that time.
when going through this process the comments in
sources.list were discarded.
i don't know about other people or what they put in
sources.list,
On Mon, Dec 4, 2023, 3:30 AM Thomas Schmitt wrote:
> .
> This seems to indicate that the firmware has a stake in the problem ...
>
> > Both the Thinkpad E14 Gen 5s had the same specifications and type number,
> > differing only in that the one with corruption of the installer has 24GB
> of
>
gene heskett wrote:
...
> I load up a file I want to 3d print in cura, slice it into gcode, click
> on save to disk. kde gets in the way so it opens a tab on the toolbar at
> the bottom of the screen and to continue I have to click on that tab.
> 20% of the time the where do you want to save it
Eduardo M KALINOWSKI wrote:
...
> He just told you to not hijack threads, and there you go and your
> immediate reply is to start talking about something completely unrelated
> to the rest of the discussion.
oops, sorry, i just replied again.
songbird
On 07/08/2023 23:45, gene heskett wrote:
On 8/7/23 21:47, Greg Wooledge wrote:
Start a new thread, and treat the problem seriously. Show us the
commands you're running and their output. Show us the relevant
parts of your configuration.
That particular problem has been solved, Greg, and 60 day
On 8/7/23 21:47, Greg Wooledge wrote:
On Mon, Aug 07, 2023 at 09:03:47PM -0400, gene heskett wrote:
And I'm back
to hunting for the reason I can ping yahoo.com but not other machines on my
local net, that are fully identified in my hosts file or vice versa
Start a new thread, and treat the pro
On Mon, Aug 07, 2023 at 09:03:47PM -0400, gene heskett wrote:
> And I'm back
> to hunting for the reason I can ping yahoo.com but not other machines on my
> local net, that are fully identified in my hosts file or vice versa
Start a new thread, and treat the problem seriously. Show us the
command
On 8/7/23 18:43, Brian wrote:
On Mon 07 Aug 2023 at 17:53:41 -0400, gene heskett wrote:
On 8/7/23 14:57, Brian wrote:
On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:
[...]
Sorry you are so offended by a hosts file user Andy, but when the guys
Did someone mention a hosts file? Is
On Mon 07 Aug 2023 at 17:53:41 -0400, gene heskett wrote:
> On 8/7/23 14:57, Brian wrote:
> > On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:
> >
> > [...]
> >
> > > Sorry you are so offended by a hosts file user Andy, but when the guys
> >
> > Did someone mention a hosts file? Is thi
On 8/7/23 14:57, Brian wrote:
On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:
[...]
Sorry you are so offended by a hosts file user Andy, but when the guys
Did someone mention a hosts file? Is this an attempt to move discussion on
to a different toic? I thought 'chattr -i' and the w
Hi Brian,
On Mon, Aug 07, 2023 at 07:57:07PM +0100, Brian wrote:
> On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:
> > Sorry you are so offended by a hosts file user Andy, but when the guys
>
> Did someone mention a hosts file?
If I understand correctly, Gene identifies himself as "a h
On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:
[...]
> Sorry you are so offended by a hosts file user Andy, but when the guys
Did someone mention a hosts file? Is this an attempt to move discussion on
to a different toic? I thought 'chattr -i' and the wisdom of using it was
under disc
On Sun, Aug 06, 2023 at 08:50:26PM -0400, gene heskett wrote:
> Sorry you are so offended by a hosts file user Andy [...]
Now this is stuff for Quote of the Day ;-)
Thank you, Gene.
Cheers
--
t
signature.asc
Description: PGP signature
Sorry you are so offended by a hosts file user Andy, but when the guys
decide to do networking differently, usually in the badly mistaken idea
that everybody runs a dhcpd server even for their isolated local
network, and don't check that their brainless changes don't screw up a
host
> On Sun, Aug 06, 2023 at 05:17:23PM +0800, Jon Smart wrote:
>> It's a VPS provided by a local ISP. The VPS has a static IPv4.
>> Do you know how to know if /etc/resolv.conf is modified by dhcp?
>
> The first thing you could do is check whether a DHCP client daemon
> is running. That's usually a s
On Sun, Aug 06, 2023 at 04:09:14PM +, Andy Smith wrote:
[...]
> And we wonder why this list ends up dealing with the aftermath of
> the Gene school of "don't understand it? Hit it with chattr +i / rm
> / apt-get purge!" so often.
I must admit that I was one of those proposing chattr +i in th
Hi Greg,
On Sun, Aug 06, 2023 at 08:48:25AM -0400, Greg Wooledge wrote:
> On Sun, Aug 06, 2023 at 07:37:35PM +0800, Jon Smart wrote:
> > These 4 steps do work great!
> > Thanks a lot.
>
> These same steps are also on the wiki page that's been discussed many
> times in this thread. You might want
Hello,
On Sun, Aug 06, 2023 at 07:37:35PM +0800, Jon Smart wrote:
> > Timothy M Butterworth wrote:
> > The file /etc.resolv.conf is just a soft link.
> >
> > You need to:
> >
> > 1: Delete /etc/resolv.conf - rm /etc/resolv.conf
> > 2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
> >
ions/907246/how-to-disable-systemd-resolved-in-ubuntu
> > >>
> > >> And I have unbound installed and enabled as local DNS server.
> > >>
> > >> But every time I reboot the server, the configuration file
> > >> /etc/resolv.conf changes to a default one.
On Sun, Aug 06, 2023 at 05:17:23PM +0800, Jon Smart wrote:
> It's a VPS provided by a local ISP. The VPS has a static IPv4.
> Do you know how to know if /etc/resolv.conf is modified by dhcp?
The first thing you could do is check whether a DHCP client daemon
is running. That's usually a sign.
Fai
On Sun, Aug 06, 2023 at 07:37:35PM +0800, Jon Smart wrote:
> Unattributed:
> > The file /etc.resolv.conf is just a soft link.
Not always.
> > You need to:
> >
> > 1: Delete /etc/resolv.conf - rm /etc/resolv.conf
> > 2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
> > 3: Configure yo
I dunno.
How about the fact that it just solves the symptom but not the real problem?
/etc/resolv.conf does not change by itself, some tool must be making the
(possibly undesired) changes, so in most cases, I'd say it's better to
configure that tool to stop changing resolv.conf,
t; And I have unbound installed and enabled as local DNS server.
>> >>
>> >> But every time I reboot the server, the configuration file
>> >> /etc/resolv.conf changes to a default one. So every time I have to
>> >> update
>> >> its
fault systemd-resolved local dns service following
> >> the link below,
> >>
> >>
> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
> >>
> >> And I have unbound installed and enabled as local DNS server.
> >>
>
gt;
> >> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
> >>
> >> And I have unbound installed and enabled as local DNS server.
> >>
> >> But every time I reboot the server, the configuration file
> >> /etc/resolv.co
/askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
>>
>> And I have unbound installed and enabled as local DNS server.
>>
>> But every time I reboot the server, the configuration file
>> /etc/resolv.conf changes to a default one. So every ti
led and enabled as local DNS server.
>
> But every time I reboot the server, the configuration file
> /etc/resolv.conf changes to a default one. So every time I have to update
> its content to:
>
> nameserver 127.0.0.1
>
> (points to unbound)
>
> How to stop the auto-
t; > > On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > > > > How to stop the auto-changes to /etc/resolv.conf after rebooting?
> > > >
> > > > https://wiki.debian.org/resolv.conf
> > > >
> > >
> > > Contrary t
On Sat, Aug 5, 2023, 10:27 PM Greg Wooledge wrote:
> On Sat, Aug 05, 2023 at 10:05:31PM -0500, Nicholas Geovanis wrote:
> > On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge wrote:
> >
> > > On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > > >
On Sat, Aug 05, 2023 at 10:05:31PM -0500, Nicholas Geovanis wrote:
> On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge wrote:
>
> > On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > > How to stop the auto-changes to /etc/resolv.conf after rebooting?
> >
On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge wrote:
> On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > How to stop the auto-changes to /etc/resolv.conf after rebooting?
>
> https://wiki.debian.org/resolv.conf
>
Contrary to what that page states, auto changes to res
On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> How to stop the auto-changes to /etc/resolv.conf after rebooting?
https://wiki.debian.org/resolv.conf
reboot the server, the configuration file
/etc/resolv.conf changes to a default one. So every time I have to update
its content to:
nameserver 127.0.0.1
(points to unbound)
How to stop the auto-changes to /etc/resolv.conf after rebooting?
Thanks.
What is the new contents of /etc/resolv.conf
file
/etc/resolv.conf changes to a default one. So every time I have to update
its content to:
nameserver 127.0.0.1
(points to unbound)
How to stop the auto-changes to /etc/resolv.conf after rebooting?
Thanks.
On 2022-12-16 13:00, Tim Woodall wrote:
Thanks Tim, I will root around in the docs a little more. Strange
because I've done multiple updates since your last backup date of Dec
2nd and not had this issue. H.
--
Regards,
John Boxall
explicitly before updates for this repository can
be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this
repository? [y/N] n
Hit:5 https://download.virtualbox.org/virtualbox/debian buster InRelease
Hit:6 https://updates.signal.org/desk
ry can
be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this
repository? [y/N] n
Hit:5 https://download.virtualbox.org/virtualbox/debian buster InRelease
Hit:6 https://updates.signal.org/desktop/apt xenial InRelease
Reading packa
ebian-Security'
N: Repository 'http://security.debian.org/debian-security buster/updates
InRelease' changed its 'Version' value from '10.13' to '10'
N: This must be accepted explicitly before updates for this repository can be
applied. See apt-secure(8) man
27;http://security.debian.org/debian-security buster/updates
InRelease' changed its 'Version' value from '10.13' to '10'
N: This must be accepted explicitly before updates for this repository
can be applied. See apt-secure(8) manpage for details.
Do you want to
s TouchPad"
> > > $ cat ~/opt/bin/touchpad-off
> > > xinput disable "SynPS/2 Synaptics TouchPad"
> > >
> > > The problem is that xinput(1) changes the name of the touchpad every
> > > now and again:
> > >
> > > $
rtcuts:
>
> $ cat ~/opt/bin/touchpad-on
> xinput enable "SynPS/2 Synaptics TouchPad"
> $ cat ~/opt/bin/touchpad-off
> xinput disable "SynPS/2 Synaptics TouchPad"
>
> The problem is that xinput(1) changes the name of the touchpad every
> now
SynPS/2 Synaptics TouchPad"
> xinput disable "SynPS/2 Synaptics TouchPad"
>
> The problem is that xinput(1) changes the
> name of the touchpad every now and again:
>
> $ dmesg| grep -i synaptics |grep "as /devices"
> [463340.358242] input: Synaptics TM2
medium
[...]
* Enable high precision timestamps with timezone information.
Use the default rsyslog file format, which provides several benefits
like:
- sortable
- time zone information
- sub-second time resolution
Testing and unstable users ought to expect changes, and they ought to
be self-aware enough to include "I'm running testing" in their emails.
Nov 5, 2022, 14:53 by j...@k4vqc.com:
> On Sat, 2022-11-05 at 11:34 +0100, local10 wrote:
>
>> Nov 5, 2022, 09:55 by scdbac...@gmx.net:
>>
>> > Hi,
>> >
>> > local10 wrote:
>> >
>> > > Any ideas as to get the old syslog date format back?
>> > >
>> >
>> > The internet points to /etc/rsyslog.con
> > > local10 wrote:
> > >
> > > > Any ideas as to get the old syslog date format back?
What caused a change? What version of Debian are you running? What
happened on the date in question (November 4) -- were some packages
updated? Which ones?
Here in Debian 11 (bullseye), I see no such chang
On Sat, 2022-11-05 at 11:34 +0100, local10 wrote:
> Nov 5, 2022, 09:55 by scdbac...@gmx.net:
>
> > Hi,
> >
> > local10 wrote:
> >
> > > Any ideas as to get the old syslog date format back?
> > >
> >
> > The internet points to /etc/rsyslog.conf and in there:
> >
> > #
> > # Use traditional t
Nov 5, 2022, 09:55 by scdbac...@gmx.net:
> Hi,
>
> local10 wrote:
>
>> Any ideas as to get the old syslog date format back?
>>
>
> The internet points to /etc/rsyslog.conf and in there:
>
> #
> # Use traditional timestamp format.
> # To enable high precision timestamps, comment out the followin
Hi,
local10 wrote:
> Any ideas as to get the old syslog date format back?
The internet points to /etc/rsyslog.conf and in there:
#
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
$ActionFileDefaultTemplate RSYSLOG_Traditional
Hi,
It looks like the syslog date format has changed for some reason (see below)
and the change is definitely less readable for me. The change maybe related to
the rsyslog upgrade that happened around November 4, 2022:
[UPGRADE] rsyslog:amd64 8.2210.0-1 -> 8.2210.0-3
Any ideas as to get th
On 2022-09-24, David Wright wrote:
>
> It's odd: virtually all the software I use (eg emacs, gnumeric,
> inkscape, even mutt) modifies either the title bar or a status bar
> as soon as I make any modification of a document (typically an
> asterisk), and removes it if I revert the change, or save i
On Sat 24 Sep 2022 at 06:43:03 (-0400), Eike Lantzsch KY4PZ wrote:
> On Samstag, 24. September 2022 00:11:01 -04 piorunz wrote:
> > On 24/09/2022 01:38, Eike Lantzsch KY4PZ wrote:
> > > did you realize that, if the backup copy fails for any reason, also
> > > the document cannot be saved and thus *
On Samstag, 24. September 2022 11:27:24 -04 Charles Curley wrote:
> On Sat, 24 Sep 2022 15:50:04 +0100
>
> piorunz wrote:
> > On 24/09/2022 11:43, Eike Lantzsch KY4PZ wrote:
> > > The problem is: if you enabled it and for some reason the backup
> > > copy cannot be written, LibreOffice also does n
On 24/09/2022 16:27, Charles Curley wrote:
That's very interesting. Where does backup copy is being written? To
the same folder where original supposed to be? Like Kate text editor
writes backups as "filename.txt~" in the same folder?
~/.config/libreoffice/4/user/backup/
Incidentally, it won'
On Sat, 24 Sep 2022 15:50:04 +0100
piorunz wrote:
> On 24/09/2022 11:43, Eike Lantzsch KY4PZ wrote:
>
> > The problem is: if you enabled it and for some reason the backup
> > copy cannot be written, LibreOffice also does not write the
> > original. The warning LibreOffice emits is: "Cannot write
On Samstag, 24. September 2022 10:50:04 -04 piorunz wrote:
> On 24/09/2022 11:43, Eike Lantzsch KY4PZ wrote:
> > The problem is: if you enabled it and for some reason the backup
> > copy
> > cannot be written, LibreOffice also does not write the original.
> > The warning LibreOffice emits is: "Cann
On 24/09/2022 11:43, Eike Lantzsch KY4PZ wrote:
The problem is: if you enabled it and for some reason the backup copy
cannot be written, LibreOffice also does not write the original.
The warning LibreOffice emits is: "Cannot write backup copy" but it does
not tell you that it will not even write
On Samstag, 24. September 2022 00:11:01 -04 piorunz wrote:
> On 24/09/2022 01:38, Eike Lantzsch KY4PZ wrote:
> > did you realize that, if the backup copy fails for any reason, also
> > the document cannot be saved and thus *all* work is lost? I
> > experienced this behaviour recently to my dismay (
On 24/09/2022 01:38, Eike Lantzsch KY4PZ wrote:
did you realize that, if the backup copy fails for any reason, also the
document cannot be saved and thus *all* work is lost? I experienced this
behaviour recently to my dismay (not to say anger).
I never used Backup copy feature, I just enabled
On Freitag, 23. September 2022 09:28:12 -04 piorunz wrote:
> On 13/09/2022 20:47, Juan R.D. Silva wrote:
> > I was pissed off to find out that autosave is desabled by default. I
> > used not to care. Looks like now I want to enable it. 😄
>
> Same! I just realized that AutoRecovery is disabled by d
On 13/09/2022 20:47, Juan R.D. Silva wrote:
I was pissed off to find out that autosave is desabled by default. I
used not to care. Looks like now I want to enable it. 😄
Same! I just realized that AutoRecovery is disabled by default, and
backup copy feature is also disabled by default. Now I ena
On Wed, 14 Sep 2022 09:37:14 +0200 (CEST)
local10 wrote:
> I actually have it disabled on purpose. The reason is I don't always
> want changes to be autosaved because sometimes the changes make the
> document worse. I wonder if there's some change tracking option in LO
> t
On 2022-09-13, DdB wrote:
> Am 13.09.2022 um 21:47 schrieb Juan R.D. Silva:
>> Oh, I did recreated it. And I even think is very close to original. :-)
>
> This is good news! Thanks for sharing it. :-)
> DdB
>
I thought he was going to say the rewrite was an *improvement*.
I think it was Hemingwa
Sep 13, 2022, 19:47 by juan.r.d.si...@gmail.com:
> I was pissed off to find out that autosave is desabled by default. I used not
> to care. Looks like now I want to enable it. :-)
>
I actually have it disabled on purpose. The reason is I don't always want
changes to be aut
On Tue, Sep 13, 2022 at 03:47:34PM -0400, Juan R.D. Silva wrote:
[...]
> Thanks for you time. Oh, I did recreated it. And I even think is very close
> to original. :-)
I'll bet it's better :-)
Cheers
--
t
signature.asc
Description: PGP signature
Am 13.09.2022 um 21:47 schrieb Juan R.D. Silva:
> Oh, I did recreated it. And I even think is very close to original. :-)
This is good news! Thanks for sharing it. :-)
DdB
(short answer) No. Its more like "shit happens!"
It does indeed :-(
Even with best of knowledge and abilities, what once was in memory (RAM)
will be reused pretty quick, and if you chose to not autosave regularly,
there won't be much left, and even if there would be, the work to get it
into pr
Juan R.D. Silva wrote:
> I edited a file for hours and then mistakenly clicked "Do not save"
> while closing file. Auto save is not enabled. No backup exist in
> LibreOffice Backup folder. The computer is not restarted yet. Temp
> folder have only old version. Any way to recover the lost edited
On 12/09/2022 23:58, Juan R.D. Silva wrote:
I edited a file for hours and then mistakenly clicked "Do not save"
while closing file. Auto save is not enabled. No backup exist in
LibreOffice Backup folder. The computer is not restarted yet. Temp
folder have only old version. Any way to recover th
Oh dear!
Been there, done that...
(short answer) No. Its more like "shit happens!"
Even with best of knowledge and abilities, what once was in memory (RAM)
will be reused pretty quick, and if you chose to not autosave regularly,
there won't be much left, and even if there would be, the work to ge
I edited a file for hours and then mistakenly clicked "Do not save"
while closing file. Auto save is not enabled. No backup exist in
LibreOffice Backup folder. The computer is not restarted yet. Temp
folder have only old version. Any way to recover the lost edited
version? Or the only option to
> On Sep 3, 2022, at 7:30 PM, Kevin Price wrote:
>
> Am 03.09.22 um 06:32 schrieb Casey Deccio:
>>> On Sep 2, 2022, at 8:14 PM, Kevin Price wrote
>
>>> We got him. :) Casey, you file the bug report, Okay?
>
>> Done! https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018999
>> Thanks for all
Am 03.09.22 um 06:32 schrieb Casey Deccio:
>> On Sep 2, 2022, at 8:14 PM, Kevin Price wrote
>> We got him. :) Casey, you file the bug report, Okay?
> Done! https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018999
> Thanks for all the help!
You are very welcome.
Thanks a lot for this conversa
> 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 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
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 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
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 Sep 1, 2022, at 10:33 PM, Casey Deccio wrote:
>
> I've come across some unexpected changes in interface behavior between
> linux-image-5.10.0-13-amd64 and linux-image-5.10.0-17-amd64.
>
Relatedly, there is this behavior change:
linux-image-5.10.0-13-amd64:
$ su
I've come across some unexpected changes in interface behavior between
linux-image-5.10.0-13-amd64 and linux-image-5.10.0-17-amd64.
Consider the following script:
$ cat test.sh
#!/bin/sh
sudo ip link add test1 type veth peer test2
sudo ip link set test1 down
sudo ip link set test2 down
1 - 100 of 1034 matches
Mail list logo
