Bug Reports

Running MASQ 0.9.6 on Ubuntu 22.04. I have installed a fresh Ubuntu virtual maschine with vmware and installed the MASQ snap. While the MASQ application is running, the journald is getting spammed with audit messages. Ubuntu-2204-Test:~$ sudo journalctl -f --system août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947871): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13122 comm="VizCompositorTh" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=47 compat=0 ip=0x7f5692f769ef code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947872): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13122 comm="VizCompositorTh" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=44 compat=0 ip=0x7f5692f76aae code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947873): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13106 comm="Chrome_ChildIOT" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=47 compat=0 ip=0x78eaa5ea29ef code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947874): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13106 comm="Chrome_ChildIOT" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=202 compat=0 ip=0x78eaa5e0dfa0 code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947875): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13106 comm="Chrome_ChildIOT" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=232 compat=0 ip=0x78eaa5ea0fde code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947876): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13106 comm="Chrome_ChildIOT" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=232 compat=0 ip=0x78eaa5ea0fde code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947877): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13106 comm="Chrome_ChildIOT" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=232 compat=0 ip=0x78eaa5ea0fde code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947878): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13106 comm="Compositor" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=202 compat=0 ip=0x78eaa5e0c3b7 code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947879): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13122 comm="VizCompositorTh" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=47 compat=0 ip=0x7f5692f769ef code=0x7ffc0000 août 03 15:14:24 Ubuntu-2204-Test kernel: audit: type=1326 audit(1722690864.750:41947880): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.masq.masq pid=13122 comm="VizCompositorTh" exe="/snap/masq/x1/build/app/masq" sig=0 arch=c000003e syscall=7 compat=0 ip=0x7f5692f67d7f code=0x7ffc0000 août 03 15:14:29 Ubuntu-2204-Test kernel: kauditd_printk_skb: 35752 callbacks suppressed I guess there is should be some kind of rule or policy which should be customized for MASQ and delivered with the snap package to prevent the application from spamming the log. To get a feeling how much data is written by the MASQ process, I have used iotop for about 3 minutes and as you can see in the attached screenshot there was written more than 4 MB to journald (there is nothing else running except for MASQ) and the MASQ process itself has written more than 90 MB.

Many IPFS domains aren't being resolved, e.g. .crypto, .nft and .x domains Reproduce: v0.9.6 on Windows In the URL bar type "brad.crypto" You'll notice that https:// is added and you're being mistakenly directed to https://brad.crypto

The keybinds (command +/-) don't do anything, it only happens when you use the menu bar. MASQ v0.9.5 M2 MacBook Air macOS Sonoma 14.0

When resizing the window, the serve and consume window doesn't move with everything else, meaning some information can get cut off if the window is too small. MASQ v0.9.5 M2 MacBook Air macOS Sonoma 14.0

win 10 Why can i right click on the consume/serve panel to change the broswer desktop background. Is there some sort of bleed going on?

I created a script wich helps me to install a systemd service for MASQNode on a Debian Linux VPS. It is working just fine with MASQNode 0.7.3 and when finished, MASQNode 0.7.3 is running as a non-root user. If i try to do the same thing with 0.8.0 beta1, i get this error when i first try to start it with this unit file ===================== [Unit] Description=MASQNode service After=network.target [Service] Type=simple ExecStart=/usr/local/bin/MASQNode --data-directory /home/masq/test1/node-files/ Restart=always RestartSec=5 WorkingDirectory=/home/masq/test1/node-files/ [Install] WantedBy=multi-user.target ===================== _____ ______ ________ ________ _______ Node Version: 0.8.0 / _ | _ /|/ __ /|/ ______/|/ __ /| Database Schema Version: 9 / / /__/// / / /|/ / / /|_____|/ /|_/ / / OS: linux / / |__|// / / __ / /_____ /|/ / '/ / / client_request_payload::MIGRATIONS (0.1) / / / / / / / / / |_____/ / / /__/ / / client_response_payload::MIGRATIONS (0.1) /__/ / /__/ /__/ /__/ /________/ /_____ / / dns_resolve_failure::MIGRATIONS (0.1) |__|/ |__|/|__|/|__|/|________|/|____/__/ / gossip::MIGRATIONS (0.1) |__|/ gossip_failure::MIGRATIONS (0.1) node_record_inner::MIGRATIONS (0.1) 2024-02-06 20:49:20.319 Thd1: ERROR: PanicHandler: src/privilege_drop.rs:83:17 - Attempt to drop group privileges failed: still root 2024-02-06 20:49:20.330 Thd1: ERROR: PanicHandler: 0: <node_lib::server_initializer::LoggerInitializerWrapperReal as node_lib::server_initi alizer::LoggerInitializerWrapper>::init::{{closure}} 1: std::panicking::rust_panic_with_hook at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panicking.rs:702 :17 2: std::panicking::begin_panic_handler::{{closure}} at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panicking.rs:586 :13 3: std::sys_common::backtrace::__rust_end_short_backtrace at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/ backtrace.rs:138 :18 4: rust_begin_unwind at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panicking.rs:584 :5 5: core::panicking::panic_fmt at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/ panicking.rs:142 :14 6: <node_lib::privilege_drop::PrivilegeDropperReal as node_lib::privilege_drop::PrivilegeDropper>::drop_privileges 7: <node_lib::server_initializer::ServerInitializerReal as node_lib::run_modes_factories::ServerInitializer>::go 8: <node_lib::run_modes::RunnerReal as node_lib::run_modes::Runner>::run_node 9: node_lib::run_modes::RunModes::go 10: node_lib::sub_lib::main_tools::main_with_args 11: MASQNode::main 12: std::sys_common::backtrace::__rust_begin_short_backtrace 13: std::rt::lang_start::{{closure}} 14: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/ops/ function.rs:280 :13 std::panicking::try::do_call at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panicking.rs:492 :40 std::panicking::try at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panicking.rs:456 :19 std::panic::catch_unwind at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panic.rs:137 :14 std::rt::lang_start_internal::{{closure}} at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ rt.rs:128 :48 std::panicking::try::do_call at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panicking.rs:492 :40 std::panicking::try at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panicking.rs:456 :19 std::panic::catch_unwind at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ panic.rs:137 :14 std::rt::lang_start_internal at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/ rt.rs:128 :20 15: main 16: <unknown> 17: __libc_start_main 18: _start ========================== the config.toml that is used looks like that (variables are replaced when it is written by the script): real-user="${REALUSER}" dns-servers="${DNS_SERVERS}" db-password="${DB_PASSWD}" chain="${CHAIN}" clandestine-port="${CLANDESTINE_PORT}" log-level="${LOG_LEVEL}" blockchain-service-url="${BLOCKCHAIN_SERVICE_URL}" neighborhood-mode="zero-hop" gas-price="50" ========================== note: after configuration is done, there will be used a more complete config.toml, but it crashes with the privilege drop error here already.

In this case Reddit. Maybe a user-agent problem.

metamask was logged out now needs seed phrase but does not add. also, the tabs dont save when you log back in

OS: EndeavourOS Linux x86_64 Kernel: 6.6.6-arch1-1 Packages: 1811 (pacman), 1 (dpkg), 6 (flatpak) Shell: zsh 5.9 CPU: AMD Ryzen 9 5900X (24) @ 3.700GHz GPU: AMD ATI Radeon RX 6600/6600 XT/6600M Memory: 11134MiB / 32015MiB Steps to reproduce: Install masq. If you dont connect masq:alsa startup should work normally connect masq:alsa on first startup Node should fail to start and connect * Notes This happens after you connect masq:alsa. even if you have successfully started up prior. for e.g., if you have say installed the browser, and have not connected masq:alsa, and used the browser N amount of times. Even after that, connecting masq:alsa causes startup failure.