Package: src:linux
Followup-For: Bug #1068356
X-Debbugs-Cc: vek.m1...@gmail.com
Please ignore this bug report - it's working as expected and isn't a bug
Package: src:linux
Version: 6.1.76-1
Severity: important
X-Debbugs-Cc: vek.m1...@gmail.com
Dear Maintainer,
* What led up to the situation?
doing systemctl hibernate led to the issue
* What exactly did you do (or not do) that was effective (or
ineffective)?
the swap space in the
On Thu, 21 Mar 2019 23:40:21 +0900 Hideki Yamane wrote:
> On Tue, 19 Mar 2019 21:08:42 +0530 "Veek.M" wrote:
> > There's a problem with using --keyring=whatever.gpg
>
> No, it's just because you've specified wrong keyring...
> For example, when I use ubuntu-archive-keyring that's not
should I report the issue to HGST in writing - i have a backup which
i'll have to scour and take protective action - I spoke to HGST soon
after the handover at their service center.. but I got the standard
reply 'don't worry they zero it for you'
I am guessing it nuked the sdc partition table and left entire
partitions entirely intact which could be recovered easily - by
scanning for ext4 signatures - this is sufficiently dangerous - yes?
I don't have the output of the command - I was in a bit of a hurry and
let the cmd run on terminal
> Do you have the output of the ddrescue command line (and its
> execution) available? Can you attach the ddrescue_GNU.log
> to the bug report? And did you check the exit code of the ddrescue
> process?
I'm enclosing my current ddrescue_GNU.log file - the disk was a 500GB
HGST 5400RPM disk that
Package: gddrescue
Version: 1.21-1
Severity: important
File: /usr/bin/ddrescue
Dear Maintainer,
This is important. My disk had crashed and about 132KB of sectors were damaged:
http://pix.toile-libre.org/upload/original/1513821694.png
I decided to recover my data, partition by partition sdc4,
Package: dolphin
Version: 4:16.08.3-3
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Don't know
Storage:
Source: xview
Version: 3.2p1.4-28.2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Not sure
[29018.708980] olwmslave[5196]: segfault at 49cdf010 ip 7f186f2b2910 sp
7ffd635dd570
Package: olwm
Version: 3.2p1.4-28.2
Severity: normal
File: /usr/bin/olwmslave
Dear Maintainer,
* What led up to the situation?
dmesg shows
olwmslave[1166]: segfault at e0cdafc0 ip 7f7d3e075910 sp
7fff1c030a40
error 5 in libxview.so.3.2.4[7f7d3e01+154000]
additionally
Package: dbus
Version: 1.10.22-0+deb9u1
Followup-For: Bug #881342
Dear Maintainer,
apt then dies miserably leaving an usuable system - when you do:
sudo dpkg --configure -a
Basically since dbus is unconfigured and exited uncleanly - you then have to
kill invoke-rc.d hoping
dbus.postinst will
Package: dbus
Version: 1.10.22-0+deb9u1
Severity: important
Dear Maintainer,
* What led up to the situation?
Tried to install
xorg hexchat k3b dolphin kdenlive gimp inkscape libreoffice
calibre xpdf kate conky mplayer vlc
using apt-get. It hung on:
Setting up libkf5windowsystem-data
To be absolutely precise it's around 00:04-00:05
13 matches
Mail list logo
