On 2020-04-09 21:25, Samuel Sieb wrote:
/dev/bus/usb/001/006 is the device name.
°
[root@Workstation-1 bobg]# ls -al /dev/bus/usb/001/006
crw-rw-r--. 1 root root 189, 5 Apr 9 20:11 /dev/bus/usb/001/006
[root@Workstation-1 bobg]# chmod 777 /dev/bus/usb/001/006
[root@Workstation-1 bobg]# ls
On 4/9/20 4:48 PM, Bob Goodwin wrote:
On 2020-04-09 18:16, Samuel Sieb wrote:
Or try doing "chmod a+w /dev/bus/001/006" (replace with the correct
numbers if you've replugged or rebooted since your post).
.
After some trial and error I wound up doing chmod 775 /dev/bus/usb but
stilt not detec
On 2020-04-09 18:16, Samuel Sieb wrote:
It seems that udev is not recognizing it or you need to add yourself
to a different group.
.
i don't know what group?
You could run xsane as root as a workaround.
.
Did that earlier, it warned me not to run as root and the did not let me
save to D
On 2020-04-10 06:46, S.Bob wrote:
>
> I had a situation where a dnf update showed nothing to do but the "Software
> Updates" GUI had updates listed. Even did a "dnf clean all" and dnf still
> showed "Nothing to do". Clicked on the Software Updates GUI to install them
> and it did... Why did dnf
All;
I had a situation where a dnf update showed nothing to do but the
"Software Updates" GUI had updates listed. Even did a "dnf clean all"
and dnf still showed "Nothing to do". Clicked on the Software Updates
GUI to install them and it did... Why did dnf not see them?
Thanks in advance
On 4/9/20 2:11 PM, Bob Goodwin wrote:
Xsane can't see my scanner as user bobg, as root is detected.
bobg]# scanimage -L
device `genesys:libusb:001:006' is a Canon LiDE 110 flatbed scanner
[bobg@Workstation-1 ~]$ lsusb
Bus 001 Device 006: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
$ sane-find-s
Hi,
> 139255322 us [ 180481085 ]
This says that the run already lasted 180 seconds and the SCSI command
to which this line belongs lasted 139 seconds. (Your patience is in
good shape.)
> INQUIRY
There are only two of these commands in the course of normal drive
examination by libburn. So
Hi,
> But when I add an output device to the image like
> xorriso -indev test.iso \
> -boot_image any keep \
> -map "$file_or_tree_on_disk" "$path_in_iso" \
> -outdev test.iso
>
> Everything magically works.
> Weird.
Hm. This should yield the same result as -dev tes
Xsane can't see my scanner as user bobg, as root is detected.
bobg]# scanimage -L
device `genesys:libusb:001:006' is a Canon LiDE 110 flatbed scanner
[bobg@Workstation-1 ~]$ lsusb
Bus 001 Device 006: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
$ sane-find-scanner
could not open USB device 0x04a9
Hi,
Sreyan Chakravarty wrote:
> Okay, so what you are doing is actually against convention.
It's fully compliant. Just moving apart the default mountable superblock
from the chain of session superblocks which need an extra option to
mount(8) in order to get mounted.
> Essentially, the OS assume
One more piece of mysterious info for the record:
VLC on Windows 10 can play a DVD just fine with the USB
drive (the exact same one that hangs on two different
linux systems I've now tried).
VLC on linux hangs just like everything else.
I think I'll now give up completely trying to understand
wh
> In Nautilus, if I right-click an .iso file, I have the option to open
> with the disk image mounter. That works.
Ok, using the command:
xorriso -dev test.iso \
-boot_image any keep \
-map "$file_or_tree_on_disk" "$path_in_iso"
Does not work even if I use right-click and
> That's the reason for my invention of emulated table of content.
> The first session does not get written to block 0 but rather to block 32.
> This leaves room for an official superblock at block 0 and thus saves
> the superblock of the first session from being overwritten by session 2.
> Now the
(On Thu, Apr 9, 2020 at 12:45 PM Stan wrote)
> It looks like you are having module problems. I don't know
> if this will help, but while testing upgrade from F31 to F32
> to look for issues, we were advised to run
> dnf module reset '*'
> to make modules behave before running the upgrade. You cou
On Thu, 9 Apr 2020 12:07:17 -0600
home user wrote:
> Nothing seems to have changed:
>
> bash.19[~]: dnf system-upgrade download --skip-broken --refresh
> --releasever=31 --best --allowerasing
> Before you continue ensure that your system is fully upgraded by
> running "dnf --refresh upgrade". D
(On Thu, Apr 9, 2020 at 12:13 PM Doug wrote)
> I tend to `dnf erase` anything that complains and reinstall it
> after the upgrade. So I wonder if you can do that with gimp
> and get it going.
(On Thu, Apr 9, 2020 at 12:16 PM Richard wrote)
> I was starting to think the same thing. Also you migh
On Thu, Apr 9, 2020 at 1:14 PM Doug Herr
wrote:
> > I'm stuck. How do I get this upgrade to work?
>
> I tend to `dnf erase` anything that complains and reinstall it after the
> upgrade. So I wonder if you can do that with gimp and get it going.
>
I was starting to think the same thing. Also you
> I'm stuck. How do I get this upgrade to work?
I tend to `dnf erase` anything that complains and reinstall it after the
upgrade. So I wonder if you can do that with gimp and get it going.
___
users mailing list -- users@lists.fedoraproject.org
To unsu
(On Thu, Apr 9, 2020 at 11:37 AM Richard wrote)
> Unfortunately it looks like that package is needed to deal
> with modules, but why it let you erase the package without
> pulling in whatever's depending on it I don't know. For now
> I think you need to reinstall it.
done.
bash.18[~]: dnf insta
On Thu, Apr 9, 2020 at 12:33 PM home user wrote:
>
> Apparently not, but that did not seem to help.
>
> The only error message now, in the last 3 tries, is
> -
> terminate called after throwing an instance of
> 'libdnf::ModulePackageContainer::EnableMultipleStreamsException'
>what(): Can
(On Thu, Apr 9, 2020 at 11:14 AM Richard wrote)
> If you do "dnf erase python2-libmodulemd" will
> anything important removed with it?
bash.14[~]: dnf erase python2-libmodulemd
Dependencies resolved.
(On Thu, Apr 9, 2020 at 11:14 AM Richard wrote)
> Do a "dnf distro-sync" to see if you have anything weird
> going on (manually installed RPMs, etc).
bash.12[~]: dnf distro-sync
Last metadata expiration check: 0:57:57 ago on Thu 09 Apr 2020 10:19:27
AM MDT.
Dependencies resolved.
=
On Thu, Apr 9, 2020 at 12:07 PM home user wrote:
> (f30 -> f31; gnome)
>
> I tried to upgrade my system from f30 to f31 as per the instructions. I
> entered
> "dnf system-upgrade download --refresh --releasever=31"
> Failed. The results are in the first attachment (problem1.txt).
>
Perhaps som
(f30 -> f31; gnome)
I tried to upgrade my system from f30 to f31 as per the instructions. I
entered
"dnf system-upgrade download --refresh --releasever=31"
Failed. The results are in the first attachment (problem1.txt).
As the dnf output suggested, I tried
"dnf system-upgrade download --skip
Hi,
Sreyan Chakravarty wrote:
> I am kind of confused as to the difference/advantage between keeping the old
> boot image versus rebuilding one.
My first multi-session proposal was to keep as much of the boot equipment
as possible.
After all, we began with the riddle why your genisoimage produced
On Thu, 09 Apr 2020 17:29:46 +0200
Thomas Schmitt wrote:
> If this was a slim drive in a fancy flat USB box i'd ask whether it gets
> its electrical power via USB cable.
> There have been cases that drives fell unconscious while speeding up
> the disc because the computer did not deliver stable vo
On Thu, Apr 9, 2020 at 9:29 AM Thomas Schmitt wrote:
> Hrmpf. strace reports "openat(2)" where libburn calls open(2).
strace reports the name of the Linux system call, which is indeed
openat. The open(2) and openat(2) functions (and open64(2) and
openat64(2) on some systems) are C library functi
On Thu, 9 Apr 2020 11:48:30 -0300
George N. White III wrote:
> The bug may only appear for certain combinations of drive and USB
> chipset. Check for firmware updates for the drive.
Yep. I'm thinking it has something to do with the chipset.
I believe I did read about some usb problem some chips
Hi,
> 139255322 us [ 180481085 ]
This says that the run already lasted 180 seconds and the SCSI command
to which this line belongs lasted 139 seconds. (Your patience is in
good shape.)
> INQUIRY
There are only two of these commands in the course of normal drive
examination by libburn. So
Sorry rather why are you disabling session history ?
Any particular reason?
On Wed, Apr 8, 2020 at 11:54 PM Thomas Schmitt wrote:
> Hi,
>
> Sreyan Chakravarty wrote:
> > xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any
> keep
> > -map /home/sreyan/anaconda-ks.cfg /isolinux
> Is there any noteworthy text to see, beyond what is quoted above ?
No you can ignore it. It was just a screenshot from VirtualBox describing
the superblocks problem I typed out.
I can't thank you enough for your in-depth explanations. Not only are you
helping me with my problem but I also lear
On 09/04/2020 12:24, Ed Greshko wrote:
On 2020-04-09 17:57, Terry Barnaby wrote:
The script already has date/time and the log shows (The Wed 8th entries entry
having the PID):
Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn /data/www
/data/vwt /data/www /data1/kvm /data/d
> I only see a black rectangle (with some framing ornaments).
> My web browser is old.
>
> Is there any noteworthy text to see, beyond what is quoted above ?
Nothing of value. You can ignore it.
I could not be more grateful for your in-depth replies. Not only are you
helping me with my problem
On Wed, 8 Apr 2020 at 22:21, Tom Horsley wrote:
> Anyone else experienced this:
>
> I have a nice modern LG WH16NS40 Blu-ray rewriter, and a nice modern
> computer case with zero drive bays, so I got an OWC external drive
> case with sata -> usb3 to hold the drive.
>
> Everything I've tried works
On Thu, 09 Apr 2020 15:33:38 +0200
Thomas Schmitt wrote:
> If /tmp/xorriso.log is long (one or two dozen KB) then send it to
> my mail address directly. I will then report what it tells me.
> If it is short, please post it here.
It sat here for about three minutes till I got bored:
zooty> xorris
Hi,
Tom Horsley wrote:
> My current theory is that it has something to do with
> the phase II region protection (which is supposed to be hardware
> rather than software)
That would be plausible.
But letting the drive hang on open with the need for power-off seems
to be a drastic reaction.
> It
On Thu, 09 Apr 2020 09:29:01 +0200
Thomas Schmitt wrote:
> That's not usual. I have a BH16NS40 in a USB box from DeLOCK. No problems
> to open it with any medium.
My current theory is that it has something to do with
the phase II region protection (which is supposed to be hardware
rather than sof
On 2020-04-09 17:57, Terry Barnaby wrote:
> The script already has date/time and the log shows (The Wed 8th entries entry
> having the PID):
>
> Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn
> /data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt
> /data/backup
On 09/04/2020 07:00, francis.montag...@inria.fr wrote:
Hi
On Tue, 07 Apr 2020 07:07:36 +0100 Terry Barnaby wrote:
# Min Hour Day Month WeekDay
# Perform incremental backup to every work day
01 23 * * 1 root /src/bbackup/bbackup-beam
01 23 * * 2 root /src/bbackup/bbackup-beam
01 23 * * 3 root /
On 08/04/2020 23:11, Cameron Simpson wrote:
On 08Apr2020 14:54, Terry Barnaby wrote:
Note this has happened a few times this year, (approx 1 in 64 x) so
not related to DST changes anyway. Might be due to chrony clock
resyncs I suppose but I think something stranger is going on here or
somethi
Hi,
Tom Horsley wrote:
> I have a nice modern LG WH16NS40 Blu-ray rewriter [...]
> trying to rip a DVD [...]
> openat(AT_FDCWD, "/dev/sr0", O_RDONLY <-- never finishes till I unplug it
That's not usual. I have a BH16NS40 in a USB box from DeLOCK. No problems
to open it with any medium.
In gener
On 4/8/20 10:37 PM, Sreyan Chakravarty wrote:
On 4/8/20 11:03 AM, Sreyan Chakravarty wrote:
Gnome Disks is expecting a disk and the .iso file looks like one:
# file Fedora-Workstation-Live-x86_64-31-1.9.iso
Fedora-Workstation-Live-x86_64-31-1.9.iso: DOS/MBR boot sector;
partition 2 : ID=0xef, sta
42 matches
Mail list logo
