I upgraded on 25th May office computer Debian Stretch to Buster. Home
directory comes from NFS server. Chromium browser now longer has the stored
passwords available.
Other browsers, Firefox and Google Chrome, do have the passwords still.
Where did chromium browser on Stretch store the passwords
On Fri Sep 4 12:07:23 2020 Greg Wooledge wrote:
> On Fri, Sep 04, 2020 at 11:09:45AM -0700, cgi...@surfnaked.ca
wrote:
>
>> OpenSSL version mismatch. Built against 1010104f, you have
1010006f
>
>> # find . -print | grep -i ssh [output abridged]
>> /etc/X11/Xsession.d/90x11-como
On Fri, Sep 04, 2020 at 11:09:45AM -0700, cgi...@surfnaked.ca wrote:
> OpenSSL version mismatch. Built against 1010104f, you have 1010006f
> # find . -print | grep -i ssh [output abridged]
> /etc/X11/Xsession.d/90x11-comon_ssh-agent
> /etc/xdg/autostart/gnome-keyring-ssh.desktop
> /usr/l
On Fri Sep 4 08:56:44 2020 Mike Kupfer
wrote:
> cgi...@surfnaked.ca wrote:
>
>> I'll continue puttering for a few more days - maybe others will
have
>> some ideas.
>
> So were there any errors or warnings in /var/log/Xorg.0.log?
Nothing there.
> I'd also check for error messages in $HOM
cgi...@surfnaked.ca wrote:
> I'll continue puttering for a few more days - maybe others will have
> some ideas.
So were there any errors or warnings in /var/log/Xorg.0.log?
I'd also check for error messages in $HOME/.xsession-errors.
regards,
mike
On Mi, 02 sep 20, 11:13:30, cgi...@surfnaked.ca wrote:
>
> I found instructions on the web for upgrading Stretch to Buster,
Do you mean these?
https://www.debian.org/releases/buster/releasenotes
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Descriptio
On Wed Sep 2 21:32:55 2020 Andy Smith wrote:
> On Wed, Sep 02, 2020 at 11:13:30AM -0700, cgi...@surfnaked.ca
wrote:
>
>> The Buster upgrade seemed to work OK. I re-booted and got to my
>> xfce login screen. But when I entered my user ID and password,
>> the screen blanked for a second or
Hello,
On Wed, Sep 02, 2020 at 11:13:30AM -0700, cgi...@surfnaked.ca wrote:
> The Buster upgrade seemed to work OK. I re-booted and got to my
> xfce login screen. But when I entered my user ID and password,
> the screen blanked for a second or so, then came back to a blank
> login screen.
Use c
The scariest part of any system upgrade is that first re-boot.
Up until then, you're still running - but after that re-boot,
maybe the machine will come up, and maybe it won't.
Mine won't, and now I have to figure out how to fix it.
I found instructions on the web for upgra
This is an Acer netbook, a year or two old, no legacy BIOS, bought with
Win10 installed. It has a hardwired SSD designated mmcblk0 and I
installed another SSD which is /dev/sda. Stretch installed with no
problem, and gives me a Windows entry in its menu. It's been OK for
about 18 months, so I tho
i have a device that runs stretch armel
if i change my repos to buster
i do apt clean all, apt update, apt install systemd
when systemd installs it fails to start and i get a series of timeouts
when i reboot i get
Begin: Running /scripts/init-bottom ... Begin: Stopping dropbear ... done.
[ 41.3
Isaac N composed on 2020-04-05 22:29 (UTC+0300):
> After upgrading to debian buster i cannot access gui. I boot up and it
> stops services like UiD1000 then stops at "started update utmp about system
> runlevel changes".
> I can log on using tty to terminal; startX terminates with
> "xinit:connect
After upgrading to debian buster i cannot access gui. I boot up and it
stops services like UiD1000 then stops at "started update utmp about system
runlevel changes".
I can log on using tty to terminal; startX terminates with
"xinit:connection to X server lost"
Starting a GUI application like firefo
On Wed 15 Jan 2020 at 08:08:30 -0800, Alan Savage wrote:
> I am trying to upgrade from stretch to buster using the nonfree
> installation DVD ISO "firmware-10.2.0-amd64-DVD-1.iso" that I downloaded
> using the torrent here:
> https://cdimage.debian.org/cdimage/unofficial
I am trying to upgrade from stretch to buster using the nonfree
installation DVD ISO "firmware-10.2.0-amd64-DVD-1.iso" that I downloaded
using the torrent here:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.2.0+nonfree/amd64/bt-dvd/
I copied the ISO to
On Ma, 24 sep 19, 22:28:59, Mark Fletcher wrote:
>
> In the end I think my problems were caused by previously having the
> deb-multimedia repositories in use and trying to move away from them
> at the same time as upgrading.
Most likely, which is why the Release Notes specifically advise to
re
Well, I really appreciate the deb-multimedia, but as I ran into similar
troubles times ago, I usually remove all non-official packages before
upgrade and reinstall them afterwards.
Greetings
Bernd
On Wed, 25 Sep 2019 20:09:40 +0200
Mattia wrote:
> So if anyone has a stretch server with owncloud-files installed and
> are planning to upgrade to buster: just don't! Wait for owncloud 10.3
> to come out.
Or consider moving to NextCloud. I have an instance running quite well
on Debian 10 (buste
Il 24/09/19 23:28, Mark Fletcher ha scritto:
I perform 5-days-a-week backups using Amanda. The machine in question
here happens to be the Amanda server as well as a client. The amanda
virtual tapes and holding disk are in a USB3 disk cage. The cage also
contains a RAID1 disk pair which contains
Hi list
This long email is just a report on my recent stretch to buster upgrade
experience. I had a bit of an adventure, didn't handle some steps well,
and thought the experience would be useful to put out there for others
to learn from / avoid some mistakes I made.
THERE IS NO QUE
Escaped from gnome. While working in gnome the visibility of my mouse
pointer became very erratic, often visible only at the margins of a
window. I would then have to move the mouse and guess where it pointed
in the window. The computer was all but unusable so I rebooted. Having
been schooled i
No sound after upgrade to Buster
Switched from lxde to gnome to use gnome/sound speaker test - Still no sound
Rebooted to old stretch on another hard drive - had sound, output
changed to line out.
Rebooted to Buster. No sound and trapped in gnome. selection of desktops
shows at sign in but c
On Wed 18 Sep 2019 at 12:06:00 (-), Curt wrote:
> On 2019-09-17, Sven Joachim wrote:
> > On 2019-09-17 11:10 -0500, David Wright wrote:
> >>
> >> Well, the only link *needed* is init, hence its dependency on package
> >> init, whose sole function is to keep the number of init configurations
>
On 2019-09-17, Sven Joachim wrote:
> On 2019-09-17 11:10 -0500, David Wright wrote:
>
>>
>> Well, the only link *needed* is init, hence its dependency on package
>> init, whose sole function is to keep the number of init configurations
>> more than zero and less than two.
>>
>> The rest of those l
On Tue, Sep 17, 2019 at 05:06:52PM -0400, Greg Wooledge wrote:
[...]
> I can't believe people are still adding cruft to sysv-rc helpers in 2019.
Luckily, "real world" is much more colourful and diverse than your
(or my -- or anyone's!) beliefs ;-)
Cheers
-- tomás
signature.asc
Description: Di
On Tue, Sep 17, 2019 at 10:59:53PM +0200, Sven Joachim wrote:
> On 2019-09-17 09:13 -0400, Greg Wooledge wrote:
> > wooledg:~$ aptitude why systemd-sysv
> > i udev Depends dpkg (>= 1.19.3) | systemd-sysv
> >
> > OK... I'll admit, I do not quite understand that dependency.
>
> The udev init scrip
On 2019-09-17 09:13 -0400, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
>> What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite understand that dep
On 2019-09-17 11:10 -0500, David Wright wrote:
>
> Well, the only link *needed* is init, hence its dependency on package
> init, whose sole function is to keep the number of init configurations
> more than zero and less than two.
>
> The rest of those links just mean that I can read, say, a 60 lin
On Tue 17 Sep 2019 at 13:29:16 -0400, Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 06:25:05PM +0100, Brian wrote:
> > Upgrades from wheezy to jessie did not change the init system because
> > libpame-systemd had the dependency
> >
> > systemd-shim (>= 8-2) | systemd-sysv
>
> https://www.debi
On Tue, Sep 17, 2019 at 06:25:05PM +0100, Brian wrote:
> Upgrades from wheezy to jessie did not change the init system because
> libpame-systemd had the dependency
>
> systemd-shim (>= 8-2) | systemd-sysv
https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html#issues-sys
On Tue 17 Sep 2019 at 09:13:30 -0400, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
> > What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite under
On Tue 17 Sep 2019 at 10:37:15 +0100, Brian wrote:
> On Sun 15 Sep 2019 at 23:31:23 +0100, Roger Lynn wrote:
>
> > I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> > running KDE and a headless server. Is there any information available
> > anywhere to tell me what will ha
On Tue 17 Sep 2019 at 09:45:21 (-0400), Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
> > I believe its name was chosen with
> > insufficient consideration, and is not in fact derived from its
> > function.
>
> You're not looking closely enough.
>
> > $ apt-
On 2019-09-17, The Wanderer wrote:
>>> Yes, but unless I'm greatly misunderstanding matters, /sbin/init is
>>> not specific to sysvinit.
>> That's okay, as I never came close to claiming it was. But you focus
>> uniquely upon this "point," while ignoring the part about the "links
>> needed for s
On 2019-09-17 at 09:45, Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
>
>> I believe its name was chosen with
>> insufficient consideration, and is not in fact derived from its
>> function.
>
> You're not looking closely enough.
>
>> $ apt-file show systemd
On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
> I believe its name was chosen with
> insufficient consideration, and is not in fact derived from its
> function.
You're not looking closely enough.
> $ apt-file show systemd-sysv
> systemd-sysv: /sbin/halt
> systemd-sysv: /sbin/init
On 2019-09-17 at 09:28, Curt wrote:
> On 2019-09-17, The Wanderer wrote:
>
>>> Why he would say "despite its name" eludes this correspondent,
>>> because the package has *everything* to do with sysvinit,
>>> providing as it does the "links needed for systemd to replace
>>> sysvinit. Installing
On 2019-09-17, The Wanderer wrote:
>> Why he would say "despite its name" eludes this correspondent,
>> because the package has *everything* to do with sysvinit, providing
>> as it does the "links needed for systemd to replace sysvinit.
>> Installing systemd-sysv will overwrite /sbin/init with a
On 2019-09-17 at 09:13, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
>
>> What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite understand that de
On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
> What causes systemd-sysv to be installed?
wooledg:~$ aptitude why systemd-sysv
i udev Depends dpkg (>= 1.19.3) | systemd-sysv
OK... I'll admit, I do not quite understand that dependency. But
what I really need to do is check this on a je
On 2019-09-17 at 04:09, Curt wrote:
> On 2019-09-16, Brian wrote:
[that on some earlier date which has been clipped out, someone else -
who happens to be The Wanderer - wrote:]
>>> The dist-upgrade will have resulted in installing the
>>> systemd-sysv package, which (despite its name) has nothi
On Sun 15 Sep 2019 at 23:31:23 +0100, Roger Lynn wrote:
> I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> running KDE and a headless server. Is there any information available
> anywhere to tell me what will happen when I attempt to upgrade them to
> Buster? The release n
On 2019-09-16, Brian wrote:
>>
>> The dist-upgrade will have resulted in installing the systemd-sysv
>> package, which (despite its name) has nothing to do with sysvinit; it is
>> the package which sets systemd as the primary / active / default init
>> system.
>>
>> Installing sysvinit-core will
On Mon, Sep 16, 2019 at 3:17 PM The Wanderer wrote:
> >> If you want to keep sysvinit, here's the order of events:
> >>
> >> change sources from stretch to buster
> >
> > Fine.
> >
> >> apt update
> >
> > Splendid.
>
l happen when I
> > >>> attempt to upgrade them to Buster? The release notes don't
> > >>> mention it and other sources I can find just talk about switching
> > >>> from systemd to sysvinit, which doesn't look easy with a desktop
On 2019-09-16 at 18:11, Brian wrote:
> On Mon 16 Sep 2019 at 15:16:34 -0400, The Wanderer wrote:
>
>> On 2019-09-16 at 15:07, Brian wrote:
>>
>>> On Sun 15 Sep 2019 at 21:52:50 -0400, Dan Ritter wrote:
apt install sysvinit-core
>>>
>>> What happens if this is not done?
>>
>> Next time yo
>>> mention it and other sources I can find just talk about switching
> >>> from systemd to sysvinit, which doesn't look easy with a desktop
> >>> environment.
> >>
> >> If you want to keep sysvinit, here's the order of events:
>
h doesn't look easy with a desktop
>>> environment.
>>
>> If you want to keep sysvinit, here's the order of events:
>>
>> change sources from stretch to buster
>
> Fine.
>
>> apt update
>
> Splendid.
>
>> apt dist-up
keep sysvinit, here's the order of events:
>
> change sources from stretch to buster
Fine.
> apt update
Splendid.
> apt dist-upgrade
Great.
> apt install sysvinit-core
What happens if this is not done?
--
Brian.
Quoting Dan Ritter (2019-09-16 03:52:50)
> Roger Lynn wrote:
> > The KDE systems have systemd-shim installed, which is not present in
> > Buster. Is this going to cause problems? Will the server be okay?
> > Should I just stay with Stretch until Bullseye is released or
> > consider moving to De
n't mention it and other sources I can find just
> talk about switching from systemd to sysvinit, which doesn't look easy with
> a desktop environment.
If you want to keep sysvinit, here's the order of events:
change sources from stretch to buster
apt update
apt dist-upgrade
a
Hi,
I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
running KDE and a headless server. Is there any information available
anywhere to tell me what will happen when I attempt to upgrade them to
Buster? The release notes don't mention it and other sources I can find just
Thanks to everybody, for all the hints.
I think the way to search in, is to create an edid file and load it at boot.
I searched in this direction before, I just abandoned that way because it did
not work.
Now the question I have is: How to create that edid file.
The tool I found creates a file i
On Thu 12 Sep 2019 at 06:23:04 (+), Jan Michael Greiner wrote:
> On Monday, September 9, 2019, 1:55:06 PM GMT+2, Charles Curley wrote:
> >> On Mon, 9 Sep 2019 10:20:37+ (UTC) Jan Michael Greiner wrote:
> >> With Debian Stretch (9.8) I had the display running with 3840x2160
> >> resolution a
Jan Michael Greiner wrote:
> Dear all,
>
> My laptop: Lenovo E520
> Graphics: Intel HD Graphics 3000 (kernel module i915)
>
> External display AOC U2879VF, 28 inch, connected by HDMI cable
>
> With Debian Stretch (9.8) I had the display running with 3840x2160 resolution
> at 24Hz reduced blank
Hi
I have a kind of same problem.
A monitor able of displaying at 1920x1080.
Intel HD Graphics 620 with driver i915/modesetting.
With old Stable (kernel 4.9.0-9) it was working fine.
With new Stable (kernel 4.19.0-6) it set max display 1024x768.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?
Dear Charles,
On Monday, September 9, 2019, 1:55:06 PM GMT+2, Charles Curley wrote:
>> On Mon, 9 Sep 2019 10:20:37+ (UTC) Jan Michael Greiner wrote:
>> With Debian Stretch (9.8) I had the display running with 3840x2160
>> resolution at 24Hz reduced blank.
>> [What worked with Debian Stretch
Thomas George wrote:
> Checked archives, installed pavucontrol but this did not help. Any
> suggestions?
check alsamixer -c0 and look for muted channels
You could run the script alsa-info (from alsa-utils) and choose to
upload/share, and send the link to this list.
Hope this helps.
On Mon, 9 Sep 2019 14:11:25 -0400
Thomas George wrote:
> Checked archives, installed pavucontrol but this did not help. Any
> suggestions?
>
Checked archives, installed pavucontrol but this did not help. Any
suggestions?
On Mon, 9 Sep 2019 10:20:37 + (UTC)
Jan Michael Greiner wrote:
> With Debian Stretch (9.8) I had the display running with 3840x2160
> resolution at 24Hz reduced blank.
And I take it you want to reproduce that on Debian 10 (buster). I
suggest you:
* Install arandr.
* Use arandr to set thing
Apparently internal snapshots of a qcow2-based vm are problematic when
the vm boots from UEFI. I found that out when my nightly snapshots
stopped working after I upgraded a server from stretch to buster.
Testing the effective line of the script with actual values, I got this
result
Hello,
I have just successfully upgraded 12 physical machines to the new Debian
release (Debian Buster) and can tell that the upgrade runs very smoothly.
Very nice job by all contributors, thank you very much!
I have noticed, that files previously existing under /usr/share/vim/vimfiles
have been
James Allsopp writes:
Hi,
I was going to upgrade to Buster, but I've got docker installed and am
running a container as an ldap server. Consequently I don't want to get rid
of it, but the install guide I read suggested removing all 3rd-party
repositories before starting.
This is the cur
I upgraded just fine with 3rd party repositories enabled. What you might
want to do is ensure the repositories match the Debian version you're
upgrading to.
Typically repositories that do different builds for different Debian
versions put the version in the repository URL. So check whether any suc
Hi,
I was going to upgrade to Buster, but I've got docker installed and am
running a container as an ldap server. Consequently I don't want to get rid
of it, but the install guide I read suggested removing all 3rd-party
repositories before starting.
This is the current situatioin with my sources
In-Reply-To: <7f9ebbad-9966-ab81-ca75-8b6fb5154...@disroot.org>
>What is the best way to edit the above anything from the 0ad reference
>and below, or should I comment these out and once buster is out add in
>the correct lines from the various source websites (e.g for 0ad the
>website will have t
Hi
When updating from Stretch to Buster I know that I need to change
references in the sources.list file
Mine is below
# deb cdrom:[Debian GNU/Linux 9.5.0 _Stretch_ - Official amd64 DVD
Binary-1 20180714-10:25]/ stretch contrib main non-free
# deb cdrom:[Debian GNU/Linux 9.5.0 _Stretch_
Keith Bainbridge
keithr...@gmail.com
+61 (0)447 667 468
On 10/2/19 10:43 am, Richard Hector wrote:
On 10/02/19 12:01 PM, deloptes wrote:
Normally, I wouldn't bother since I usually only upgrade every other
release after LTS ceases on my primary install. But this time, Buster
includes supp
Hi Paul,
> Updated from Stretch to Buster (non-free) the other day all went fine, just
> undertaken
>
> apt update && apt upgrade
>
> today and all seem to go fine, The process seems to be pretty painless for
> the most part.
I do hope you did
apt dist-upgrade
too. ;-)
Bonno Bloksma
On Sun, 10 Feb 2019 00:01:47 +0100
deloptes wrote:
> Patrick Bartek wrote:
>
> > As for me, I'm the patient, very practical type. Debian is my distro
> > of choice after almost 20 years of using other Linuxes because of its
> > philosophy of stability and bug-freeness above all else. I'll wait
The freeze for buster will happen according to the following timeline:
* 2019-01-12 - Transition freeze
* 2019-02-12 - Soft-freeze
* 2019-03-12 - Full-freeze
via https://release.debian.org/buster/freeze_policy.html
On 2/9/19 3:01 PM, deloptes wrote:
Patrick Bartek wrote:
As for me, I'm
On 10/02/19 12:01 PM, deloptes wrote:
>> Normally, I wouldn't bother since I usually only upgrade every other
>> release after LTS ceases on my primary install. But this time, Buster
>> includes support for AMD's Ryzen APU series which a notebook I'm
>> considering purchasing around summertime use
Patrick Bartek wrote:
> As for me, I'm the patient, very practical type. Debian is my distro
> of choice after almost 20 years of using other Linuxes because of its
> philosophy of stability and bug-freeness above all else. I'll wait
> until Buster is in Release Candidate status before testing it
AM, Patrick Bartek wrote:
>>>> On Fri, 8 Feb 2019 15:06:34 +
>>>> Paul Sutton wrote:
>>>>
>>>>> Updated from Stretch to Buster (non-free) the other day all went fine,
>>>>> just undertaken
>>>> Why? Buster i
On Sat, 9 Feb 2019 07:48:00 +
Paul Sutton wrote:
> On 09/02/2019 02:22, Peter Ehlert wrote:
> >
> > On 2/8/19 11:09 AM, Patrick Bartek wrote:
> >> On Fri, 8 Feb 2019 15:06:34 +
> >> Paul Sutton wrote:
> >>
> >>> Updated from St
On 09/02/2019 02:22, Peter Ehlert wrote:
>
> On 2/8/19 11:09 AM, Patrick Bartek wrote:
>> On Fri, 8 Feb 2019 15:06:34 +
>> Paul Sutton wrote:
>>
>>> Updated from Stretch to Buster (non-free) the other day all went fine,
>>> just undertaken
>>
On 2/8/19 11:09 AM, Patrick Bartek wrote:
On Fri, 8 Feb 2019 15:06:34 +
Paul Sutton wrote:
Updated from Stretch to Buster (non-free) the other day all went fine,
just undertaken
Why? Buster is still alpha. A lot can still go wrong. Hope it's not
your primary use distro.
Wh
On Fri, 8 Feb 2019 15:06:34 +
Paul Sutton wrote:
> Updated from Stretch to Buster (non-free) the other day all went fine,
> just undertaken
Why? Buster is still alpha. A lot can still go wrong. Hope it's not
your primary use distro.
> apt update && apt upgra
to Buster (non-free) the other day all went fine,
just undertaken
apt update && apt upgrade
today and all seem to go fine, The process seems to be pretty painless
for the most part.
Paul
On 2/8/19 8:06 AM, Paul Sutton wrote:
> Hi
>
> Updated from Stretch to Buster (non-free) the other day all went fine,
> just undertaken
>
> apt update && apt upgrade
>
> today and all seem to go fine, The process seems to be pretty painless
> for the most
Hi
Updated from Stretch to Buster (non-free) the other day all went fine,
just undertaken
apt update && apt upgrade
today and all seem to go fine, The process seems to be pretty painless
for the most part.
Paul
--
Paul Sutton
http://www.zleap.net
https://www.linkedin.com/in/zlea
82 matches
Mail list logo
