[qubes-users] Whonix Tor Browser 13.0.15 is very slow starting
Hi!
With the current updates Tor Browser in Whonix takes very long to
display a local file
(file:///usr/share/doc/homepage/whonix-welcome-page/whonix.html).
The Browser Console had to say:
--
Browser Console Mode
Parent process only(Fast)
Multiprocess(Slower)
1716504658322 addons.xpi WARN Checking
/home/user/.tb/tor-browser/Browser/distribution/extensions for addons
1716504658488 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232}
WARN Loading extension '{73a6fe31-595d-460b-a920-fcc0f8843232}':
Reading manifest: "applications" property ignored and overridden by
"browser_specific_settings"
1716504659021 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232}
WARN Loading extension '{73a6fe31-595d-460b-a920-fcc0f8843232}':
Reading manifest: "applications" property ignored and overridden by
"browser_specific_settings"
1716504659092 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232}
WARN Loading extension '{73a6fe31-595d-460b-a920-fcc0f8843232}':
Reading manifest: "applications" property ignored and overridden by
"browser_specific_settings"
SecurityLevel: Listening for messages from NoScript. SecurityLevel.jsm:251
SecurityLevel: Initializing security-prefs.js SecurityLevel.jsm:352
SecurityLevel: security-prefs.js initialization complete
SecurityLevel.jsm:386
TorConnect: init() TorConnect.sys.mjs:866:15
TorConnect: Entering Initial state TorConnect.sys.mjs:197:13
TorConnect: Try transitioning from Initial to Disabled
TorConnect.sys.mjs:835:15
TorConnect: Exited Initial state TorConnect.sys.mjs:202:15
TorConnect: Entering Disabled state TorConnect.sys.mjs:197:13
1716504659709 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232}
WARN Loading extension '{73a6fe31-595d-460b-a920-fcc0f8843232}':
Reading manifest: "applications" property ignored and overridden by
"browser_specific_settings"
TorError: GETINFO circuit-status -> 510 Command filtered
TorControlPort.sys.mjs:316:5
unreachable code after return statement
RemoteWebNavigation.sys.mjs:82:4
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001
(NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]
_collectStartupConditionsTelemetry
resource:///modules/BrowserGlue.sys.mjs:1800
BG__onFirstWindowLoaded resource:///modules/BrowserGlue.sys.mjs:1912
BG_observe resource:///modules/BrowserGlue.sys.mjs:1132
_delayedStartup chrome://browser/content/browser.js:2132
BrowserGlue.sys.mjs:1809:15
Sending message that cannot be cloned. Are you trying to send an XPCOM
object? ConduitsChild.sys.mjs:59:19
holder.deserialize is not a function ExtensionChild.sys.mjs:180
emit resource://gre/modules/ExtensionChild.sys.mjs:180
recvRuntimeMessage resource://gre/modules/ExtensionChild.sys.mjs:383
_recv resource://gre/modules/ConduitsChild.sys.mjs:77
receiveMessage resource://gre/modules/ConduitsChild.sys.mjs:189
Error: Could not get children of
file(/home/user/.tb/tor-browser/Browser/TorBrowser/Data/Browser/profile.default/thumbnails)
because it does not exist PromiseWorker.sys.mjs:102
Sending message that cannot be cloned. Are you trying to send an XPCOM
object? ConduitsChild.sys.mjs:59:19
holder.deserialize is not a function ExtensionChild.sys.mjs:180
emit resource://gre/modules/ExtensionChild.sys.mjs:180
recvRuntimeMessage resource://gre/modules/ExtensionChild.sys.mjs:383
_recv resource://gre/modules/ConduitsChild.sys.mjs:77
receiveMessage resource://gre/modules/ConduitsChild.sys.mjs:189
sendSyncMessage
moz-extension://e0d0f7c7-cbc3-4b22-9a66-308e8d9c05f4/nscl/common/SyncMessage.js:244
refetch
moz-extension://e0d0f7c7-cbc3-4b22-9a66-308e8d9c05f4/content/staticNS.js:124
fetchLikeNoTomorrow
moz-extension://e0d0f7c7-cbc3-4b22-9a66-308e8d9c05f4/content/staticNS.js:139
moz-extension://e0d0f7c7-cbc3-4b22-9a66-308e8d9c05f4/content/syncFetchPolicy.js:223
moz-extension://e0d0f7c7-cbc3-4b22-9a66-308e8d9c05f4/content/syncFetchPolicy.js:227
inject resource://gre/modules/ExtensionContent.sys.mjs:581
AsyncFunctionNext self-hosted:852
HTTPS-Only Mode: Not upgrading insecure request
“http://ocsp.digicert.com/” because it is exempt.
Key event not available on GTK2: key=“u” modifiers=“accel shift”
id=“new-identity-key” browser.xhtml
Key event not available on some keyboard layouts: key=“r”
modifiers=“accel,alt” id=“key_toggleReaderMode” browser.xhtml
Key event not available on some keyboard layouts: key=“i”
modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml
Clipboard changed: private true, hash
TCRjGHOrB210mKKjQ27JGSWpjFTdLyuchLL5a7HkORU=. BrowserGlue.sys.mjs:218:19
-
Regards,
Ulrich
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[qubes-users] qubes-app-menu[70878]: IndexError: list index out of range
Hi!
As the Qubes Template Manager told me there are upgradable templates
available (even though my templates were upgraded/updated in-place), I
downloaded those gigabytes and waited a long time until the templates
were installed (why is that so slow, BTW?)
At the end of that process, the templates were outdated regarding the
current updates (I had installed the updates in my templates before the
manager replaced them), so I ran updates again for all the templates.
As a check, I wanted to run the updater again, an at that moment I
noticed this error in the journal:
May 24 00:25:52 dom0 qubes-app-menu[70878]: Traceback (most recent call
last):
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/updater.py", line 58, in
do_activate
May 24 00:25:52 dom0 qubes-app-menu[70878]: self.perform_setup()
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/updater.py", line 155, in
perform_setup
May 24 00:25:52 dom0 qubes-app-menu[70878]:
self.intro_page.populate_vm_list(self.qapp, self.settings)
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/intro_page.py", line 106,
in populate_vm_list
May 24 00:25:52 dom0 qubes-app-menu[70878]:
self.refresh_update_list(settings.update_if_stale)
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/intro_page.py", line 122,
in refresh_update_list
May 24 00:25:52 dom0 qubes-app-menu[70878]: in
output.decode().split("\n", maxsplit=1)[0]
May 24 00:25:52 dom0 qubes-app-menu[70878]:
^^
May 24 00:25:52 dom0 qubes-app-menu[70878]: IndexError: list index out
of range
May 24 00:25:52 dom0 qubes-app-menu[70878]: Traceback (most recent call
last):
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/updater.py", line 58, in
do_activate
May 24 00:25:52 dom0 qubes-app-menu[70878]: self.perform_setup()
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/updater.py", line 155, in
perform_setup
May 24 00:25:52 dom0 qubes-app-menu[70878]:
self.intro_page.populate_vm_list(self.qapp, self.settings)
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/intro_page.py", line 106,
in populate_vm_list
May 24 00:25:52 dom0 qubes-app-menu[70878]:
self.refresh_update_list(settings.update_if_stale)
May 24 00:25:52 dom0 qubes-app-menu[70878]: File
"/usr/lib/python3.11/site-packages/qui/updater/intro_page.py", line 122,
in refresh_update_list
May 24 00:25:52 dom0 qubes-app-menu[70878]: in
output.decode().split("\n", maxsplit=1)[0]
May 24 00:25:52 dom0 qubes-app-menu[70878]:
^^
May 24 00:25:52 dom0 qubes-app-menu[70878]: IndexError: list index out
of range
And I realized that one of my VMs not uses "qubes-app-menu[70878]:
IndexError: list index out of range" as windows title where there should
be the VM name, I guess.
Kind regards,
Ulrich
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/02d7fea2-126a-4b01-955d-3e5294cee638%40gmail.com.
[qubes-users] Issue with shutdown; is it mdmon@.service?
Hi! I had reported some time ago that Qubes OS hangs quiote some time (1 min 30 sec) on shutdown. It seems some process isn't terminating properly. For some time I noticed this message in the journal: systemd[1]: /usr/lib/systemd/system/mdmon@.service:28: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. Could it be related? I have two Intel Matrix Storage Manager (IMSM) RAIDs on my machine, and one RAID used LVM and an encryped partition that is not used by Qubes OS... Kind regards, Ulrich -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f355ff6c-7be2-40c2-87d0-d907a33de611%40gmail.com.
[qubes-users] Issues with new "Block Device widget
Hi! I discovered two issues with the new widget for block devices in Qubes OS 4.2.1: 1) The icon looks as if "greyed-out", while it seems to be working 2) I have a partitioned USB stick that only worked if the whole device was added to a qube (never investigated what the problem was); however the current widget does no longer have the whole device listed. Instead there are some odd entries (I didn't manage to make a screenshot showing that menu). Kind regards, Ulrich -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4c3913a7-a22c-4813-a59b-f079d19a7a0c%40gmail.com.
[qubes-users] Issues updating qubes (Qubes OS 4.2.1 (R4.2))
Hi! When trying to update qubes today, I had two unexpected issues so far: 1) Whonix Worksattion 17 caused this syslog message: dom0 qubesd[5091]: vm.whonix-workstation-17: Invalid 'os-eol' value '', expected -MM-DD Otherwise the update worked fine. 2) Updating Debian-12 caused thise message: Updating debian-12 Refreshing package info Refreshing packages. Fail to refresh InRelease: https://deb.debian.org/debian bookworm InRelease from https://deb.debian.org/debian/dists/bookworm/InRelease The issue is that the update process just seems to hand indefinitely, even after having pressed "Cancel updates". Also the messages shown in the updater are not "refreshed realtime", so maybe some messages are pending (buffered), but cannot be seen. I don't know whether that can be fixed easily, but it would be nice to see messages as they are created. Kind regards, Ulrich -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d4f6131f-4542-42a4-9354-692c356d85d5%40gmail.com.
