I'm on Ubuntu 19.04 as well and having issues with this.
I have an i7-8750h paired with a gtx 1050ti in a Dell G515.
I don't exactly what I did, but I can give a general idea:
I decided this morning that battery life was important to me, so I
tinkered around with TLP. After I did that
Still present in 19.04, although as a workaround, the nvidia drivers
have reverted to installing without modeset=1, so external monitors
work, and Optimus users get dreadful tearing on their laptop's internal
screen.
With modeset=1 (which in my case was a setting preserved during the update to
** Description changed:
When played in Totem some videos will play sound but video output is a
series of green and pink screens (see screenshot).
+
+ Problem appeared following update to 19.04, all files played fine under
+ previous releases.
When run from the commandline Totem gives
Public bug reported:
When played in Totem some videos will play sound but video output is a
series of green and pink screens (see screenshot).
When run from the commandline Totem gives the following error.
(totem:1601): Gtk-WARNING **: 20:03:46.890: Drawing a gadget with
negative dimensions.
Public bug reported:
Description:
CPU usage spikes to 110-130% (across 4 cores) when a large document (~260
pages, mainly text) is opened.
Steps to reproduce:
Open large document
Observe CPU spike and fan spin up
Close file
Observe CPU drop and fan spin down
Expected result:
Small spike in CPU
bug could have been received by email on yahoo on another linked
computer
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1823698
Title:
dont know
Status in xorg package in Ubuntu:
Public bug reported:
could be via email ?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
Thanks Olivier, I changed my mount point (under /media) and it's
working fine now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1820543
Title:
[snap] libreoffice can not see
Public bug reported:
I have a encrypted luks volume which is under lvm management. I mount it
manually from a script.
It's mounted to /opt1
the libreoffice snap does not see this mounted directory; it is not part of the
filesystem known to the snap.
** Affects: libreoffice (Ubuntu)
I had the same issue a few weeks ago, now however with 3.31.92 (on
Disco) I do get the configuration dropdown when selecting my HDMI Audio
device. It came up blank initially, but appears to have saved the
correct setting since.
--
You received this bug notification because you are a member of
Hi Peter,
Thanks for your bug report.
I was one of the original authors the system-monitor extension however
no longer actively involved in the project. gnome-shell extensions are
not supported by Canonical/Ubuntu (unless they are installed in the
default session) or GNOME. You would need to
/bugs/1716857
>
> Title:
> gdm3, hybrid nvidia with modeset=1, no external monitors detected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions
>
--
Tim Richardson
--
You received this bug not
gdm3, hybrid nvidia with modeset=1, no external monitors detected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Desktop
P
bug 1725676 is about not being able to select a different keyboard
layout while this is about being able to select a different layout, but
it not actually working. It's unrelated.
bug 1652618 sounds similar, but the solution makes it seem to be
different. I went in and changed the settings to
apport information
** Tags added: apport-collected bionic
** Description changed:
I was using 16.04 with Dvorak and US-Qwerty keyboard layouts and was
able to utilize both on the login screen. My default layout was Dvorak
(defined in /etc/default/keyboard).
When I upgraded to 18.04
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1813304/+attachment/5233767/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1813304/+attachment/5233768/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
I was using 16.04 with Dvorak and US-Qwerty keyboard layouts and was
able to utilize both on the login screen. My default layout was Dvorak
(defined in /etc/default/keyboard).
When I upgraded to 18.04 the login became Dvorak only, but after some
searching I found the
Public bug reported:
https://snapcraft.io/network-manager lists the description for
NetworkManager as “Network management based on NeworkManager” (sic).
NeworkManager should be NetworkManager.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: snap
I switched to KDE to have a look at it, by installing KDE Neon from the
PPAs. Otherwise the same environment. The slow suspend doesn't happen in
plasma, it suspends in five seconds, while still suspending properly
(including open VMWare virtual machines). So it's not simply Chrome, the
bug needs
sddm works too: I just put kde plasma on my ThinkPad P50 with ubuntu
18.10, it works well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
gdm3, hybrid nvidia with
Still present in 18.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/996552
Title:
file roller does not open files with odt ending
Status in File Roller:
New
Status in
Bug still exists in 18.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/887331
Title:
file-roller cannot open filetypes with derived mimetypes (e.g. epub
and ods files)
.launchpad.net/bugs/1600622
>
> Title:
> Screen doesn't lock or go to sleep when certain Chrome tabs are open
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
>
--
Tim Richardson
--
You re
sleep when certain Chrome tabs are open
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Desktop
Packages,
The second error message is when specifying the exact path in the script like
this:
lo_proc =
subprocess.Popen(shlex.split("/snap/libreoffice/current/lib/libreoffice/program/soffice
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo
--nodefault"))
--
You received this bug
Public bug reported:
It's not possible to use pyoo, which uses the Uno connector to
Libreoffice, on a machine where the Libreoffice Snap is installed. The
pyoo/Uno connector works fine with the libreoffice Apt packages.
To reproduce run this script:
#!/usr/bin/env python3
import pyoo
import
apport-collect -p xorg wants to run some tests an other users? under
ssh session, this asks for passwords, but still is writing s to the
display. I'm not sure it took my authentication. Should I run as root?
then it won't have my cached credentials. Trying again under -39
--
You
Last ones are from no-display -38 kernel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/174
Title:
Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36
Status in
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205592/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205581/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DkmsStatus.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205580/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205588/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205587/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205591/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205590/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgConf.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205589/+files/XorgConf.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205586/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205585/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205584/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205583/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/174
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205582/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/174
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205579/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205577/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205578/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Description changed:
Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
running on VGA, DVI and display port all connected to the dock. BIOS
mode set to run external displays ONLY with nvidia chipset. prime-select
nvidia run.
When running under
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205575/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205573/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205574/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgConf.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205572/+files/XorgConf.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205564/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DkmsStatus.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205563/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205571/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205567/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205569/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205568/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205570/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205566/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/174
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205565/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/174
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205562/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Both apport-collect logs are already attached. Xorg.0.log from -38
already attached. Adding -39
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/174
Title:
Xorg loads, no display on
** Attachment added: "Xorg.0-39.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+attachment/5205558/+files/Xorg.0-39.log
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
** Tags added:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205561/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ".proc.driver.nvidia.params.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205559/+files/.proc.driver.nvidia.params.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205560/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Fixed for me, I didn't do anything different or change anything, I guess
one of the Ubuntu updates must've fixed it
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Probably the tracker patch needs to be updated, there seem to be a
couple of new modules using tracker that didnt exist when I wrote that
patch.
Upstream last I check only supports optional tracker at build time. Not
run-time detection like we did in distro patches in Ubuntu.
--
You received
** Bug watch added: Debian Bug tracker #908800
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800
** Also affects: nautilus via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
thumbnailers are working fine for me, both tiff and jpg, perhaps there
is still a missing dependency, that is normally otherwise pulled in by
vanilla-gnome-desktop. I generally only test gnome3-staging on systems
with that meta package.
Can you file a separate bug for nautilus not starting
can you try reinstall tracker 2.1.3 and see if that file exists on your
filesystem? If it doesnt please run apport-collect which should
colllect your dpkg/apt logs.
see this page for manually getting backtraces
https://wiki.ubuntu.com/DebuggingProgramCrash
On 12/09/18 18:06, Harry wrote:
> I
Hi Harry,
Thank you for your bug report.
I am running nautilus 3.30 with tracker 2.1.3 on two system and they
are both working, so we will need some more info. Thumbnails are working
also
That default.rule file does exist in the tracker 2.1.3-1~cosmic1
package, is it not installed on
Public bug reported:
nvidia-prime 0.8.9
with display manager lightdm, choose the nvidia driver on my Optimus Thinkpad
P50 does not work.
the nvidia driver does not load.
It works with gdm3, and so does prime-select intel (only tested in x.org
session so far)
** Affects: nvidia-prime
Yes have been testing on cosmic.
they are both on gnome3-team/gnome3-staging ppa. Tracker is at 2.1.3
there, but has already my patch that was the only change in 2.1.4.
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+sourcepub/9389719/+listing-archive-extra
Public bug reported:
To go along with the rest of GNOME 3.30
Both tracker and tracker-miners 2.1.4 will be synced from Debian.
tracker is not installed by default on any Ubuntu Flavours, but does
provide an important part of the GNOME-Shell experience.
These releases bring lots of fixes and a
Hi Ryan, my solution uses bbswitch to turn off the card, which is what Ubuntu
used before 18.04. If it works for your hardware in 16.04 (up to and including
17.10) it will work in 18.04. Also if it was working and then stopped working,
it must be something you did.
If you'd like support
I tried downgrading wpa-supplicant (mentioned by Lauwie), and it did not
help this.
If Petr is correct, the fix would actually require downgrading OpenSSL
(or whatever used to supply the missing 3DES cipher prior to Bionic),
right?
What's the Ubuntu equivalent of the Fedora workaround for this?
I found this worked around the problem (Dell XPS 9360):
Open alsamixer, enable sound on 'Headphone' (next to 'Master'). If there's a
hissing/popping sound in the background but sound at 0 on 'Headphone Mic Boost'
--
You received this bug notification because you are a member of Desktop
uBlock fixes it for me and others ... But there should be some user
control
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep
It looks like the problem here is that the Brother's official driver installer
is installing an outdated driver file. This was found previously:
https://forums.linuxmint.com/viewtopic.php?t=262330#p1425901
instead of downloading and installing the latest brscan4-0.4.5-1.amd64.deb
it is
hread 7 "scan-thread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd8f7c700 (LWP 4914)]
0x7fffd866a26f in make_cache_block ()
from /usr/lib/x86_64-linux-gnu/sane/libsane-brother4.so.1
(gdb) where
#0 0x7fffd866a26f in make_cache_block ()
from
Public bug reported:
I have a Brother MFC-L2710DW printer/scanner combo. I set it up in
ubuntu 16.04 using the manufacturers installer (via wifi). I can print
to it fine. When I run simple scan and select the scanner in
preferences, and choose to "scan all pages from feeder", it begins the
I've made a few tweaks which you can see here
https://github.com/timrichardson/Prime-Ubuntu-18.04
it now works between reboots. I should do a fresh install to make sure
it works without action. For example, I've made a note that after
install I did
sudo systemctl enable prime-socket
the
Matthieu's code is the best solution I've seen, as long as you are ok with
lightdm.
The multi-dispatch aspects of the new module are a good simplification,
Matthieu's approach looks like it's now easy to switch between intel and hybrid
modes; he just blacklists modules.
Dear maintainers, it
Removing amdgpu-pro by running "amdgpu-pro-uninstall" from ubuntu
recovery mode solved this problem for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1762127
Title:
Ubuntu stuck in
Public bug reported:
Install failed after upgrade from 16.04 to 17.10
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: totem-plugins 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm
You should read the changelog.
nvidia-prime doesn't use bbswitch anymore, I don't know why. The
changelog doesn't say.
It now uses the built-in kernel mechanism for turning off the nvidia card.
Unfortunately, this method requires the nouveau driver and unfortunately you
can't load the nouveau
I can not reproduce this. Have marked invalid.
** Changed in: nvidia-prime (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1765887
Title:
This is not a new problem, and it affects every gdm3-based distro that I have
used. Long story short; if you want to use modeset=1 with nvidia to get rid of
tearing (which would be every linux Optimus user on the planet), gdm3 doesn't
work. No one seems to know why.
Change your display manager
*** This bug is a duplicate of bug 1765363 ***
https://bugs.launchpad.net/bugs/1765363
** This bug has been marked a duplicate of bug 1765363
prime-select intel is not powering off the nvidia card
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
The new prime-select has some problems.
It is very slow to switch, since it does initramfs -u each time
It leaves my two optimus laptops without graphics if you leave it in
prime-select intel but boot with discrete nvidia. Previously this would load
nvidia drivers.
These
Public bug reported:
I don't know how to replicate this bug yet, I will update if I learn more.
Several times as I test prime-select on my Thinkpad P50, I have ended up in
situations where the laptop will not start graphics. This always happens if you
leave the laptop in prime-select intel and
However, I do not have this problem on my Thinkpad P50. The nvidia card
is definitely turned off when in hybrid graphics after prime-select
intel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
Public bug reported:
Right now, it seems that prime-select intel makes sure the nvidia driver is not
loaded, as nvidia-settings reports.
But my power consumption is > 20W.
cat /proc/acpi/bbswitch reports the card is still on.
If bbswitch and powertop are reliable, then the nvidia card is
Public bug reported:
1) to save power, sudo prime-select intel
and boot in hybrid graphics
This is the only way I know to get the nvidia card off which is the only reason
I boot like this
This still works, although it is really slow.
2) to go back to multi-monitors, reboot, at bios turn on
attachment is generated by the nvidia-bug-reporting tool, which collects
many logs
** Attachment added: "nvidia-gathered logs"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1764089/+attachment/5116362/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you
Public bug reported:
I have a Thinkpad W520. In Optimus mode, lightdm presents a blank screen after
login. Virtual terminals work.
On the same laptop, gdm3 allows me to log in to ubuntu desktop.
In pure Nvidia mode, login works.
The bug report tool told me that log files will be attached.
also includes libzip 1.5.1 release from today
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libzip in Ubuntu.
https://bugs.launchpad.net/bugs/1674057
Title:
[FFe] upgrade libzip to version 1.5.0
Status in libzip package in Ubuntu:
I landed this in a silo, at Laney's request.
https://bileto.ubuntu.com/#/ticket/3230
ignition-fuel-tools:s390x is dep wait, as it also is in the archive,
everything else built fine on all arches.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Changing back to confirmed, we still need to work out what to do with
smbpasswd.
** Changed in: nautilus-share (Ubuntu Bionic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus-share in
Packaging should be good to go now, pending FFe approval. All remaining
debian/patches are upstream cherry-picks that will be included in next
upstream release.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libzip in Ubuntu.
301 - 400 of 1937 matches
Mail list logo
