Re: libreoffice crash
On 2020-02-08, Ólafur Jens Sigurðsson wrote:
> Hi, I upgraded my system to Buster finally but after that then
> LibreOffice crashes on me. I have tried to uninstall it and reinstall,
> no luck there. I tried as a different user, same crash there.
>
> I am out of ideas. I have pasted an strace -f of opening localc from the
> command line https://pastebin.com/Ev55tVUH
> Any ideas on what could be the problem here?
You might try moving your old config out of the way as a stab
in the dark to see if that might improve things.
mv ~/.config/libreoffice{,.old}
> TIA, Oli
>
>
--
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud
Re: Anyone with experience scanning with Epson
On Sat 08 Feb 2020 at 09:48:19 -, Curt wrote: > On 2020-02-07, kaye n wrote: > > > > Hello Friends! > > > > I'm running: > > Kernel: 4.19.0-6-amd64 x86_64 > > bits: 64 > > Desktop: Xfce 4.12.4 > > Distro: Debian GNU/Linux 10 (buster) > > > > My printer is an Epson L220. It's connected to my laptop's USB port. > > > > The command lsusb shows: > > Bus 002 Device 003: ID *04b8:08d1* Seiko Epson Corp. > > > > Therefore in the file, /etc/sane.d/epkowa.conf > > I added this line: > > > > > > *usb 0x04b8 0x08d1* > > The printer can print just fine, but ImageScan and XSane would not run. > > > > ImageScan says: > > Could not send command to scanner. Check the scanner's status. > > > > XSane says: > > Failed to open device 'epkowa:usb:002:003': > > Access to resource has been denied. > > > > Thank you for your time! > > > > You might try one or both of the workarounds in the Epson > troubleshooting section here > > https://help.ubuntu.com/community/sane_Troubleshooting > > They seem to advise trying the first workaround first (and then, if that > fails, the iscan workaround in addition to that). Here's the first > workaround listed (which appears to deal with your permission problems): > > sudo ln -sfr /usr/lib/sane/libsane-epk* /usr/lib/x86_64-linux-gnu/sane/ Against doing this is the fact that Epson does not provide a package for the L220 that employs the epkowa backend. That is because epkowa is not meant for that device. Maybe the OP has found this out by now. (Incidentally, the bug that the Ubuntu advice is targeting is one that was never present in Debian stable, testing or unstable). -- Brian.
Re: libreoffice crash
On Sun, 9 Feb 2020 09:22:47 - (UTC) Curt wrote: Hello Curt, >You might try moving your old config out of the way as a stab >in the dark to see if that might improve things. Even easier is to, from the command line, start 'soffice --safe-mode' -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" The public gets what the public wants Going Underground - The Jam pgpWSWzH2Kb1l.pgp Description: OpenPGP digital signature
Re: Anyone with experience scanning with Epson
Renato Gallo wrote: > try iscan or simple-scan +1 using iscan works perfectly fine, but I am not sure how recent and working is the latest version you can find. I had to patch 2.30.1 when moved to stretch mainly because libpng16 replaced libpng12. I am using E 330 for couple of years already.
Re: Anyone with experience scanning with Epson
On 2020-02-09, Brian wrote: > > Against doing this is the fact that Epson does not provide a package > for the L220 that employs the epkowa backend. That is because epkowa > is not meant for that device. Maybe the OP has found this out by now. Did you tell the OP that? I missed it. Oh, I see you asked what file the OP downloaded and that question was left hanging without a response. Epson only seems to provide a single generic package for their scanners/multifunction printers. http://support.epson.net/linux/en/imagescanv3.php http://download.ebz.epson.net/man/linux/imagescanv3_e.html#sec6-1 I was thrown off by the OP's error message: Failed to open device 'epkowa:usb:002:003': Maybe that's related to the (perhaps unwise) entry the OP added to /etc/sane.d/epkowa.conf. It's true the installation manual linked above makes no mention of it. > (Incidentally, the bug that the Ubuntu advice is targeting is one > that was never present in Debian stable, testing or unstable). That too, I guess. -- "J'ai pour me guérir du jugement des autres toute la distance qui me sépare de moi." Antonin Artaud
Re: libreoffice crash
On Sun, Feb 09, 2020 at 10:04:45AM +, Brad Rogers wrote: > On Sun, 9 Feb 2020 09:22:47 - (UTC) > Curt wrote: > > Hello Curt, > > >You might try moving your old config out of the way as a stab > >in the dark to see if that might improve things. > > Even easier is to, from the command line, start 'soffice --safe-mode' Hi, thanks for the suggestions but no luck, still crashes Cheers, Oli
Cross debootstrap without root rights
Hi Debian users, I'd like to run the second stage of debootstrap without root rights, but for another architecture (host is x86_64 and target is arm64). I know how to do all that with root rights (i.e qemu-aarch64-static works perfectly here, also, I can recommend using qemu-debootstrap), but I can't figure out a way how to do that without root rights. I was expecting that fakechroot and fakeroot will do the necessary "magic" to make chroot work for my use-case, but that's not the case (I need to have libfakeroot.so and libfakechroot.so in the target rootfs, but I could not find a reliable way to get them in). I found some emails in the archives about similar use cases (from ~10 years ago). But I failed to identify the solution in those cases. Therefore I'd like to ask if anyone has a solution for my use case or some hints/pointers. Thanks, Christoph
Re: Anyone with experience scanning with Epson
On Sun 09 Feb 2020 at 10:20:54 -, Curt wrote: > On 2020-02-09, Brian wrote: > > > > Against doing this is the fact that Epson does not provide a package > > for the L220 that employs the epkowa backend. That is because epkowa > > is not meant for that device. Maybe the OP has found this out by now. > > Did you tell the OP that? I missed it. Oh, I see you asked what file the > OP downloaded and that question was left hanging without a response. > > Epson only seems to provide a single generic package for their > scanners/multifunction printers. There is also an iscan-bundle, which has libsane-epkowa. > http://support.epson.net/linux/en/imagescanv3.php The imagescan bundle uses libsane-imagescan. > http://download.ebz.epson.net/man/linux/imagescanv3_e.html#sec6-1 > > I was thrown off by the OP's error message: > > Failed to open device 'epkowa:usb:002:003': The imagescan bundle is what is offered by Epson for the L220 at http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX Permissions on the USB bus wouldn't have been top of my list to look at. > Maybe that's related to the (perhaps unwise) entry the OP added to > /etc/sane.d/epkowa.conf. It's true the installation manual linked above > makes no mention of it. > > > (Incidentally, the bug that the Ubuntu advice is targeting is one > > that was never present in Debian stable, testing or unstable). > > That too, I guess. Ubuntu took the SANE packages from experimental to put into 18.04 LTS. You reap what you sow. -- Brian.
Re: Cups no longer accepting remote connections for printing.
On Sun 09 Feb 2020 at 02:06:22 +, James Allsopp wrote: > HI, > My printer on a remote machine works when access from that machine, I've > checked port 631 isn't blocked using Xnat, but I can't work out why I can't > print. > All the user pages say forbidden, and a test page from my local cups hangs. Please give the printer make and model and the outputs of 'lpstat -t' on server and client. -- Brian.
Re: Cross debootstrap without root rights
[ sent again, without 8bit headers to please Debian MTAs ] Hi Christoph, Quoting Christoph Müllner (2020-02-09 12:54:56) > I'd like to run the second stage of debootstrap without root rights, > but for another architecture (host is x86_64 and target is arm64). > > I know how to do all that with root rights (i.e qemu-aarch64-static > works perfectly here, also, I can recommend using qemu-debootstrap), > but I can't figure out a way how to do that without root rights. > > I was expecting that fakechroot and fakeroot will do the necessary > "magic" to make chroot work for my use-case, but that's not the case > (I need to have libfakeroot.so and libfakechroot.so in the target > rootfs, but I could not find a reliable way to get them in). > > I found some emails in the archives about similar use cases (from ~10 > years ago). But I failed to identify the solution in those cases. > > Therefore I'd like to ask if anyone has a solution for my use case or > some hints/pointers. Have a look at mmdebstrap! The author of that tool - Johannes Schauer - has long fought for ways to eliminate the need for being root to bootstrap Debian, and mmdebstrap is as I understand it the state of the art of that! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: libreoffice crash
On 2020-02-09, Ólafur Jens Sigurðsson wrote: >> >> Even easier is to, from the command line, start 'soffice --safe-mode' > > Hi, thanks for the suggestions but no luck, still crashes I'm uncertain what version you're using in Buster (packages.debian.org is not responding from here), but another stab in the darkness would be to turn off opengl, which can be done in versions >= 5.3 soffice --safe-mode Select "Configure" -> "Disable Hardware Acceleration (OpenGL, OpenCL)" or in versions 5.2 and older by editing the 'registrymodifications.xcu' file found in your user profile folder and setting the 'UseOpenGL' and 'ForceOpenGL' entries to false. > Cheers, Oli > > -- "J'ai pour me guérir du jugement des autres toute la distance qui me sépare de moi." Antonin Artaud
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
David wrote: ... >Device to use as root file system /dev/mapper/sda4_crypt >Mount separate /boot parititionYes >Mount separate /boot/efi parititionYes >Rescue operations Force GRUB installation to the >EFI removable media path > -> Yes >Rescue operations Reboot the system > >Power down at POST. Remove debian-10.2.0-amd64-xfce-CD-1 USB >stick. > >Power up. Press F2 to enter Setup. Boot sequence starts with >"debian". Exit. > >Boots into Debian GNU/Linux. >Thanks! :-) \o/ -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Re: Cups no longer accepting remote connections for printing.
Hi, Thanks Brian, this is the server; scheduler is running system default destination: HL-2030-series device for HL-2030-series: usb://Brother/HL-2030%20series?serial=L0J260292 HL-2030-series accepting requests since Sun 23 Jul 2017 21:21:32 BST printer HL-2030-series is idle. enabled since Sun 23 Jul 2017 21:21:32 BST The is the client; scheduler is running no system default destination lpstat: Forbidden lpstat: Forbidden lpstat: Forbidden lpstat: Forbidden lpstat: Forbidden Here's an nmap for the port on the server. # nmap -sS -p631 hawaiian Starting Nmap 7.70 ( https://nmap.org ) at 2020-02-09 14:07 GMT Nmap scan report for hawaiian (192.168.1.206) Host is up (0.022s latency). Other addresses for hawaiian (not scanned): fde6:4511:f54::1a3 fde6:4511:f54::a55 rDNS record for 192.168.1.206: hawaiian.frankexchangeofviews.uk PORTSTATE SERVICE 631/tcp open ipp MAC Address: 00:1D:7D:0D:2A:9D (Giga-byte Technology) Nmap done: 1 IP address (1 host up) scanned in 0.53 seconds On Sun, 9 Feb 2020 at 12:13, Brian wrote: > On Sun 09 Feb 2020 at 02:06:22 +, James Allsopp wrote: > > > HI, > > My printer on a remote machine works when access from that machine, I've > > checked port 631 isn't blocked using Xnat, but I can't work out why I > can't > > print. > > All the user pages say forbidden, and a test page from my local cups > hangs. > > Please give the printer make and model and the outputs of 'lpstat -t' > on server and client. > > -- > Brian. > >
Re: Cups no longer accepting remote connections for printing.
On Sun 09 Feb 2020 at 14:08:41 +, James Allsopp wrote: > Hi, > Thanks Brian, this is the server; > > scheduler is running > system default destination: HL-2030-series > device for HL-2030-series: usb://Brother/HL-2030%20series?serial=L0J260292 > HL-2030-series accepting requests since Sun 23 Jul 2017 21:21:32 BST > printer HL-2030-series is idle. enabled since Sun 23 Jul 2017 21:21:32 BST Nothing untoward here that I can see. You should, if this queue is shared, be able to see its URI from the client with 'lpinfo -v' and 'lpstat -l -e'. What do they give? > The is the client; > scheduler is running > no system default destination > lpstat: Forbidden > lpstat: Forbidden > lpstat: Forbidden > lpstat: Forbidden > lpstat: Forbidden I've never come across that before. "Forbidden" simply shouldn't happen. It looks like the client is denying access to its cupsd. A common way to access the print queue on the server is to set a queue up on the client. The state of this *local queue* is shown by the lpstat command run on the client. What is happening on the server is of no consequence. Are you using a client.conf in $HOME/.cups or /etc/cups? Anything in /etc/cups/ppd? What do you have for 'ls -l /etc/cups/cupsd.conf? -- Brian.
Re: Cups no longer accepting remote connections for printing.
Hi, James Allsopp wrote: [...] > > # Restrict access to the server... > > Order allow,deny > Allow localhost > Allow 192.168.1.* > > ServerAlias * > # Restrict access to the admin pages... > > Order allow,deny > Allow localhost > Allow 192.168.1.* > > Don't mix DNS wildcard '*' with network netmask '/xx' Both are different things and not compatible. Correct is in your case: Allow 192.168.1.0/24 Regards, Klaus. -- Klaus Singvogel GnuPG-Key-ID: 1024R/5068792D 1994-06-27
Re: Swaks usage.
From: Celejar Date: Sun, 26 Jan 2020 12:07:26 -0500 > Take a look at: > > https://www.hostgator.com/help/article/535-incorrect-authentication-data > https://stackoverflow.com/questions/14297264/password-not-accepted-from-server-535-incorrect-authentication-data-when-send/44564332#44564332 > https://github.com/PHPMailer/PHPMailer/issues/1074 OK, thanks. Also found this on the mail server. Secure SSL/TLS Settings (Recommended) Username: .@.ca Password: Use the email accountâs password. Incoming Server:mail.east.ca IMAP Port: 993 POP3 Port: 995 Outgoing Server:mail.east.ca SMTP Port: 465 IMAP, POP3, and SMTP require authentication. The -au parameter in the earlier swaks command was wrong. This succeeds. peter@dalton:/home/peter$ swaks -a PLAIN,LOGIN -au pe...@east.ca \ -ap -tlsc --port 465 -s mail.east.ca === Trying mail.east.ca:465... === Connected to mail.east.ca. === TLS started with cipher TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 === TLS no local certificate set === TLS peer DN="/OU=Domain Control Validated/OU=Hosted by HostGator.com, LLC./OU=PositiveSSL Wildcard/CN=*.websitewelcome.com" <~ 220-ccx.websitewelcome.com ESMTP Exim 4.92 #2 Sun, 09 Feb 2020 09:05:11 -0600 <~ 220-We do not authorize the use of this system to transport unsolicited, <~ 220 and/or bulk e-mail. ~> EHLO dalton.invalid <~ 250-ccx.websitewelcome.com Hello dalton.invalid [142.103.107.137] <~ 250-SIZE 52428800 <~ 250-8BITMIME <~ 250-PIPELINING <~ 250-AUTH PLAIN LOGIN <~ 250 HELP ~> AUTH PLAIN <~ 235 Authentication succeeded ~> MAIL FROM: <~ 250 OK ~> RCPT TO: <~ 250 Accepted ~> DATA <~ 354 Enter message, ending with "." on a line by itself ~> Date: Sun, 09 Feb 2020 07:05:11 -0800 ~> To: pe...@east.ca ~> From: peter@dalton.invalid ~> Subject: test Sun, 09 Feb 2020 07:05:11 -0800 ~> Message-Id: <20200209070511.004076@dalton.invalid> ~> X-Mailer: swaks v20181104.0 jetmore.org/john/code/swaks/ ~> ~> This is a test mailing ~> ~> ~> . <~ 250 OK id=1j0o92-001FBJ-6E ~> QUIT <~ 221 ccx.websitewelcome.com closing connection === Connection closed with remote host. Also works with the "-s ccx.websitewelcom.com". There must be some advantage to the account specific server name. Thanks, ... P. -- https://en.wikibooks.org/wiki/Medical_Machines https://en.wikibooks.org/wiki/Oberon Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Cross debootstrap without root rights
Hi, (please CC me, I'm not subscribed to d-user@l.d.o) Quoting Christoph Müllner (2020-02-09 12:54:56) > I'd like to run the second stage of debootstrap without root rights, but for > another architecture (host is x86_64 and target is arm64). > > I know how to do all that with root rights (i.e qemu-aarch64-static works > perfectly here, also, I can recommend using qemu-debootstrap), but I can't > figure out a way how to do that without root rights. > > I was expecting that fakechroot and fakeroot will do the necessary "magic" to > make chroot work for my use-case, but that's not the case (I need to have > libfakeroot.so and libfakechroot.so in the target rootfs, but I could not > find a reliable way to get them in). > > I found some emails in the archives about similar use cases (from ~10 years > ago). But I failed to identify the solution in those cases. > > Therefore I'd like to ask if anyone has a solution for my use case or some > hints/pointers. yes, there are several solutions. Either: a) You can use mmdebstrap which is a debootstrap replacement that focuses on not requiring superuser privileges and has foreign architecture support built in: $ mmdebstrap --arch=arm64 unstable debian-unstable.tar b) There is a proof-of-concept that allows one to run debootstrap with unprivileged usernamespaces here: https://bugs.debian.org/829134 This will probably also work with --second-stage c) Getting fakechroot and fakeroot to work with foreign architectures is tricky and requires the right libfakechroot.so being installed and several environment variables to be set differently. You can have a look at how mmdebstrap does this so that you can maybe replicate that for debootstrap: https://sources.debian.org/src/mmdebstrap/0.6.0-4/mmdebstrap/#L1942 Thanks! cheers, josch signature.asc Description: signature
Re: libreoffice crash
On Sun, Feb 09, 2020 at 01:04:18PM -, Curt wrote: > On 2020-02-09, Ólafur Jens Sigurðsson wrote: > >> > >> Even easier is to, from the command line, start 'soffice --safe-mode' > > > > Hi, thanks for the suggestions but no luck, still crashes > > I'm uncertain what version you're using in Buster (packages.debian.org > is not responding from here), but another stab in the darkness would be > to turn off opengl, which can be done in versions >= 5.3 > > soffice --safe-mode > Select "Configure" -> "Disable Hardware > Acceleration (OpenGL, OpenCL)" > > or in versions 5.2 and older by editing the 'registrymodifications.xcu' > file found in your user profile folder and setting the 'UseOpenGL' and > 'ForceOpenGL' entries to false. Well, dpkg -s libreoffice gives me "Version: 1:6.1.5-3+deb10u5", so that is > 5.3 and soffice --safe-mode crashes on me so I can't disable HA from there. Cheers, Oli
Re: Cross debootstrap without root rights
Hello Christoph, Missatge de Christoph Müllner del dia dg., 9 de febr. 2020 a les 12:55: > I was expecting that fakechroot and fakeroot will do the necessary "magic" > to make chroot work for my use-case, but that's not the case (I need to have > libfakeroot.so > and libfakechroot.so in the target rootfs, but I could not find a reliable > way to get them in). > > I found some emails in the archives about similar use cases (from ~10 years > ago). > But I failed to identify the solution in those cases. Nowadays I use debos if I need to create rootless filesystems, you can read the following article to get an idea how it works: https://ekaia.org/blog/2018/07/03/introducing-debos/ Regards -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Re: libreoffice crash
On Sun, Feb 9, 2020 at 11:11 AM Ólafur Jens Sigurðsson wrote: > On Sun, Feb 09, 2020 at 01:04:18PM -, Curt wrote: > > On 2020-02-09, Ólafur Jens Sigurðsson wrote: > > >> > > >> Even easier is to, from the command line, start 'soffice --safe-mode' > > > > > > Hi, thanks for the suggestions but no luck, still crashes > I run sid, and had pretty consistent crashing after an "aptitude full-upgrade" a month or so back.Typically I'd leave a doc open while I went and did something else for a while, and then come back to find that LO was no longer open. I looked into it a bit, but not a lot, figuring, "Meh, I run sid; expect brokenness." Then after a week or two, another full-upgrade seems to have solved the problem. Sorry I don't have better info to help, but maybe there's a clue here that means something to someone. -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
Re: Cross debootstrap without root rights
Hi Jonas, thanks for the pointer. I was hoping for a solution like mmdebstrap. Will give it a try or will at least use it as inspiration. Thanks a lot, Christoph On Sun, Feb 9, 2020 at 1:25 PM Jonas Smedegaard wrote: > Hi Christoph, > > Quoting Christoph Müllner (2020-02-09 12:54:56) > > I'd like to run the second stage of debootstrap without root rights, > > but for another architecture (host is x86_64 and target is arm64). > > > > I know how to do all that with root rights (i.e qemu-aarch64-static > > works perfectly here, also, I can recommend using qemu-debootstrap), > > but I can't figure out a way how to do that without root rights. > > > > I was expecting that fakechroot and fakeroot will do the necessary > > "magic" to make chroot work for my use-case, but that's not the case > > (I need to have libfakeroot.so and libfakechroot.so in the target > > rootfs, but I could not find a reliable way to get them in). > > > > I found some emails in the archives about similar use cases (from ~10 > > years ago). But I failed to identify the solution in those cases. > > > > Therefore I'd like to ask if anyone has a solution for my use case or > > some hints/pointers. > > Have a look at mmdebstrap! > > The author of that tool - Johannes Schauer - has long fought for ways to > eliminate the need for being root to bootstrap Debian, and mmdebstrap is > as I understand it the state of the art of that! > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private >
Re: Cross debootstrap without root rights
Hi Hector, thanks for the pointer to debos. That tool seems to fit quite well (especially the ability to invoke user scripts for customizations), although access to /dev/kvm is quite some price to pay (but already much much better than root rights). Thanks a lot, Christoph On Sun, Feb 9, 2020 at 6:14 PM Hector Oron wrote: > > Hello Christoph, > > Missatge de Christoph Müllner del dia dg., 9 > de febr. 2020 a les 12:55: > > > I was expecting that fakechroot and fakeroot will do the necessary "magic" > > to make chroot work for my use-case, but that's not the case (I need to have libfakeroot.so > > and libfakechroot.so in the target rootfs, but I could not find a reliable way to get them in). > > > > I found some emails in the archives about similar use cases (from ~10 years ago). > > But I failed to identify the solution in those cases. > > Nowadays I use debos if I need to create rootless filesystems, you can > read the following article to get an idea how it works: > https://ekaia.org/blog/2018/07/03/introducing-debos/ > > Regards > -- > Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Re: libreoffice crash
On Sun, Feb 09, 2020 at 01:04:18PM -, Curt wrote: > On 2020-02-09, Ólafur Jens Sigurðsson wrote: > >> > >> Even easier is to, from the command line, start 'soffice --safe-mode' > > > > Hi, thanks for the suggestions but no luck, still crashes > > I'm uncertain what version you're using in Buster (packages.debian.org > is not responding from here), but another stab in the darkness would be > to turn off opengl, which can be done in versions >= 5.3 > > soffice --safe-mode > Select "Configure" -> "Disable Hardware > Acceleration (OpenGL, OpenCL)" Ahh, so sorry, my problem reporting skills are suboptimal at the moment it seems. The crash of libreoffice happens immediately, I don't get up any interface. This is why I ran strace and pasted it in pastebin so someone who knows how to read strace could perhaps find out what the problem is. Cheers, Oli
Repair bootable USB stick
I recently helped a friend install Mint on her computer, and I made a bootable USB stick using their .iso and dd. It's a 16Gb drive, and the .iso was 3.9Gb. I now have the problem that I can only format 3.9Gb of the drive. I'm on Debian 10.2 with KDE. GNOME Disks utility recognizes the device as "16 Gb Thumb Drive / Sandisk Cruzer Glide," and it shows three partitions: a 2Gb ISO9660 for Mint, a 2.5Mb FAT, and 14Gb free space. It also shows partitioning as "Master boot record." But when I press "-" on the Mint partition I get the following error: "Error deleting partition /dev/sdc1: Failed to read partition table on device '/dev/sdc/ (/dev/sdc: unrecognised disk label) (udisks-error-quark, 0)" When I try to format the free space, I get this error: "Don't know how to create partitions this partition table of type '(null)' (udisks-error-quark, 0)" Originally I got an error from GNOME Disks that the device had no partition table. I tried the KDE partition editor to no avail. That app made a new MS-DOS partition table for the device, but it believed it was only 3.9G. Making that partition table has not changed the results in Disks, other than to change it from the no partition table error to the unrecognized disk label error. Can anyone offer any help? Thanks, jon
Re: Repair bootable USB stick
Hi, dd brought your stick into this state. dd should get it out too. dd if=/dev/zero bs=512 count=2 of=/dev/sdc should zap the MBR partition table and the GPT header block. (Of course verify three times that /dev/sdc is the address of the stick before erasing its partition table.) Then do hdparm -z /dev/sdc or unplug and re-plug the USB stick. A partition editor should afterwards perceive it as unpartitioned. > I recently helped a friend install Mint on her computer, [...] > I now have the problem that I can only format 3.9Gb of the drive. > "Error deleting partition /dev/sdc1: Failed to read partition table on > device '/dev/sdc/ (/dev/sdc: unrecognised disk label) (udisks-error-quark, > 0)" Mint 64bit ISOs have the same isohybrid layout as Debian amd64 ISOs. I.e. MBR partition table with nested partitions and outer partition type 0 plus an invalid GPT. It would be interesting to see whether a more conservative layout would be more digestible to the partition editors offered by Debian. Have a nice day :) Thomas
Re: Repair bootable USB stick
On 2020-02-09 14:27, Thomas Schmitt wrote: dd if=/dev/zero bs=512 count=2 of=/dev/sdc When I want to zero-fill a USB flash drive: 1 1M = 1024*1024 byte blocks read and write much faster than 512 byte blocks. 2. I zero-fill the whole flash drive (by omitting 'count'): a. Get rid of any leftovers from any source, known or unknown. b. Verifies fast. c. Once I have written an image: i. I know that non-zero bytes came from the image. ii. If I take an image later, zeroes compress nicely. 3. Debian provides human-readable /dev/disk/by-id device nodes. Using them reduces the chance that I will blow away the wrong drive. So, I would suggest the following (adjust device node to suit): # time dd if=/dev/zero bs=1M of=/dev/disk/by-id/usb-SanDisk_Ultra_Fit_-0\:0 Optional: 4. 'status=progress' 5. 'time dd ' David
Re: Anyone with experience scanning with Epson
Hello Friends! I'm the OP.
Problem solved.
One laptop. Two printers. Epson L220 (USB connected) and Epson L355 (wifi
connected). I can now print and scan with both printers, one connected
via USB, and the other over wifi.
With regards to scanning, if I have been scanning with L220, then for some
reason I need to switch to wifi scanner L355 to scan something else, all I
need to do is edit /etc/sane.d/epkowa.conf by:
commenting out
*usb 0x04b8 0x08d1*
and uncommenting *net 192.168.X.XXX *(so I can switch to scanning over
wifi).
Unfortunately I'm not sure exactly what got it to work. I can only tell
you what I installed, and what files I created and edited.
Weird as it is, it seems I have to install these two. Again, not sure if
it was indeed the solution that got it working.
*sudo dpkg --install imagescan_3.57.0-1epson4debian8_amd64.deb *
(which is inside the core folder of this file:
*imagescan-bundle-debian-8-3.57.0.x64.deb.tar.gz)*
and
also using dpkg command on the deb files in the core and data folders of
this file: *iscan-bundle-1.0.0.x64.deb.tar.gz*
Furthermore, here are some things that I'm not sure is necessary. I will
leave it as is because everything is working fine and I'm too lazy to rule
out anything that's not needed.
In */etc/sane.d/dll.conf *, notice what is commented and uncommented.
#epjitsu
#epson
#epson2
#epsonds
epkowa
Also, created the files
*/etc/udev/rules.d/49-sane-missing-scanner.rules*
and
*/etc/udev/rules.d/myVendor.rules*
and added the following lines in them:
*SUBSYSTEM=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}==”08d1″,
MODE="0664", GROUP=”scanner”,
ENV{libsane_matched}=”yes"SUBSYSTEM=="usb_device", ATTRS{idVendor}=="04b8",
ATTRS{idProduct}==”08d1″, MODE="0664", GROUP=”scanner”,
ENV{libsane_matched}=”yes"*
That's about all the things I did. Sorry I can't be more helpful. Been
using Linux for years but compared to you guys I know next to nothing.
Thank you very much for all your input!
On Sun, Feb 9, 2020 at 8:07 PM Brian wrote:
> On Sun 09 Feb 2020 at 10:20:54 -, Curt wrote:
>
> > On 2020-02-09, Brian wrote:
> > >
> > > Against doing this is the fact that Epson does not provide a package
> > > for the L220 that employs the epkowa backend. That is because epkowa
> > > is not meant for that device. Maybe the OP has found this out by now.
> >
> > Did you tell the OP that? I missed it. Oh, I see you asked what file the
> > OP downloaded and that question was left hanging without a response.
> >
> > Epson only seems to provide a single generic package for their
> > scanners/multifunction printers.
>
> There is also an iscan-bundle, which has libsane-epkowa.
>
> > http://support.epson.net/linux/en/imagescanv3.php
>
> The imagescan bundle uses libsane-imagescan.
>
> > http://download.ebz.epson.net/man/linux/imagescanv3_e.html#sec6-1
> >
> > I was thrown off by the OP's error message:
> >
> > Failed to open device 'epkowa:usb:002:003':
>
> The imagescan bundle is what is offered by Epson for the L220 at
>
> http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
>
> Permissions on the USB bus wouldn't have been top of my list to look
> at.
>
> > Maybe that's related to the (perhaps unwise) entry the OP added to
> > /etc/sane.d/epkowa.conf. It's true the installation manual linked above
> > makes no mention of it.
> >
> > > (Incidentally, the bug that the Ubuntu advice is targeting is one
> > > that was never present in Debian stable, testing or unstable).
> >
> > That too, I guess.
>
> Ubuntu took the SANE packages from experimental to put into 18.04 LTS.
> You reap what you sow.
>
> --
> Brian.
>
>
