Public bug reported:
I am using Ubuntu Studio 8.10, 64-bit version.
To reproduce the bug: start kompozer, type some text in the new page,
highlight it and click "Format". kompozer will crash.
** Affects: kompozer (Ubuntu)
Importance: Undecided
Status: New
--
kompozer crashes when
I'm seeing the same problem (the "Error initializing camera: -60: Could
not lock the device") with Jaunty Jackalope beta and a Kodak Z712 IS.
Under Intrepid Ibex, it worked like a charm.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You receiv
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25249767/Dependencies.txt
--
linux kernel 2.6.28-11-generic fails to find /dev/disk/by-uuid/[number] and
drops to shell
https://bugs.launchpad.net/bugs/359620
You received this bug notification because you are a member of
Public bug reported:
I am running Jaunty Jackalope beta, and updated this morning, which
apparently included an update to the 2.6.28-11 kernel. When I restarted,
the boot failed, with the message
ALERT! /dev/disk/by-uuid/cf103646-c12b-4573-89ed-cf0387df4cd8 does not exist.
Dropping to a shell!
a
I have a homebrew system with
Sempron 2400+
512 MB RAM
160 GB hard drive
ECS KT600A motherboard
I had difficulties with the nVidia MX400 AGP graphics card I was using,
and upgraded to an MX4000 card. (This was with Breezy Badger.) I then
started to have the bug reported here: display locks, x.org
Public bug reported:
Using Ubuntu Studio based on Hardy Heron beta, 64-bit w/AMD Athlon 64
x2. The other computer involved is a 32-bit Sempron running Gutsy
Gibbon. I followed instructions on http://czarism.com/easy-peasy-ubuntu-
linux-nfs-file-sharing to make a directory on the Gutsy system
avail
I can confirm that the problem Antje H. describes is still present in
Karmic Koala.
--
users-admin deletes privileges granted to ADS domain users with the command
line utility (adduser)
https://bugs.launchpad.net/bugs/164475
You received this bug notification because you are a member of Ubuntu
B
I made the changes described in comment #6, after disabling the on
motherboard graphics/sound, and my system now indeed recognizes the
audio device(s) on the GT220 card:
$ aplay -l
List of PLAYBACK Hardware Devices
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdev
Yes, I added the repository to my sources.list, installed the linux-
alsa-driver-modules-2.6.xx-xx that matches the kernel installed on the
computer, and added the line
options snd-hda-intel enable_msi=0 probe_mask=0x,0xfff2
to /etc/modprobe.d/sound.conf (had to reboot twice; I mistyped
enabl
So for card #n, n - 1 0x, and then a 0xfff2. Got it; thanks!
--
support for Nvidia GT220 is missing
https://bugs.launchpad.net/bugs/550655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Make that n; I can't put -1 of something in the file. :)
--
support for Nvidia GT220 is missing
https://bugs.launchpad.net/bugs/550655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Confirmed; works like a charm. Thank you!
--
support for Nvidia GT220 is missing
https://bugs.launchpad.net/bugs/550655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
My situation appears to match Mihai's; despite the report, I can still
change size, switch format, etc.
--
ClearWeatherScreenlet.py crashed with TypeError in show_error()
https://bugs.launchpad.net/bugs/420747
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I'm seeing this error also, though as far as I can tell, it doesn't
preclude the installation or upgrade of other packages I've installed or
upgraded so far. On my system (an RPi4, 8GB, with Ubuntu 20.10 installed
with Berryboot), /boot/firmware exists, but it's just a plain directory
and not a mou
Public bug reported:
This cccurred when upgrading to 18.04 final beta.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.7+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
Uname: Linux 4.15.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvid
Public bug reported:
After my system was upgraded from linux 3.13.0-149 -> 3.13.0-151, my
windows 7 virtual machine fails to boot. I tried both my existing disk
image, and the windows 7 installer. Both either hang early in the boot
process or enter a reboot loop. The windows 10 installer boots
For me, it's counterclockwise. I tried setting the "lock rotation"
option referenced in https://askubuntu.com/questions/874487/ubuntu-
gnome-16-10-screen-orientation-spontaneously-changes (had to switch to
Unity 8 to find it), but it didn't make a difference when I logged back
in under Cinnamon, th
Had the same problem this morning. After problems trying to get the
334.21 NVIDIA driver installed on Mint for a new 750Ti card, I decided
to just install the Ubuntu 14.04 and then use a PPA with the driver I'd
found. The install went smoothly, I *think*. Part way through, the
graphics on the scree
While I did not install grub myself, I did put it on the wrong drive, as
I noticed when reinstalling. Corrected that (and told it not to install
proprietary drivers during the initial install, so it wouldn't try
something that didn't (quite) work on a recently acquired 750Ti graphics
card and I cou
Today I grabbed the daily build of 17.10 and booted into it from a USB
drive. It still rotates--but at times I can't predict, the screen will
blank out and then come back rotated. (Should I create a new bug for
17.10?) I should mention that this happens on my laptop, an HP Pavilion
with AMD graphic
Public bug reported:
I was using the Kubuntu 17.10 from a couple of days ago to install,
written to a USB flash drive, to install 17.10 on my desktop (an attempt
at upgrade failed--I was doing other things while the upgrade (from the
command line) was preparing packages for installation, and when
Happened to me when upgrading from 15.10 to 16.04 Beta 2. The UPS
battery was fully charged, but during the upgrade the battery icon
showed the battery as fully discharged and the computer was shut down
before the upgrade completed.
--
You received this bug notification because you are a member o
Public bug reported:
I am trying to install 16.04 to use UEFI rather than legacy BIOS. I
looked at the instructions and created a 200 MiB FAT32 partition as it
said I should. I did not specify a mount point--it said that the
installation would cause it to be mounted at /boot/efi.
I expected the i
After reporting, I realized I'd forgotten to mark the partition as
bootable. Doing so did not by itself solve the problem.
Contrary to https://help.ubuntu.com/community/UEFI ("Mount point:
/boot/efi (remark: no need to set this mount point when using the manual
partitioning, the Ubuntu installer w
I am seeing this as well; grabbed the i386 ISO yesterday (2011-10-16),
and my netbook has been sitting in "Configuring target system" for
something like half an hour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
I am using Ubuntu 12.10 (64-bit), and the glabels version I'm using is
3.0.0-3ubuntu1.
I don't believe this is the same bug as #300550, because while I do have
quite a few fonts installed, I've not seen this level of slowness until
upgrading to 12.10; glabels 3.0.0 does have
** Description changed:
I am using Ubuntu 12.10 (64-bit), and the glabels version I'm using is
3.0.0-3ubuntu1.
I don't believe this is the same bug as #300550, because while I do have
quite a few fonts installed, I've not seen this level of slowness until
upgrading to 12.10; glabels
Yesterday this started happening to me. Until then I was able to connect
my Cowon S9 and have it mount automatically, but now I get an "Unable to
mount COWON S9 Not Authorized" popup. I typically connect it and use
gpodder to get current podcast episodes on it each weekday before work,
so most like
Strange. After updating and rebooting, I can once again mount the Cowon
S9. Attached is the diff between dpkg.log before and dpkg.log after.
** Patch added: "dpkg.log.diff"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/518533/+attachment/1621356/+files/dpkg.log.diff
--
Unable to mo
29 matches
Mail list logo
