endeavouros-community-editions / sway Goto Github PK

Android devices does not connect and doesnt show in file managers. i tried installing adb but it still did not show in file explorer, so i tried it in terminal. i can access the device through terminal but only in read mode (idk of this is eos issue or not). i tried the fixes in community forum still not fixed.

Seems like pamixer is not installed out of the box.

The weather custom Waybar module seems broken, as spotted in #22.

I don't entirely understand how Waybar's modules works, but the weather.sh script takes argument but I don't see any arg passed from the Waybar config.

in /.config/waybar/config

"backlight#icon": { 
"format": "{icon}",    	
"format-icons": [""],    	
"on-scroll-down": "brightnessctl -c backlight set 5%",
"on-scroll-up": "brightnessctl -c backlight set +5%-"
},

"backlight#value" :{ "format": "{percent}%",
"on-scroll-down": "brightnessctl -c backlight set 5%", 
"on-scroll-up": "brightnessctl -c backlight set +5%"
}

Right now scrolling down set the brightness levels at 5%
"on-scroll-down": "brightnessctl -c backlight set 5%-"
"on-scroll-up": "brightnessctl -c backlight set +5%"
gives scrolling on the brightness the intended effect.

I saw in the README that you are looking for new contributors but there are no open issues so I'm not entirely sure where to start. A bit of guidance would be helpful! I'm a big fan of the project and would love to help however I can.

After changing the config for sway (only changed scratchpad's minus to z and the variable name for the terminal to $term), waybar would close shortly after loading the config. I thought by reverting everything to the default, it'd stay open, which did seem to work at first, but it never really stayed. I even put in the setup I had for a floating urxvt terminal, which did work, but when I opened it, waybar would close then and there. I thought it was just that it didn't like the for_window argument.

The one way I can get it to stay open is by clicking on any of the objects/shortcuts on the right side. At first I thought it was the tooltips, but that never seemed to work 100%.

If possible, I'd like to see if waybar generates any crash logs, or if there's be a way to log it. I'm also wondering if it's stability is very dependent on whats in the various configs.

Hi. I've noticed that we export some flags in ~/.profile. For example to launch firefox using wayland. Problem is, for me anyway that it does not work. As far as I know arch is looking for .bash_profile, .bash_login, and .profile in that order. So if it finds .bash_login it does not read .profile file.

I noticed this behaviour when firefox was not scaling well on my hidpi display. Blurry UI and fonts. I checked and it was running on xwayland instead of wayland. I fixed it by exporting MOZ_ENABLE_WAYLAND=1 in the .bash_profile file instead of .profile.

Please correct me if I'm wrong and commands in .profile are executed and this is some weird bug.

Hello!

I was just wondering is this is possible to install on another distro, I'm using Fedora. I think the only thing I would need to change is maybe the package name in the text file, but I'm not exactly sure?

Hi,

When I try to fully restart sway by logout and relogin, I get a black screen and about after 2 minutes, lightdm login prompt appears. If I try to open a tty with ctrl alt f4, I can login nornally, and by exec sway I can get the system work again.

What am I missing here?

Thanks

i need offline iso, could anyone help me please? Thanks.

Termbin: http://termbin.com/3j96

2022-09-02 - 16:10:19 [6]:     .. Running ("pacman", "-S", "--noconfirm", "--noprogressbar", "--needed", "--disable-download-timeout", "libwnck3", "mesa-utils", "xf86-input-libinput", "xorg-xdpyinfo", "xorg-server", "xorg-xinit", "xorg-xinput", "xorg-xkill", "xorg-xrandr", "xf86-video-amdgpu", "xf86-video-ati", "xf86-video-intel", "b43-fwcutter", "broadcom-wl-dkms", "dhclient", "dialog", "dnsmasq", "dnsutils", "ethtool", "gnu-netcat", "ipw2100-fw", "ipw2200-fw", "iwd", "modemmanager", "nbd", "ndisc6", "networkmanager", "networkmanager-openvpn", "nmap", "nss-mdns", "openconnect", "openvpn", "ppp", "pptpclient", "rp-pppoe", "sshfs", "usb_modeswitch", "vpnc", "whois", "wireless-regdb", "wireless_tools", "wpa_supplicant", "xl2tpd", "firewalld", "python-pyqt5", "python-capng", "downgrade", "pacman-contrib", "pkgfile", "rebuild-detector", "reflector", "yay", "accountsservice", "bash-completion", "bluez", "bluez-utils", "ffmpegthumbnailer", "gst-libav", "gst-plugin-pipewire", "gst-plugins-bad", "gst-plugins-ugly", "libdvdcss", "libgsf", "libopenraw", "mlocate", "poppler-glib", "xdg-user-dirs", "xdg-utils", "efitools", "haveged", "nfs-utils", "nilfs-utils", "ntp", "smartmontools", "unrar", "unzip", "xz", "adobe-source-han-sans-cn-fonts", "adobe-source-han-sans-jp-fonts", "adobe-source-han-sans-kr-fonts", "cantarell-fonts", "freetype2", "noto-fonts", "ttf-bitstream-vera", "ttf-dejavu", "ttf-liberation", "ttf-opensans", "alsa-firmware", "alsa-plugins", "alsa-utils", "pavucontrol", "pipewire-pulse", "wireplumber", "pipewire-alsa", "pipewire-jack", "rtkit", "amd-ucode", "dmidecode", "dmraid", "hdparm", "hwdetect", "intel-ucode", "lsscsi", "mtools", "sg3_utils", "sof-firmware", "power-profiles-daemon", "upower", "endeavouros-theming", "eos-apps-info", "eos-hooks", "eos-log-tool", "eos-packagelist", "eos-quickstart", "eos-rankmirrors", "eos-update-notifier", "grub-tools", "reflector-simple", "welcome", "yad-eos", "duf", "findutils", "fsarchiver", "git", "glances", "hwinfo", "inxi", "meld", "nano-syntax-highlighting", "neofetch", "pv", "python-defusedxml", "python-packaging", "rsync", "tldr", "sed", "vi", "wget", "linux-zen", "linux-zen-headers", "acpi", "arc-gtk-theme-eos", "archlinux-xdg-menu", "boost-libs", "brightnessctl", "dex", "diffuse", "egl-wayland", "endeavouros-xfce4-terminal-colors", "eos-qogir-icons", "eos-sddm-theme", "eos-skel-ce-sway", "file-roller", "grim", "gtk-engine-murrine", "gtk-layer-shell", "htop", "imv", "jq", "lxappearance", "mako", "network-manager-applet", "oniguruma", "awesome-terminal-fonts", "polkit-gnome", "qt6-wayland", "slurp", "sway", "swaybg", "swayidle", "swaylock", "sysstat", "thunar", "thunar-archive-plugin", "thunar-media-tags-plugin", "thunar-volman", "ttf-jetbrains-mono", "ttf-nerd-fonts-symbols", "ttf-ubuntu-font-family", "waybar", "wayland-protocols", "wl-clipboard", "wofi", "xdg-desktop-portal-wlr", "xed", "xfce4-terminal", "xorg-xhost", "xorg-xwayland") 
2022-09-02 - 16:10:19 [6]: [PYTHON JOB]: "warning: xz-5.2.6-1 is up to date -- skipping" 
2022-09-02 - 16:10:19 [6]: [PYTHON JOB]: "warning: freetype2-2.12.1-1 is up to date -- skipping" 
2022-09-02 - 16:10:19 [6]: [PYTHON JOB]: "warning: findutils-4.9.0-1 is up to date -- skipping" 
2022-09-02 - 16:10:19 [6]: [PYTHON JOB]: "warning: sed-4.8-1 is up to date -- skipping" 
2022-09-02 - 16:10:19 [6]: [PYTHON JOB]: "error: target not found: ttf-nerd-fonts-symbols" 

I just installed EndeavourOS yesterday (and pre-installed Sway along with it). I decided to copy the config file of Sway like what the Sway wiki said in order to edit the config file (https://github.com/swaywm/sway/wiki). Today, everything somehow reseted back to the normal config, abd I'm unable to open anything. Help?

for trush and volume manager, we need gvfs and friends in file manager.

Open Terminal Here not working in file manager

I install i3 as my WM first, then I follow the README git clone and bash sway-install.sh, logout or reboot, choose sway from the bar, type the password and enter, but fail to login into the desktop, choose the i3 again, it works OK.

BTW:

I'm trying it in VirtualBox

I must admit I do not even know what login manager is being used, all I can do is describe the problem at this point;

I run a 4k screen on my laptop. Scaling works near perfect everywhere out of the box. Except for in the login manager where there seems to be no scaling at all (1x). This doesn't look too sexy.

Once I login, sway perfectly scales for my monitor.

Edit: obviously this is not a major issue and all functionality is still in place!

Package Manager error occurred when I installed

termbin

I installed the system about two weeks ago. My problem is that the system for the second day after coming out of suspend mode does not respond to keyboard presses, TTY change does not work either. I only see the lock menu on the screen. I tried to reproduce the problem manually but it does not work. I put the system to suspend before going to sleep and then resume in the morning. My hardware is a Dell latitude 3510 laptop, i5 10210u, it has no video card other than the integrated one. My system has a swap partition (8gb), btrfs file system and encryption enabled. I manually checked suspend, hybrid-sleep, hibernation and suspend then hibernation via systemctl. There is no problem with resuming the laptop.

Upon install, both a ~/.bash_profile and ~/.profile were created, which caused bash to ignore ~/.profile and the environment variables inside.
Deleting ~/.bash_profile resolved the issue.

From the bash man page:

it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable.

I think this is a bug in this line in the config:

Hi, can you please switch from pulseaudio to pipewire?

lockman.sh is using swayidle, which is set to turn off screen after 5 seconds. Doing this overrides the initial swayidle timeouts that is run once on startup from sway/script/default

I think networkmanager tui and networkmanager applet are not needed together in installation.

I am filing this as a bug of this edition of EndeavourOS because I am not sure what else could be the result of this. Essentially, the version of endeavourOS I use is this one. I have not checked if this applies to other versions for me as that would take quite a lot of time, and if you don't think that this could be contingent to this version, I can move this post elsewhere. However inexplicably, after about 3-5 days of use whenever I use this edition of EndeavourOS, the ethernet stop being recognized entirely. I have got it working again a few times after forum post scrawling, but it is just weird this one specific things randomly breaks after the same amount of time on fresh installs of this distro.

for android studio show blank screen and window, we need add to ~/.profile that:

if [ "$XDG_SESSION_DESKTOP" = "sway" ] ; then
export _JAVA_AWT_WM_NONREPARENTING=1
fi

Per https://forum.endeavouros.com/t/shutdown-hangs-at-stop-job-for-simple-desktop-display-manager/37627, it seems that the upstream version of sddm (aur/sddm-git) fixed the issue, so it should be installed by default instead

I had a problem on my install that I could not do screensharing in Firefox and Chromium, despite setting all the env vars launch arguments and about:configs and chrome://flags that I could find, in several places on my machine.

When going through the excellent xdg-desktop-portal-wlr troubleshooting guide, I found out that there was a problem with the xdg-desktop-portal. Instead of just exporting the XDG_CURRENT_DESKTOP env var, we need to explicitly pass it along to the systemd and dbus environments.

#52 fixes this