Public bug reported:
I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS)
with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and
natural install, no funky custom kernel or drivers or anything...
Everything worked fine (with the 4.13.* kernel) until I've upgraded
Well ? What should I understand from what you just did ?
You are no longer committed to fix this bug ?
OK, I'll report this bug 10 times over, until someone helps me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is nothing there. No files in that folder (URL).
Also, please, it's really enough with testing kernels... how many more
are there ???
I understand that you need to track down the problem but it's pretty
obvious where it is... it's somewhere betweeb 4.13 and 4.14
Let's find a solution,
Not working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen in a normal sequence
To manage
This kernel works !
It has loaded novueau and I got the graphical interface and login
screen.
"lshw -c video" reveals the fact that the driver in use is claimed, and
is Nouveau.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It still freezes, and I don't get the login screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen
Well ?...
Seriously, this bug is quite old now...
Should I just say goodbye to ever being able to use my video card driver
on my laptop ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
It still freezes, and I don't get the login screen.
However, the message is different now: "nouveau bus MMIO write of ...
FAULT at ..."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Same problem.
Console Error: "nouveau: fb: trapped write at ... on channel ... engine
... client ... VRAM_LIMIT"
No login screen and freezing of laptop in console state.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry. I didn't noticed that.
OK, tested with this latest kernel "201809190746".
It crashes with Console Message:
"nouveau fb: trapped write at <>" something like this... and I never get
the Login Screen and the whole thing freezes...
--
You received this bug notification because you are a
I've already testest that kernel.
It doesn't work. (linux-image-
unsigned-4.14.0-041400-generic_4.14.0-041400.201809190746_amd64.deb)
And the generic 4.15.0-33 also doesn't work (tested with the official
ubuntu kernel, not the one on the website).
--
You received this bug notification because
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen in a normal sequence
To manage
Well ? I'm back ! Any progress ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen in a normal
Well, it's strange...
The kernel you provided me works, but only half of it.
If I boot the above kernel it gives me the login screen, so it loads the driver
correctly (I assume), but the laptop immediately freezes and I cannot do
anything on it (I assume it kernel panics somewhere).
I have to
Yes. The latest v4.14 also works great !!! I have nouveau drivers loaded
and working perfectly.
In fact, I am running it now: "4.14.0-041400-generic" and I shall stay
on this kernel (the latest kernel which works decently for me).
But the first kernel of the 4.15 series does not work anymore.
Yes. The system crashes with this version. It no longer works with
4.15-rc1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook
v4.13 Final is GOOD
v4.14-rc1 is also GOOD (a little screen flickering, but that is
acceptable)
v4.15, however, doesn't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau
I can confirm the following:
I had to revert to: 4.13.16-041316-generic and it works great with this kernel !
I'll stick with this kernel until the problem gets solved.
However, from 4.15.* it seems like it doesn't work (with the kernels I
tested).
I also tested with
I cannot authorize this computer to my Launchpad account, as this is a
work computer.
Tell me which logs do you need, and I will gladly provide them.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hello,
This is a duplicate of bug #1783957 !
Yes, I confirm this is a duplicate that above bug, because nobody is
taking care of my problem of the above bug !!! Sadly ! And I will
(normally, with decency, not abusing of anything) report this on more
forums and more bug
I will start a new bug report, as nobody cares with this bug, I see.
Opensource community fixing bugs more rapidly than commercial software
companies ? I'll think again about that one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen in a normal
one last thing I can give you:
A coredump:
PID: 1066 (sddm-greeter)
UID: 118 (sddm)
GID: 126 (sddm)
Signal: 11 (SEGV)
Timestamp: Fri 2018-08-17 10:58:44 EEST (4min 40s ago)
Command Line: /usr/bin/sddm-greeter --socket /tmp/sddm-:0-OglRQe --theme
is anyone alive here ??? or should I
just give up on everything ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel
I've upgraded my system to Bionic: 18.04.1.
The problem still exists, however it has a different behaviour now: I
have a mouse cursor :-)
>From what I have seen, this bug is not yet Assigned. When will it be
assigned ?
--
You received this bug notification because you are a member of Ubuntu
???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen in a normal sequence
To manage notifications
Well ? What is the situation ?
This morning, I had a Kernel and Xorg update. Kernel: 4.15.0-30 and Xorg
1:7.7
I really hoped that this will solve our problem, but it did not ! why ?
The same problem: "sddm-greeter[1161]: segfault at 1a ip
7fc9325a7179 sp 7fff62927ba0 error 4 in
No, again, I am sorry, I cannot do that.
I purged the new kernel right after testing because it wasn't installed
properly and it got me all kind of problems.
This is a production computer, I barely got out of the problem by
reverting to the original kernel and purging the new one.
I am using
Well, what is the situation ? I really need this bug fixed !!!
This morning I had to make a Presentation on a Projector in front of a
couple of people.
Since I am running in "recovery mode" with no Video Drivers loaded (lshw
-c video -> Display: UNCLAIMED), the system didn't detect my secondary
I'm sorry, but it is not possible for me to do this.
I already installed the new kernel a few days ago, just for testing
purposes, and I had a couple of crashes or other inconsistencies, I
barely got out of it.
This is a production computer, I cannot play with the packages as I
please.
I
I've tested the new kernel, it doesn't work. It also hangs at the screen
where the login screen should apperar.
However, not all the new kernel packages were installed. I've selected
only for amd64 architecture, but at one particular package, the headers
or something, it asked me for libssl1.1
Yeah.
After installing apport-collect, when I try to run it:
ERROR: Could not import module, is a package upgrade in progress?
Error: No module named PyQt5.QtCore
This is a 2-3 year old bug... it's still not fixed... should I have any
hope for my bug ? :-)))
** Changed in: linux (Ubuntu)
** Changed in: apport (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627790
Title:
ERROR: Could not import module, is a package upgrade in progress?
Well... any updates on this one ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627790
Title:
ERROR: Could not import module, is a package upgrade in progress?
Error: No module named
Still doesn't work.
administrator@itlap:~$ sudo apt install python-qtpy
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package python-qtpy
administrator@itlap:~$ sudo apt install python3-qtpy
Reading package lists... Done
Public bug reported:
I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS)
with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and
natural install, no funky custom kernel or drivers or anything...
Everything worked fine (with the 4.13.* kernel) until I've upgraded
OK, it is a debdiff that fixes this... but how about an update included
in the repos ?... It's painfull to put that diff on an USB stick and do
all those tasks on 30 computers.
Why don't you just simply include the update in the Update Manager ?
--
[SRU] gnome-keyring doesn't unlock ssh key
ok, Thank you :) I didn't know the exact procedure :)
I've installed the patch, it works great ! Thank you. I really hope it
gets in the repos soon.
--
[SRU] gnome-keyring doesn't unlock ssh key
https://bugs.launchpad.net/bugs/631980
You received this bug notification because you are a member
When can I expect a quick resolve to this bug ?... or who is fixing this bug
?...
To whoever is fixing bugs, Please, I want this bug resolved a.s.a.p !
When it gets resolved, will there be an Update trough the Update Manager
? or how can I apply the update ?
--
gnome-keyring doesn't unlock ssh
Please resolve this A.S.A.P. !
It's very annoying to do this on 30 computers at my work place.
I have the private keys, I have the Seahorse Daemon running, seahorse
can see the private key, but I cannot remeber for good or permanently
the password for that private key in it's default keyring.
40 matches
Mail list logo
