Re: www/ungoogled-chromium: fix name in .desktop file
On 7/31/23 18:22, Klemens Nanni wrote: > Using the same as www/chromium means both browsers show up identically > in graphical shells like Xfce and GNOME. > > OK? OK aisha@ > Index: Makefile > === > RCS file: /cvs/ports/www/ungoogled-chromium/Makefile,v > retrieving revision 1.67 > diff -u -p -r1.67 Makefile > --- Makefile 27 Jul 2023 11:08:33 - 1.67 > +++ Makefile 31 Jul 2023 20:19:29 - > @@ -11,6 +11,7 @@ V= 115.0.5790.110 > UGV= ${V}-1 > > DISTNAME=ungoogled-chromium-${V} > +REVISION=0 > > DISTFILES+= ${CHROMIUM_DISTFILES} \ > ${UGOOGLE_DISTFILES}:0 \ > Index: files/ungoogled-chromium.desktop > === > RCS file: /cvs/ports/www/ungoogled-chromium/files/ungoogled-chromium.desktop,v > retrieving revision 1.1.1.1 > diff -u -p -r1.1.1.1 ungoogled-chromium.desktop > --- files/ungoogled-chromium.desktop 4 Oct 2022 12:55:55 - 1.1.1.1 > +++ files/ungoogled-chromium.desktop 31 Jul 2023 22:20:13 - > @@ -1,6 +1,6 @@ > [Desktop Entry] > Version=1.0 > -Name=Chromium Web Browser > +Name=Ungoogled Chromium Web Browser > # Only KDE 4 seems to use GenericName, so we reuse the KDE strings. > # From Ubuntu's language-pack-kde-XX-base packages, version 9.04-20090413. > GenericName=Web Browser >
Re: www/ungoogled-chromium
On 10 Oct 12:04, Uwe Werler wrote: > On 10 Oct 07:59, Robert Nagy wrote: > > On 09/10/22 16:34 -0700, Heppler, J. Scott wrote: > > > On current, ungoogled-chromium errors out - unable to access > > > /dev/drm/card0. I replaced with www/iridium and it ran fine. > > > I suspect pledge/unveil was not fully implemented in ungoogled-chromium. > > > > > > A second issue is that it likely cannot be installed with www/chromium > > > as both use ~/.config/chromium. > > > > This has been fixed in -current. > > > > Hi all, > > ungoogled-chromium still tries to access ~/-cache/chromium instead of > ~/.cache/ungoogled-chromium: > > [2490:-379226272:1010/115913.915092:ERROR:process_singleton_posix.cc(335)] > Failed to create /home/uwerler/.config/chromium/SingletonLock: No such file > or directory (2) > [2490:-379226272:1010/115913.915390:ERROR:chrome_browser_main.cc(1440)] > Failed to create a ProcessSingleton for your profile directory. This means > that running multiple instances would start multiple browser processes rather > than opening a new window in the existing process. Aborting now to avoid > profile corruption. > > For now I linked ~/.cache/chromium to ~/.cache/ungoogled-chromium and it > starts up also with all my extensions/addons from chrome instead of changing > the path in /etc/ungoogled-chromium/unveil.main > > Regards Uwe > > -- > wq: ~uw > Sorry for the noise - it's the same issue Scott already mentioned (not in ~/.cache but in ~/.config). -- wq: ~uw
Re: www/ungoogled-chromium
On 10 Oct 07:59, Robert Nagy wrote: > On 09/10/22 16:34 -0700, Heppler, J. Scott wrote: > > On current, ungoogled-chromium errors out - unable to access > > /dev/drm/card0. I replaced with www/iridium and it ran fine. > > I suspect pledge/unveil was not fully implemented in ungoogled-chromium. > > > > A second issue is that it likely cannot be installed with www/chromium > > as both use ~/.config/chromium. > > This has been fixed in -current. > Hi all, ungoogled-chromium still tries to access ~/-cache/chromium instead of ~/.cache/ungoogled-chromium: [2490:-379226272:1010/115913.915092:ERROR:process_singleton_posix.cc(335)] Failed to create /home/uwerler/.config/chromium/SingletonLock: No such file or directory (2) [2490:-379226272:1010/115913.915390:ERROR:chrome_browser_main.cc(1440)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption. For now I linked ~/.cache/chromium to ~/.cache/ungoogled-chromium and it starts up also with all my extensions/addons from chrome instead of changing the path in /etc/ungoogled-chromium/unveil.main Regards Uwe -- wq: ~uw
Re: www/ungoogled-chromium
On 09/10/22 16:34 -0700, Heppler, J. Scott wrote: > On current, ungoogled-chromium errors out - unable to access > /dev/drm/card0. I replaced with www/iridium and it ran fine. > I suspect pledge/unveil was not fully implemented in ungoogled-chromium. > > A second issue is that it likely cannot be installed with www/chromium > as both use ~/.config/chromium. This has been fixed in -current.