Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED]Trouble with running GNOME

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
ChrisPL
Posts: 14
Joined: 2017-09-10 20:16

[SOLVED]Trouble with running GNOME

#1 Post by ChrisPL »

I try to install GNOME on a fairly old laptop Acer TravelMate with Intel 82830M graphics card. Installation process did not expose any issues but GNOME doesn't start properly. I can't pass through login screen which returns back after a few seconds (login and pass are OK of course).
I have installed Debian first and there were no problems. Then I tried with GNOME.

The journal for gnome-shell is as follows and shows many failings:

Code: Select all

-- Logs begin at Mon 2017-10-16 23:11:20 CEST, end at Mon 2017-10-16 23:20:40 CEST. --
Oct 16 23:14:26 TravelMate gnome-shell[537]: Failed to apply DRM plane transform 0: Invalid argument
Oct 16 23:14:26 TravelMate org.gnome.Shell.desktop[537]: glamor: EGL version 1.4 (DRI2):
Oct 16 23:14:26 TravelMate org.gnome.Shell.desktop[537]: Require OpenGL version 2.1 or later.
Oct 16 23:14:26 TravelMate org.gnome.Shell.desktop[537]: Failed to initialize glamor
Oct 16 23:14:26 TravelMate org.gnome.Shell.desktop[537]: Failed to initialize glamor, falling back to sw
Oct 16 23:14:34 TravelMate org.gnome.Shell.desktop[537]: Window manager warning: Failed to allocate cursor texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:44 TravelMate gnome-shell[537]: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or directory)
Oct 16 23:14:52 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:52 TravelMate gnome-shell[537]: cogl_object_ref: assertion 'object != ((void *)0)' failed
Oct 16 23:14:52 TravelMate gnome-shell[537]: clutter_texture_set_cogl_texture: assertion 'cogl_is_texture (cogl_tex)' failed
Oct 16 23:14:52 TravelMate gnome-shell[537]: clutter_texture_set_cogl_texture: assertion 'cogl_is_texture (cogl_tex)' failed
Oct 16 23:14:52 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:52 TravelMate gnome-shell[537]: clutter_texture_set_cogl_texture: assertion 'cogl_is_texture (cogl_tex)' failed
Oct 16 23:14:52 TravelMate gnome-shell[537]: JS ERROR: could not get remote objects for service org.gnome.SettingsDaemon.Smartcard path /org/gnome/SettingsDaemon/Smartcard: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Smartcard was not provided by any .service files
                                             _proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:83
Oct 16 23:14:52 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:52 TravelMate gnome-shell[537]: cogl_object_ref: assertion 'object != ((void *)0)' failed
Oct 16 23:14:52 TravelMate gnome-shell[537]: clutter_texture_set_cogl_texture: assertion 'cogl_is_texture (cogl_tex)' failed
Oct 16 23:14:54 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:54 TravelMate gnome-shell[537]: clutter_texture_set_cogl_texture: assertion 'cogl_is_texture (cogl_tex)' failed
Oct 16 23:14:54 TravelMate gnome-shell[537]: clutter_texture_set_cogl_texture: assertion 'cogl_is_texture (cogl_tex)' failed
Oct 16 23:14:54 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:54 TravelMate gnome-shell[537]: cogl_object_ref: assertion 'object != ((void *)0)' failed
Oct 16 23:14:54 TravelMate gnome-shell[537]: clutter_texture_set_cogl_texture: assertion 'cogl_is_texture (cogl_tex)' failed
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:14:57 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Oct 16 23:15:09 TravelMate gnome-shell[537]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Thanks for help.
Last edited by ChrisPL on 2017-10-20 20:28, edited 1 time in total.

User avatar
HuangLao
Posts: 485
Joined: 2015-01-27 01:31
Been thanked: 1 time

Re: Trouble with running GNOME

#2 Post by HuangLao »

first, Gnome3 is not designed for old or low powered hardware. Try Mate, Xfce or Lxde instead.
example:

Code: Select all

apt install xfce4 
ref: https://wiki.debian.org/Xfce

imazighen-thamzgha
Posts: 38
Joined: 2017-04-21 09:38

Re: Trouble with running GNOME

#3 Post by imazighen-thamzgha »

Or you don't have the right drivers install, try the non-free section
ⵉⵎⴰⵣⵉⵖⴻⵏ / imaZighen

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Trouble with running GNOME

#4 Post by debiman »

what's "fairly old"?
hardware specs please.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Trouble with running GNOME

#5 Post by stevepusser »

imazighen-thamzgha wrote:Or you don't have the right drivers install, try the non-free section
This makes no sense at all with older Intel graphics. Recent Intel graphics (skylake and above) do require non-free firmware. And 100 Internet demerits to the next person to confuse firmware with drivers here.

Chris, install inxi and give us the output of (as standard user)

Code: Select all

inxi -F
in a code box so we can really see what's in your machine. The errors indicate that your older hardware just can't support the version of openGL that GNOME 3 requires.
MX Linux packager and developer

ChrisPL
Posts: 14
Joined: 2017-09-10 20:16

Re: Trouble with running GNOME

#6 Post by ChrisPL »

That's inxi output:

Code: Select all

System:  Host: TravelMate Kernel: 4.9.0-3-686-pae i686 (32 bit) Console: tty 
Distro: Debian GNU/Linux 9 (stretch)
Machine:  Device: laptop System: Acer product: TravelMate 220 v: -1
Mobo: Acer model: Intel Almador-M v: -1 BIOS:ACER v:V3.3 R01-A0W EN date:10/01/2002
CPU:      Single core Mobile Intel Celeron (-UP-) cache: 256 KB speed: 1333 MHz (max)
Graphics: Card: Intel 82830M/MG Integrated Graphics Controller
Display Server: X.org 1.19.2 driver: N/A tty size: 128x48 Advanced Data: N/A out of X
Audio:    Card Intel 82801CA/CAM AC'97 Audio Controller driver: snd_intel8x0 Sound: ALSA v: k4.9.0-3-686-pae
Network:  Card: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too
IF: enp1s5 state: unknown speed: 100 Mbps duplex: full mac: 00:00:e2:85:c3:f5
Drives:   HDD Total Size:20.0GB (23.2% used)
ID-1: /dev/sda model: IC25N020ATCS04  20.0GB
Partition:ID-1: / size: 18G used: 3.4G (21%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 1.06GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:  System Temperatures: cpu: 58.0C mobo: 45.0C
Fan Speeds (in rpm): cpu: N/A
Info:     Processes: 106 Uptime:37m 8 min Memory: 141.5/996.5MB Init: systemd runlevel: 5
Client: Shell (bash) inxi: 2.3.5

nnm
Posts: 16
Joined: 2017-10-07 10:11
Location: /dev/zero

Re: Trouble with running GNOME

#7 Post by nnm »

Try the X11 gnome session instead of the wayland one.
Debian 9 (Stretch)
Asus Vivobook S551LB

ChrisPL
Posts: 14
Joined: 2017-09-10 20:16

Re: Trouble with running GNOME

#8 Post by ChrisPL »

So what should I do?

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Trouble with running GNOME

#9 Post by stevepusser »

Use a less demanding desktop environment that GNOME 3--which any other one is. Take your pick.
MX Linux packager and developer

User avatar
None1975
df -h | participant
df -h | participant
Posts: 1389
Joined: 2015-11-29 18:23
Location: Russia, Kaliningrad
Has thanked: 45 times
Been thanked: 66 times

Re: Trouble with running GNOME

#10 Post by None1975 »

ChrisPL wrote:So what should I do?
Use Mate or XFCE.
OS: Debian 12.4 Bookworm / DE: Enlightenment
Debian Wiki | DontBreakDebian, My config files on github

User avatar
HuangLao
Posts: 485
Joined: 2015-01-27 01:31
Been thanked: 1 time

Re: Trouble with running GNOME

#11 Post by HuangLao »

See first reply, then mark solved.

ChrisPL
Posts: 14
Joined: 2017-09-10 20:16

Re: Trouble with running GNOME

#12 Post by ChrisPL »

XFCE seems to work. Thanks.

rtimai
Posts: 6
Joined: 2016-09-22 08:53

Re: [SOLVED]Trouble with running GNOME

#13 Post by rtimai »

On my X86_64 system (Stretch/Stable,) kernel 4.9.0-3-amd64 was the last release that allowed me to boot to Gnome-shell on X11, and booting into Wayland resulted in all kinds of screen craziness (e.g., four screen sections displaced, flickering, rolling, etc.)

With the kernel 4.9.4-amd64 and 4.9.5 update, I found that I could no longer log into Gnome-shell on X11, (blank screen on authentication, then auto-shutdown after 1-3 minutes.)

Then by accident I found that I could log in to Gnome-shell on Wayland, which began to run with fewer problems starting with 4.9.0-4-amd64 (fewer incidents, and recoverable by closing all windows with Alt-F4.) But there are still issues with several critical applications, most seriously, sudo doesn't work on my system on Wayland.

Oddly enough, I found that if I booted FIRST into Gnome-Wayland, and logged out, I was THEN able to log back in successfully to Gnome-X11 which restored sudo support for me. This is the only way currently that I can run gnome-shell with sudo support (other than reverting to kernel 4.9.0.3.) Oh yes -- and running gnome-x11 using this logout/in method has the same screen issues that occurred in Wayland.

I think the many current issues are caused by major underlying changes in Debian recently, namely the migration from sysV to Systemd, GTK+ to QT, and X11 to Wayland. For linux beginners, the first transition involves system initialization, the second involves the software layer that enables the operating system and applications to communicate with each other, and the third involves the display server. The x11-wayland transition is monumentally tricky, because if the display server fails for anyone, they have zero error feedback (can't see anything,) and they're faced with system recovery. So, practically everybody is involved in this, and moving very cautiously, I'm sure.

But I believe this overhaul of linux is unavoidable if it is to shed the burden of legacy support that almost no one needs anymore. Just my opinion, of course. I hope the logout/in procedure might help a few others, especially if they're having sudo issues.

Post Reply