profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/grigorig/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

grigorig/stcgal 393

Open Source STC MCU ISP flash tool

grigorig/chachapoly 17

RFC 7539 compliant ChaCha20-Poly1305 AEAD implementation in plain C99

grigorig/android_packages_apps_Effem 8

FM radio app for CyanogenMod

grigorig/mittagv2 2

Automated lunch selection for Lübeck Hochschulstadtteil

grigorig/android_device_zte_blade 0

CyanogenMod device config

grigorig/android_system_netd 0

Android network daemon

grigorig/ch341-linux 0

notes on adding parity control to ch341 linux usb serial driver

grigorig/dnsfilexfer 0

File transfer via DNS

issue commentmicrosoft/vscode

mouse cursor get shifted when enabling wayland support

I suppose this is an Electron issue? I couldn't find anything in the Electron issue tracker though. Anyone got any idea what's going on? Does Chrome/Chromium 89 (which Electron 12 is based on) have similar issues under Wayland?

500InternalError

comment created time in a day

push eventgrigorig/mutter-performance

Grigori Goronzy

commit sha 78cff28a23588c5cb2574112416a68b9cd281cd6

Add !1762

view details

push time in 4 days

push eventgrigorig/gnome-shell-performance

Florian Müllner

commit sha f74a0b0086cbfcf37f98ae9c64dc59a474a45d8a

Mark bundled provides

view details

Florian Müllner

commit sha 31c78388e1a86b46558fc86cb5829549af79bf2f

Update to 40.3

view details

Grigori Goronzy

commit sha dad90278932385fcb07cdfd14e350a2df739548f

Merge remote-tracking branch 'upstream/f34' into f34

view details

Grigori Goronzy

commit sha 005602fd21587f7de8a8fc49119f363f572880c3

Update !1862

view details

push time in 4 days

push eventgrigorig/mutter-performance

Jonas Ådahl

commit sha b19ccc1480298e85cd1dc696b42bf15fcf4cbe48

Mark cogl and clutter as bundled The version specified are the ones at the point they were forked.

view details

Andrey Brusnik

commit sha e5083145e2ff4ef07ea6549036907f132685b438

Apply upstream fix for libwacom tablet mapping to monitor

view details

Florian Müllner

commit sha fa750f882cb5b6f19e306d45be50a7ae4980a33e

Update to 40.3

view details

Grigori Goronzy

commit sha 780499d30507e388eb2e4f8598405eb1419e889c

Merge remote-tracking branch 'upstream/f34' into f34

view details

push time in 4 days

startedrobingenz/capacitor-firebase-authentication

started time in 5 days

startedbaumblatt/capacitor-firebase-auth

started time in 5 days

startedPelionIoT/mbed-coap

started time in 16 days

startedfilips123/FirefoxPWA

started time in 22 days

issue commentwwmm/pulseeffects

Use PipeWire filter infrastructure

The fact that PulseEffects uses virtual devices to do its thing is an implementation detail. It's confusing for users, because the regular audio control panel normally controls which physical device sound is directed to, but with PulseEffects, it doesn't do that anymore. If you want to use PulseEffects, all audio must go into the virtual device. Users now need to change the actual output device inside PulseEffects.

IMHO it would be more sensible to transparently inject filtering into individual output (or input) devices on a per-device basis. Not sure if that is actually feasible with PipeWire right now, though.

grigorig

comment created time in 23 days

issue commentwwmm/pulseeffects

Use PipeWire filter infrastructure

It's mostly confusing that the sound control panel stops making sense (e.g. in GNOME).

grigorig

comment created time in 23 days

issue openedwwmm/pulseeffects

Use PipeWire filter infrastructure

PipeWire now has support for filtering built-in. I wonder whether it makes sense to implement PulseEffects filtering using that instead of virtual sinks and sources, which can be confusing.

created time in 25 days

issue commentdortania/OpenCore-Legacy-Patcher

Big Sur boot fails after enabling FileVault

Any idea what's possibly going wrong here?

grigorig

comment created time in a month

startedpushandplay/cordova-plugin-apprate

started time in a month

issue commentcapacitor-community/firebase-analytics

Build fails in getAppInstanceId()

I can confirm it's looking good here now. Turned out I misunderstood a little bit how CocoaPods' dependency management actually works, too.

grigorig

comment created time in a month

issue commentdortania/OpenCore-Legacy-Patcher

Big Sur boot fails after enabling FileVault

Here's the OpenCore DEBUG log.

opencore-2021-06-22-150858.txt

At the end of the file there's a sequence of zero bytes--is this expected?

grigorig

comment created time in a month

issue openeddortania/OpenCore-Legacy-Patcher

Big Sur boot fails after enabling FileVault

Describe the bug On a fresh Big Sur 11.4 installation (onto an external USB SSD) and enabling FileVault, booting macOS fails with OCLP 0.1.9. SIP and SBM are enabled. The system is stuck on the initial black screen with white Apple logo. Enabling verbose mode in OCLP does nothing.

Any idea what to try next?

To Reproduce Steps to reproduce the behavior:

  1. Install Big Sur
  2. Enable FileVault
  3. Reboot

Hardware (please complete the following information):

  • OS: Big Sur 11.4
  • OCLP 0.19
  • MacBookPro9,1

created time in a month

issue openeddortania/OpenCore-Legacy-Patcher

Separate configuration support for Big Sur and Monterey

OCLP currently munges support for Big Sur and Monterey together, which is problematic. For instance, a MacBookPro9,1 can perfectly use SIP and SBM on Big Sur. That way, you can use FileVault without any issues, which is one of the features OCLP is advertised with (right in the README). With the "one size fits all" approach however, SIP and SBM need to be disabled since it won't work with Monterey.

OCLP should have separate configurations based on model and target OS version to fix these problems. If that isn't possible near-term, at least the documentation should be updated and point out how to configure OCLP.

created time in a month

push eventgrigorig/gnome-shell-performance

Grigori Goronzy

commit sha a52f7dda3931677103cd29f8fbaf178caabb4cde

Add !1884

view details

push time in a month

push eventgrigorig/mutter-performance

Jonas Ådahl

commit sha e11f6d18ceea5cbbd527868df311c477a9218f52

Fix crash regression Resolves: #1971193 Resolves: #1971184 Resolves: #1971176 Resolves: #1971158

view details

Florian Müllner

commit sha 4a8a517efc1dcee51e87d3e2792f0f698c5d23a3

Update to 40.2.1

view details

Grigori Goronzy

commit sha fbf248768da0d32c43afaefa8f4842e4b9b7b300

Merge remote-tracking branch 'upstream/f34' into f34

view details

push time in a month

CommitCommentEvent

push eventgrigorig/mutter-performance

Grigori Goronzy

commit sha d87262444f4d055f333eec8e1cac1402f790259b

Disable !1241 for now

view details

push time in a month

push eventgrigorig/gnome-shell-performance

Florian Müllner

commit sha 381cb6c820c370d89aae769741d48186c8373bcb

Update to 40.2

view details

Grigori Goronzy

commit sha 5e136372b115fd5377d2b8aacb2be6b003bcab45

Merge remote-tracking branch 'upstream/f34' into f34

view details

Grigori Goronzy

commit sha 8a89754a214e868a9a0fd69e016f2698a69e6ead

Drop !1869

view details

push time in a month

push eventgrigorig/mutter-performance

Florian Müllner

commit sha 2a9f31361f30632470250d583d1fa7e590df49e2

Update to 40.2

view details

Grigori Goronzy

commit sha 08ba9269ce2c85178c31f45503df866165c26bfc

Merge remote-tracking branch 'upstream/f34' into f34

view details

push time in a month

issue openedcapacitor-community/firebase-analytics

Build fails in getAppInstanceId()

Describe the bug The plugin native build fails in the function getAppInstanceId() with the error Cannot force unwrap value of non-optional type 'String'.

This seems to be a version conflict of the native Firebase SDKs. The return type of the native Firebase SDK function Analytics.appInstanceId() was changed at some point and Cocoapods decided to install the wrong version for this plugin. I also use the Capacitor Firebase Crashlytics plugin, maybe that's why.

Maybe this plugin should define the required Firebase SDK version range in Podfile?

To Reproduce Steps to reproduce the behavior:

  1. Install both this plugin and @capacitor-community/firebase-crashlytics
  2. Run Capacitor update/sync
  3. Build project

Desktop (please complete the following information):

  • OS: macOS 10.15.7
  • CocoaPods: 1.10.1
  • Version: 1.0.0

created time in 2 months

startedjepiqueau/capacitor-video-player

started time in 2 months

push eventgrigorig/mutter-performance

Grigori Goronzy

commit sha 634303d9dfe6f56fe8d443bce69708954ef4fadd

Update !1241 Fixes a warning.

view details

push time in 2 months

push eventgrigorig/mutter-performance

Grigori Goronzy

commit sha fc972a32e117ff400791aa0099ef26fa1e4621f3

Fix !1241

view details

push time in 2 months

push eventgrigorig/gnome-shell-performance

Grigori Goronzy

commit sha 2aa11e7660fb27ed84d662360da4cd3ff9796759

Add copr custom build Makefile

view details

push time in 2 months

push eventgrigorig/mutter-performance

Grigori Goronzy

commit sha d763dfd32505a7d6ed573781e47e1e129bfd5725

Add copr custom build Makefile

view details

push time in 2 months

push eventgrigorig/mutter-performance

Grigori Goronzy

commit sha ebd29533705699042808c416095c571631fa4f61

Add copr custom build Makefile

view details

push time in 2 months