Super, I was just looking for a way to build kernels in a Docker
container.
Maybe the Docker image could be modified to build dwarves for itself at
some point.
I think you can request more space for a PPA from launchpad.
--
You received this bug notification because you are a member of Ubuntu
B
Still seeing this spurious libc 2.33 dependency (I *assume* it's not the
kernel people who decide to change their libc policy in the middle of a
release series -- so it's spurious) in 5.10.35.
Are the Ubuntu / Canonical people notified? I'm not sure who takes care
of this "Mainline PPA" (which doe
It would be unfortunate for the "LTS" kernel version to not be
installable on LTS Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with Hirsuit
Aha, it's Teh Apparmor. Edit /etc/apparmor.d/usr.bin.evince and add
/**.[tT][tT][fF] rw,
after the other supported formats (bmp, djvu etc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/631088
Ti
Still not working in 14.04. Strangely, using "strace -eopen evince" I
can see that an open() system call returns EACCES, even though from the
shell I can access the symlink (and its target)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
For me it seems to happen with symlinks from /usr/share/fonts to a
different partition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396048
Title:
Evince misses font and only displays squares in me
Also, https://github.com/msgpack/msgpack-python/issues/97 and apparently
https://github.com/msgpack/msgpack-python/issues/101
The original report refers to 124, which only affects the pure python
implementation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Also, https://github.com/msgpack/msgpack-python/issues/114 (fixed in
0.4.3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443213
Title:
Data corruption with msgpack <= 0.4.5, >= 0.4.2 -- upgrade to
Public bug reported:
Please upgrade to 0.4.6 to avoid data corruption:
https://github.com/msgpack/msgpack-python/issues/124
Utopic also needs the upgrade.
** Affects: msgpack-python (Ubuntu)
Importance: Undecided
Status: New
** Tags: upgrade-software-version vivid
--
You receiv
Update to 0.4.6, because 0.4.2 (the current Vivid version) to 0.4.5 have
DATA CORRUPION bugs: https://github.com/msgpack/msgpack-
python/issues/124
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
This seems to have been fixed in unity-greeter, but not lightdm-gtk-
greeter. And in any case, how can the unity-greeter inactivity timeout
be tuned? gsettings under the lightdm account?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing this with linux-lowlatency-lts-utopic...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at boot time
To manage notifications about this
Sorry, this is on Trusty amd64, with linux-lowlatency-lts-utopic
3.16.0.31.24
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at boot time
To manag
The vivd package *still* doesn't provide opencl-icd, so after installing
fglrx, python-pyopencl tries to pull in beignet...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129409
Title:
Nvidia and AM
Trusty was affected too by the Conflicts: thing; I've been running
manually-patched fglrx drivers for a while now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129409
Title:
Nvidia and AMD graphic
This is... nightmarish. @nukedathlonman, why don't you state clearly
which package needs to be compiled and what needs to be modified in
debian/control?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/11
With encrypted resume it's even worse, because you can't enter the
passphrase since plymouth hogs the screen and keyboard. 'plymouth quit'
as in #11 indeed solves the problem. CAN SOMEONE PATH uswsusp PLEASE?
Also, it seems uswsusp is really old and unsupported; is it possible to
get compressed, e
Still a problem on Trusty (!), fixed with /etc/init.d/screen-cleanup start.
screen == 4.1.0~20120320gitdb59704-9
It seems screen-cleanup is not activated by default in rc.d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I can't get light-locker to do anything at all. No matter how long my
laptop sits unused, there is no blanking of the screen and no locking.
This is on a vanilla Lubuntu 14.04 install (and ps confirms light-locker
is running)
--
You received this bug notification because you are a member of Ubunt
Even on MS Windows you can dig out fsck messages with the eventviewer.
This is stupid, lazy and arrogant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in
I've backported a 1.3-3 from saucy (!) in my PPA
(https://launchpad.net/~danmbox/+archive/ppa). I still get a bunch of
junk:
13:31:17 libtorsocks(28806): WARNING: The symbol res_query() was not found in
any shared library with the reported error: Not Found!
Also, we failed to find the symbol __
Public bug reported:
You don't have to depend on nvidia-current just to ensure nvidia. Some
people have nvidia-319, nvidia-319-updates etc.
** Affects: pycuda (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Since I installed xserver-xorg-dev-lts-raring, I can't build some
packages that insist on depending on xserver-xorg-dev. And due to a
separate bug I can't change the Build-Depends: line, because debuild -S
reverts my changes. I don't know how you accomplished that. But you
sho
Public bug reported:
When modifying the build-depends line in debian/control for
http://packages.ubuntu.com/saucy/nvidia-319-updates, any changes are
reverted by debuild -S. How did you manage to accomplish this amazingly
useful effect?
** Affects: nvidia-graphics-drivers-319-updates (Ubuntu)
In my PPA (https://launchpad.net/~danmbox/+archive/ppa) I've tried
backporting ocl-icd_2.0.2-1ubuntu1 (after backporting khronos-opencl-
headers), but it's not compilable (weird warnings-turned-into-errors)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Is anybody backporting (or at least THINKING about backporting) all
these wonderful changes for us plebs on 12.04 LTS using the OFFICIAL
linux-generic-lts-raring series, or do we no longer count as real users,
despite LTS promises from Ubuntu?
--
You received this bug notification because you are
That was absolute bull. Ubuntu obviously ships with /etc/profile, which
is a "version" of bash_profile, so #8 was a specious argument. And
placing "profiley" stuff into bashrc slows down the shell (as if it's
not slow enough already!)
Some .xsessionrc file (or whatever is read by the *dm's) must m
Brad, can you comment on the problems I've shown for 3.2 and 3.8 on
precise -lts kernels? Do you want to push through those kernels and then
have to deal with separate bugs. I know there's a lot of noise in this
thread, but there were some relevant tests and errors.
--
You received this bug notif
With linux-image-3.5.0-41-generic = 3.5.0-41.64~precise1 there are no
Buffer I/O errors, either with mkswap or mkfs.ext2
With linux-image-3.2.0-54-generic = 3.2.0-54.82 the errors are the same
as in linux-image-3.8.0-31-generic = 3.8.0-31.46~precise1
So the lts-quantal image is good, the others a
I've tested 3.8.0-31-generic (linux-image-3.8.0-31-generic =
3.8.0-31.46~precise1). To the admins: when asking us to test "the latest
in -proposed", please tell us which package and which version. It makes
it easier to interpret the record in the future, when the "latest in
proposed" may be differe
@dino99, do you also have problems with flash or firefox?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228882
Title:
nvidactl (misspelled) in /etc/apparmor.d/abstractions/ubuntu-
browsers.d/mult
Bug #893835 was incorrectly (in my opinion) marked as a duplicate of
this. The problem in that case is that ubuntu-bug fails if the system-
wide $BROWSER no longer exists. People in that situation cannot report
bugs anymore.
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 893056 ***
https://bugs.launchpad.net/bugs/893056
This fails whenever $BROWSER can't be opened (e.g. when you set up the
system-wide BROWSER to chromium-browser then uninstall chromium). This
is not a good thing.
--
You received this bug notification becaus
Public bug reported:
/etc/apparmor.d/abstractions/ubuntu-browsers.d/multimedia mis-spells an
nvidia device:
# If we allow the above, nvidia based systems will also need these
/dev/nvidactl rw,
/dev/nvidia0 rw,
(should of course be nvidiactl). This seems to be the case in all
apparmor versi
@Kenneth Parker: if your problem is that zram shows up EVEN AFTER dpkg
--purge zram-config, please **file a separate bug**. Note that "service
zram-config stop" stops zram after the system is up, which means it has
already potentially damaged your system. What you want is for the zram
module to nev
With 3.8.0-31-lowlatency, try this if you're willing to reboot:
rmmod zram; modprobe zram; echo -n 6710 > /sys/block/zram0/disksize;
mkswap /dev/zram0; dmesg -T | tail
It will bring you into a state where you can't rmmod zram (!).
# rmmod zram
ERROR: Removing 'zram': Device or resource busy
Kenneth, zram-config is a red herring. Even if you purge it completely
and set up zram manually,
modprobe zram
echo -n 67108864 > /sys/block/zram/size
mkswap /dev/zram0
swapon /dev/zram0
You still get the error messages and eventually the lock-ups. This is
not a script problem, it's a kernel prob
Since several bugs with much more details were merged into this one, the
most likely early warning of zram problems are messages like
Buffer I/O error on device zram0, logical block 257912 [repeated X
times]
You get those right after modprobing / formatting zram. If you don't see
those with the n
A week seems like an extremely short time, especially for ALL releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications abo
*** This bug is a duplicate of bug 1217189 ***
https://bugs.launchpad.net/bugs/1217189
I'm marking this as a duplicate of bug #1217189. I don't find @timg-
tpi's comment very reassuring. This is a critical bug for the LTS
release.
** This bug has been marked a duplicate of bug 1217189
Buff
This bug also occurs on linux-lts-quantal, I think (I remember booting
to a lts-quantal kernel after seeing the raring bug). There was a
backport to zram on both branches that is causing this.
Note that in Bug #1218278, Tim Gardner (timg-tpi) wrote at #19: "There
will be a linux-lts-saucy shortly
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813003/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Titl
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812997/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buff
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812998/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buff
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813004/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Bu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813000/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813002/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812999/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12171
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813001/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121
apport information
** Attachment added: "Card1.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812995/+files/Card1.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
apport information
** Tags added: apport-collected staging
** Description changed:
This is on linux-image-generic-lts-raring (which I recently upgraded to
3.8.0-29; the problem didn't occur before upgrading AFAIR)
I see this junk in my dmesg when creating / formatting a zram swap, and
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812996/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812992/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "ArecordDevices.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812990/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812993/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812989/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "Card0.Codecs.codec.1.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812994/+files/Card0.Codecs.codec.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812988/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812991/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Titl
@timg-tpi: Have you seen bug #1217189, involving machine lock-ups due to
this error, probably triggered after heavy swapping?
Do you have any suggestions as to why regular raring users seem
unaffected by this bug (or at least they're not complaining)?
--
You received this bug notification becaus
This might explain the reasons
https://lkml.org/lkml/2013/8/13/22
(assuming this was a change backported to 3.8 and 3.5 by Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218278
Title:
When
@damian-sawicki: yes, but once such memory errors DO occur, I think your
system is basically compromised; you don't know when it will crash (*)
and you don't know what else gets corrupted before the lock-up (why not
filesystem errors, security etc?). That's why I would cut this at the
root.
(*) In
The way to list your swaps is swapon -s. If zram0 is listed, something
still enables it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly caus
might be related to bug #1217189 which raises the possibility of hard
machine LOCK-UPS due to zram errors. I've had several such lock-ups on
precise after the most recent linux-lts-raring updates (and none before
that) that seemed to go away after disabling zram.
** Changed in: linux (Ubuntu)
Changed to Confirmed as per @jsalisbury's instructions, since
@konrad.hofer forgot to. In any case, I doubt raring (and thus linux-
lts-raring on precise) will upgrade to 3.11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Bug #1218278 might be a duplicate (though it doesn't talk about lock-
ups). Apparently this is fixed in 3.11, though I don't see how this
helps with raring and linux-lts-raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@damian-sawicki: a lot of people have zram due to the zram-config
package, which you must remove with dpkg --purge zram-config (otherwise
it won't go away completely). But in my case zram *still* starts up, and
I can't track what sets it up. I think the easy solution is to break the
zram modules (e
@damian-sawicki: do you also get lock-ups?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly causing complete machine
lockup)
To manage notif
@variona So, no lock-ups after downgrading? You should also test the
NEWER kernel WITHOUT enabling zram and see if the crashes still occur.
I've run 3.8.0-29 WITHOUT zram for almost a day (not quite enough to
give it a clean pass)
--
You received this bug notification because you are a member of
Public bug reported:
This is on linux-image-generic-lts-raring (which I recently upgraded to
3.8.0-29; the problem didn't occur before upgrading AFAIR)
I see this junk in my dmesg when creating / formatting a zram swap, and
then periodically. Then at some point after heavy swapping incidents,
the
"id; touch newfile; stat newfile"
OK, you are right "-o permissions" alone accurately preserves owners and
permissions, which is sort of what I needed. I was confused by some
experiments I did with memory sticks accessed from Windows.
"Yes, that should be expected. You cannot both define the owne
Note, my shell log shows the behavior with mount -o
uid=500,gid=500,umask=000. The same behavior (chmod has no effect)
occurs when using mount -o permissions,uid=500,gid=500,umask=000 (as if
-o permissions is being silently ignored).
--
You received this bug notification because you are a member
Public bug reported:
At the moment, it seems that mount.ntfs-3g disables -o permissions if -o
uid=UUU and/or uid=GGG are also specified. This (combined with Ubuntu's
compilation options disallowing user mounts for NTFS-3g) prevents
unprivileged users from easily accessing NTFS systems while preser
The only way I can get out of this bug, when it bites, is to exit my X
(and presumably dbus) session and log back in. Really annoying. evince
prints all sorts of useless console clutter, but fails to print any
useful diagnostics in this case.
--
You received this bug notification because you are
Run
uname -a
on the command line and post the results. You're probably not running a
real-time kernel, because those stopped at around 2.6.33. But log the
results here anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@David (#36): are you running a RT kernel though? PA tends to get killed
for many other reasons, being the stable piece of software that it is...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
T
... which is only a dream at this point :)
I guess I should request a backport to my installed version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726471
Title:
dbus de-prioritizes XDG_DATA_HOME
Then please ignore my previous comment and file a separate bug. This bug
is about unclean shutdowns, while yours sounds like the machine hangs on
shutdown -- a different symptom.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
There are other bugs in Ubuntu that can cause shutdown problems, for
example Bug #665195 and bug #665176.
I fixed my problems by creating a /etc/init.d/sysshutdown as attached
(and adding it to the various runlevels). This at least gives you a
chance to examine the situation (in Virtual Console 9)
Thanks, I missed the second status line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726471
Title:
dbus de-prioritizes XDG_DATA_HOME -- can't customize user session
--
ubuntu-bugs mailing list
u
I wonder why this bug is marked as Fix Released? Upstream has indeed
fixed the problem, but on a different branch (dbus 1.4.8). Ubuntu has
1.4.6 and AFAICT the fix hasn't been backported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's an interrupted syscall -- there is no result... And the for loop
only repeats on EINTR.
I take it that no support, or at least help, will be forthcoming from
the Ubuntu side?
Even though the lead PA developer seems like a smart guy who understands
real-time quite well, I'm sorry to say that
Thanks David. I am streaming from qmmp, and I have completely removed
gstreamer0.10-pulseaudio (and, yes, as per comment #25, I have a
backported natty pulseaudio).
I have performed the steps I planned in #28 and have obtained several
backtraces. They all look the same. Strangely, the kernel sends
>From setrlimit(2): setrlimit allows the user to specify two limits -- a
soft one and a hard one. For RLIMIT_RTTIME, upon exceeding the soft
limit, the kernel sends a SIGXCPU every second, then a SIGKILL.
Unfortunately, pulseaudio sets the soft limit equal to the hard limit,
so no warning is possi
Doesn't the log-level = debug take care of that, Daniel?
I didn't attach a full log because minutes pass between the last printed
message and the SIGKILL.
Is there a way to see how much "rttime" a task has been using (with ps
or something else)?
And (less likely) is there a way to configure the
This is hard to diagnose. I built 0.9.22 packages from natty, then
installed pulseaudio-dbg_0.9.22+stable-queue-24-g67d18-0ubuntu3_i386.deb
In ~/.pulse/daemon.conf, I enabled
log-level = debug
log-meta = yes
log-time = yes
log-backtrace = 1
then ran pulseaudio under gdb with
$ killall pulseaudio
Bug #496616 is marked as a duplicate of bug #644644...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
Title:
PulseAudio gets killed mysteriously on RT kernels
--
ubuntu-bugs mailing list
ubu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762929
Title:
wmdrawer hangs when killed, segfaults when killed again
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Public bug reported:
Binary package hint: wmdrawer
$ wmdrawer &
$ killall wmdrawer
# wmdrawer doesn't go away, but doesn't bring up the drawer either anymore
$ killall wmdrawer
Bye bye, thx to use wmdrawer
[1]+ Segmentation fault wmdrawer
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Packag
Trivial patch added, since there seems to be no response to the original
report. Please apply or at least comment on the issue.
** Patch added: "depend on libdbus-glib-1-dev (debdiff)"
https://bugs.launchpad.net/ubuntu/+source/patchage/+bug/730506/+attachment/2025152/+files/patchage-depend-on-
** Summary changed:
- Karmic acroread does not become the default PDF handler for email even after
answering "Yes" to the debconf question
+ acroread does not become the default PDF handler for email even after
answering "Yes" to the debconf question
** Tags added: lucid
--
You received this
As the comments in the Debian bug report show, Fedora 14 is packaging
netpbm-10.47.17, so presumably the license problems invoked by Debian
aren't that bad.
The Debian maintainer has quite clearly decided to kill this package. He
hasn't posted updates in the bug report for almost 4 years. Is there
I have reported this bug upstream and it has been confirmed.
http://www.mail-archive.com/dash@vger.kernel.org/msg00401.html
Apparently dash 0.5.6 fixes it, but releases up to Natty still use 0.5.5
** Tags added: maverick natty
--
You received this bug notification because you are a member of
If you're seeing data corruption due to shutdown, see also this bug:
https://bugs.launchpad.net/ubuntu/maverick/+source/sysvinit/+bug/665185
(again there is a fixed version in my PPA, and Ubuntu will also soon
provide a Lucid update)
--
You received this bug notification because you are a membe
I have a fixed version in my PPA,
https://launchpad.net/~danmbox/+archive/ppa/
Attaching debdiff against that version. This is a trivial change, but
from what I can see Ubuntu is very selectively maintained, and providing
a patch makes it slightly more likely that a maintainer will act.
Again, p
The bug obviously affects Maverick and Natty as well. It has been fixed
in GIT and will be in 1.4.8:
https://bugs.freedesktop.org/show_bug.cgi?id=35569
I hope this fix will be backported to 1.4.6 (on freedesktop.org and/or
here), because it would be quite annoying to have to deal with buggy
Ubunt
Great, thanks. Now what do I have to do to get this fix into Lucid,
where it actually *is* a problem (killall5 doesn't overflow on Natty,
because it's been fixed, but it does on Lucid)?
The LTS release still has years left of support, but I'm really getting
the all-around feeling that it is shunne
Steve, note that while this issue has been masked in Maverick & Natty by
making killall5 accept any number of OMITPIDs, it is still a problem in
Lucid for those who have upstart jobs that won't shut down. The symptom
is a journal replay (or heaven forbid worse) after every single reboot
(because ki
** Tags removed: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742964
Title:
shift-click & ctrl-click not working
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Public bug reported:
In xtightvncviewer shift-click and ctrl-click behave as normal clicks,
making it impossible to select multiple items. Server is tightvnc, and
can be on a windows or on a linux host with the same result.
Easiest to reproduce by running a tightvncserver, then connecting to it
w
1 - 100 of 165 matches
Mail list logo
