Yes, this seems to be fixed for me now on Kubuntu 12.04 using libdrm
from precise-proposed on a Dell Precision T1650 with Xeon E3-1225 V2
CPU P4000 integrated graphics.
Thanks - much appreciated.
root@blackbox:~# lspci -nnvv | fgrep Graphics
00:02.0 VGA compatible controller [0300]: Intel
** Attachment added: lightdm.log
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/870373/+attachment/2525443/+files/lightdm.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in 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/870373
Title:
guest session will not open
Status in “lightdm” package in Ubuntu:
New
Bug description:
What I expected to happen:
Public bug reported:
What I expected to happen:
By choosing the guest session option (either from the login screen or
the user menu when logged in to a normal account) a guest session should
be launched.
What happened instead:
By choosing either method, the screen goes blank for a moment
Done. Please find attached the terminal output.
Incidentally, I made a new install on another partition, this time from
the release version of 11.10, and on that I can open a guest session
without a problem (just to be clear, the terminal output is from the old
install).
** Attachment added:
This happened to me yesterday in kubuntu 10.04. Resolved it with
service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start
This is nasty - if you can't get a network connection up manually and
don't have any other web access, it's very difficult
The following bug report:
https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/840082
reports the same bug, and offers a workaround. I don't want to mark this
one as a duplicate because the other is lodged against gnome-net-tool,
which isn't the right program.
--
You received this bug
I'm seeing the same issue with Kodi crashing in the same manner on
startup, with the same resolution (package downgrade).
This may be related to an internal Nvidia bug ID: 1835736
This is referenced here:
Public bug reported:
On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that
Ubuntu 22.04 currently includes exiv2 0.27.3
Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file
format has been the Canon camera-raw file format since mid 2018, and is
probably one
>
> I am uploading exiv2 now to Ubuntu as packaged in Debian.
>
I just looked at
https://ftp.debian.org/debian/pool/main/e/exiv2/exiv2_0.27.5-1.debian.tar.xz
and I don't think it enables BMFF at build time, so I don't think this will
enable CR3 support:
$ grep ENABLE debian/rules
Many thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1959508
Title:
enable BMFF support in exiv2
Status in exiv2 package in Ubuntu:
Fix Released
Status in exiv2 package in
*** Bug 13393 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 gtk2-engines-oxygen in Ubuntu.
https://bugs.launchpad.net/bugs/1309132
Title:
oxygen-gtk2 makes scilab crash
Status in
(In reply to Sergio Callegari from comment #10)
Could be useful to list the issue and the workaround somewhere with the
scilab release notes, though, to prevent this bug from being reopened
multiple times and to help users who may encounter this issue
release notes added at
(In reply to Sergio Callegari from comment #7)
The issue is also present in the just released kubuntu Trusty (14.04 that is
a release with long term support). Also here, moving away from
gtk2-oxygen theme fixes the crash. There is a bug open in ubuntu's launchpad,
but is declared invalid as
Solved?
Thanks for this forum Ubuntu. I'm a Fedora user, but I frequently find
solutions here
I have an XPS 9550 along with the issue of the headphone microphone not
working. I changed /etc/modprobe.d/alsa.conf from:
options snd-hda-intel single_cmd=1 probe_mask=1 model=dell-headset-multi
I encountered something very similar to this issue (maybe even this
issue?) when my docker containers could not start (using snap on Ubuntu
20.04.3 LTS under VirtualBox with a Windows 10 host). Similar to others,
`sudo apt install libblockdev-mdraid2` seems to have fixed it.
In case these log
16 matches
Mail list logo
