Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2024-06-09

00:27:48 Quit massiveH (Quit: Leaving)
01:21:15***Saving seen data "./dancer.seen"
01:57:57 Quit hactar|ant (Read error: Connection reset by peer)
01:58:21 Join hactar|ant [0] (~zem@
03:21:19***Saving seen data "./dancer.seen"
04:06:39 Quit PheralSparky (Quit: Leaving)
04:34:21 Quit CH23[m] (Read error: Connection reset by peer)
04:36:15 Join CH23[m] [0] (~CH23@revspace/participant/ch23)
04:56:49 Join dnickc [0] (
05:11:31 Quit CH23[m] (Ping timeout: 272 seconds)
05:12:38 Join CH23[m] [0] (~CH23@revspace/participant/ch23)
05:21:23***Saving seen data "./dancer.seen"
05:41:40 Quit dnickc (Ping timeout: 246 seconds)
06:03:27 Quit CH23[m] (Ping timeout: 272 seconds)
06:05:00 Join CH23[m] [0] (~CH23@revspace/participant/ch23)
06:13:07 Quit danwellby (Quit: Watch out For sysops carrying carpet and quicklime)
06:23:23 Quit CH23[m] (Read error: Connection reset by peer)
06:23:43 Join CH23[m] [0] (~CH23@revspace/participant/ch23)
06:25:54 Quit wLLm (Quit: ZNC -
06:27:13 Join danwellby [0] (
06:59:55 Join dnickc [0] (
07:21:24***Saving seen data "./dancer.seen"
07:28:29 Quit CH23 (Ping timeout: 240 seconds)
07:32:45 Quit dnickc (Ping timeout: 256 seconds)
07:52:29 Quit CH23[m] (Ping timeout: 240 seconds)
07:53:26 Join CH23[m] [0] (~CH23@revspace/participant/ch23)
07:54:33 Quit CH23[m] (Client Quit)
09:04:14rb-bluebotBuild Server message: New build round started. Revision 8c6b579b32, 304 builds, 9 clients.
09:04:14rb-bluebotFS #13435: Update Polish Translation (Adam Rak) by Solomon Peachy
09:12:39rb-bluebotBuild Server message: Build round completed after 505 seconds.
09:12:40rb-bluebotBuild Server message: Revision 8c6b579b32 result: All green
09:21:28***Saving seen data "./dancer.seen"
11:21:32***No seen item changed, no save performed.
12:30:48 Join CH23 [0] (~CH23@revspace/participant/ch23)
12:36:52 Join munkis [0] (
12:56:24 Join othello7 [0] (
12:58:22 Quit othello7 (Client Quit)
13:21:35***Saving seen data "./dancer.seen"
15:21:38***No seen item changed, no save performed.
15:44:35 Quit chamlis (Remote host closed the connection)
15:44:49 Join chamlis [0] (~chamlis@user/chamlis)
16:48:53 Join dnickc [0] (
16:51:19 Quit dnickc (Remote host closed the connection)
16:51:43 Join dnickc [0] (
17:15:00 Join jacobk [0] (~quassel@2600:1700:9e1e:7800:c40c:5464:17f4:498c)
17:21:39***Saving seen data "./dancer.seen"
17:28:11 Quit dnickc (Ping timeout: 264 seconds)
17:45:16 Join wLLm [0] (~wLLm@2a10:3781:3ed0::3)
17:56:26 Quit CH23 (Ping timeout: 252 seconds)
18:03:32 Quit jacobk (Quit: - Chat comfortably. Anywhere.)
18:33:59 Join CH23 [0] (~CH23@revspace/participant/ch23)
19:07:40 Join massiveH [0] (~massiveH@2600:4040:a982:c800:f1b3:d937:3f58:19f8)
19:19:22speachysweet, we now have two folks who agreed to be language maintainers. :D
19:21:42***Saving seen data "./dancer.seen"
21:21:45***No seen item changed, no save performed.
22:53:40 Quit massiveH (Quit: Leaving)
23:21:47***Saving seen data "./dancer.seen"
23:32:13 Join dconrad [0] (~dconrad@
23:33:45dconradOk, I've got some bizarro-world behavior hopefully someone smarter than me can make heads or tails of... The line-out detection on the erosq native does indeed seem to be broken. But the symptoms don't make any damn sense:
23:35:39dconrad1) Line-out detection seems to be some sort of electrical detection, whereas headphone detection seems to be mechanical (I added some log statements to detect this... my unit's hp out is worn enough it needs to be pushed in a certain direction to detect it. not a problem due to this being the default)
23:37:02dconrad2) Line-out detection always works at boot, even with an aux-in cable which is not plugged into anything on the other end attached to the LO port
23:38:29dconrad3) /Removal/ of something plugged into the line-out port is always detected.
23:40:33dconrad4) If I plug a headphone extension into the line-out port, I can connect some headphones electrically, remotely, and it detects this.
23:43:44dconrad5) If I then remove the headphones from the headphone extension, it continues to say that it has detected the line-out
23:44:07dconrad(that is to say, it does /not/ detect the removal of the headphones)
23:44:58dconradSo I am... utterly baffled, and frustrated that these symptoms don't even line up to if it's a hardware or software problem
23:52:10dconradSo whatever we're doing at boot to detect the line-out port state needs to be repeated as a poll, i guess? Not sure why it's different though
23:53:21dconradAnd why can we reliably detect removal of the line-out port? That throws a wrench into the works
23:53:52dconrad(sorry for the spam everybody, but I could really use a second/third/fourth opinion)
23:55:15dconradanyway, let that stew and I'll check the logs tomorrow. G'night
23:55:35 Quit dconrad ()

Previous day | Next day