@sbeattie I tested the package you built for 22.04 and it fixes the
problem for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults and assertion failures
@sbeattie It's broken in mantic too. In xwayland, the window dies. in
xorg, the session crashes, badly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults
Yeah, for me it crashed 100% of the time with no changes, and removing a
configuration file (which among other things removed my non-default
preference for grayscale antialias) completely stopped the crashing.
This is in a kvm/qemu VM. So from my perspective, and from a few others
users, it looks
for what it's worth, JetBrains bug reports find that the problem is
triggered by requesting grayscale anti-aliasing.
https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I use the wayland session. I sort of have this bug. The screens do power
off, but then the backlights resume. It is still a blank screen
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
ifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions
>
>
--
Tim Richardson
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.ne
screenshot 2, chatgpt suggestion which contained the fix
** Attachment added: "firefox_bug_2.png"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726921/+files/firefox_bug_2.png
** Description changed:
- I have the mozilla stable version installed using the
screen shot of icon problem
** Attachment added: "firefox_bug_0.png"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726922/+files/firefox_bug_0.png
** Description changed:
this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
Public bug reported:
this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
firefox-desktop-file-missing-startupwmclass/37400
I have the mozilla stable version installed using the mozilla binary
method, and snap for the beta channel. The snap icon is broken, both in
the menu entry
This is happening in lunar beta 23.04,.
I install nautilus-share.
Turned on sharing in Gnome preference (both options)
When attempting to share a folder:
'net usershare' returned error 255: net usershare: cannot open usershare
directory /var/lib/samba/usershares. Error Permission denied
You do
see also https://bugzilla.redhat.com/show_bug.cgi?id=2072070 for lengthy
discussion.
** Bug watch added: Red Hat Bugzilla #2072070
https://bugzilla.redhat.com/show_bug.cgi?id=2072070
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Ubuntu 22.04.
I still have this problem
intel-media-va-driver 22.3.0
tigerlake laptop
$ apt-cache show intel-media-va-driver
Package: intel-media-va-driver
Architecture: amd64
Version: 22.3.0+dfsg1-1
tim@ochre:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API
(... Ubuntu 21.10)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
Status in evolution-data-server:
Unknown
Status in
I used proposed-updates today to get the latest evolution, and contact sync
works again.
So 3.40.4-1ubuntu2 works. (amd64 arch)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
No data available from (1) or (2) and the problem has not reoccurred.
I have commented line 23 of crashdb.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1927767
Title:
All
//bugs.launchpad.net/bugs/1816497
>
> Title:
> [snap] vaapi chromium no video hardware decoding
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
>
--
Tim Richardson
--
You received this b
I just installed Ubuntu 20.10 on a machine that was running Pop!os 20.04
and 20.10 (a fairly new AMD Ryzen desktop system, different to the
machine I had the problem on earlier, which was a laptop). Not 24 hours
later, this problem again. I thought there was something wrong with Team
app ('bloody
My sound control panel reports three speech-dispatcher entries in Volume
Levels. I don't know why.
My session is about two days old and I haven't had any instance of
distortion, so the workaround referred to in my previous comment, a
config change, may be a good idea for package maintainers to
If you want to test this, force YouTube to serve H264, which your card
supports judging by the vainfo results. A 4k 60fps YouTube video won't
be in a codec your hardware can handle, I guess. There are 'h264ify'
extensions for Chromium.
--
You received this bug notification because you are a
I will try this workaround/config change:
https://github.com/brailcom/speechd/issues/198#issuecomment-619605269
** Bug watch added: github.com/brailcom/speechd/issues #198
https://github.com/brailcom/speechd/issues/198
--
You received this bug notification because you are a member of Desktop
This bug started affecting me in the past week although I've been on
20.04 since launch. I have removed the packages including orca.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to speech-dispatcher in Ubuntu.
@vasyl: thanks, good comment. It pays to RTFM, apparently.
--
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/1765363
Title:
prime-select intel is not powering off the nvidia card
For me in 20.04, bug is definitely still present. I have earlyoom active, and
32 gb a few seconds of "freeze" (which is not really a freeze) earlyoom
activates and nukes a few things, including Firefox, which brings back
interactive response. It also killed Chrome and Remmina, which was
I have been investigating other bug reports. I can't find anything that
helps my very much, but I did note references to timing. It is very
puzzling why I don't have problems when booting from the installation to
an external drive. That drive is actually a USB stick (ext4 formatted).
My internal
I have been trying to work out how to log a failed session with plymouth debug
messages. I finally succeeded, it is attached.
Note that at the end of log file, it goes into suspend. That was me trying to
power off the machine, and not holding the button long enough. It actually
suspends and
I installed 20.04 beta on a usb drive on the same machine, and reinstalled
packages to resemble my main install as closely as possible. The bug does not
occur when booting from the usb drive.
The most significant difference I can think of is that the main install is on
an lvm partition
** Attachment added: "boot messages with plymouth debugging messages"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in
** Summary changed:
- booting with splash hangs when external monitors are connected (pure intel
laptop)
+ booting with splash hangs when external monitors are connected (pure intel
8th gen laptop)
** Description changed:
+ I think this is a problem with the splash boot loader. This problem
** Summary changed:
- booting with splash hangs when external monitors are connected
+ booting with splash hangs when external monitors are connected (pure intel
laptop)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "journalctl -b-1 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
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/1872159
Title:
booting with splash hangs when external
@Alberto, couldn't prime-select do this when going into hybrid or
Optimus mode? Only users with nvidia hybrid graphics would go down this
logic path, and they are only ones who need the fix (but only if they
are using gdm3, sddm and lightdm continue to be unaffected by this)
The set of users who
This bug persists in 20.04 daily.
The one-line Pop!OS solution
(https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26)
works, just logout and login.
Pop!OS has used this for several releases now, just saying.
** Summary changed:
- nvidia-drm.modeset=1, gdm3 and optimus
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => Fix Released
--
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/1765888
Title:
Please revert to debian-alternatives
You are correct. Thanks. I was so puzzled by this.
I am using KDE. Possibly the network manager interface is different. This is
what I did.
Imported the openvpn config file into networkmanger. It makes a connection, it
times out, and no amount of debugging gives any more hint.
I edit the
I haven't had this problem for several releases, so it is only triggered
under some circumstances. I suspected the hangouts extension (which I no
longer use)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
A very similar thing just happened to me, with the 435 drivers via ppa.
Reverting to 430 solved it. Ubuntu 19.04, P50. USB mouse works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
> nvidia-drm.modeset=1 results in no monitors detected by Xorg
>
> 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 D
"gdm3 compile without wayland", I meant
--
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:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
Status in gdm3
What we know about this bug is that gdm3, nvidia and modeset=1 is broken
under configurations which are not broken when sddm and lightdm are
used.
we know that gdm3 sessions with external monitors work with root
permissions.
we know that gdm3 compiled with wayland also works (according to the
I posted here:
https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in-
modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes-
it-is-an-nvidia-bug/?offset=3#5351122
--
You received this bug notification because you are a member of Desktop
Packages, which is
User generix reports that when gdm3 is compiled without wayland support,
this bug is not seen.
--
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:
nvidia-drm.modeset=1
I will post your findings to the nvidia developers forum.
--
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:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
Hi Daniel, thanks for not forgetting about this, unlike everyone else :)
Have you communicated this observation to Nvidia at all?
--
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
This works. Thanks. What does gdm3 do that requires this?
--
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 modeset=1, no external monitors
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
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)
/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
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
.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,
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
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
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
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
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.
gdm3 and nvidia binary drivers don't work together yet. Maybe 18.04 although
there's not much evidence that anyone who knows how to fix this problem is
working on it.
This problem has emerged since the default Ubuntu session now uses gdm3 (as of
17.10) but standard gnome users on all recent
Celebratory fireworks from me.
It seems to work. For ubuntu the only difference is
[Service]
ExecStartPre=/usr/share/gdm/generate-config
becomes
[Service]
ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config
I have a proper ubuntu gnome session running with gdm, an external
monitor
ubuntu user Hon Weng Chong has emailed me as he continues to investigate the
problem.
He believes he has proof that it is is GDM configuration issue and has provided
the following fix
Hey Tim,
I figured out a hack solution to the GDM prime issue. If you replace
#22 worked for me, after logout/login.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1620806
Title:
gedit edit window is transparent when using Ambiance and Radiance
themes
Status
** Summary changed:
- no gdm3 greeter with nvidia quadro and modeset=1
+ no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not
optimus)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Context:
17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia
driver.
ubuntu desktop (gnome shell), fresh install
ThinkPad W520 in Nvidia Optimus bios mode.
Nvidia profile.
Result:
no external monitors are detected.
xrandr does not even list them
As of the latest updates to gdm3, I still can't boot with my laptop when it's
in discrete mode (nvidia graphics only). Does not get to the greeter.
syslog is full of countless repetitions of "Stopping NVIDIA persistence
Daemon".
CPU must be high because the fan comes on. I've reported this but
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+attachment/4943940/+files/Error_syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
This is to track
https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1
causes loop, does not launch greeter "
I don't know if this is an nvidia bug or a gdm3 bug but it requires both
to reproduce.
[reply] [−] Description t...@tim-richardson.net
I've been testing 1.19.x in 17.04 pre-release for a few weeks, hoping to
take advantage of the Nvidia PRIME synchronisation fix for laptops with
Optimus hybrid graphics. As of 1.19.3, PRIME sync works (with a modprobe
fix related to the nvidia driver). This is a huge improvement for nvidia
Optimus
I have a ThinkPad P50 and Prime sync is now working for me. I don't know
what change happened, sorry; it was two weeks since I did an update, and
it could be an updated kernel or updated xserver packages from Timo's
PPA. I have the 375 driver. And it works really well, it's marvellous
to behold
The bug is fixed. No more assertion, no more crash.
A message informs me that the wired connection is now established.
Then the next message says that the "ethernet" connection is disconnected.
Despite that final message, the change from VPN to normal wired connection now
works fine.
--
You
It is not fixed for me. I have proposed-updates and the network-manager
version is 1.2.0-0ubuntu0.16.04.2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1578962
Title:
I hvae reported this bug here, where I am adding information in response
to questions:
https://bugzilla.gnome.org/show_bug.cgi?id=765830
** Bug watch added: GNOME Bug Tracker #765830
https://bugzilla.gnome.org/show_bug.cgi?id=765830
--
You received this bug notification because you are a
buntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1576162
>
> Title:
> network-manager crashes when exiting a vpn connection
>
> To manage notific
Public bug reported:
i have an openvpn connection configured. i use network manager to
connect successfully. later i use nm to swap back to the wired
connection. network-manager crashes, the icon is gone. however, the
connection does change.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package:
Didn't know it was a button. This works.
** Changed in: unity-control-center (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
Public bug reported:
new install of 16.04
went to add a second admin user via the control center immediately after
install
the user can be created but password is not requested and the user is disabled.
i could not progress via the control panel.
i added a password from the shell.
correct:
Public bug reported:
This is 14.04 32 bit intel.
I have installed OpenVPN access server on another machine. It is configured
with username and password security.
By logging in to it, a configuration file can be downloaded.
I want to set up a VPN network connection for this.
So I go to the
this is a kernel bug. git bisect completed and reported on the upstream
report https://bugs.freedesktop.org/show_bug.cgi?id=76520
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1290787
this is a kernel bug
** Package changed: lightdm (Ubuntu) = linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1290787
Title:
[TOSHIBA Satellite U400] suspend/resume
testing reveals that the bug is linked to lightdm
It is not reproducible when lightdm is not running. When lightdm is running, a
wide range of kernels show the resume fail. These kernels do not fail resume
when lightdm is not running
** Description changed:
does not resume (no backlight on
My bug message is bad. The bug reporting indicates that it is actually a
kernel panic.
Please close this bug. automatic bug reporting was fixed when I changed the
login user to belong to group sudo.
see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721
and
Public bug reported:
Hardware is
*-display:0
description: VGA compatible controller
product: Mobile GM965/GL960 Integrated Graphics Controller
(primary)
vendor: Intel Corporation
physical id: 2
bus info: pci@:00:02.0
I have a Dell D420. The problem still exists in 12.10 although the fix from
comment #24 has fixed the problem after I logged out and back in.
tim@bach:~$ lspci -nn|grep -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics
*** Bug 45416 has been marked as a duplicate of this bug. ***
--
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/817013
Title:
[Upstream] bullet points change to rectangle glyphs
98 matches
Mail list logo
