Why using find and zip gives zip I/O error?

scasey · 05-31-2023, 02:32 PM

Quote:

Originally Posted by anmac1789

When I typed this command it said [CODE]ls: cannot access 'log/': No such file or directory
[

Code:

ls -ltr /var/log

Sorry for the typo…corrected in #5:

anmac1789 · 05-31-2023, 04:31 PM

Code:

syslog:


2023-05-31T15:41:20.370688-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 2 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:50:38.445643-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.103' (uid=1000 pid=2234 comm="/usr/libexec/tracker-miner-fs-3" label="unconfined")
2023-05-31T15:50:38.463338-04:00 azeem-virtual-machine systemd[1206]: Starting tracker-extract-3.service - Tracker metadata extractor...
2023-05-31T15:50:38.581994-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
2023-05-31T15:50:38.582379-04:00 azeem-virtual-machine systemd[1206]: Started tracker-extract-3.service - Tracker metadata extractor.
2023-05-31T15:50:53.346567-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:50:59.274813-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 18 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:51:00.774050-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T15:51:01.055260-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:51:01.065513-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:51:01.623610-04:00 azeem-virtual-machine nautilus[3796]: gtk_widget_is_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed
2023-05-31T15:51:40.196485-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:51:50.976584-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 3 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:51:56.821815-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.103' (uid=1000 pid=2234 comm="/usr/libexec/tracker-miner-fs-3" label="unconfined")
2023-05-31T15:51:56.855836-04:00 azeem-virtual-machine systemd[1206]: Starting tracker-extract-3.service - Tracker metadata extractor...
2023-05-31T15:51:56.994492-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
2023-05-31T15:51:56.994790-04:00 azeem-virtual-machine systemd[1206]: Started tracker-extract-3.service - Tracker metadata extractor.
2023-05-31T15:51:58.790387-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:52:01.352611-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 17 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:52:01.426224-04:00 azeem-virtual-machine dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.90' (uid=1000 pid=3796 comm="/usr/bin/nautilus --gapplication-service" label="unconfined")
2023-05-31T15:52:01.427873-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T15:52:01.465394-04:00 azeem-virtual-machine systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
2023-05-31T15:52:01.585491-04:00 azeem-virtual-machine dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.hostname1'
2023-05-31T15:52:01.585808-04:00 azeem-virtual-machine systemd[1]: Started systemd-hostnamed.service - Hostname Service.
2023-05-31T15:52:02.024894-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:52:10.170744-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 47 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:52:10.611387-04:00 azeem-virtual-machine nautilus[3796]: gtk_widget_is_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed
2023-05-31T15:52:37.857212-04:00 azeem-virtual-machine systemd[1]: systemd-hostnamed.service: Deactivated successfully.
2023-05-31T15:53:35.909530-04:00 azeem-virtual-machine gnome-shell[1403]: Window manager warning: Ping serial 8845373 was reused for window W44, previous use was for window W18.
2023-05-31T15:54:07.130767-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.103' (uid=1000 pid=2234 comm="/usr/libexec/tracker-miner-fs-3" label="unconfined")
2023-05-31T15:54:07.159596-04:00 azeem-virtual-machine systemd[1206]: Starting tracker-extract-3.service - Tracker metadata extractor...
2023-05-31T15:54:07.325321-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
2023-05-31T15:54:07.325985-04:00 azeem-virtual-machine systemd[1206]: Started tracker-extract-3.service - Tracker metadata extractor.
2023-05-31T15:54:34.195592-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.103' (uid=1000 pid=2234 comm="/usr/libexec/tracker-miner-fs-3" label="unconfined")
2023-05-31T15:54:34.219626-04:00 azeem-virtual-machine systemd[1206]: Starting tracker-extract-3.service - Tracker metadata extractor...
2023-05-31T15:54:34.349060-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
2023-05-31T15:54:34.349257-04:00 azeem-virtual-machine systemd[1206]: Started tracker-extract-3.service - Tracker metadata extractor.
2023-05-31T15:54:38.282991-04:00 azeem-virtual-machine nautilus[3796]: gtk_widget_is_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed
2023-05-31T15:54:38.306488-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:54:43.379526-04:00 azeem-virtual-machine kernel: [ 8912.545604] perf: interrupt took too long (2529 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
2023-05-31T15:54:58.827800-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 21 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:55:00.935959-04:00 azeem-virtual-machine gnome-shell[1403]: libinput error: event2  - VirtualPS/2 VMware VMMouse: client bug: event processing lagging behind by 148ms, your system is too slow
2023-05-31T15:55:04.440588-04:00 azeem-virtual-machine tracker-extract[6836]: Call to gst_discoverer_discover_uri(file:///home/azeem/Documents/Camera/20220618_125211.mp4) failed: This file contains no playable streams.
2023-05-31T15:55:10.029326-04:00 azeem-virtual-machine tracker-extract[6836]: Call to gst_discoverer_discover_uri(file:///home/azeem/Documents/Camera/20221016_140241.mp4) failed: This file contains no playable streams.
2023-05-31T15:55:15.630748-04:00 azeem-virtual-machine tracker-extract[6836]: Call to gst_discoverer_discover_uri(file:///home/azeem/Documents/Camera/20220730_153455.mp4) failed: This file contains no playable streams.
2023-05-31T15:55:18.680391-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:55:20.192412-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 4 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:55:20.668495-04:00 azeem-virtual-machine dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.90' (uid=1000 pid=3796 comm="/usr/bin/nautilus --gapplication-service" label="unconfined")
2023-05-31T15:55:20.682504-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T15:55:20.713311-04:00 azeem-virtual-machine systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
2023-05-31T15:55:20.839760-04:00 azeem-virtual-machine dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.hostname1'
2023-05-31T15:55:20.840850-04:00 azeem-virtual-machine systemd[1]: Started systemd-hostnamed.service - Hostname Service.
2023-05-31T15:55:21.349174-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:55:26.014503-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 16 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:55:26.062881-04:00 azeem-virtual-machine nautilus[3796]: gtk_widget_is_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed
2023-05-31T15:55:32.517423-04:00 azeem-virtual-machine systemd[1206]: tracker-extract-3.service: Consumed 5.432s CPU time.
2023-05-31T15:55:53.501905-04:00 azeem-virtual-machine systemd[1]: systemd-hostnamed.service: Deactivated successfully.
2023-05-31T15:56:03.772024-04:00 azeem-virtual-machine NetworkManager[1004]: <info>  [1685562963.7715] dhcp4 (ens33): state changed new lease, address=192.168.154.129
2023-05-31T15:56:32.891199-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T15:56:33.351578-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 7 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T15:56:33.748299-04:00 azeem-virtual-machine nautilus[3796]: gtk_widget_is_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed
2023-05-31T15:56:34.273747-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:02:07.611800-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 6 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:02:12.423899-04:00 azeem-virtual-machine systemd[1206]: Started app-gnome-org.gnome.Terminal-6974.scope - Application launched by gnome-shell.
2023-05-31T16:02:12.559553-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:02:17.205973-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 42 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:02:17.211678-04:00 azeem-virtual-machine systemd[1206]: Started app-gnome-org.gnome.Terminal-7003.scope - Application launched by gnome-shell.
2023-05-31T16:02:17.233251-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:02:17.307378-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 5 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:02:17.541772-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T16:02:17.555179-04:00 azeem-virtual-machine systemd[1206]: Started vte-spawn-3db0e115-890a-42e0-b894-a6197734d7f2.scope - VTE child process 7011 launched by gnome-terminal-server process 4921.
2023-05-31T16:02:27.948999-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:03:57.168573-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 11 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:03:59.330673-04:00 azeem-virtual-machine nautilus[3796]: gtk_widget_is_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed
2023-05-31T16:04:23.567643-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:04:24.699215-04:00 azeem-virtual-machine systemd[1206]: Started app-gnome-org.gnome.eog-7033.scope - Application launched by gnome-shell.
2023-05-31T16:04:25.744756-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T16:04:26.176477-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.103' (uid=1000 pid=2234 comm="/usr/libexec/tracker-miner-fs-3" label="unconfined")
2023-05-31T16:04:26.211547-04:00 azeem-virtual-machine systemd[1206]: Starting tracker-extract-3.service - Tracker metadata extractor...
2023-05-31T16:04:26.374522-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
2023-05-31T16:04:26.375162-04:00 azeem-virtual-machine systemd[1206]: Started tracker-extract-3.service - Tracker metadata extractor.
2023-05-31T16:04:26.679146-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:04:26.983150-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 3 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:04:27.417357-04:00 azeem-virtual-machine systemd[1206]: app-gnome-org.gnome.eog-7033.scope: Consumed 1.535s CPU time.
2023-05-31T16:04:27.963200-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:04:31.236055-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 27 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:04:31.276256-04:00 azeem-virtual-machine dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.90' (uid=1000 pid=3796 comm="/usr/bin/nautilus --gapplication-service" label="unconfined")
2023-05-31T16:04:31.278435-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T16:04:31.321026-04:00 azeem-virtual-machine systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
2023-05-31T16:04:31.429531-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:04:31.461700-04:00 azeem-virtual-machine dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.hostname1'
2023-05-31T16:04:31.462717-04:00 azeem-virtual-machine systemd[1]: Started systemd-hostnamed.service - Hostname Service.
2023-05-31T16:04:31.844976-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:04:40.290292-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 7 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:04:41.078623-04:00 azeem-virtual-machine nautilus[3796]: gtk_widget_is_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed
2023-05-31T16:05:08.801277-04:00 azeem-virtual-machine systemd[1]: systemd-hostnamed.service: Deactivated successfully.
2023-05-31T16:05:20.375482-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:05:45.234783-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 3 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:05:50.700375-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Activating service name='org.gnome.TextEditor' requested by ':1.123' (uid=1000 pid=3796 comm="/usr/bin/nautilus --gapplication-service" label="unconfined")
2023-05-31T16:05:51.294455-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Successfully activated service 'org.gnome.TextEditor'
2023-05-31T16:05:53.704913-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T16:05:54.644463-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:05:55.135228-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 12 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:05:57.362326-04:00 azeem-virtual-machine kernel: [ 9586.518414] capability: warning: `gvfsd-admin' uses 32-bit capabilities (legacy support in use)
2023-05-31T16:05:57.413236-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T16:05:58.777782-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 3 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T16:06:00.459733-04:00 azeem-virtual-machine gnome-text-edit[7087]: Failed to load file: There was a character encoding conversion error and it was needed to use a fallback character.
2023-05-31T16:06:00.460198-04:00 azeem-virtual-machine gnome-text-edit[7087]: Failed to load document: There was a character encoding conversion error and it was needed to use a fallback character.
2023-05-31T16:11:04.121011-04:00 azeem-virtual-machine NetworkManager[1004]: <info>  [1685563864.1204] dhcp4 (ens33): state changed new lease, address=192.168.154.129
2023-05-31T16:17:01.956522-04:00 azeem-virtual-machine CRON[7153]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
2023-05-31T16:26:03.773709-04:00 azeem-virtual-machine NetworkManager[1004]: <info>  [1685564763.7730] dhcp4 (ens33): state changed new lease, address=192.168.154.129
2023-05-31T16:30:01.028499-04:00 azeem-virtual-machine CRON[7164]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
2023-05-31T16:33:58.384867-04:00 azeem-virtual-machine systemd[1]: Started anacron.service - Run anacron jobs.
2023-05-31T16:33:58.387624-04:00 azeem-virtual-machine anacron[7168]: Anacron 2.3 started on 2023-05-31
2023-05-31T16:33:58.388057-04:00 azeem-virtual-machine anacron[7168]: Normal exit (0 jobs run)
2023-05-31T16:33:58.388651-04:00 azeem-virtual-machine systemd[1]: anacron.service: Deactivated successfully.
2023-05-31T16:41:03.772732-04:00 azeem-virtual-machine NetworkManager[1004]: <info>  [1685565663.7722] dhcp4 (ens33): state changed new lease, address=192.168.154.129
2023-05-31T16:42:29.453702-04:00 azeem-virtual-machine kernel: [11778.590394] perf: interrupt took too long (3178 > 3161), lowering kernel.perf_event_max_sample_rate to 62750
2023-05-31T16:56:03.780696-04:00 azeem-virtual-machine NetworkManager[1004]: <info>  [1685566563.7767] dhcp4 (ens33): state changed new lease, address=192.168.154.129
2023-05-31T17:11:03.775233-04:00 azeem-virtual-machine NetworkManager[1004]: <info>  [1685567463.7746] dhcp4 (ens33): state changed new lease, address=192.168.154.129
2023-05-31T17:17:01.079694-04:00 azeem-virtual-machine CRON[7188]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
2023-05-31T17:20:49.672497-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T17:20:49.780109-04:00 azeem-virtual-machine gnome-text-edit[7087]: Failed to load file: There was a character encoding conversion error and it was needed to use a fallback character.
2023-05-31T17:21:00.364365-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T17:21:01.937513-04:00 azeem-virtual-machine gnome-shell[1403]: message repeated 5 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]
2023-05-31T17:21:02.338177-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Activating service name='org.gnome.TextEditor' requested by ':1.123' (uid=1000 pid=3796 comm="/usr/bin/nautilus --gapplication-service" label="unconfined")
2023-05-31T17:21:02.501155-04:00 azeem-virtual-machine dbus-daemon[1240]: [session uid=1000 pid=1240] Successfully activated service 'org.gnome.TextEditor'
2023-05-31T17:21:03.964780-04:00 azeem-virtual-machine gnome-shell[1403]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
2023-05-31T17:21:07.556054-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T17:21:07.623180-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)
2023-05-31T17:21:11.746492-04:00 azeem-virtual-machine gnome-text-edit[7201]: Failed to load file: There was a character encoding conversion error and it was needed to use a fallback character.
2023-05-31T17:21:11.747042-04:00 azeem-virtual-machine gnome-text-edit[7201]: Failed to load document: There was a character encoding conversion error and it was needed to use a fallback character.
2023-05-31T17:21:16.295359-04:00 azeem-virtual-machine gnome-shell[1403]: (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)

here is a google drive link to the entire /var/logs folder from ubuntu

https://drive.google.com/file/d/1KiX...usp=drive_link

anmac1789 · 06-02-2023, 11:20 AM

Has anyone taken a look at the log folder from my previous post ?

scottieH · 06-14-2023, 01:57 PM

Code:

find ."/sdcard/DCIM/Camera" -exec zip -0 -r "/home/ubuntu/Documents/test.zip" {} +

I see a few issues here.
Depending on your shell, you may need to escape the plus sign.

Code:

{} \+

The -r option to zip means "Recursive." The fille/directory specified by {} will include all files and directories under the /sdcard/DCIM/Camera director EVERY TIME a file is found. To wit:

Code:

$ ls -lR mydir
drwx-- .
drwx-- subdir_A
drwx-- subdir_B
-rwx-- file_1
-rwx-- file_2

./subdir_A
-rwx-- file_A_1
-rwx-- file_A_2

./subdir_B
-rwx-- file_B_1
-rwx-- file_B_2

$ find mydir 
./file_1
./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Because you are using the + in your find command, all of the files are placed on the command line. After substitution, you will actually be executing this command:

Code:

$ zip -0 -r ./file_1 ./file_2 ./subdir_A/file_A_1 ./subdir_A/file_A_2 ./subdir_B/file_B_1 ./subdir_B/file_B_2

The -r option then translates to "read all subdirectories". So, when zip see it's first file, it will travers the subdirectories:

Code:

zip -0 -r ./file_1

zip will read all of the subdirectories (and files) under ./ add and them to the zip file. This it what zip will try to add to the archive:

Code:

./file_1
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

When zip processes the second file, ./file_2, it will try to add all of the files and subdirectories under ./ to the archive:

Code:

./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Internally, this is the list that zip sees of files to process:

Code:

./file_1
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Zip processes all of thes files internally. For a large group of files & subdirectories, zip will run out of space reading all of these files.

What to do:
Option 1: get rid of the -r in the zip command and add -type f to the find command

Code:

$ find mydir -type f  <-- only return filenames (with paths)
./file_1
./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Option 2: Leave the -r in the zip command and add -type d to the find command

Code:

$ find mydir -type d   <-- only return (sub)directory names 
./
./subdir_A
./subdir_B

If you still have trouble:
add the grow (append) option to the zip command and change the + to ; (or \

at the end of the find command.

Code:

$ find mydir -type d -exec zip -0 -r -g zipfile.zip {} \;

Changing the + to ; passes only 1 line at a time to the zip command. This saves you memory, but requires zip to run multiple times.
The line above (with

translates into this:

Code:

zip -0 -r -g zipfile.zip ./
zip -0 -r -g zipfile.zip ./subdir_A
zip -0 -r -g zipfile.zip ./subdir_B

As opposed to ending with a plus, which translates to the:

Code:

zip -0 -r  zipfile.zip ./ ./subdir_A ./subdir_B

The first one calls zip 3 times, with fewer files to process. The second one calls zip once, but with more files ro process.

anmac1789 · 06-14-2023, 02:36 PM

Quote:

Originally Posted by scottieH

Code:

find ."/sdcard/DCIM/Camera" -exec zip -0 -r "/home/ubuntu/Documents/test.zip" {} +

I see a few issues here.
Depending on your shell, you may need to escape the plus sign.

Code:

{} \+

The -r option to zip means "Recursive." The fille/directory specified by {} will include all files and directories under the /sdcard/DCIM/Camera director EVERY TIME a file is found. To wit:

Code:

$ ls -lR mydir
drwx-- .
drwx-- subdir_A
drwx-- subdir_B
-rwx-- file_1
-rwx-- file_2

./subdir_A
-rwx-- file_A_1
-rwx-- file_A_2

./subdir_B
-rwx-- file_B_1
-rwx-- file_B_2

$ find mydir 
./file_1
./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Because you are using the + in your find command, all of the files are placed on the command line. After substitution, you will actually be executing this command:

Code:

$ zip -0 -r ./file_1 ./file_2 ./subdir_A/file_A_1 ./subdir_A/file_A_2 ./subdir_B/file_B_1 ./subdir_B/file_B_2

The -r option then translates to "read all subdirectories". So, when zip see it's first file, it will travers the subdirectories:

Code:

zip -0 -r ./file_1

zip will read all of the subdirectories (and files) under ./ add and them to the zip file. This it what zip will try to add to the archive:

Code:

./file_1
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

When zip processes the second file, ./file_2, it will try to add all of the files and subdirectories under ./ to the archive:

Code:

./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Internally, this is the list that zip sees of files to process:

Code:

./file_1
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Zip processes all of thes files internally. For a large group of files & subdirectories, zip will run out of space reading all of these files.

What to do:
Option 1: get rid of the -r in the zip command and add -type f to the find command

Code:

$ find mydir -type f  <-- only return filenames (with paths)
./file_1
./file_2
./subdir_A/file_A_1
./subdir_A/file_A_2
./subdir_B/file_B_1
./subdir_B/file_B_2

Option 2: Leave the -r in the zip command and add -type d to the find command

Code:

$ find mydir -type d   <-- only return (sub)directory names 
./
./subdir_A
./subdir_B

If you still have trouble:
add the grow (append) option to the zip command and change the + to ; (or \

at the end of the find command.

Code:

$ find mydir -type d -exec zip -0 -r -g zipfile.zip {} \;

Changing the + to ; passes only 1 line at a time to the zip command. This saves you memory, but requires zip to run multiple times.
The line above (with

translates into this:

Code:

zip -0 -r -g zipfile.zip ./
zip -0 -r -g zipfile.zip ./subdir_A
zip -0 -r -g zipfile.zip ./subdir_B

As opposed to ending with a plus, which translates to the:

Code:

zip -0 -r  zipfile.zip ./ ./subdir_A ./subdir_B

The first one calls zip 3 times, with fewer files to process. The second one calls zip once, but with more files ro process.

Ok so this makes a little more sense..have you tried it with multiple files on your machine? I mistakingly corrupted my zip file because I was deleting a file from zip within windows and then I noticed that the process stalled so I went to task manager and clicked cancel and then it corrupted the entire zip file after opening it again. So now, I have to go back to reconstruct the whole thing again. Also, I am using ubuntu 23.04 and sometimes I also use fedora 38 on virtual machines. I will test this later tonight

update: even with the escape character \+ it gives me

zip I/O error: Bad address
zip error: Output file write failure (write error on zip file)

Is there a way to only add 5 files at a time so my memory is not overwhelmed. Btw I have 32 GB of RAM

scottieH · 06-19-2023, 12:04 PM

Quote:

update: even with the escape character \+ it gives me

zip I/O error: Bad address
zip error: Output file write failure (write error on zip file)

Is there a way to only add 5 files at a time so my memory is not overwhelmed. Btw I have 32 GB of RAM

The actual ram doesn't matter much in this case, it is the "internal stack" of the zip program.

You can remove the zip file you created: if the file exists (and possibly corrupt) and you use

Code:

zip -r

, you're asking for trouble. Since you already have issues, it's best to start fresh.

Have you tried replace the + with a ; ?

Yes, you can add 5 files at a time. I'll have to look at the correct syntax. Can you manually create the zip file, without using the find command?

anmac1789 · 06-19-2023, 12:12 PM

Quote:

Originally Posted by scottieH

The actual ram doesn't matter much in this case, it is the "internal stack" of the zip program.

You can remove the zip file you created: if the file exists (and possibly corrupt) and you use

Code:

zip -r

, you're asking for trouble. Since you already have issues, it's best to start fresh.

Have you tried replace the + with a ; ?

Yes, you can add 5 files at a time. I'll have to look at the correct syntax. Can you manually create the zip file, without using the find command?

Quote:

it is the "internal stack" of the zip program.

Can you be a little more specific here?

Quote:

it's best to start fresh.

I have and all these retries have resulted in the same error it always fails to make a zip file

Quote:

Have you tried replace the + with a ; ?

Indeed I have and same error --- I have tried \; and ; {}

Quote:

Can you manually create the zip file, without using the find command?

What do you mean by this? Like selecting a bunch of files and compressing them ? Or do you mean by using terminal and the zip command itself ?

pan64 · 06-19-2023, 12:23 PM

Quote:

Originally Posted by anmac1789

Can you be a little more specific here?

I have and all these retries have resulted in the same error it always fails to make a zip file

Indeed I have and same error --- I have tried \; and ; {}

What do you mean by this? Like selecting a bunch of files and compressing them ? Or do you mean by using terminal and the zip command itself ?

selecting a few of them and try to create a zip. Not all of them, just to try if that works. But it won't.
see post #40, #43 it is not a problem with zip. You cannot solve it by adding flags to zip or find.
You posted a log which does not contain anything related to webdav.

anmac1789 · 06-19-2023, 12:36 PM

Quote:

Originally Posted by pan64

selecting a few of them and try to create a zip. Not all of them, just to try if that works. But it won't.
see post #40, #43 it is not a problem with zip. You cannot solve it by adding flags to zip or find.
You posted a log which does not contain anything related to webdav.

The other guy told me to check for all the logs so I included all those logs. Also, I can create zip files manually perfectly when the zip file source is from local to local. but it doesnt work when its from webdav to local

scottieH · 06-19-2023, 02:59 PM

Quote:

Originally Posted by anmac1789

Also, I can create zip files manually perfectly when the zip file source is from local to local. but it doesnt work when its from webdav to local

A-Ha!
Since your Find path starts with . I am guessing you are in the /webdav directory structure when you run the zip command. I am also going to guess the /webdav is not writeable.

The zip command does create temporary files. Try add

Code:

-b /tmp

to the zip command. That tells it to use /tmp for temporary files instead of the current directory.

anmac1789 · 06-19-2023, 03:05 PM

Quote:

Originally Posted by scottieH

A-Ha!
Since your Find path starts with . I am guessing you are in the /webdav directory structure when you run the zip command. I am also going to guess the /webdav is not writeable.

The zip command does create temporary files. Try add

Code:

-b /tmp

to the zip command. That tells it to use /tmp for temporary files instead of the current directory.

Well yes since I am copying from a webdav server share to local folder, the find . --> the period starting point is from within the webdav folder when its mounted in ubuntu. The webdav directory should be writable, since I am using the app called webdav server pro and also I havent tested copying any files or folder when my android is mounted inside ubuntu since I did not want to tinker with the file and folder timestamps. But if you can download it and test it yourself you can see that it is writable

The -b /tmp --> is this inside the /home/username/tmp ? or can I select any place to set it as a temporary folder location ?

scottieH · 06-19-2023, 04:43 PM

Quote:

Originally Posted by anmac1789

The -b /tmp --> is this inside the /home/username/tmp ? or can I select any place to set it as a temporary folder location ?

You can set it anyplace you'd like.

scottieH · 06-19-2023, 05:06 PM

How much data are you tring to zip? There is a size limit.

Here's another possibility:

Quote:

rm -f /home/ubuntu/Documents/test.zip; find ."/sdcard/DCIM/Camera" -type f | zip -@ "/home/ubuntu/Documents/test.zip"

First, remove the test.zip file
The find path is the same. The -type f option specifies only files will be printed.

Instead of using the -exec option, let find print out all of the files it finds, 1 per line.

For the zip command, the -@ says read the files to compress from STDIN, and not on the command line.
The pipe after the find command takes STDOUT and routs it to STDIN for the zip command.

anmac1789 · 06-19-2023, 07:33 PM

Quote:

Originally Posted by scottieH

How much data are you tring to zip? There is a size limit.

Here's another possibility:

First, remove the test.zip file
The find path is the same. The -type f option specifies only files will be printed.

Instead of using the -exec option, let find print out all of the files it finds, 1 per line.

For the zip command, the -@ says read the files to compress from STDIN, and not on the command line.
The pipe after the find command takes STDOUT and routs it to STDIN for the zip command.

I'm trying to zip a large amount of data approx 18-20 GB of photos/videos from the DCIM folder. What does the STOUT and STIN mean ? Will it still copy the files uncompressed ? can I set zip -0 as the option? Also, what is the difference if any between using exec in terms of file integrity when used with pipe or without pipe??

Quote:

rm -f /home/ubuntu/Documents/test.zip; find ."/sdcard/DCIM/Camera" -type f | zip -@ "/home/ubuntu/Documents/test.zip"

When I piped with zip, I got:
zip warning: file size changed while zipping ./DCIM/Camera/20220617_192506.jpg

There are quite a large number of messages such as above for many files

When I used

Quote:

find ."/sdcard/DCIM/Camera" -type f | zip -0 -@ "/home/ubuntu/Documents/test.zip"

then I get the following error in the screenshot (I know I'm using fedora sorry about that but the process should be the same lol)

scottieH · 06-20-2023, 11:40 AM

Quote:

I'm trying to zip a large amount of data approx 18-20 GB of photos/videos from the DCIM folder. What does the STOUT and STIN mean ? Will it still copy the files uncompressed ? can I set zip -0 as the option? Also, what is the difference if any between using exec in terms of file integrity when used with pipe or without pipe??

The maximum size of a .zip file is 4GB or 64K files.

Try zipping just 1 small directory and see if you have the same issue.