| 2023-08-30 02:13:47 +0000 | hightower4 | (~hightower@141-136-175-225.dsl.iskon.hr) |
| 2023-08-30 02:16:31 +0000 | hightower3 | (~hightower@141-136-157-92.dsl.iskon.hr) (Ping timeout: 258 seconds) |
| 2023-08-30 02:37:47 +0000 | td_ | (~td@i5387092A.versanet.de) (Ping timeout: 246 seconds) |
| 2023-08-30 02:39:35 +0000 | td_ | (~td@i53870918.versanet.de) |
| 2023-08-30 03:44:23 +0000 | gauge | (~gauge@user/gauge) (Read error: Connection reset by peer) |
| 2023-08-30 03:44:49 +0000 | gauge | (~gauge@user/gauge) |
| 2023-08-30 04:18:46 +0000 | amenonsen | (~amenonsen@pitta.toroid.org) (Remote host closed the connection) |
| 2023-08-30 04:19:08 +0000 | amenonsen | (~amenonsen@pitta.toroid.org) |
| 2023-08-30 04:24:10 +0000 | gauge | (~gauge@user/gauge) (Quit: Quitting) |
| 2023-08-30 04:24:59 +0000 | gauge | (~gauge@user/gauge) |
| 2023-08-30 04:26:41 +0000 | gauge | (~gauge@user/gauge) (Read error: Connection reset by peer) |
| 2023-08-30 04:30:17 +0000 | redgloboli | (~redglobol@user/redgloboli) |
| 2023-08-30 04:30:39 +0000 | gauge | (~gauge@user/gauge) |
| 2023-08-30 05:46:14 +0000 | [Leary] | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2023-08-30 05:46:32 +0000 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2023-08-30 05:57:56 +0000 | td_ | (~td@i53870918.versanet.de) (Quit: waking up from the american dream ...) |
| 2023-08-30 06:20:09 +0000 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) (Quit: done!) |
| 2023-08-30 06:52:55 +0000 | td_ | (~td@i5387090D.versanet.de) |
| 2023-08-30 07:58:18 +0000 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-08-30 08:20:17 +0000 | tv | (~tv@user/tv) (Read error: Connection reset by peer) |
| 2023-08-30 08:36:12 +0000 | tv | (~tv@user/tv) |
| 2023-08-30 09:16:14 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2023-08-30 09:36:03 +0000 | T_X_ | (~T_X@diktynna.open-mesh.org) |
| 2023-08-30 09:36:29 +0000 | T_X | (~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer) |
| 2023-08-30 09:58:35 +0000 | ft | (~ft@p508db658.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-08-30 10:06:10 +0000 | cfricke | (~cfricke@user/cfricke) (Ping timeout: 255 seconds) |
| 2023-08-30 11:36:43 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2023-08-30 11:37:31 +0000 | tv | (~tv@user/tv) (Ping timeout: 255 seconds) |
| 2023-08-30 11:52:07 +0000 | tv | (~tv@user/tv) |
| 2023-08-30 13:16:56 +0000 | thunderrd | (~thunderrd@183.182.114.166) (Remote host closed the connection) |
| 2023-08-30 14:17:08 +0000 | tv | (~tv@user/tv) (Ping timeout: 246 seconds) |
| 2023-08-30 14:18:23 +0000 | thyriaen | (~thyriaen@2a01:aea0:dd4:6de3:6245:cbff:fe9f:48b1) |
| 2023-08-30 14:30:20 +0000 | <thyriaen> | geekosaur, i only really want to have 2 config files for desktop and laptop |
| 2023-08-30 14:30:35 +0000 | <thyriaen> | and only have some values replaced -- this is something i would do with a preprocessor |
| 2023-08-30 14:30:47 +0000 | <thyriaen> | is there a more elegant solution how it should be done ? |
| 2023-08-30 14:31:07 +0000 | tv | (~tv@user/tv) |
| 2023-08-30 14:38:02 +0000 | thyriaen | (~thyriaen@2a01:aea0:dd4:6de3:6245:cbff:fe9f:48b1) (Quit: Leaving) |
| 2023-08-30 14:41:04 +0000 | thyriaen | (~thyriaen@2a01:aea0:dd4:6de3:6245:cbff:fe9f:48b1) |
| 2023-08-30 14:44:52 +0000 | <geekosaur> | the problem with a preprocessor is you will need a build script to tell it what to do |
| 2023-08-30 14:45:14 +0000 | <geekosaur> | you might look into template haskell instead |
| 2023-08-30 14:45:48 +0000 | <[Leary]> | I suggest something like `data Host = LaptopHostname | DesktopHostname | Other; main = do { host <- parseHost <$> readProcess "hostname" [] ""; xmonad (buildConfig host) }`. |
| 2023-08-30 14:46:10 +0000 | <[Leary]> | There's just no need for a preprocessor or template haskell here. Ordinary Haskell will do. |
| 2023-08-30 14:46:12 +0000 | <geekosaur> | there is alaso that |
| 2023-08-30 14:52:55 +0000 | <geekosaur> | do remember that your config is a program, you can look things up and change behavior however you wish |
| 2023-08-30 15:14:05 +0000 | <thyriaen> | [Leary] my mind is blown |
| 2023-08-30 15:14:27 +0000 | <thyriaen> | however it will be too complicated for me i think |
| 2023-08-30 15:14:39 +0000 | <geekosaur> | huh? |
| 2023-08-30 15:15:07 +0000 | <geekosaur> | it's surely better than TH and almost certainly easier than maintaining a buildscript to set defines for a preprocessor |
| 2023-08-30 15:30:41 +0000 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 4.0.4) |
| 2023-08-30 15:44:26 +0000 | thyriaen | (~thyriaen@2a01:aea0:dd4:6de3:6245:cbff:fe9f:48b1) (Remote host closed the connection) |
| 2023-08-30 16:42:11 +0000 | ml| | (~ml|@user/ml/x-5298235) (Ping timeout: 260 seconds) |
| 2023-08-30 16:56:20 +0000 | ml| | (~ml|@user/ml/x-5298235) |
| 2023-08-30 17:02:23 +0000 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2023-08-30 18:27:00 +0000 | jeeeun8 | (~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat) |
| 2023-08-30 18:30:30 +0000 | jeeeun8 | (~jeeeun@78.40.148.178) |
| 2023-08-30 19:25:31 +0000 | ft | (~ft@p508db658.dip0.t-ipconnect.de) |
| 2023-08-30 19:55:33 +0000 | bear34 | (~bear@c-76-131-115-3.hsd1.co.comcast.net) |
| 2023-08-30 19:57:42 +0000 | <bear34> | hey folks, i'm running into issues when booting into xmonad where things like firefox don't start for up to 30 seconds. journalctl shows an error like this: |
| 2023-08-30 19:57:44 +0000 | <bear34> | Aug 30 13:38:58 linux xdg-desktop-por[3337]: Failed to create secret proxy: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached |
| 2023-08-30 19:58:14 +0000 | <bear34> | I'm guessing xmonad isn't starting some of the regular sevices that get started if i boot into PopOS, but i cant' for the life of me figure out how to make sure some of these things are started so that stuff "just works" |
| 2023-08-30 20:10:22 +0000 | <geekosaur> | usually you just need to wrap whatever's starting xmonad for you in dbus-launch |
| 2023-08-30 20:10:43 +0000 | bear34 | (~bear@c-76-131-115-3.hsd1.co.comcast.net) (Quit: Client closed) |
| 2023-08-30 23:03:07 +0000 | Guest26 | (~Guest26@c-76-131-115-3.hsd1.co.comcast.net) |
| 2023-08-30 23:10:49 +0000 | Guest26 | (~Guest26@c-76-131-115-3.hsd1.co.comcast.net) (Quit: Client closed) |
| 2023-08-30 23:14:01 +0000 | bear34 | (~bear34@c-76-131-115-3.hsd1.co.comcast.net) |
| 2023-08-30 23:14:11 +0000 | <bear34> | geekosaur: i actually did this already |
| 2023-08-30 23:14:48 +0000 | <bear34> | there seems to be a bug in xdg-desktop-portal: https://github.com/flatpak/xdg-desktop-portal/pull/985 |
| 2023-08-30 23:15:08 +0000 | <bear34> | https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/74 |
| 2023-08-30 23:15:26 +0000 | <bear34> | apparently something is way broken, cause lots of people are having issues loading programs |
| 2023-08-30 23:15:38 +0000 | <bear34> | what i don't understand is how this isn't breaking when i boot into popos instead of xmonad |
| 2023-08-30 23:16:34 +0000 | <bear34> | i have a /usr/share/xsessions/smonad.desktop file and it contains this: |
| 2023-08-30 23:16:36 +0000 | <bear34> | Exec=dbus-launch --exit-with-session xmonad |
| 2023-08-30 23:16:47 +0000 | <bear34> | (before, the last part was xmonad-session |
| 2023-08-30 23:17:08 +0000 | <bear34> | i'm so not an expert, but currently i can't launch most programs, they hang for upwards of 10 minutes because of this bug it seems |
| 2023-08-30 23:17:40 +0000 | <bear34> | https://bbs.archlinux.org/viewtopic.php?id=285590 |
| 2023-08-30 23:17:54 +0000 | <bear34> | everyone is suggesting removing xdg-desktop-portal-gnome, but i can't because it's a popos dependency |
| 2023-08-30 23:18:00 +0000 | <geekosaur> | I presume popos runs a mutter (gnome) desktop |
| 2023-08-30 23:18:10 +0000 | <geekosaur> | that's pretty much the default on any linux these days |
| 2023-08-30 23:18:35 +0000 | <bear34> | yeah that's right |
| 2023-08-30 23:18:47 +0000 | <bear34> | they've fixed it in xdg-desktop-portal 1.16, but popos is on 1.14 |
| 2023-08-30 23:19:00 +0000 | <bear34> | am i just hosed? (again though, no idea how it works correctly when logging in to pop) |
| 2023-08-30 23:19:38 +0000 | <geekosaur> | "featuring a customized GNOME desktop environment known as COSMIC" |
| 2023-08-30 23:19:54 +0000 | <geekosaur> | yes, I think you're stuck until popos upgrades |
| 2023-08-30 23:21:16 +0000 | <bear34> | i'd try rocking arch but everyone i know complains about things breaking all the time |
| 2023-08-30 23:21:17 +0000 | <geekosaur> | or you can do something like moving the system package executable out of the way and replacing it with a symlink to /bin/true |
| 2023-08-30 23:21:20 +0000 | <bear34> | no idea if that's fair though |
| 2023-08-30 23:21:55 +0000 | <bear34> | why would this work on popos? you'd think if xdg-desktop-portal was broken it'd break there too, but it doesn't |
| 2023-08-30 23:22:08 +0000 | <bear34> | perhaps there's something else i need to initialize? |
| 2023-08-30 23:23:35 +0000 | <geekosaur> | it's trying to talk to mutter, which is gnome's window/desktop/file/everything else manager |
| 2023-08-30 23:25:01 +0000 | <bear34> | doesn't it do that through the xdg-desktop-portal-gnome provider |
| 2023-08-30 23:27:57 +0000 | <geekosaur[c]> | Which is what is timing out |
| 2023-08-30 23:29:27 +0000 | <geekosaur[c]> | And there is no xdg-desktop-portal-xmonad provider, nor would it help since it doesn't try anything else until the gnome one times out |
| 2023-08-30 23:29:32 +0000 | <bear34> | apologies for my naivete - why doesn't the same thing happen on popos proper? |
| 2023-08-30 23:29:51 +0000 | <bear34> | that is, why doesn't it time out |
| 2023-08-30 23:30:21 +0000 | <geekosaur[c]> | See my quote above. Pop!OS uses a customized gnome |
| 2023-08-30 23:30:50 +0000 | <geekosaur[c]> | So the gnome provider can connect |
| 2023-08-30 23:31:13 +0000 | <bear34> | _sigh_ |
| 2023-08-30 23:31:37 +0000 | <bear34> | it seems one of the providers must work eh |
| 2023-08-30 23:31:45 +0000 | vanvik | (~vanvik@78.156.11.181) (Ping timeout: 244 seconds) |
| 2023-08-30 23:31:46 +0000 | <bear34> | because eventually firefox opens |
| 2023-08-30 23:31:50 +0000 | <bear34> | like 30 seconds later |
| 2023-08-30 23:32:19 +0000 | <geekosaur[c]> | No, it just eventually times out and continues |
| 2023-08-30 23:32:29 +0000 | <bear34> | oh |
| 2023-08-30 23:32:40 +0000 | <bear34> | like DataGrip hangs for 30 seconds, then fails to authenticate |
| 2023-08-30 23:32:54 +0000 | <bear34> | i think b/c it's trying to store / retrieve a password in the secret daemon |
| 2023-08-30 23:32:57 +0000 | <bear34> | which times out |
| 2023-08-30 23:34:57 +0000 | <geekosaur[c]> | That one would be harder unless it works to start gnome-keyring-daemon --daemonize --login |
| 2023-08-30 23:35:37 +0000 | <geekosaur[c]> | Which is what my mate session is running but I don't have this portal stuff |
| 2023-08-30 23:39:48 +0000 | vanvik | (~vanvik@78.156.11.181) |
| 2023-08-30 23:53:00 +0000 | bear34 | (~bear34@c-76-131-115-3.hsd1.co.comcast.net) (Quit: Client closed) |