rijenkii

Actually, it's a `vmware-modconfig` causes the problem ``` gdb --args /usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware-modconfig --appname=VMware Workstation --icon=vmware-workstation GNU gdb (GDB) 7.12 ... Reading symbols from /usr/lib/vmware/bin/vmware-modconfig...(no debugging symbols found)...done. (gdb) run Starting...

Considering that Widevine L3 decryptors were [DMCAd from GitHub by Google](https://github.com/github/dmca/blob/master/2020/11/2020-11-09-Google.md), IMHO this issue can be marked as unresolvable.

Just experienced same issue with `@vuedoc/md`. `yarn` installs it without any problem.

Just to mention: CSDs can be removed from Xfce 4.16 applications with [libxfce4ui-nocsd](https://github.com/Xfce-Classic/libxfce4ui-nocsd). It works with gtk3-nocsd as far as I can tell.

Also, because of namespace stripping, it is currently impossible to deserialize following xml: ```xml ``` Naive approach does not work, as expected: ```rust #[derive(Debug, serde::Deserialize)] #[serde(rename = "list")] struct List...

I have just exported the root component and import it as I need into my components: ```typescript // main.ts export default createApp(App).use(router).mount("#app"); ``` ```vue import { useRouter } from "vue-router";...

I do find it very interesting, in fact I am trying to implement something inspired by that RFC. Maybe I should have a looksie at how it is implemented in...

Extension of discriminated unions would be *really* useful, because for now I have to do this: ```typescript z.discriminatedUnion(otherDiscriminatedUnion.discriminator, [ otherDiscriminatedUnion.options[0].extend({ field: "value" }), otherDiscriminatedUnion.options[1].extend({ field: "value" }), otherDiscriminatedUnion.options[2].extend({ field: "value"...

I'm pretty sure this is working as intended, as both of the types are correct. It's just that your component is defined using `script setup`, and `FormKitKitchenSink` is defined with...

https://github.com/vuejs/core/discussions/7524 > Because :deep() is specifically as feature of `scoped` css, not `module`. It does not translate to how CSS modules work. This issue can be closed as "won't fix"...