Ick, I'd forgotten about this (again!) and I won't have time to work on
this in the next couple of weeks.
You can't really re-use my merge request: it was rejected, and you can't
upload to my branch (which the merge request was for). You can send a
new merge request, though.
I'm afraid I no longer have access to the hardware needed to reproduce
this bug (and I doubt running recent versions of Ubuntu on hardware
supported by viafb is something many other people do, either).
Please do whatever's necessary to reflect that to this bug's state,
assuming leaving it
Please note that the first patch I attached (which seems to be the one
that went into the builds mentioned in comment #4) is not good: it fixes
alt+backspace but unfixes utf8 keybindings. Dropping the patch
completely is saner than applying that patch. I have attached a second
patch to the irssi
There is a thread on the linux-wireless list that sounds like it might
fix this problem, see http://www.spinics.net/lists/linux-
wireless/msg53115.html and especially http://www.spinics.net/lists
/linux-wireless/msg53204.html (The patch lets me use wifi). I have not
yet actually tested this patch
This is indeed because of the mpris plugin. Relevant part of the stack
is just:
#0 0x00172642 in rb_shell_player_get_playback_state (player=0x822d000,
shuffle=0x0, repeat=0xbfffefcc) at rb-shell-player.c:1817
#1 0x038005a3 in get_loop_status (plugin=value optimized out) at
The linked branch lp:~marienz/ubuntu/maverick/rhythmbox/fix-crash-on-
random-with-mpris might fix this. My ppa has an amd64 build of that
branch (see https://launchpad.net/~marienz/+archive/ppa/+build/1930205
), but I cannot test it and the i386 one is still pending.
Please do not add my entire
I had completely forgotten about this, but can probably address the
review comments next week (possibly sooner). If someone else wants to
beat me to it that is fine too, of course.
--
ubuntu-bug should fall back to using its argument as a command name
(ubuntu-bug ubuntu-bug should work)
That does indeed fix it (I should have read the debconf documentation
and figured this out myself...).
Updated package is in my ppa (it just has a db_stop call added after
db_reset aiccu/password).
--
Upgrade to 10.04 beta1 blocked by aiccu
https://bugs.launchpad.net/bugs/544910
You received
This does not just break upgrading, the same thing happens when
installing aiccu on an already-running system.
What seems to be going on is this:
- debconf launches the postinst script, using an extra pipe
(connected to fd 3 in the script) to communicate.
- The postinst script eventually
** Patch added: Close all fds when daemonizing
http://launchpadlibrarian.net/45817305/09_close_fds.patch
--
Upgrade to 10.04 beta1 blocked by aiccu
https://bugs.launchpad.net/bugs/544910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
My vga16fb problem may be the same one from bug 538893 comment #1, at
least in that the garbage I see in text mode seems to be influenced by
what was on the screen in X. And yes, that's a different bug.
Blacklisting vga16fb is not necessary as long as X works: I get a brief
period of garbage
Public bug reported:
After upgrading from karmic to lucid my laptop turns off its lcd panel
early during boot, after which I cannot figure out a way to turn it back
on. X starts (I can hear the gdm drums and log in blindly), I can
ctrl+alt+f1 out of X and alt+f7 back into X, but during all this I
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/44063371/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/44063372/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/44063373/ArecordDevices.txt
*** This bug is a duplicate of bug 518623 ***
https://bugs.launchpad.net/bugs/518623
** This bug has been marked a duplicate of bug 518623
[KM400] Black screen after boot, no text console possible
--
viafb and vga16fb turn off lcd on an acer aspire 1350
As mentioned on the duplicate I just filed: adding blacklist viafb and
blacklist vga16fb to /etc/modprobe.d/blacklist.conf makes things work
here.
Karmic's kernel (2.6.31-20-generic) also works, but that is because
viafb is not loaded there by default, not because viafb works. If I stop
gdm and
This interrupted the upgrade from karmic to lucid (I'm sorry, I don't
have exactly how logged). A manual reinstall attempt at the commandline
gave me:
Setting up yaml-mode (0.0.4-2) ...
emacsen-common: Handling install of emacsen flavor emacs
emacsen-common: Handling install of emacsen flavor
And I can no longer reproduce this using linux-image-2.6.32-16-generic
2.6.32-16.24 (now in main) either, which (if I read the changelog right)
has the same DRM backport. Closing this as fixed, thanks!
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Fix Released
--
I cannot reproduce the problem using the kernel from that PPA.
--
[r300] mouse cursor disappears after xrandr change
https://bugs.launchpad.net/bugs/532676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: xserver-xorg-video-ati
My ubuntu lucid system with a radeon 9600 xt (r300 driver) using kms
loses its mouse cursor if I change the refresh frequency through xrandr.
Certain actions bring it back (I've been using the animated workspace
switch in compiz,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/40251105/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/40251106/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/40251107/Dependencies.txt
**
This is the change I mentioned in my previous comment. Applying this
might make sense even if it does not turn out to fix this crash.
** Patch added: fix (?) applied to indicator-messages
http://launchpadlibrarian.net/38924097/messages-service.patch
--
indicator-messages-service crashed with
I tried to debug this. While I did not understand the attached gdb
session (how can sl_item be NULL if serverentry and serverentry-data
are not?) I did notice some suspicious code higher up: if serverentry
*is* NULL a new *local* sl_item is created and then thrown away, leaving
the sl_item in the
Public bug reported:
Binary package hint: quassel
On a fairly vanilla lucid install with no kde and at least almost no qt
packages installed sudo apt-get install quassel-client-qt4 wants to
install things like kdebase-runtime and kdelibs5 that I would prefer not
to have installed. This seems to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38200840/Dependencies.txt
--
apt-get install quassel-client-qt4 still pulls in kde
https://bugs.launchpad.net/bugs/510914
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ah, great. Just --no-install-recommends doesn't do the trick though: I
had tried that already and found kcm-phonon-xine is a Depends of phonon-
backend-xine, not a Recommends. Unless I missed something in the
dependency tree kcm-phonon-xine being a Suggests would give me a kde-
free
Public bug reported:
Binary package hint: pyflakes
The pyflakes package only installs a changelog, a copyright file and a
manpage. Those would be more useful if the actual program was also
included :)
I fixed this (following a few hints in the python-support README) by
removing
Distutils does honor PYTHONUSERBASE, but it only does so when using
--user (which is what I expect). When I do *not* use --user whether
PYTHONUSERBASE is set or not should not matter, but in ubuntu it does.
Let me try to show what I mean with an example:
Create a setup.py containing just:
from
*** This bug is a duplicate of bug 462961 ***
https://bugs.launchpad.net/bugs/462961
Looks like this got fixed as bug #462961 so marking this as a duplicate
of that. If someone can teach me what caused that bug report to be
picked up and fixed instead of this one I would appreciate it, so I
Public bug reported:
Binary package hint: python2.6
The PYTHONUSERBASE variable sets the base directory for the *user* site
directory. This defaults to ~/.local, and sensible values for it will
generally include $HOME. This is not very well documented, but see for
example
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35202306/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35202308/XsessionErrors.txt
--
PYTHONUSERBASE should not affect distutils.sysconfig.get_python_lib and friends
** Branch linked: lp:~marienz/apport/maximize-button
--
apport Content of the report window should have a maximize button
https://bugs.launchpad.net/bugs/447749
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
No, I do not see a maximize button. If I saw a maximize button I would
not have filed this bug. And yes, I'm in karmic, as I was assuming the
apport-provided extra information would tell you. What's probably
relevant though is I'm using metacity, not compiz (this laptop cannot
run compiz). And it
It's not hard to do this in python directly either, see the attached
branch (not heavily tested, but since getting this exactly right isn't
critical it may be good enough).
** Branch linked: lp:~marienz/apport/search-for-executable
--
ubuntu-bug should fall back to using its argument as a
** Attachment added: One of the crash reports bzr produced
http://launchpadlibrarian.net/33387578/bzr-20091010024415-7709.crash
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33387579/Dependencies.txt
** Branch linked: lp:~marienz/+junk/import-dsc-hack
--
bzr
Public bug reported:
Binary package hint: bzr-builddeb
import-dsc sets author information from debian/changelog and/or
debian/control as revision property as bytestrings. At least using bzr
2.0 chk_serializer's write_revision_to_string tries to encode those to
utf-8, which fails if the names
** Attachment added: CrashReports.txt
http://launchpadlibrarian.net/33387828/CrashReports.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33387829/Dependencies.txt
--
apport Content of the report window should have a maximize button
Public bug reported:
Binary package hint: apport
The dialog Send problem report to the developers? has an expandable
Content of the report section that I would expect people new to the
system to want to skim through. This area is much too small to read at
the default window size, and while the
Public bug reported:
Binary package hint: apport
ubuntu-bug understands package names and the full path to a program. If
the argument I give it is neither but is the name of an executable on
$PATH it should do what I mean and use that. It could optionally confirm
that with me first (Did you mean
** Attachment added: CrashReports.txt
http://launchpadlibrarian.net/33388012/CrashReports.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33388013/Dependencies.txt
--
ubuntu-bug should fall back to using its argument as a command name
(ubuntu-bug ubuntu-bug
I use cryptsetup to encrypt my swap file. I can try disabling that, but
I'm not hitting this bug consistently (I haven't hit it across the last
couple of reboots) so I'm not the most useful tester for this.
--
[karmic] Xorg 100% CPU utilization -- only after first login
Note that system - preferences - startup applications allows you to
turn off GNOME Login Sound, which I'm assuming covers the disable
login/out sounds and keep the rest of the system sounds case (but does
not let you do everything the old preferences panel did).
--
gnome-volume-control missing
Sorry for losing track of this. The version of openchrome in karmic
(xserver-xorg-video-openchrome-0.2.903+svn758-0ubuntu1) is still
affected by this. Upgrading that package to r800 fixed it. So this is
indeed fixed upstream, and it might be nice to get a newer snapshot in
the xorg-updates ppa or
Public bug reported:
Binary package hint: grub2
I'm encountering this on a system using lvm with a separate /boot
partition outside of lvm used by jaunty but no separate /boot for
karmic, but I think it will affect every system with grub 1 on a
separate /boot partition, not just those also using
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33221201/XsessionErrors.txt
--
os-prober entries do not use correct /boot device
https://bugs.launchpad.net/bugs/445367
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Branch linked: lp:~marienz/ubuntuone-client/ubuntuone-client-
preferences-first-run
--
Ubuntu One crashed on launch
https://bugs.launchpad.net/bugs/441039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is going to sound pretty dumb, but how do I get the driver to use a
resolution different from the native panel resolution?
Both the driver from the .ppa and current svn head (revision 777) with
the patch applied log ViaPanelGetIndex: Mode not supported by Panel.
or ViaPanelGetIndex:
I haven't been able to get a logfile out yet. I can confirm it will not
work correctly: I'm seeing some old video memory contents with some
corruption drawn on top of it, and then the system locks. Not just X:
magic sysrq and ctrl+alt+del do not work, and my ssh connection dies.
Neither Xorg.0.log
Public bug reported:
I have an acer aspire 1350 laptop with (from lspci -nn):
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc.
KM400/KN400/P4M800 [S3 UniChrome] [1106:7205] (rev 01)
Using jaunty it needs the x-updates ppa for X to start at all (at least without
an xorg.conf).
** Attachment added: very ugly but working patch
http://launchpadlibrarian.net/30508577/xserver-xorg-video-openchrome_0.2.903%2Bsvn741-1build1.diff
--
xv does not work (badalloc, using the x-updates ppa)
https://bugs.launchpad.net/bugs/415964
You received this bug notification because you
Yes, that patch (applied to the source package from the x-updates ppa)
still gives me working xv. Note via_swov.c:Upd_Video still uses
NativeMode-Width, but I don't know if it's actually possible to trigger
that code, or what would happen if it got a 0 width (dwWidth would be
set to 0, but I don't
Public bug reported:
Binary package hint: ubuntu-dev-tools
mk-sbuild-lv tries to modprobe dm_snapshot and bails if this fails,
assuming snapshots will not work. But the kernel I'm running (jaunty's
default linux-image-2.6.28-13-generic kernel) has CONFIG_DM_SNAPSHOT=y,
so that modprobe fails
Public bug reported:
As documented on
http://www.crummy.com/software/BeautifulSoup/3.1-problems.html the 3.1
BeautifulSoup branch uses a different parser to be compatible with
Python 3. Unfortunately this parser does much worse on invalid html than
the old one did, and a very common reason to use
Public bug reported:
Binary package hint: hal
If the account with uid 0 is not called root (this is sometimes
recommended for security reasons) hal does not start successfully, most
likely because the dbus policy file for hal says only the root and
dbusdaemon user may claim the nameThis is not a
53 matches
Mail list logo
