Converted to a question as this is a system configuration issue.
I will see you there.
** Changed in: linux-hwe (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/linux-hwe/+question/684606
--
You received this bug notification
converted to a question.
** Changed in: gedit (Ubuntu)
Status: Incomplete => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/gedit/+question/684506
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Guilherme; Well
As this no longer appears to be a bug, I am moving this to Launchpad Answers.
I will meet you there and we will further explore your issue.
Thanks for taking the time to make ubuntu better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Guilherme; Hey -
The fact of the matter is that "sudo" is no longer the means to enable
'root's" use of GUI applications; as gksu is depreciated. Not a miss-
configuration of the system either.
Preferable is "admin://" - though there are 2 other alternates that I am aware
of.
If you do, as I,
Hello Guilherme
You do not say how you are starting gedit. As policykit now applies what
results:
gedit admin:///etc/apt/sources ?
** Changed in: gedit (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hekko Gareth Evans ;
the error:
"PKCS#7 signature not signed with a trusted key" is generally hardware driver
related - specifically Nvidia.
What results when attempting to boot with the nomodeset boot parameter:
A common kernel (boot)parameter is nomodeset, which is needed for some graphic
Hello Christopher -
Thank you for taking the time to report this issue and helping to make Ubuntu
better. Examining the information you have given us, this does not appear to be
a bug report so we are closing it and converting it to a question in the
support tracker.
This is more a proper
** Changed in: grub2-signed (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842518
Title:
package grub-efi-amd64-signed 1.34.20+2.02~beta2-9ubuntu1.17
Nachiketa Roychoudhury; Hello -
I be that harbinger of ill news.
As "DistroRelease: Ubuntu 14.04"
"Ubuntu 14.04 LTS (Trusty Tahr) was the 20th release of Ubuntu. !End-of-life
was April 25th, 2019. Paid support (ESM) is available."
The software repository no longer exists.
-All good things
Joanna; hello
Provide some background information, please.
You show booting a 4.8 kernel on the xenial (16.04) release.
However !
linux-image-generic xenial == Version 4.4.0.154.162 (xenial)
linux-generic-hwe-16.04 == Version 4.15.0.54.56 (bionic)
xorg == Version 1:7.7+13ubuntu3.1 (xenial)
Try and push this along.
Is this a packaging error ? As the Xorg file indicates:
4.976] (==) ModulePath set to "/usr/lib/xorg/modules"
However, the nvidia directive does not exist there:
sysop@x1904:~$ ls -al /usr/lib/xorg/modules
total 864
drwxr-xr-x 5 root root 4096 Nov 14 23:26 .
drwxr-xr-x
Update:
With today's update - kernel 4.18.0-11-generic and new nvidia files - the 390
version driver does install however does not load.
see the attached /var/log/Xorg.0.log, and /var/log/gpu-manager.log .
What is promising is 'lshw' shows the nvidia driver as loaded/
sysop@x1904:~$ sudo lshw -C
** Attachment added: "gpu-manager.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1803275/+attachment/5213591/+files/gpu-manager.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sudo apt purge nvidia-dkms-390 successful in also removing nvidia-driver-390*.
However, sudo apt install nvidia-driver-390 results in same error condition of
"Errors were encountered while processing:
nvidia-dkms-390
nvidia-driver-390
E: Sub-process /usr/bin/dpkg returned an error code (1)
"
** Attachment added: "build log file"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1803275/+attachment/5212508/+files/make.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Loading new nvidia-390.87 DKMS files...
Building for 4.18.0-10-generic
Building for architecture x86_64
Building initial module for 4.18.0-10-generic
Error! Bad return status for module build on kernel: 4.18.0-10-generic (x86_64)
Consult
Public bug reported:
command: ' redshift -l 35.458866:-92.033032 -t 5500:4000 -b 0.8:0.6 & disown '
works as expected in 18.04, however, in 18.10 and 19.04 fails with the
advisements:
"Failed to start adjustment method randr.
Trying next method...
Using method `vidmode'.
Waiting for initial
apt update results with the warning:
(appstreamcli:1748): GLib-CRITICAL **: 12:54:05.288: g_atomic_ref_count_dec:
assertion 'g_atomic_int_get (arc) > 0' failed
Proceeding to install the upgrades >>
Possibly unrelated, but, Since seeing the warning and upgrading packages I have
experienced the
18 matches
Mail list logo
