2023/04/10

2023-04-10 01:12:19 +0200catman(~catman@user/catman)
2023-04-10 01:28:13 +0200catman(~catman@user/catman) (Ping timeout: 276 seconds)
2023-04-10 02:09:10 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca)
2023-04-10 02:10:18 +0200hightower3(~hightower@249-144.dsl.iskon.hr) (Remote host closed the connection)
2023-04-10 02:10:40 +0200hightower3(~hightower@249-144.dsl.iskon.hr)
2023-04-10 02:10:58 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Remote host closed the connection)
2023-04-10 02:11:38 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca)
2023-04-10 03:41:47 +0200hightower3(~hightower@249-144.dsl.iskon.hr) (Read error: Connection reset by peer)
2023-04-10 03:43:11 +0200hightower3(~hightower@141-138-50-69.dsl.iskon.hr)
2023-04-10 04:18:31 +0200td_(~td@i5387091C.versanet.de) (Ping timeout: 276 seconds)
2023-04-10 04:19:38 +0200td_(~td@i53870914.versanet.de)
2023-04-10 04:32:33 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Read error: Connection reset by peer)
2023-04-10 04:37:29 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca)
2023-04-10 05:31:17 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Ping timeout: 246 seconds)
2023-04-10 09:54:00 +0200hightower3(~hightower@141-138-50-69.dsl.iskon.hr) (Read error: Connection reset by peer)
2023-04-10 10:01:54 +0200Maeda(~Maeda@91-161-10-149.subs.proxad.net) (Quit: o/)
2023-04-10 10:55:44 +0200c0c0(~coco@212-51-146-137.fiber7.init7.net)
2023-04-10 16:54:50 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-04-10 17:16:00 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de)
2023-04-10 18:05:09 +0200jchia[m](~jchiamatr@2001:470:69fc:105::c50b)
2023-04-10 20:05:35 +0200ikci(~ikci@79.184.236.186.ipv4.supernova.orange.pl)
2023-04-10 20:20:13 +0200exordiri_exordiri
2023-04-10 20:29:51 +0200gdd(~gdd@2001:470:1f13:187:1478:b52c:44e2:14d6) (Ping timeout: 260 seconds)
2023-04-10 20:31:44 +0200gdd(~gdd@129.199.146.230)
2023-04-10 21:34:59 +0200c0c0(~coco@212-51-146-137.fiber7.init7.net) (Quit: WeeChat 3.7.1)
2023-04-10 21:37:39 +0200hrberg(~quassel@171.79-160-161.customer.lyse.net) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2023-04-10 21:37:58 +0200hrberg(~quassel@171.79-160-161.customer.lyse.net)
2023-04-10 22:00:00 +0200ikci(~ikci@79.184.236.186.ipv4.supernova.orange.pl) (Quit: Client closed)
2023-04-10 22:50:29 +0200horzion(~horzion@ProtonDB/horzion)
2023-04-10 22:52:41 +0200 <horzion> i am trying to figure out and fix why discord is crashing everytime i am being mentioned. i am almost certain it has to do with that a notification appears in that case, but i dont know the fix. i know that i had a similar issue on kde before
2023-04-10 22:52:54 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-10 22:53:08 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-10 22:54:03 +0200 <geekosaur> is there a notification daemon running?
2023-04-10 23:05:29 +0200 <horzion> how would i tell?
2023-04-10 23:05:57 +0200 <geekosaur> if you don't know, you probably aren't
2023-04-10 23:06:29 +0200 <horzion> then maybe thats the issue? that discord tries to reach one?
2023-04-10 23:06:33 +0200 <geekosaur> but you should be able to run `notify-send hi` and get a notification window
2023-04-10 23:06:39 +0200 <horzion> ok
2023-04-10 23:06:49 +0200 <geekosaur> if you aren't, dunst is a common one for use with xmonad
2023-04-10 23:07:04 +0200 <horzion> yeah i didnt get anything
2023-04-10 23:07:17 +0200 <horzion> i will read into it, thank you. will report back
2023-04-10 23:24:33 +0200 <horzion> yup
2023-04-10 23:24:39 +0200 <horzion> that did the trick, thank you