Public bug reported:
Regular package updates today brought these packages (and a few libpam-
XXX):
grub-common:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3)
grub2-common:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3)
grub-pc:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3)
grub-pc-bin:amd64
Public bug reported:
Steps to reproduce:
- Have Ubuntu installed.
- Install lightdm. This makes lightdm the active window manager, as far as I
can remember.
- Uninstall lightdm.
- Reboot.
Expected result:
- System booting another available window manager (gdm3 in this case).
- At very least
Public bug reported:
Not sure for which package to report this bug, as it shows up in
multiple applications.
Ubuntu 20.04 came with a newer GhostScript, which swapped the Nimbus-L
series of fonts (e.g. Nimbus Mono L, format PostScript Type 1) for a
Nimbus-PS series (e.g. Nimbus Mono PS, format
Installed packages don't matter if their content isn't in use. It does
matter whether you run an X11 or a Wayland session.
To switch between both, log out to get to the login screen. There is a
gears icon right above the password entry field, click on it. This
should open a menu allowing to
If you're running on Wayland it might be related to this:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510
It looks like a busy gnome-shell (or -extension) can eat mouse movement
events, so it might eat keystrokes as well. Second way to reproduce the
issue (for testing whether you
When putting emphasis on a stable system, staying with Xorg is probably
a good idea for the time being. While I use Xwayland daily now, it
definitely comes with a number of quirks.
- Transparency comes and goes. For example, moving a window to near the
top of the screen makes the top menu bar
I can confirm that upgrading to 18.10 solves this issue. While there are
still a few caveats (e.g. toolbar becoming intransparent when launching
an application), the hardware which failed before can now log into
'Ubuntu' as well as 'Ubuntu on Wayland'.
Well done, Ubuntu, thank you very much!
--
Great news! Thank you for your work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Login screen never appears on early generation Intel GPUs (Core2 and
Atom etc)
To manage
Oh, Ubuntu does boot on such hardware just fine. And seeing how well it
works I'd feel guilty of wasting money and polluting the environment
when buying newer hardware.
It does not boot all up into native Wayland. Nevertheless, one can run
X11 just fine.
How to turn Wayland off? Key is to
With 18.04 the situation got worse. Apparently, the login screen tries
to run now on Wayland as well, so the opportunity to turn it off is
gone. Booting simply stops at the Ubuntu logo, with the first of these
five dots filled.
Booting in recovery mode, then choosing 'continue'(?) gives a black
> explain yourselves Ubuntu
Never seen Ubuntu explaining anything, helping people with debugging or
something like this in the last five years. Eventually the problem will
go away some way or another, but even this event most likely won't get
reported. So, don't expect too much.
That said,
Even on a desktop, gnome-software not running all the time makes hardly
a distinction. Searches for software may take a second longer (probably
gnome-software startup time), still it works perfectly fine.
One can try this by killing gnome-software, then searching for something
using the
> "cannot open display" either means ...
Thank you! This is valuable information.
So far I thought that the bug is about gnome-shell not starting. With
this solved, it's now mutter. Well, interesting adventure game :-)
--
You received this bug notification because you are a member of Ubuntu
Daniel, your current efforts apparently put much emphasis on alienating
users capable of fixing bugs. Also on getting rid of allies for low end
hardware support.
I really wish you had put half as much efforts into explaining the
software situation a bit. For example, what does this "cannot open
Success, part II:
When attempting a Wayland session, the relevant syslog section grew from
107 lines to 396 lines. 'gnome-shell' messages are gone, it looks like a
session gets actually started. And then there are now a lot of messages
like this one:
Oct 31 18:08:01 piccard
Success! Applying the attached Diff keeps gnome-shell working for Xorg,
still makes these shader compilation errors going away. More of this
success see next comment here.
This Diff is not a solution, of course, but it should narrow down the
problematic area a lot.
** Patch added:
Great to see you're into supporting "old" hardware. I'm pretty sure the
times when people bought new hardware every other year are long gone.
This G33 PC is a Core2Duo 2.1 GHz and it's perfectly up to speed for all
the daily tasks, including software development.
"Older" hardware also comes with
Intel integrated graphics is probably the most widely used PC graphics
on this planet. The problem is apparently that shaders are called
without being present, which applies to many most recent hardware
platforms as well. Calling it High is more than accurate.
Instead of trying to discuss the
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996317/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected artful package-from-proposed third-
party-packages
** Description changed:
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
Upgraded from 17.04 today.
Steps to reproduce:
- Start the PC or log out/end
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996315/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996316/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996318/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Thanks for the help, @Brian. I thought about the package 'wayland', too,
but trying to report a bug against it came out like this:
$ ubuntu-bug wayland
dpkg-query: no packages found matching wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> It seems that your bug report is not filed about a specific source
package
See, Mr. Bot, if I'd knew the package, I'd report the bug not here, but
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As requested in the other bug I turned on GDM debugging and tried to log
in again. Relevant section (identified by time stamp) see attached.
Totally different set of messages. These appear to indicate something
going wrong:
gnome-shell[5180]: Shader compilation failed:#0120:44(42): warning:
Other than reported at #1726192 I can't get into a Wayland desktop
shortly after a Xorg session either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Wayland does not start up
To
This one sounds similar: https://bugs.launchpad.net/ubuntu/+source
/gnome-desktop/+bug/1726192
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Wayland does not start up
To manage
This one sounds similar: https://bugs.launchpad.net/ubuntu/+bug/1727356
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726192
Title:
17.10 Login To Wayland Fails Unless User Logs Into Unity First
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
Upgraded from 17.04 today.
Steps to reproduce:
- Start the PC or log out/end session in case it's running with an Xorg desktop
already.
- Attempt to log in, using 'Ubuntu'
Expected to happen:
Desktop
Here's a similar, older bug:
https://bugzilla.redhat.com/show_bug.cgi?id=879801 , workarounds
included there, see comments 13, 14, 15.
** Bug watch added: Red Hat Bugzilla #879801
https://bugzilla.redhat.com/show_bug.cgi?id=879801
--
You received this bug notification because you are a
Running kernel -21 from the general repo I managed to grab the attached
output of 'top'. khugepaged going 100%, staying there forever. System
load eventually went up to 8 or more. System didn't freeze entirely,
just slowed down a lot.
** Attachment added: "top"
Had a freeze with -14, too, after 3 days of operations (hibernating at
night)
That said, it doesn't exactly look like there's somebody keen on fixing
this bug. Workarounds like adding swap just postpone the problem. And
Ubuntu folks went silent.
--
You received this bug notification because you
Congratulations for managing to get a backtrace, @Jonas Slivka!
Did you run a kernel with debug symbols, perhaps? My kern.log has zero
backtraces, despite at least 5 freezes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just had kind of a freeze with -17 after about two hours of operation.
While other freezes so far manifested in the cursor vanishing and
everything becoming unresponsive, this freeze resulted in single
applications freezing on input attempts. Like freezing after opening a
menu and selecting
Just had a kernel freeze after some 20 hours of operation with -18:
$ uname -a
Linux piccard 4.10.0-18-generic #20-Ubuntu SMP Wed Apr 5 17:18:34 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Will now try -17 to confirm sles' findings and also to have a working
kernel until somebody has an idea on
Right. Missing video hardware acceleration (and missing audio, ACPI) was
due to the kernel extras package not installed. Corrected this situation
and now giving 4.10.0-18 another try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just booted 4.10.0-18 and graphics apparently fell back to software
rendering. Only one screen size (1600x1200) available, animations run
very slow, CPU fan spins up when moving windows, such things.
Will run this for two days to see wether it's at least not freezing.
--
You received this bug
I'll give -9 an additional day to be sure. If you want to continue,
4.10.0-14 is the next candidate.
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12139078
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the hint, 4.10.0-9 now running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684010
Title:
17.04, i915 freeze on VGA compatible controller: Intel Corporation
Xeon E3-1200 v2/3rd Gen
4.10.0 from mainline works fine here. Running it for two days now
without flaws.
$ uname -a
Linux piccard 4.10.0-041000-generic #201702191831 SMP Sun Feb 19 23:33:19 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
Hmm. 4.10.0 from mainline works, 4.10.0(.19) from the regular repo does not.
Now I'm
> Kernel 4.10.0.19 from the regular 17.04 repo appears to work fine
Too bad, this was a false positive. Today this kernel froze, too.
Firefox became a zombie () twice.
@sles, finding a working kernel is certainly good help for the moment,
but not really a solution. Think of all the people not
Kernel 4.10.0.19 from the regular 17.04 repo appears to work fine,
working for some 12 hours now. It's slightly different than the one
@Vaclav Rehak reported above as not working:
$ uname -a
Linux piccard 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
A few additional debugging bits:
- Here this typically happens when watching video. As if some memory
region gets exhausted after viewing some 100'000 frames.
- I've seen the mouse freezing once, typically it stays movable.
- Audio continues while video freezes.
- I've seen Firefox going (in
One way to fix the issue is to use Visolate latest release, 3.1.1:
https://github.com/Traumflug/Visolate/tree/master/releases
Just download the release file and run it with
java -jar visolate-3.1.1.jar
No package installation other than the Java packages required.
--
You received this bug
These JAR packages work with OpenJDK 8, but not (yet) with OpenJDK 9
(SIGSEGV somewhere in libjava).
Solving this bug would also solve bug #1597782.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried with OpenJDK 8, too, same result.
$ java -version
openjdk version "1.8.0_91"
OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14)
OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
However, looking at bug #1597769, the JAR packages provided in the
Github
$ java -version
openjdk version "9-internal"
OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src)
OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src,
mixed mode)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Steps to reproduce:
$ sudo apt-get --no-install-recommends install visolate
$ visolate
This results in:
$ visolate
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError:
Public bug reported:
The original author intentionally abandoned the project, another one
picked it up and forwarded it to now version 3.1.1. Original author was
notified and had no objections with the "takeover".
The new code repository is on Github:
https://github.com/Traumflu
Attached is a screenshot of the dialog which made me reporting this bug.
It happens on about every reboot, sometimes an hour later. There is no
hint on which package or problem brings up this dialog.
** Attachment added: "Problem with System Application.png"
Public bug reported:
Just did what the bug triagers requested: 'ubuntu-bug upower' on the
command line.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: upower 0.99.3-1build2
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion:
> $: ubuntu-bug upower
This resulted in another bug:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1515998
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513149
Title:
General, unspecific
Clickable link to the other bug:
https://bugs.launchpad.net/ubuntu/+bug/1513149
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515998
Title:
Package specific report as requested in bug 1513149
To
I just changed the bug title to a more appropriate one. Sorry for being
so confusing. 'Report a bug' on Launchpad refuses to accept bugs at all
and 'ubuntu-bug' on the command line refuses to accept bugs without a
package name. The description given on the help page is plain wrong:
The bug was intentionally not filed against a specific package. It's
apparently a bug in the way the packages work together.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513149
Title:
Public bug reported:
Occasionally I get a small window with some unspecified text along the
lines of "A system error occured" together with two buttons, "Ignore"
and "Report". Neither of these buttons does something noticeable, much
less there is some indication on what the problem might be. So I
With current Git HEAD, the crashing code is located at line 6286 in
src/action.c:
6285: /* save both ends of line */
6286: Crosshair.AttachedLine.Point2.X = ptr2->Point1.X;
6287: Crosshair.AttachedLine.Point2.Y = ptr2->Point1.Y;
Point1 is the result of a previous
** Also affects: geda-project
Importance: Undecided
Status: New
** Changed in: geda-project
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930787
Title:
** Also affects: geda-project
Importance: Undecided
Status: New
** Changed in: geda-project
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424176
Title:
** Also affects: pcb
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930787
Title:
pcb-gtk crashed with SIGSEGV in ActionUndo()
To manage notifications
*** This bug is a duplicate of bug 1028251 ***
https://bugs.launchpad.net/bugs/1028251
** This bug has been marked a duplicate of bug 1028251
pcb-20110918: Crash on editing text
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Works well indeed. Just upgraded using this PPA and Inkscape works fine
(including this bugfix).
Thank you for fixing this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335523
Title:
Well, this whoever runs the PPA is actually Inkscape Developers:
https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335523
Title:
0.48.x
Excellent hint. Thank you, @Timo.
As your command installs all available lenses --ther're a ton of them--,
I opened Synaptic and tried with reinstalling only the already installed
ones.
- Reinstalling the existing unity-lens-* changed nothing.
- Looking at unity-scope-home showed this wasn't
Public bug reported:
Since upgrading from 13.04 to 13.10 (beta) I can no longer launch
applications by searching them in the dash (topmost entry in the
launcher bar). Whatever I enter as a search term, the spinning circle
rotates, rotates, without ever showing any results. No message about
Can report success for the Intel G33, too. Now the system menu is gone
and the dash searches forever without results - different story.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222602
Title:
Q35 is one of the successors of the 945, too. More to the higher end, if
not the top model, of this family at some point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222602
Title:
[regression]
Yes, this workaround works and brings the description flags, search
panel and restart dialog back to expected speed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232888
Title:
Transparent stuff
*** This bug is a duplicate of bug 1222602 ***
https://bugs.launchpad.net/bugs/1222602
** This bug has been marked a duplicate of bug 1222602
[gen3] Bad performance on GMA950 and GMA3150
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Just updated to 13.10 (beta) from 13.04 and found transparent stuff on
the desktop to be extremely slow. For example, moving the cursor over an
item in Unities application bar takes about 3 seconds to display the
description of it. The bar it's self moves out of and back into
To reproduce the bug, you have to use a locale which has something
different than a dot for the decimal separator. Also, the bug is
sometimes not obvious, as the output looks the same on the first page,
but contains invalid PostScript for additional pages.
I've attached my environment, it's the
As of today, this package doesn't show up in my installation:
$ date dpkg -s pcb
Di 5. Jun 01:04:53 CEST 2012
Package: pcb
Status: install ok installed
[...]
Version: 20110918-4
[...]
I'm subscribed to precise-updates, precise-proposed and precise-
backports. What is going wrong?
--
You
** Branch linked: lp:ubuntu/precise/pcb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988503
Title:
PostScript output is invalid on non-english locales
To manage notifications about this bug go
https://code.launchpad.net/~mah-jump-ing/ubuntu/precise/pcb/fix-
for-988503/+merge/103688
** Changed in: pcb (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The previous merge request accidently included a temporary file, a new
merge request followed:
https://code.launchpad.net/~mah-jump-ing/ubuntu/precise/pcb/fix-
for-988503-2/+merge/103767
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
When exporting or printing to PostScript from the command line, the
resulting output is invalid. With a german locale, decimal dots inside
the file are replaced by commas.
Fix is known.
$ lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
$ apt-cache
Fix attached, it's a one-liner. Taken as-is from pcb's git repository.
** Patch added: 0001-Fixed-command-line-batch-output-for-some-exporters.patch
Now I hope somebody who knows how to forward this fix into the package
update system picks up (or shows me how to do it myself).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988503
Title:
Here (USB-to-parallel cable, LaserJet 2100) the update apparently works
only if the printer is turned on while plugging USB in. Turning the
printer off for a while and on again, the connection is gone. Cycle the
USB plug while the printer is on, and the connection re-appears.
--
You received
-- This shouldn't be wishlist, as it's actually a regression from
Ubuntu 11.04. Dragging to bookmarks worked with the older Nautilus just
fine.
-- At least for me, this applies to self-made bookmarks only. Dragging
to the predefined bookmarks (Desktop, Pictures, Music, ...) works just
fine. Too
There's another Gnome bug tracking this:
https://bugzilla.gnome.org/show_bug.cgi?id=645353
Diagnosis: instead of making a working feature dummy-proof, they removed
the feature because it's not dummy-proof.
OUCH!
** Bug watch added: GNOME Bug Tracker #645353
The log isn't a good source for doing this comparison, as it will
eventually become way to huge to be handled. Nice thing is, this log
apparently knows about command line installations, so it's a general
packaging system feature.
This marking as manually installed thing is a good one and once
Have anybody here had a look to the /apps/gnome-power-
manager/lock/use_screensaver_settings gconf key? If you look there with
the gconf-editor app, you even see keys to override this indepedently
from the screen saver.
That said, it appears all this screen-lock-disabling stuff is pretty
Public bug reported:
Binary package hint: pulseaudio
Steps to reproduce:
1. Install Ubuntu 10.10.
2. Plug in an USB audio device, like one of these C-Media headsets.
3. Open gnome-volume-control to get that device into use, i.e. make it
the default audio device.
4. Try to get test sounds, or
Public bug reported:
For a few days now, virtually all applications using OpenGL segfault.
For example:
$ glxgears
Segmentation fault
$
Running the same in gdb reveals the following:
Program received signal SIGSEGV, Segmentation fault.
0x77e5812e in XF86DRIQueryVersion () from
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685285
Title:
Segfault in libGL for glxgears, Blender, Meshlab, visolate, and probably more
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Looks like this library is in the fglrx package.
** Package changed: ubuntu = fglrx-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685285
Title:
Segfault in libGL for glxgears,
*** This bug is a duplicate of bug 442574 ***
https://bugs.launchpad.net/bugs/442574
Got it.
The package emc2-sim depends on fglrx and removing both packages made
all OpenGL applications work again.
** This bug has been marked a duplicate of bug 442574
mesa doesn't work when fglrx is
** Tags added: lucid
** Tags removed: needs-retested-on-lucid-by-june
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442574
Title:
mesa doesn't work when fglrx is installed
--
ubuntu-bugs mailing
Well, it was the most recent version when I reported the bug. As I no
longer have the equipment to test for this bug, please close it.
--
Pendrive boot disk works only once
https://bugs.launchpad.net/bugs/312709
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I came along this trying to make my usb mic (capture only device, has no
outputs) working as master device, while piping output with alsa_out
(jack) or jack_load audioadapter (jack2) via resampling to a soundcard.
using the soundcard as output device in straight jack
forget it, someone was already faster than me:
http://trac.jackaudio.org/changeset/3848
--
jack alsa driver unable to initialize capture-only mode
https://bugs.launchpad.net/bugs/494223
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
It still happens for me on Karmic x86_64:
http://groups.google.com/group/devede-
forum/browse_thread/thread/8e737d82911799f0
** Also affects: devede
Importance: Undecided
Status: New
--
DeVeDe does not complete conversion in Jaunty 64-bit
https://bugs.launchpad.net/bugs/413460
You
Am 28.10.2009 um 18:21 schrieb Nigel Pallett:
The problem occurs when I'm using virt-manager or virsh to run the
Virtual Machines under kqemu.
I can't help here as I use qemu without any managers. Typical
strategy here is to try find out which commands these managers try to
launch and
Am 28.10.2009 um 18:21 schrieb Nigel Pallett:
The problem occurs when I'm using virt-manager or virsh to run the
Virtual Machines under kqemu.
I can't help here as I use qemu without any managers. Typical
strategy here is to try find out which commands these managers try to
launch and
They are kidding, aren't they? .xession or .xsessionrc files are in
existence and well documented for some 20 years and now they want
distros to craft their own flavour? Sligthly different for each distro?
--
The new gdm doesn't give an option to use .xsession
Shht. The kqemu packages still work great in combination with qemu built
from source.
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
/usr/bin/qemu: invalid option -- '-domid'
That's odd, as qemu doesn't have a feature domid. Even the
unavailable options are listed with qemu -help.
Are you sure to use the newly compiled qemu? which qemu will tell you.
Which sources are you using? I'm using the plain sources from
OK, so the problem is, the US layout is added each time I boot.
The outputs as requested right after booting:
m...@piccard:~/Desktop$ grep ^X /etc/default/console-setup
XKBMODEL=pc105
XKBLAYOUT=us,de
XKBVARIANT=,
XKBOPTIONS=grp:alts_toggle
m...@piccard:~/Desktop$ gconftool -R
1 - 100 of 181 matches
Mail list logo
