On 9/11/2019 7:01 PM, Miroslav Skoric wrote:
> Well, I noticed that issue after I recently upgraded to Stretch, but not
> had it in Jessie. Whatever. Having in mind that Stretch is oldstable for
> a while, and you had the issue in Buster, it seems that the issue goes
> through the versions intact :
On 9/11/19 12:12 AM, Ben Caradoc-Davies wrote:
I saw the same problem when I tried lightlocker after upgrading to XFCE
4.14, so I went back to good old xscreensaver. Ugly bitmaps fonts and no
theming, but secure and reliable. There is a new locker in XFCE, but
there have been reports of segf
On 9/10/19 8:11 PM, Christopher David Howie wrote:
On 9/10/19 4:30 AM, Miroslav Skoric wrote:
After upgrading the old laptop from Jessie to Stretch, I noticed that
the screensaver in Mate environment does not work for me as before. For
example, when the screen goes black after some time of inac
On 11/09/2019 06:11, Christopher David Howie wrote:
On 9/10/19 4:30 AM, Miroslav Skoric wrote:
After upgrading the old laptop from Jessie to Stretch, I noticed that
the screensaver in Mate environment does not work for me as before. For
example, when the screen goes black after some time of inac
On 9/10/19 4:30 AM, Miroslav Skoric wrote:
> After upgrading the old laptop from Jessie to Stretch, I noticed that
> the screensaver in Mate environment does not work for me as before. For
> example, when the screen goes black after some time of inactivity, for
> returning back it is not enough jus
Hello,
After upgrading the old laptop from Jessie to Stretch, I noticed that
the screensaver in Mate environment does not work for me as before. For
example, when the screen goes black after some time of inactivity, for
returning back it is not enough just to touch the touchpad or press any
k
On 9/3/19 7:55 AM, Reco wrote:
However, I wonder whether the other partitions (/, /usr, /var) shall
remain ext3 in fstab, or they shall be changed to ext4 too.
blkid has an answer for that. If it says that your /, /usr and /var are
ext3 - leave them as that.
Reco
Exactly, blkid said ju
Le 03/09/2019 à 01:47, Miroslav Skoric a écrit :
On 9/2/19 1:19 AM, Pascal Hambourg wrote:
You should have upgraded the kernel as
soon as you upgraded from Wheezy to Jessie. Same when upgrading from
Jessie to Stretch.
Probably you are right. But it makes me wonder why the previous upgrade
Hi.
On Tue, Sep 03, 2019 at 01:38:49AM +0200, Miroslav Skoric wrote:
> Now I suppose that the above commands (plan A) are not needed.
Yep, there's no need for them now.
> However, I wonder whether the other partitions (/, /usr, /var) shall
> remain ext3 in fstab, or they shall be change
On 9/2/19 1:19 AM, Pascal Hambourg wrote:
Sure. I upgraded Jessie to Stretch last week. And it worked well for
me until Friday eve. (And before that I upgraded Wheezy to Jessie cca
year ago. It worked well for me too.)
Until is doesn't work any more. You cannot run a new system with an old
On 9/2/19 5:39 PM, Reco wrote:
Hi.
On Mon, Sep 02, 2019 at 04:44:18PM +0200, Miroslav Skoric wrote:
On 9/2/19 10:28 AM, Reco wrote:
Judging from the pictures, it's the ext4 filesystem.
So, let's proceed to the destructive steps:
fsck.ext4 -f /dev/localhost/tmp
mount -t ext4 /dev/loc
Le 02/09/2019 à 16:44, Miroslav Skoric a écrit :
On 9/2/19 10:28 AM, Reco wrote:
fsck.ext4 -f /dev/localhost/tmp
mount -t ext4 /dev/localhost/tmp /tmp
umount /tmp
fsck.ext4 -f /dev/localhost/tmp
If the mounting succeeds, change filesystem type to ext4 for /tmp in
/etc/fstab, and do the same fo
Hi.
On Mon, Sep 02, 2019 at 04:44:18PM +0200, Miroslav Skoric wrote:
> On 9/2/19 10:28 AM, Reco wrote:
>
> >
> > Judging from the pictures, it's the ext4 filesystem.
> > So, let's proceed to the destructive steps:
> >
> > fsck.ext4 -f /dev/localhost/tmp
> > mount -t ext4 /dev/localhost/
On Mon 02 Sep 2019 at 09:09:13 (+0200), Pascal Hambourg wrote:
> Le 02/09/2019 à 00:51, Miroslav Skoric a écrit :
> >
> > Sure. I sent few photos on the commands' output. Don't know if the
> > list accepts attachments.
>
> I don't think it accepts binary files.
These small PNGs posted ok:
https
Le 02/09/2019 à 09:56, Miroslav Skoric a écrit :
lsblk didn't bring any difference regardless the stick is inserted or
not. So I send photos :-)
There was a wrong free block count on /dev/localhost/tmp, but it seems
to be corrected now. Anyway this kind of minor error should not prevent
mou
Hi.
On Mon, Sep 02, 2019 at 09:56:16AM +0200, Miroslav Skoric wrote:
> On 9/1/19 9:25 PM, Reco wrote:
>
> >
> > lsblk to get the device name of your USB stick.
> > mount /dev/ /mnt
> >
> > Don't forget to "umount /mnt" afterwards.
> >
> > > Or to wait that I copy/paste the output by ha
Le 02/09/2019 à 00:51, Miroslav Skoric a écrit :
Sure. I sent few photos on the commands' output. Don't know if the list
accepts attachments.
I don't think it accepts binary files.
Le 02/09/2019 à 00:44, Miroslav Skoric a écrit :
On 9/2/19 12:26 AM, Pascal Hambourg wrote:
Le 01/09/2019 à 22:59, Miroslav Skoric a écrit :
root@(none):/# uname -a
Linux (none) 3.2.0-4-486 #1 Debian 3.2.96-2 i686 GNU/Linux
So you upgraded from Jessie to Stretch but still ran the old kernel
On 9/1/19 7:52 PM, Étienne Mollier wrote:
The output of the above command (version dumpe2fs 1.43.4
31-Jan-2017) is the same as yours, with *one addition*:
inline_data
Good news, this is consistent with Reco's observation in the
other thread. Follows his recommendations and see what happens.
On 9/2/19 12:26 AM, Pascal Hambourg wrote:
Le 01/09/2019 à 22:59, Miroslav Skoric a écrit :
root@(none):/# uname -a
Linux (none) 3.2.0-4-486 #1 Debian 3.2.96-2 i686 GNU/Linux
So you upgraded from Jessie to Stretch but still ran the old kernel from
Wheezy all this time ? Wow.
Sure. I upg
Le 01/09/2019 à 22:59, Miroslav Skoric a écrit :
root@(none):/# uname -a
Linux (none) 3.2.0-4-486 #1 Debian 3.2.96-2 i686 GNU/Linux
So you upgraded from Jessie to Stretch but still ran the old kernel from
Wheezy all this time ? Wow.
If the dist upgrade was not complete (and if the system no
On 9/1/19 8:40 PM, Pascal Hambourg wrote:
Le 01/09/2019 à 17:01, Miroslav Skoric a écrit :
EXT3-fs (dm-6): error: couldn't mount because of unsupported optional
features (8000)
This is not the same as the previous error message you showed while
using the Debian Jessie 8.11 installer in res
On Sun, Sep 01, 2019 at 09:19:43PM +0200, Miroslav Skoric wrote:
> On 9/1/19 5:33 PM, Reco wrote:
>
> >
> > So, let's do something easy and non-destructive first (I assume that
> > /tmp does not contain anything useful):
> >
> > tune2fs -l /dev/localhost/tmp
> >
> > fsck.ext3 -f -n /dev/localho
On 9/1/19 5:33 PM, Reco wrote:
So, let's do something easy and non-destructive first (I assume that
/tmp does not contain anything useful):
tune2fs -l /dev/localhost/tmp
fsck.ext3 -f -n /dev/localhost/tmp
fsck.ext4 -f -n /dev/localhost/tmp
fsck.ext3 -b 8193 -f -n /dev/localhost/tmp
fsck.ex
Le 01/09/2019 à 17:01, Miroslav Skoric a écrit :
EXT3-fs (dm-6): error: couldn't mount because of
unsupported optional features (8000)
This is not the same as the previous error message you showed while
using the Debian Jessie 8.11 installer in rescue mode :
EXT4-fs (dm-6): couldn't mount
Misko, on 2019-09-01:
> On 9/1/19 1:20 PM, Étienne Mollier wrote:
> >
> > Hi Miroslav,
> >
> > Pascal is probably right. If you manage to have access to the
> > command "dumpe2fs" in your rescue environment, what is the
> > output of:
> >
> > # dumpe2fs /dev/mapper/localhost-home | grep '^File
On 9/1/19 1:20 PM, Étienne Mollier wrote:
Hi Miroslav,
Pascal is probably right. If you manage to have access to the
command "dumpe2fs" in your rescue environment, what is the
output of:
# dumpe2fs /dev/mapper/localhost-home | grep '^Filesystem features:'
Actual Ext3 should probably
Hi.
On Sun, Sep 01, 2019 at 05:01:39PM +0200, Miroslav Skoric wrote:
> On 8/31/19 3:48 PM, Reco wrote:
>
> > On Sat, Aug 31, 2019 at 03:41:12PM +0200, Miroslav Skoric wrote:
> > > On 8/31/19 3:26 PM, Reco wrote:
> > >
> > > >
> > > > Boot with init=/bin/bash kernel commandline parameter
On 8/31/19 3:48 PM, Reco wrote:
On Sat, Aug 31, 2019 at 03:41:12PM +0200, Miroslav Skoric wrote:
On 8/31/19 3:26 PM, Reco wrote:
Boot with init=/bin/bash kernel commandline parameter, remount root
filesystem read-write, fix your /etc/fstab (systemd is picky about
filesystems it's not able to
On 01/09/2019 01.20, Pascal Hambourg wrote:
> Le 01/09/2019 à 01:04, Miroslav Skoric a écrit :
>>
>> # dmesg | tail reported (among the other):
>>
>> EXT4-fs (dm-6): couldn't mount as ext3 due to feature incompatibilities
>> EXT4-fs (dm-5): couldn't mount as ext3 due to feature incompatibilities
>>
Le 01/09/2019 à 01:04, Miroslav Skoric a écrit :
# dmesg | tail reported (among the other):
EXT4-fs (dm-6): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (dm-5): couldn't mount as ext3 due to feature incompatibilities
# mount reported that /, /usr, and /var were there, but n
On 8/31/19 3:26 PM, Étienne Mollier wrote:
Maybe a check
of the memory and SMART data, if those options are available
from your BIOS, could be welcome, especially SMART since some
messages were mentioning checking the disk.
I checked the system memory and hard disk self test (quick test and
Misko, on 2019-08-31:
> On 8/31/19 3:26 PM, Étienne Mollier wrote:
> > If operations here over do not make any difference, then you
> > really should consider creating a Rescue drive on an USB thumb.
> > I have had a good experience with SystemRescueCD over the
> > years:
> >
> > http://www.sys
On 8/31/19 3:26 PM, Étienne Mollier wrote:
Perhaps you can attempt a boot in "Recovery Mode", see the
"Advanced Boot Options" at the Grub menu stage of the boot.
It could have a positive effect if a faulty kernel module is
loaded and causes this loop in the boot sequence. Maybe a check
of the
On Sat, Aug 31, 2019 at 03:41:12PM +0200, Miroslav Skoric wrote:
> On 8/31/19 3:26 PM, Reco wrote:
>
> >
> > Boot with init=/bin/bash kernel commandline parameter, remount root
> > filesystem read-write, fix your /etc/fstab (systemd is picky about
> > filesystems it's not able to mount, and no, "
On 8/31/19 3:26 PM, Reco wrote:
Boot with init=/bin/bash kernel commandline parameter, remount root
filesystem read-write, fix your /etc/fstab (systemd is picky about
filesystems it's not able to mount, and no, "noauto" won't fix it),
reboot once more.
Reco
Hi,
Sorry for my ignorance, but
Misko, on 2019-08-31:
> After upgrading the old laptop from jessie to strech, it worked
> well for few days (although more slowly than it was with
> jessie). But after last proper shutdown, it does not boot
> anymore. In fact, it starts to boot until it comes to a point
> where it says:
>
> "You ar
Hi.
On Sat, Aug 31, 2019 at 02:00:18PM +0200, Miroslav Skoric wrote:
> Any idea what to do? Thanks.
Boot with init=/bin/bash kernel commandline parameter, remount root
filesystem read-write, fix your /etc/fstab (systemd is picky about
filesystems it's not able to mount, and no, "noauto" w
Hello,
After upgrading the old laptop from jessie to strech, it worked well for
few days (although more slowly than it was with jessie). But after last
proper shutdown, it does not boot anymore. In fact, it starts to boot
until it comes to a point where it says:
"You are in emergency mode. A
On Jo, 19 dec 13, 18:39:07, John Hasler wrote:
>
> There is no need for him to "track" Jessie once he has upgraded enough
> to run his program. Just read the security list and upgrade individual
> packages as needed.
This smells like dependency hell.
Kind regards,
Andrei
--
http://wiki.debian.
On Jo, 19 dec 13, 10:23:35, John Hasler wrote:
> Read and follow the release notes and you'll be ok.
For Jessie? They don't exist yet.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/
On 12/20/2013 10:56 AM, John Hasler wrote:
> Verde Denim writes:
>> Is it possible for me to upgrade glibc/libffi to the Jessie release
>> and leave everything else in Wheezy?
> Upgrading glibc and libffi will force the upgrade of packages that depend
> on specific versions of those libraries. Use
On Friday 20 December 2013 15:24:41 Verde Denim wrote:
> Is
> it possible for me to upgrade glibc/libffi to the Jessie release
> and leave everything else in Wheezy?
Have you looked at wheezy-backports?
http://backports.debian.org/
http://packages.debian.org/search?keywords=glibc
I see that you
Verde Denim writes:
> Is it possible for me to upgrade glibc/libffi to the Jessie release
> and leave everything else in Wheezy?
Upgrading glibc and libffi will force the upgrade of packages that depend
on specific versions of those libraries. Use 'apt-get -s' to see what
would happen.
--
John H
On 12/19/2013 07:39 PM, John Hasler wrote:
> Bob Proulx writes:
>> Jessie is at least a year from release. There are still major changes
>> planned for it. I expect Jessie to go through some cyclic stability,
>> instability, stability, instability before it releases at least a year
>> from now.
>
Bob Proulx writes:
> Jessie is at least a year from release. There are still major changes
> planned for it. I expect Jessie to go through some cyclic stability,
> instability, stability, instability before it releases at least a year
> from now.
There is no need for him to "track" Jessie once h
Verde Denim wrote:
> Stan Hoeppner wrote:
> > Why take any chances? Install/run Jessie and the application in a
> > virtual machine.
>
> Thanks for the reply. I thought of that, but the package I'm after is an
> integral part of my test platform for assessing mobile code. I really do
> need to ha
Verde Denim writes:
> ...is there more control I can exercise over the updating of the
> distro other than 'apt-get dist-upgrade' ?
First do 'apt-get upgrade'. This will do everything that can be done
without any removals or installation of new packages. It may suffice to
get you to the point wh
On 12/19/2013 11:23 AM, John Hasler wrote:
> Read and follow the release notes and you'll be ok.
John
Thanks for the reply. If you're suggesting the release notes for Jessie,
I agree that they should be reviewed. Aside from reviewing these notes,
is there more control I can exercise over the updati
On 12/19/2013 11:07 AM, Stan Hoeppner wrote:
> On 12/19/2013 9:54 AM, Verde Denim wrote:
>> Just checking in to get a consensus -
>>
>> I'm running a (very stable) Debian workstation with Wheezy that has a
>> lot of development/testing applications installed. I tried an install of
>> hopper disasse
Read and follow the release notes and you'll be ok.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bo0cernc
On 12/19/2013 9:54 AM, Verde Denim wrote:
> Just checking in to get a consensus -
>
> I'm running a (very stable) Debian workstation with Wheezy that has a
> lot of development/testing applications installed. I tried an install of
> hopper disassembler that threw errors concerning GLIBC and libffi
Just checking in to get a consensus -
I'm running a (very stable) Debian workstation with Wheezy that has a
lot of development/testing applications installed. I tried an install of
hopper disassembler that threw errors concerning GLIBC and libffi so I
contacted the package maintainers who told me
53 matches
Mail list logo
