Public bug reported:
By dist-upgrade:
sudo apt update && sudo apt dist-upgrade
OK:1 http://archive.canonical.com/ubuntu bionic InRelease
Holen:2 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
OK:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
OK:4 http://archive.ubuntu.com
Am 20.02.2018 um 14:41 schrieb Jean-Baptiste Lallement:
> Thanks for your report.
>
> Are you able to reproduce this crash and could you provide the steps to
> do it?
>
> Thanks.
>
> ** Changed in: gnome-software (Ubuntu)
> Status: New => Incomplete
>
I think the crash are in the Future by
gdm3 no mouse function but move.
gnome Displaysystems not boot and then boot no mouse function but move.
lightdm goes into Automatic login. why? Have changed this manually.
gdm3 is Ubuntu adjusted, why. But no mouse function to change this, no
click possible.
--
You received this bug notificat
Public bug reported:
pim-data-exporter : Hängt ab von: libkf5akonadicore5abi1 (>=
4:16.12.3+git20170414) ist aber nicht installiert
Hängt ab von: libkf5mailtransport5abi2 (>=
17.07.70+git20170701) ist aber nicht installiert
pim-sieve-editor : Hängt ab von: libkf5mailtranspo
Am 15.09.2017 um 18:08 schrieb Nicolás Abel Carbone:
> Is there a missing piece in the bug
It's a missing piece.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714330
Title:
gnome-shell crashed wit
*** This bug is a duplicate of bug 1707369 ***
https://bugs.launchpad.net/bugs/1707369
The bug is not existens in new Update. Ubuntu 17.10 31.07.2017.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
By upgrade with:
sudo apt update && sudo apt upgrade
and
sudo apt autoremove
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu11
ProcVersionSignature: Ubuntu 4.9.0-3.4-generic 4.9.0-rc7
Uname: Linux 4.9.0-3-generic x86_64
Public bug reported:
By first start a Programm crashed
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: plasma-workspace (not installed)
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: We
Am 21.01.2016 um 04:15 schrieb li0n:
> everything works fine!
> Thank you so much !!
>
> пн, 18 янв. 2016 г. в 21:55, Andrew Black <1529...@bugs.launchpad.net>:
>
>> Maybe it helps for reproducing the problem: I wanted to install today's
>> daily in a Parallels virtual machine and got this error.
>
Public bug reported:
ubiquity crashed at Step2-3.
I can~t test Kubuntu 16.04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.42
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CasperV
Am 23.06.2014 21:21, schrieb Frank Schindler:
> Am 23.06.2014 18:41, schrieb Rohan Garg:
>> I don't know if wubi is a supported installation mechanism.
>> Yes wubis installation is at the moment not supported. I forgot . Is
>> Alpha2
--
You received this bug notification because you are a membe
Am 23.06.2014 18:41, schrieb Rohan Garg:
> I don't know if wubi is a supported installation mechanism.
>
Yes wubis installation is at the moment not supported. I forgot . Is Alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
2. Part of Bug report!
Install crashed by set the Keyboard!!!
Installation from USB-Stick
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.18.9
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3
Public bug reported:
2. Part of Bug report!
Install crashed by set the Keyboard!!!
Installation from USB-Stick
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.18.9
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3
Public bug reported:
By installtion wubu crashed and by Step Account make,the installer
crashed.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.18.9
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3-0ubuntu2
Archit
There is a workaround for this bug which has plagued the HP Compaq
nc6120 I'm using ever since, well, forever. I was put on the track of
this workaround by reading an old Advogato blog entry
(http://www.advogato.org/person/mjg59/diary/62.html) where someone by
the handle of 'mjg59' tells about his
Interesting enough, I was forced to re-install my little sisters whole
computer. Grub said that there was no such partition, and indeed there
was not much of any partition there (All I could find was scrambled
data, no tools I installed on the live “CD” could do anything about it).
And after I had
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885988
Title:
The software center Ain't really working at all...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
Public bug reported:
This does not really affect only myself, but also my little sisters computer.
You can't really browse software center, it's REALLY slow...
Also there is two banners at the top, it shows "OpenShot" and "Braid" --
it did that on my sisters computer a few days ago too.
But, yo
@BavarianPH: it seems that there are people in the project who interpret
any negative statement about Ubuntu, or any positive statement against
one of its 'avowed enemies' as 'heresy' and use that to 'punish' the
'heretic' who dared to utter it. This happens in the forums - which I no
longer use si
Why does bug watch updater still bother with this bug? I'd say close it
as 'fixed' until someone reopens it on a newer release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/319210
Title:
[jaunty] s
Deleting the /usr/share/icons/gnome/icon-theme.cache file brought gtk
back to life. I use a theme called 'wild-shine' but tried with many
other themes. The gnome icon-theme seems to be used by all of those.
As to what caused that cache file to become corrupt is a question I have
no answer to. Thes
valgrind log
** Attachment added: "valgrind.log"
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/690244/+attachment/1765871/+files/valgrind.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
Running up to date natty (11.04, last update Tue Dec 14 17:30)
All gtk2.0 and many Qt apps crash in gtkicontheme due to an
uninitialized parameter (theme_name). This currently makes it impossible
to log in through X since the gdm greeter also crashes. When logging in
using st
Installing a new package in a terminal is also slowed down tremendously
by this memory and processor hogging bit of python prototype code. An
example might help so here it goes. I just installed the new Opera beta
by downloading the package and pointing dpkg -i at it. Dpkg went to
work...
$ s dpkg
This crash is not limited to Thunderbird 3.x: Firefox 4.x hangs on
startup while Seamonkey 2.x crashes on startup due to appmenu-gtk.
The affected seamonkey identifies itself as follows:
Mozilla/5.0 (X11; Linux i686; rv:2.0b4pre) Gecko/20100815
SeaMonkey/2.1a3pre
Firefox 4.x:
Mozilla/5.0 (X11;
I just got bitten by this bug on Lucid. Currently gnome-power-manager
uses ~120 MB resident memory after running for about two weeks:
$ ps auxw|grep gnome-power-manager|grep -v grep
frank 2735 0.0 16.1 186140 123588 ? SApr03 8:09
gnome-power-manager
Most of that memory is used o
I'll send a message to the mesa-dev list to see what the reaction is.
While the patch makes it possible to run software which depends on RGBA
visuals it is clear that it does not always work as it should, eg. text
in clutter shows up as black or white rectangles. This might be caused
by a faulty im
Instead of fiddling with filenames you can just purge the gnome-codec-
install package:
sudo dpkg -P gnome-codec-install
or
sudo apt-get autoremove --purge gnome-codec-install
--
Rhythmbox keeps trying to install codecs
https://bugs.launchpad.net/bugs/204566
You received this bug notification
Do you happen to have a media player like rhythmbox running in the
background? Some of those also try to mount MTP devices and will happily
mount your camera making it inaccessible to other programs.
For rhythmbox the solution is simple: disable the MTP plugin.
--
can't mount digital camera sho
I noticed that the original submitter runs the framebuffer at 16bpp
instead of 24. The patch does NOT add RGBA modes for 16 bit visuals so
to use clutter he'll have to switch to 24bpp.
--
netbook-launcher crashed with SIGSEGV in glGetString()
https://bugs.launchpad.net/bugs/467474
You received th
I have patched the savage driver so it exposes modes with non-zero alpha
depth. The patch only changes the modes which the driver exposes, I have
not verified that all exposed modes are actually functional. Using the
patched driver clutter applications are functional (within the
constraints of the
OK, I have made some progress with Clutter and the savage. There are two
things at play here:
1) clutter always requests non-zero alpha depth when looking for
visuals. The savage driver does not support non-zero alpha depth so it
does not return any visuals. Clutter uses RGB visuals by default but
OK, I have made some progress with Clutter and the savage. The failure
to acquire a visual is caused by clutter requesting non-zero alpha depth
when checking for available visuals. The savage driver does not support
alpha so it never returns a usable visual. I changed clutter to get rid
of this req
*** This bug is a duplicate of bug 467474 ***
https://bugs.launchpad.net/bugs/467474
Never mind... wrong cut/paste...
--
Double-clicking Ubuntu icon on top-left corner right after startup
https://bugs.launchpad.net/bugs/473200
You received this bug notification because you are a member of Ub
*** This bug is a duplicate of bug 467474 ***
https://bugs.launchpad.net/bugs/467474
possible dup? https://bugs.launchpad.net/ubuntu/+source/netbook-
launcher/+bug/473200
--
Double-clicking Ubuntu icon on top-left corner right after startup
https://bugs.launchpad.net/bugs/473200
You received
As it stands now all clutter apps crash when using the savage driver (on
a T23). This is what the clutter test apps do:
(gdb) c
Continuing.
ClutterX11-Message: [BACKEND] ./clutter-backend-x11.c:143: XOpenDisplay on
':0.0'
ClutterX11-Message: [BACKEND] ./clutter-backend-x11.c:170: Getting the X sc
This problem is increasing in importance as Clutter gets added to more
and more programs. I just tried to import some photos using gthumb:
$ gthumb
(gthumb:24916): ClutterGLX-CRITICAL **: Unable to find suitable GL
visual.
** ERROR **: Unable to initialize GtkClutter
aborting...
GLX works, glxg
I have not seen this problem in Lucid so for my part this bug can be
considered 'fixed'.
--
Pulseaudio dies after hogging the cpu for a while, points blame at alsa: 'Mhmm,
actually there is nothing to rewind'
https://bugs.launchpad.net/bugs/385616
You received this bug notification because you a
Same here on Lucid as well as before on Karmic. Printing PDF to my
networked Laserjet 2200 either results in a vey slow job or a
blinking attention light and no output but mostly it just silently
fails. Printing the same document using the foomatic/pxlmono driver
works but gives mediocre qu
BTW, to get cups to print again until this bug is fixed please downgrade
libpoppler to 0.12.0. This version can be downloaded from the 'pool':
http://archive.ubuntu.com/ubuntu/pool/main/p/poppler/ (find the version
for your architecture)
--
Compilation fails because of changed interface in libpo
PS. to find out what version of libpoppler is used in a bug report you
can look at the 'dependencies' file which is (or should be) attached to
the report (in posting #1)
http://launchpadlibrarian.net/36212913/Dependencies.txt
...
...
libpng12-0 1.2.40-1
libpoppler5 0.12.2-2.1ubuntu1
libpopt0 1.15
This bug also causes current cups on current Lucid (with libpoppler
0.12.2) to refuse printing anything as it was compiled with the old
version of libpoppler. It does not print because pdftopdf fails
complaining about a missing symbol:
symbol lookup error: LaserJet_2200: undefined symbol:
_ZN13Gfx
Your build servers are out of date, please update them. Current version
of libpoppler on Lucid is 0.12.2-2.1ubuntu1, not 0.12.0-0ubuntu2. The
build failure occurs as stated with *current* Lucid... One of the
changes between 0.12.0 and 0.12.2 is the aforementioned patch.
--
Compilation fails becau
New bug opened in cups:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/489791
--
pdftopdf crashes
https://bugs.launchpad.net/bugs/488752
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.
Public bug reported:
Binary package hint: cups
The current cups package does not compile since an interface in
libpoppler has changed. The interface change in libpoppler comes from
this patch:
http://lists.freedesktop.org/archives/poppler/2009-October/005198.html
This has caused the interface t
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/36212910/BootDmesg.txt
** Attachment added: "CupsErrorLog.txt"
http://launchpadlibrarian.net/36212911/CupsErrorLog.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/36212912/CurrentDmesg.txt
** A
This is not a bug in poppler. It is a bug in pdftopdf as bundled with
cups. Currently cups can not be compiled with the latest libpoppler
because the interface to iccColorSpaceCache (in libpoppler) has changed
as can be seen in the patch linked to above.
--
pdftopdf crashes
https://bugs.launchpad
Me Too!
Demangled the missing function is GfxColorSpace::parse(Object*, Gfx*)
This seems to have been introduced by this patch:
http://lists.freedesktop.org/archives/poppler/2009-October/005198.html
--
pdftopdf crashes
https://bugs.launchpad.net/bugs/488752
You received this bug notification be
There is a notice in Mono's Uri.cs that there is a difference between
Mono 1.2 and Mono 2.0 in how scheme name characters are checked:
// Check scheme name characters as specified in RFC2396.
// Note: different checks in 1.x and 2.0
(mcs/class/Syste
Sebastien: the easiest way to import a 'buggy' image (?) is to remove
the colon from the name... or is that not what you meant?
To get f-spot to run as it is (without any patches) I'd suggest changing
the name of the picture on the filesystem and in the database. Even
though you could %-encode col
It does seem to be the colon in the filename which causes the crash. I
ran a photos.db through an instrumentd f-spot with the following result:
...
...
AppendValues ( Gtk.TreeIter, 2003%20Kitchen%20Before)
AppendValues ( Gtk.TreeIter, Michigan)
AppendValues ( Gtk.TreeIter, Volume%202)
AppendVal
I notice there is a colon in that filename. Unix has no problems with
that but Windows does. Maybe mono does as well? That would be a bug by
the way...
--
F-spot crashes when i start It.
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
B
To respond to my own question: I had a look at clutter (clutter/glx
/clutter-glx-texture-pixmap.c to be specific) and saw that it tries to
use GL_ARB_texture_non_power_of_two followed by
GL_ARB_texture_rectangle. The savage driver does not support those
extensions. As to whether it is possible to a
Problem still exists on latest Lucid with T23 / SuperSavage. Does
Clutter require non power of two support like Compiz does? If so that
will be the culprit as the current Savage driver does not support this.
--
Crash with ClutterGLX critical
https://bugs.launchpad.net/bugs/293201
You received thi
As I already stated in #28 this bug has *nothing* to do with compiz,
compositors, window managers or anything else of that sort. If turning
off compiz changes something you should file another bug for *compiz*.
--
GNOME "Main Menu" panel applet slow to open on first click (NOT compiz related)
htt
Yep, the problem is still alive and kicking. Just opened the menu, it
took 25 seconds to appear...
--
Gnome menu is slow when clicking for the first time
https://bugs.launchpad.net/bugs/12040
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Looking at the differences between svolume_sse.c from pulseaudio 0.9.16
and the current one I noticed that those changes are only cosmetical -
only a comment has changed. It does not make sense to try to patch
that... But you can of course try the patch I posted in #19 and see if
that works for you
PPS: yes I know that usplash has been deactivated...
--
udev 147 outputs warnings about default rules
https://bugs.launchpad.net/bugs/430654
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.u
PS Scott #20, why would there be any danger of hosing the system by
fixing a bug? Those {unique} parameters currently cause problems, they
are a new addition to the rules file, it works fine without (just check
the file used in Debian for an example). If and when udev starts
supporting them they ca
I should add that I run pulseaudio on a Thinkpad T23 with a Pentium
III-m which does NOT support SSE2. As I do not have any systems
available which do support SSE2 I can not test the validity of
svolume_sse.c (which actually contains SSE2 code, not SSE...). Someone
else, like the original bug repor
OK, I found it. The problem - in my case at least - lies in
svolume_mmx.c (not svolume_sse.c). Reverting that file back to the
previous version gets rid of the problem. These are the changes which
caused the appearance of the distorted sound problem on my box:
diff -pruN ../pulseaudio-0.9.16~test7
Another observation: the volume control on a client (in my case mpd)
does not actually change the volume. There are three states:
volume maxed, sound OK
volume between maxed and minimum, sound distorted at full volume
volume minimized, no sound
--
pulseaudio crackle/distortion with cs46xx on lat
Reverted svolume_sse.c does NOT solve the problem - the bug lives
elsewhere.
--
pulseaudio crackle/distortion with cs46xx on latest update
https://bugs.launchpad.net/bugs/428619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
After modifying that incantation a bit by adding PULSE_NO_SIMD=1 to the
mpd init script as mpd starts its own version of pulseaudio the noise
dissappeared... in other words the recent problems with distorted sound
ARE caused by the SSE-optimized code... There are very few changes to
the actual asse
Same problem here on different hardware running latest pulseaudio from
ubuntu-audio-dev. Symptoms are the same: sound is sort of allright when
the volume client is maxed, anything below that sounds from bad to
worse. Being that the symptoms seem to be volume-related I wonder if
this is due to some
Edit that file (/lib/udev/rules.d/50-udev-default.rules) and remove the
'unique' classifiers. The attached patch will accomplish this. This
solved the issue for me.
** Attachment added: "Revert to normal SYMLINK, remove the 'unique' classifiers"
http://launchpadlibrarian.net/31965047/udev-50-d
Broken in Karmic here as well, seems to coincide with the introduction
of bash 4.
To get tab completion working again I used a relatively ancient version
of /etc/bash_completion (RELEASE: 20060301) in combination with the
existing /etc/bash_completion.d directory. This file (which comes from
an ea
OK, I see. I assumed that the upstream patch was integrated in the
vanilla source, which it wasn't...
--
pulseaudio crashed with SIGILL in pa_volume_memchunk()
https://bugs.launchpad.net/bugs/418448
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
...and stranger still, the source I get from the PPA does NOT contain
the patch. How can that be?
$ grep -c -i sse2
pulseaudio-0.9.16~test7-14-g7ca81/src/pulsecore/svolume_sse.c
0
zero? And the binary also contains the 'original' function names:
$ nm -D /usr/lib/libpulsecore-0.9.16.so |g
It seems like the patch did succeed this time around, version
1:0.9.16~test7-14-g7ca81-0ubuntu3~ubuntuaudiodev1 works on my T23...
What went wrong last time?
--
pulseaudio crashed with SIGILL in pa_volume_memchunk()
https://bugs.launchpad.net/bugs/418448
You received this bug notification because
Unfortunately the latest version from the ubuntu-audio-dev
(1:0.9.16~test7-14-g7ca81-0ubuntu2~ubuntuaudiodev1) exhibits the same
bug again:
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 0xb3d3cb70 (LWP 25096)]
0x001f03b4 in pa_volume_s16ne_sse (samples=0xb3d7e028, volum
As the main problem of the current pulseaudio code lies in the fact that
it claims to use 'SSE' optimised code while it actually uses SSE2 (or
later) optimized code, the simplest solution is to change the activation
threshold for these optimisations. The attached patch achieves this and
works on my
...and the version in the ubuntu-audio-dev
(pulseaudio-0.9.16~test7-14-g7ca81) does NOT fix the problem:
fr...@ostrogoth:/usr/src/pulseaudio-0.9.16~test7-14-g7ca81/src$ pulseaudio
-k;script -c 'gdb pulseaudio' ~/debug_pa_5
E: main.c: Failed to kill daemon: No such file or directory
Script started
Attached is a scripted dump of gdb running pulseaudio through the crash.
The salient bits are:
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 0xb3d48b70 (LWP 19218)]
0x00163d2e in pa_volume_s16ne_sse (samples=0xb3d7e028, volumes=0xb3d45ca0,
channels=2, length=4144)
Public bug reported:
Binary package hint: autoconf2.13
I've seen this happen before with autoconf2.13 and worked around it by
manually uninstalling it. Now the latest updates tried to install it
again, with the same results:
Unpacking autoconf2.13 (from .../autoconf2.13_2.13-59_all.deb) ...
Leav
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/30341878/AptOrdering.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/30341879/Dmesg.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/30341880/DpkgTerminalLog.gz
--
packag
To whoever lies behind the decision to put a revenue-gathering extension
in the base browser package: this is not the way to win support from
free software users. If you want to enable your users to assist in
gathering revenue for your company or group do it in a totally open and
completely volunta
This bug also occurs on my T23 (PIII-m -> x86) with current Karmic.
--
'These windows do not support "save current setup"' metacity warning when
logging in with gdm 2.26
https://bugs.launchpad.net/bugs/395324
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/27732641/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/27732642/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27732643/Dependencies.txt
** A
Public bug reported:
Pulseaudio stops playing sound and starts hogging the cpu with regular
intervals since updating to karmic. After hogging around for a bit it
dies, only to be revived like a Phoenix a few moments later. This new
instance will play sound for a bit but eventually it also fails (r
OK, and now the same with autoconf2.13 installed...
s apt-get install autoconf2.13
...
The following NEW packages will be installed:
autoconf2.13
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 351kB of archives.
After this operation, 1356kB of additional disk space wi
Sure:
$dpkg-divert --list | grep auto
$
(sound of crickets in the background)
In other words, zilch...
--
autoconf failed to install
https://bugs.launchpad.net/bugs/328270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I can confirm this problem with a homebrew 2.6.30-rc2 kernel and the
ath5k driver. As to whether networkmanager, wpa_supplicant or any other
piece of the wireless action is the culprit here I can not give an
answer. I do suspect that this has something to do with the ath5k driver
(and, obviously, o
For all you 'unsubscribe' parrots here's a clue + solution:
Follow this link:
https://bugs.launchpad.net/ubuntu/+source/hotkey-
setup/+bug/356157/+subscribe
Click the button. Voila, you're unsubscribed without spamming everyone
with failed attempts to do so. That link can be found on any LP bug
A missing 'fi' (after 'if') causes the init script to bail out. The
attached patch solves this problem.
** Attachment added: "Add missing 'fi' statement to fix error on
upgrade/startup"
http://launchpadlibrarian.net/24860046/hotkey-setup_fix_missing_fi.patch
--
package hotkey-setup 0.1-23ubu
Good to hear, then I'll be able to ditch the 'reinstall_minicommander'
script (sudo dpkg -r mini-commander; sudo apt-get -f install; sudo dpkg
-i --force-all $minicommander)
--
should not ship mini-commander files when it's not built
https://bugs.launchpad.net/bugs/347653
You received this bug no
related Gnome bug: http://bugzilla.gnome.org/show_bug.cgi?id=576613
--
should not ship mini-commander files when it's not built
https://bugs.launchpad.net/bugs/347653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Sure, I can try to get their attention again... it has been a while...
--
should not ship mini-commander files when it's not built
https://bugs.launchpad.net/bugs/347653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Here's a new version of the patch which corrects a problem for those who
actually want to build the gnome-applets package WITH mini-commander,
instead of using an external mini-commander. The bug was that I used the
wrong directory name in the Makefile.in (but not in Makefile.am)
** Attachment add
Original bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/34732
Link to patch: http://launchpadlibrarian.net/22037527/20_mini-
commander_include_server_file_only_when_built.patch
(patch should still apply to current version)
--
package gnome-applets-data 2.26.0-0ubuntu1
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24294515/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/24294516/DpkgTerminalLog.gz
--
package gnome-applets-data 2.26.0-0ubuntu1 [modified:
usr/lib/bonobo/servers/GNOME_MiniCo
Public bug reported:
Binary package hint: gnome-applets
gnome-applets still, after 3 years, contains the
'/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server' file for the
long-deprecated mini_commander applet. This makes it impossible to use a
stand-alone version of mini_commander without r
I doubt that the i815 acceleration-related problem is caused by the same
bug so it would not surprise me if that problem remains after 1.6 has
been pulled.
--
[jaunty] segfault during X startup with randr < 1.2 drivers
https://bugs.launchpad.net/bugs/319210
You received this bug notification beca
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/22912641/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/22912642/DpkgTerminalLog.gz
--
package python-support 0.8.7ubuntu1 failed to install/upgrade: package
python-support is
Public bug reported:
Binary package hint: apt
This appeared during a dist-upgrade. Since when is it considered an
error to update/install a package which has already been installed? I
know that dpkg has no qualms about reinstalling packages:
s dpkg -i /var/cache/apt/archives/python-support_0.8.7
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/22535037/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/22535038/DpkgTerminalLog.gz
--
autoconf failed to install
https://bugs.launchpad.net/bugs/328270
You received this bug no
Public bug reported:
Binary package hint: autoconf
This came up during the last dist-upgrade in Jaunty. An attempt to
manually install the package from cache fails like this:
s dpkg -i /var/cache/apt/archives/autoconf_2.63-2ubuntu1_all.deb
[sudo] password for frank:
(Reading database ... 28382
I am seeing file corruption when copying from a Windows NT4 server to an
up-to-date version of Jaunty with a 2.6.29-rc2 kernel (but also using
the stock Jaunty kernel) using gvfs. The files in question have NOTHING
to do with OOo, they are JPEG's from a digital camera. Files are
reliably corrupted
Now, almost three years after the initial bug report this problem still
remains...
I made a small patch to get rid of all traces of mini-commander in the
gnome-applets package when it is not built. If anyone knows of a valid
reason to keep the server file for a non-existent applet around please
sp
1 - 100 of 154 matches
Mail list logo
