nvidia 304 graphics causes Login loop in Ubuntu Budgie

[Diogo Gomes]

Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie.

Steps:
- Enter password
- System shows top bar (half cropped)
- Sometimes dock appears
- Screen goes off (with no signal in monitor)
- Screen shows login screen again

System description:
- OS: Ubuntu Budgie 17.04 (daily build)
- GPU: Nvidia GeForce 6150SE nForce 430

Packages:
- Budgie Desktop 10.2.9
- Nvidia Graphics Drivers 304

Notes:
The system it's updated (full-upgrade)

[fossfreedom (fossfreedom)]

when did you install?

Was the desktop working recently - then stopped working after some updates?

Is this in virtualbox or a real desktop install?

CTRL+ALT+F2

login

journal -ae --full > ~/output

We need to see that output file - you'll need to drag that from your computer somehow - suggest boot from a live ISO - you should see the hard-disk in files and get the file.

[Rob Peters (makitso)]

I saw this a while back but only using Virtualbox. Have not seen is in a week or so.

[Diogo Gomes (diogogomes)]

I install it yesterday in real desktop.

I suppose is related to nvidia-304 drivers.

It's working with nouveau.

My system report another bug with atachments to x-org.

I don't know if it is related. Can you help me to see if it's related and to merge two reports?

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1675858

[Diogo Gomes (diogogomes)]

I think the bug is bigger than I expected.

With nouveau drivers, the system crash randomly.

[fossfreedom (fossfreedom)]

I can't see that bug report - but yeah - I suspect it is due to the recent xorg upgrade that has occurred in the last week or so.

I need to see the journal -ae log to see where the crash is occurring.

[Diogo Gomes (diogogomes)]

I tried again with nvidia-304 drivers and I can't login.

There is the journal output.

[fossfreedom (fossfreedom)]

yep - looks like the nvidia driver is killing the budgie-window manager

Suggest purge the nvidia driver you have installed for the moment.

this looks relevant:

mar 24 18:14:08 Asus-UbuntuBudgie kernel: NVRM: Xid (PCI:0000:00:0d): 1, Channel 00000002 Method 00000060 Data beef0233
mar 24 18:14:08 Asus-UbuntuBudgie kernel: NVRM: Xid (PCI:0000:00:0d): 1, Channel 00000002 Method 00000060 Data beef0233
mar 24 18:14:08 Asus-UbuntuBudgie kernel: NVRM: Xid (PCI:0000:00:0d): 1, Channel 00000002 Method 00000060 Data beef0233
mar 24 18:14:08 Asus-UbuntuBudgie kernel: NVRM: Xid (PCI:0000:00:0d): 1, Channel 00000002 Method 00000060 Data beef0233
mar 24 18:14:08 Asus-UbuntuBudgie kernel: NVRM: Xid (PCI:0000:00:0d): 1, Channel 00000002 Method 00000060 Data beef0233
mar 24 18:14:08 Asus-UbuntuBudgie budgie-wm[1791]: The program 'budgie-wm' received an X Window System error.
                                                   This probably reflects a bug in the program.
                                                   The error was 'BadMatch (invalid parameter attributes)'.
                                                     (Details: serial 919 error_code 8 request_code 134 (SYNC) minor_code 16)
                                                     (Note to programmers: normally, X errors are reported asynchronously;
                                                      that is, you will receive the error a while after causing it.
                                                      To debug your program, run it with the GDK_SYNCHRONIZE environment
                                                      variable to change this behavior. You can then get a meaningful
                                                      backtrace from your debugger if you break on the gdk_x_error() function.)
mar 24 18:14:08 Asus-UbuntuBudgie kernel: do_trap: 30 callbacks suppressed
mar 24 18:14:08 Asus-UbuntuBudgie kernel: traps: budgie-wm[1791] trap int3 ip:7efbfa36ade1 sp:7ffea31d4d20 error:0
mar 24 18:14:08 Asus-UbuntuBudgie kernel: in libglib-2.0.so.0.5200.0[7efbfa31b000+111000]
mar 24 18:14:08 Asus-UbuntuBudgie dbus-daemon[1496]: Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service'
mar 24 18:14:08 Asus-UbuntuBudgie systemd[1460]: Starting Tracker metadata database store and lookup manager...
mar 24 18:14:08 Asus-UbuntuBudgie gnome-session-binary[1480]: Entering running state
mar 24 18:14:08 Asus-UbuntuBudgie at-spi2-registr[1680]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
mar 24 18:14:08 Asus-UbuntuBudgie at-spi2-registr[1680]: Unable to register client with session manager
mar 24 18:14:10 Asus-UbuntuBudgie nvidia-settings-autostart.desktop[1877]: ERROR: Error querying target relations
mar 24 18:14:10 Asus-UbuntuBudgie nvidia-settings-autostart.desktop[1877]: ERROR: Error querying target relations
mar 24 18:14:11 Asus-UbuntuBudgie dbus-daemon[1496]: Activating via systemd: service name='org.ayatana.bamf' unit='bamfdaemon.service'
mar 24 18:14:11 Asus-UbuntuBudgie nautilus-autostart.desktop[1895]: sys:1: PyGIWarning: Nautilus was imported without specifying a ver...

[Diogo Gomes (diogogomes)]

It's stable for now.

Do you recommend open another issue related to nvidia-304 package or update the title and description of this one?

[Diogo Gomes (diogogomes)]

False positive.

I got a screen freeze after ~20 minutes.

[fossfreedom (fossfreedom)]

I would recommend you try this staging PPA - https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

it brings the latest X stack - if it resolves your issues please report that fact here on the bug report tracking the request to bring this X stack to zesty:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

[GizmoChicken (gizmochicken)]

Sorry if I missed this in your bug report, but what model Nvidia GPU are you testing?

[Diogo Gomes (diogogomes)]

My GPU is Nvidia GeForce 6150SE nForce 430

[GizmoChicken (gizmochicken)]

Okay, I was hoping that I'd be able to suggest, as a simple fix, trying a newer driver. But I see that v304 is, indeed, the most recent Linux driver available for your GPU.

http://www.nvidia.com/Download/Find.aspx?lang=en-us

[Diogo Gomes (diogogomes)]

Yes, I know.

This GPU driver works well in Ubuntu, Ubuntu Mate, etc.

Only not works in Budgie.

I test install Budgie DE in Ubuntu Mate and I can't login in Bugdie DE neither, only in Mate DE.

[fossfreedom (fossfreedom)]

 I suspect you will have the same issue with gnome-shell. budgie and
gnome-shell use the same window manager.

On 25 March 2017 at 18:04, Diogo Gomes <email address hidden> wrote:
> Yes, I know.
>
> This GPU driver works well in Ubuntu, Ubuntu Mate, etc.
>
> Only not works in Budgie.
>
> I test install Budgie DE in Ubuntu Mate and I can't login in Bugdie DE
> neither, only in Mate DE.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1675830
>
> Title:
> nvidia 304 graphics causes Login loop in Ubuntu Budgie
>
> Status in Ubuntu Budgie:
> New
> Status in nvidia-graphics-drivers-304 package in Ubuntu:
> New
>
> Bug description:
> Nvidia 304 graphics kills budgie-window manager process and causes
> login loop in Ubuntu Budgie.
>
> Steps:
> - Enter password
> - System shows top bar (half cropped)
> - Sometimes dock appears
> - Screen goes off (with no signal in monitor)
> - Screen shows login screen again
>
> System description:
> - OS: Ubuntu Budgie 17.04 (daily build)
> - GPU: Nvidia GeForce 6150SE nForce 430
>
> Packages:
> - Budgie Desktop 10.2.9
> - Nvidia Graphics Drivers 304
>
> Notes:
> The system it's updated (full-upgrade)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+subscriptions

[Diogo Gomes (diogogomes)]

Okay, I'm in. I replace the window manager installing compiz and now I can login with nvidia 304.

Steps:
- Install compiz
- Add "compiz --replace" to autostart
- Install nvidia-304
- Reboot

Result:
 In first login, I have a loop and in the second time that I enter password, I am enable to login.

Notes:
This confirms that is an incompatibility with budgie window manager and nvidia 304.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marcos Nascimento (wstlmn)]

I am having the same problem with ubuntu 17.10 and 6800TX graphics card. Everything was working. After some updates, I can not log in anymore.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "journal -ae --full" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[fossfreedom (fossfreedom)]

Mutter has now been updated to GNOME 3.26 on 17.10. Please can you retest.

thanks