gnome :: #gnome

18 May 2017
00:22blackdout-ryanmrevd[m]: Have you already edited your terminal profile?
13:58ice9on Wayland i feel the animations are a bit laggy and also the battery drains faster, any idea?
14:01ice9according to this page http://us.download.nvidia.com/XFree86/Linux-x86/375.20/README/kms.html#drm-kms-known-issues
14:01ice9they say if the moseset is enabled and those kernel options, wayland can run on the prop driver
14:01ice9but after applying this, wayland is still ont using nvidia
14:03borschtywhich version of mutter do you use?
14:03borschtyand do you maybe have a laptop with switchable graphics cards?
14:04ice9borschty, 3.24.2-1
14:04ice9borschty, right it's optimus
14:06borschtywhich distro?
14:06ice9borschty, Arch
14:08ice9borschty, sorry i was d/c
14:08ice9i'm using Arch
14:11borschtyecho $XDG_SESSION_TYPE
14:12ice9borschty, wayland
14:15borschtyi think fedora has a patch to automatically use X for these laptops, because switching gpus doesn't work on wayland yet
14:15borschtybut i'm not really sure about that
14:19ice9borschty, if the nvidia drivers are loaded during kerne boot and modeset is enabled then nvidia should be the primary GPU to be used
14:19ice9the issue is why gnome is not picking it up
14:20ice9i have both X and Wayland session in GDM btw; when i select X, it uses Nvidia by default
14:20ice9even if i set intel in xorg.conf; it throws some errors and doesn't start gnome
14:21borschtyhow do you check which driver is being used?
14:21ice9glxinfo | grep "OpenGL renderer"
14:22borschtythat goes through xwayland though, so that might not be accurate (no idea how exactly that stuff works though)
14:23ice9does gnome have a log file somewhere?
14:23borschtyeverything is logged to the systemd journal
15:24ice9why would battery drain fastser when using Wayland?
15:24ice9faster*
18:16enteeenel[m]hi, I am trying to build gnome's msitools. I cloned the repository, ran autogen.sh, then when I run make -32 I got the following errors:
18:16enteeenel[m]hi, I am trying to build gnome's msitools. I cloned the repository, ran autogen.sh, then when I run make -32 I got the following errors:
18:16enteeenel[m]error: Package `libmsi-1.0' not found in specified Vala API directories or GObject-Introspection GIR directories
18:16enteeenel[m]error: Package `libgcab-1.0' not found in specified Vala API directories or GObject-Introspection GIR directories
18:17enteeenel[m]Inside my /usr/local/lib64/girepository-1.0/, I have GCab-1.0.typelib
18:18enteeenel[m]Inside /usr/local/lib64/pkgconfig, I have libgcab-1.0.pc, and libR.pc
18:19enteeenel[m]I tried to run GIRDIR=/usr/local/lib64/girepository-1.0/ PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig make -j32 but still got the same error messages. How should I fix this?
20:16iz Hi , using budgie(17.04) have problem connecting to brother scanner.. i can get it working ok on 16.10 but 17.04 gives me segmenation dump.. hope this is the place to ask. Thanks
20:21borschtythat sounds more like a sane/distro issue
20:21borschtywhat are you using to scan?
20:21borschtyand what does the dump say?
20:24izi actually get the same error in other versions of ubuntu 17.04 (budgie, gnome)
20:24izSegmentation fault (core dumped)
20:24izusing simple scan
20:25izi get the error after "scanimage -l"
20:25izsimple scan doesn't show the scanner (i've installed brother drivers just like in ubuntu 16.10)
20:27borschtyiirc i had to add a udev rule to access the scanner as a user when i last used a brother scanner
20:35dboleshave you tried running under gdb and grabbing a backtrace from that segfault?
22:16dazoHi, any developers here who knows something about using g_bus_own_name() and owning system bus names ... In my code, only the GBusNameLostCallback is called, and I don't understand why
22:17dazo(I've connected to the same bus and name using QtDbus, Python D-Bus and dbus-c++)
23:15hughmy left windows key launches the application overview, but the right one doesn't. Is this normal behaviour?
19 May 2017
No messages
   
Last message: 65 days and 11 hours ago