On 2021-01-31 13:03, Ramon Fischer wrote:
> The USE flag "gtk" was not removed:
>
>-IUSE="caps emacs gnome-keyring fltk gtk ncurses qt5"
>+IUSE="caps emacs gnome-keyring gtk ncurses qt5"
>
> Since when is this obsolete and is there any alternative?
I cannot comment directly on the obsole
Hi Silvio,
I think the problem is that you have told portage to use both nouveau
and nvidia as a driver for your card. If you have both drivers installed
and do not blacklist one of them, the other will not work.
> # modprobe nvidia
> modprobe: ERROR: could not insert 'nvidia': No such device
If
Hi Steve,
On 2020-06-30 20:35, Steve Freeman wrote:
> I have a local gentoo repo mirror that has been running well for
> years. It is essentially the same setup as described at
> https://wiki.gentoo.org/wiki/Local_Mirror except that it runs on a
> non-default port.
I sadly cannot reproduce this
On 2020-06-16 12:05, Peter Humphrey wrote:
> So I created a ~/.cache/bwtmp directory and passed TMPDIR= to
> bitwarden, but then it threw another error. I'd better take this up
> with BitWarden.
I just tried getting it to work again. If this is anything like on my
system, once the noexec problem i
On 2020-06-14 23:20, Peter Humphrey wrote:
> On Sunday, 14 June 2020 19:06:36 BST Wynn Wolf Arbor wrote:
>
> That was a good idea - but it didn't help, so that's not the answer.
If you're still interested in debugging this, did the error message stay
the same?
On 2020-06-14 18:45, Peter Humphrey wrote:
> Yes; this is what I get:
>
> $ ./Bitwarden*/opt/Bitwarden/bitwarden
> A JavaScript error occurred in the main process
> Uncaught Exception:
> Error: /tmp/.org.chromium.Chromium.QkN0cP: failed to map segment from shared
> object
> --->8
>From what I re
Hi Peter,
On 2020-06-14 12:43, Peter Humphrey wrote:
> Afternoon all,
>
> Has anyone some experience of bitwarden on Gentoo? It doesn't run for
> me, and I suspect a java problem. I have icedtea here.
>
> I'm talking about the installed version, not the firefox extension,
> which seems to work.
Hi,
I'm currently using the 390 slot since when I installed that card,
that is what it showed. I'm almost 100% certain I checked this when
installing this card. My question is, is it normal for nvidia to
change the series of drivers for cards like this?
A driver series is not necessarily bo
On 2020-05-01 09:18, tu...@posteo.de wrote:
A very *#BIG THANK YOU#* for all the great help, the research and
the solution. I myself am back in "normal mode" :)
Glad it helped!
One thing remains...
I want to prevent this kind of hassle in the future... ;)
The most important thing to keep in
On 2020-04-30 22:21, Andrea Conti wrote:
It won't, as long as it recognizes it as a protective MBR. Which is the
right thing to do, as a disk with a protective MBR and no valid GPT is
inherently broken.
True. It was more my intention to depict what the system "should" do in
order to access th
Hi Meino,
On 2020-04-30 21:46, tu...@posteo.de wrote:
I had booted into my old system, attached the disks and both show the
same behaviour: Only the device itself (/dev/sdb) was recognized.
Now that is very curious. Just to make sure, the old system definitely
does not understand GPT? CONFIG_
All the following assuming that the disk was originally partitioned as
GPT, but after that exclusively accessed as an MBR disk.
PT fdisk (gdisk) version 1.0.5
Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!
This makes sense since the GPT backup at th
Hi Meino,
Thanks very much for the info. At this point I'm convinced you're
running into the problem Andrea described in another reply in this
thread - best to follow up there :)
--
Wolf
Hi,
On 2020-04-30 13:17, Wols Lists wrote:
All I can suggest is to check the kernel and see if it's an option that
has been disabled (512-byte sectors, that is).
As far as I know the kernel still uses 512 bytes internally [1], and I
do not recall having seen an option that enables or disables
14 matches
Mail list logo