As with #4, I was/am trying to upgrade from 12.04 LTS to 14.04 LTS.
It appears that the 14.04 upgrade is trying to do:
update-initramfs: Generating /boot/initrd.img-3.2.0-89-generic-pae
which is the my kernel from 12.04. Whether or not it should be doing
this, I don't know.
The files it
I've just hit this problem. Are there any suggestions for a fix? Or
trying one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356033
Title:
package initramfs-tools 0.99ubuntu13.5 failed to
I resolved this by removing postgresql-9.3-postgis-2.1.
It would be great if the upgrade tools could give hints about possible
problems, or display `cat apt.log | grep -i broken` in /var/log/dist-
upgrade. Any pointers would be better than nothing, which is the status
quo.
** Changed in:
Public bug reported:
I run: sudo update-manager -d
Update manager says: You must check for updates manually. Options: Check and
Close.
I click: Check.
It does: Updating cache.
Then says: There are no updates to install.
It says: New Ubuntu release '14.04.3 LTS' is available.
I click: upgrade.
Thanks, Chris.
It's sad for me, but this event was the straw the broke the camel's
back, and I have abandoned Linux on the desktop after ~15 years (Debian
hamm). If a so-called LTS release could not support an essential
function in one of the handful of its most important applications, then
I can
This is really astonishing, I just upgraded Ubuntu's Firefox to version
26.0 and geolocation is still not working. The identical version from
Mozilla works flawlessly.
I am very disappointed that there has been no acknowledgement of this
bug by Ubuntu.
--
You received this bug notification
I just upgraded Ubuntu's firefox from the repos. It is now on version
25.0.1. Geoloacation is still not working in the Ubuntu version.
The identical version from Mozilla works flawlessly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I confirm the above patch works. Thanks, Thomas.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/1210936
Title:
Warnings in munin-graph.log during each graph rendering run
To manage
I confirm the above patch works. Thanks, Thomas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210936
Title:
Warnings in munin-graph.log during each graph rendering run
To manage notifications
I installed firefox v23.01 to /opt. It picked up my settings from
~/.mozilla and everything, including geolocation worked fine.
I then let it upgrade to v25. No problems, everything, including
geolocation, worked fine.
So, I swapped back to Ubuntu Firefox v25. Sadly, geolocation stopped
working.
Looking here:
https://bugzilla.mozilla.org/show_bug.cgi?id=919153
It seems that each distro needs a new key from Google for location
tracking, er, discovery. Presumably this is at the root of the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This problem still occurs in Firefox v25.
Mozilla reported some changes to Google's API requirements that might be
the issue:
https://bugzilla.mozilla.org/show_bug.cgi?id=919153
To test:
https://developers.google.com/maps/documentation/javascript/examples
/map-geolocation
and
Robert Dyer wrote: Just grab the source code and compile it yourself -
it isn't that hard!
Let's see:
1. googled for ubuntu gnome-do source
2. found it here: https://launchpad.net/ubuntu/maverick/+source/gnome-do
3. extracted the archive
4. cd'd into it
5. ran ./configure, which moaned:
Fair enough, but do you know why the upstream fix has not rippled
through? The fix has been in place for six months now. Is there anything
we can do expedite this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This problem is still very much alive and well.
I now use a script alias to ease the pain:
alias snd='killall pulseaudio; killall gnome-volume-control-applet;
pulseaudio -D; nohup gnome-volume-control-applet /tmp/gnome-
volume.log 2 /dev/null '
pulseaudio goes to 100% on one cpu at every
Kernel 260.19.12 didn't improve matters here :( Back to 256.53 for me.
--
NVRM: os_raise_smp_barrier(), invalid context!
https://bugs.launchpad.net/bugs/656279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Seems that the Nvidia forum is down too. I'm getting 404s on
http://www.nvnews.net/vbulletin/, so can't report there atm.
--
NVRM: os_raise_smp_barrier(), invalid context!
https://bugs.launchpad.net/bugs/656279
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I left the machine for 1/2 hour, but it does not progress from the blank
screen. I simply cannot use 260.19.06-0ubuntu1. This is a huge
regression for me. I appreciate it is not this bug, but I cannot find
the appropriate bug to file against . Can anyone point me to the
appropriate bug for:
To be honest, looking at the nvidia package installed, I'm not clear
what I should or should not have. I've not had problems here before, so
I've never looked. For background, this machine was upgraded from Lucid.
I have the following installed:
nvidia-173-modaliases
nvidia-96-modaliases
Thanks for the suggestion, but I really shouldn't have to be using
backports on a system that has always worked. That doesn't solve the
problem.
I have been running 10.10 since it went beta and have solved plenty of
issues since then, as is expected, but this is bonkers.
A mainline aptitude
Maverick/GeForce GT 330M/Sony Vaio f-series
Update to 260.19.06-0ubuntu1 has resulted in my system displaying a
black screen where gdm/login should occur, Logs show no issues. Machine
is currently unusable.
How do I revert this?
--
nvidia 256.53 xorg-server 1.9.0 performance regression with
Someone over on the nvidia forums kindly suggested installing 256.53
from the nvidia repos. That has me up and running. I have no idea how
this affects further Ubuntu updates, however. The Additional drivers
tool still says (version current) [Recommended], which seems
meaningless now. Why is there
The patronising straw man lecture is really not welcomed.
Can we please stick to the facts.
--
Nvidia 173 driver does not work with xserver 1.9
https://bugs.launchpad.net/bugs/626918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I workaround my issue by installing the 256.53 drivers directly from
nvidia. So anyone else facing an unusable machine that was fine before
the 260 downdate, give this a try.
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
@quiricada How long did you leave the blank screen before the login
screen appeared. Two minutes, five, ten, twenty?
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You received this bug notification because you are a member
The only person who mentioned production machines is you. Now, please,
please, go away, Mr Straw, we are trying to fix things around here.
--
Nvidia 173 driver does not work with xserver 1.9
https://bugs.launchpad.net/bugs/626918
You received this bug notification because you are a member of
A regular aptitude upgrade installed the updated nvida-173-modaliases
and has made my maverick machine useless. I get a black screen after
starting X. No gdm/login appears. /var/log/Xorg.0.log indicates no
problems at all; it reaches enabled.
Maverick/GeForce GT 330M/Sony Vaio f-series
--
ABI
A regular aptitude upgrade installed the updated nvida-173-modaliases
and has made my maverick machine useless. I get a black screen after
starting X. No gdm/login appears. /var/log/Xorg.0.log indicates no
problems at all; it reaches enabled.
Maverick/GeForce GT 330M/Sony Vaio f-series
--
Hmm Well, X is 1.9 and nouveau is reporting that it is built for
1.8.99.905 (5 Aug, as it happens).
Then it loops through a bunch of drmOpenMinor calls, all of which return
-1 (geek for fail, I suspect).
Then finally reports
[drm] failed to open device
No devices detected.
Fatal server
As far as I remember, yes. I used ctrl+c while in gdb to get to the
prompt. But I'm pretty sure that it was still @ 100% CPU.
--
(On usb card removed) pulseaudio process goes to 100% CPU and cannot be
restarted
https://bugs.launchpad.net/bugs/636901
You received this bug notification because
There are so many regressions here it is getting very hard to test this.
The sound card is now only being recognised by the system randomly -- it
was 100% earlier. This would be okay if restarting PA (and gnome-volume-
control-applet, which appears to be far, far too tightly coupled to PA)
fixed
While debugging #11, I found that if I didn't have the card plugged in
first then it would never be recognised.
The only way that it would randomly be recognised is if I started PA,
plugged in the card, then started gnome-volume-control-applet. When the
card wasn't found, the following was
Appears to have been a one-time event. So please close.
--
cron.daily fails after upgrade to Maverick
https://bugs.launchpad.net/bugs/630922
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: gnome-settings-daemon
Description:Ubuntu maverick (development branch)
Release:10.10
Regular boot via gdm. At end of desktop start-up graphics change to
1970s-style X
.xsession-errors ends:
Error grabbing key 173, 0x9812038
Error grabbing
I rebooted with the USB sound card attached. Ubuntu sees this just fine.
I followed the instructions and attach the output. PA goes to 100%
immediately, within 1 second of removing the USB connection.
** Attachment added: pulseverbose.log
I also tried rebooting with the card disconnected. Then connected it
after login, then removed it. The same occurred as above.
I observed that memory use does not appear to be increasing while it
loops; I guess it's a loop.
--
pulseaudio process goes to 100% CPU and cannot be restarted
Further discovery. Once I have killed PA, as above, and relaunched it, I
cannot make it rediscover the USB sound card, even if I completely
remove ~./pulse
For the sound card to function again, I have to reboot.
--
pulseaudio process goes to 100% CPU and cannot be restarted
Seems we've gone to 2.6.35-21
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: pulseaudio
Description:Ubuntu maverick (development branch)
Release:10.10
When I unplug my USB sound card, which works fine, the pulse audio
process goes to 100% CPU (on one processor) and remains in that state.
Attempts at a restart result
Attached is the result of:
echo autospawn = no ~/.pulse/client.conf
killall pulseaudio
LANG=C pulseaudio - ~/pulseverbose.log 21
pacmd set-log-time 1
sudo /etc/init.d/pulseaudio start
** Attachment added: pulseverbose.log
$ pulseaudio --start
N: main.c: User-configured server at
{c10255de8cac4c5c96d4ac784c091d51}unix:/home/marc/.pulse/c10255de8cac4c5c96d4ac784c091d51-runtime/native,
not autospawning.
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
You
To get restarted, I have to:
pulseaudio -D
killall gnome-volume
/usr/bin/gnome-volume-control-applet
Seems to me that the last is a bug too. The applet disappears when
pulseaudio is killed, but remains in memory and doesn't reappear when
another pulseaudio instance is started.
--
pulseaudio
I forgot, I also deleted ~./pulse
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I mean ~/.pulse
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Guess it's back to the drawing board then :(
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Both mics still not working using the PPA. File attached.
I can still get the ext mic working by using HDAanalyzer to toggle the
switches and set the volume.
These are my notes to myself:
1. node0x23 mute and unmute Val0 because it shows default unmuted but in
fact it is muted
2.
I guess you _could_ call it a feature. A bit like having a car with an
engine that you can't ever switch off. Not a very useful feature. I have
a rule that says that removing something is not a feature. A design
choice, but not a feature.
I am in the same situation regarding a shared switch for
Yup, apache installed here too.
Nice find, Bilal.
--
init script resets isig flag in an incorrect manner
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Oh, and btw, it's voilà. Viola is a big violin, and the female
protagonist in the Patrick Ness trilogy Chaos Walking ;)
Right, off to confirm your test findings.
--
init script resets isig flag in an incorrect manner
https://bugs.launchpad.net/bugs/626723
You received this bug notification
Just rebooted and the problem has gone.
--
init script resets isig flag in an incorrect manner
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Confirmed fixed.
--
Bluetooth device absent after 20100906 update to maverick
https://bugs.launchpad.net/bugs/631818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hmm I prefer to stay with aptitude, so this should work:
$ sudo aptitude install pkgname=version
and perhaps
$ sudo aptitude hold pkgname
So, now I need to know the package name and source, since I presume the
required package comes out of the lucid repos.
Currently,
$ aptitude versions gdm
i
After leaving the machine switched off over night, I can now, at least,
load bluetooth-properties.
However, the panel icon is still missing. I've tried restarting the
gnome panel a few times, but that doesn't improve things. Each time I
restart the panel I get the following msg in
I installed blueman and everything just works. Including the icon and
the ability to deactive bluetooth.
--
bluetooth-properties crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/631548
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tried on Ubuntu 10.10.
After loading there are 3 bluetooth process: blueman-applet, bluetoothd,
blueman-mechani
About 15 second after bluetooth is deactivated via the widget, first
blueman-mechani fails, then almost immediately bluetoothd.
Because of this I get:
$rfkill list
1: sony-bluetooth:
Dude, using a separate tool to determine, unequivocally, that all the
hardware components work and are inter-operate, removes any doubt that
the problem is machine-specific. In debugging terms, that's pretty darn
useful information.
As you might say, tu petes plus haut que ton cul.
--
Installing linux-alsa-driver-modules-2.6.35-19-generic killed all audio
outputs. See attached.
** Attachment added: missing audio outputs.png
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1549961/+files/missing%20audio%20outputs.png
--
[Realtek ID 275] No
** Attachment added: expected audio outputs.png
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1549962/+files/expected%20audio%20outputs.png
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
You received this bug
There ya go.
** Attachment added: alsa-info.txt.1f2vLBUiFV
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1550660/+files/alsa-info.txt.1f2vLBUiFV
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
You received this
Can you give me a pointer as to how to do that. I'm technical, so terse
instructions should do.
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: bluez
Description:Ubuntu maverick (development branch)
Release:10.10
Bluetooth was working fine in maverick until today's update, 20100906.
The panel widget, previously fine, is now absent.
bluetoothd is running
When I try to run
$ rfkill list
0: sony-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: sony-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard
$ hcitool scan
Scanning ...
$ hcitool dev
Devices:
hci02C:81:58:B9:F4:43
$ sudo hciconfig hci0 reset
$ hcitool scan
Scanning ...
$
--
Bluetooth device absent after 20100906 update to maverick
https://bugs.launchpad.net/bugs/631818
You received this bug notification because you are a
Possibly related to change here:
http://www.ubuntuupdates.org/packages/show/214599
which added build-depends on libgconf2-dev. Possible further dep issues,
since this is a dev package.
--
Bluetooth device absent after 20100906 update to maverick
https://bugs.launchpad.net/bugs/631818
You
I confirm crash reproduced after reboot. No change.
--
bluetooth-properties crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/631548
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I did, of course, upgrade before rebooting.
Package: gnome-bluetooth
State: installed
Automatically installed: no
Version: 2.31.6-0ubuntu3
Priority: optional
Section: gnome
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Uncompressed Size: 1,135k
--
That said, my bug:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/631818
was marked as a duplicate of this bug, and it might well no be.
--
bluetooth-properties crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/631548
You received this bug notification because
Perhaps I should add that I have checked
apps/gdm/simple-greeter/disable_user_list
--
Hitting send at login seems to restart X
https://bugs.launchpad.net/bugs/630453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: logrotate
Description:Ubuntu maverick (development branch)
Release:10.10
Version: 3.7.8-6ubuntu1
After upgrading from Lucid to Maverick, I received this email.
Subject:
Anacron job 'cron.daily' on blah
Body:
/etc/cron.daily/logrotate:
Due to the lack of response, in desperation -- I was about to move to
Debian -- I upgraded to Maverick. The problem is no longer there. For me
Maverick is an improvement on Lucid in almost every way.
--
System freeze when plugging in USB audio device
https://bugs.launchpad.net/bugs/612077
You
Public bug reported:
Binary package hint: gdm
Boot machine.
gdm login screen appears.
Scenario one:
Type nothing
Hit send - screen goes black, which looks like an X restart.
gdm login screen reappears.
Login as expected.
Scenario two:
Type user name
Hit send - screen goes black, which looks
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/630453/+attachment/1544189/+files/Dependencies.txt
--
Hitting send at login seems to restart X
https://bugs.launchpad.net/bugs/630453
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not meaning to confuse things, but I upgraded to Maverick and there have
been some changes for me.
Speaker previously required linux-alsa-driver-modules-2.6.32-??-generic,
but they now work without this package; the kernel is now 2.6.35-19.
The inbuilt and plug-in mics still don't work, although
Fix noted here:
http://code.google.com/p/vaio-f11-linux/wiki/EnableMicrophone
Fill attached.
** Attachment added: alsa-info.txt.DvImsQC6Lj
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1540244/+files/alsa-info.txt.DvImsQC6Lj
--
[Realtek ID 275] No audio
I just tested the same device on the same machine with Linux Mint, which
is based on Lucid. The device works fine. Here is the dmesg:
[ 1119.152738] usb 2-1.5: new full speed USB device using ehci_hcd and address 6
[ 1119.628177] hub 2-1:1.0: unable to enumerate USB device on port 5
[
I notice that there is useful debug information in the attached
WifiSyslog.txt:
Jul 31 15:59:12 localhost kernel: [21311.163931] usb 2-1.5: new full speed USB
device using ehci_hcd and address 5
Jul 31 15:59:13 localhost kernel: [21311.679546] hub 2-1:1.0: unable to
enumerate USB device on port
Public bug reported:
When I plug in a Novation X-Station (a usb soundcard) and then try to
perform any other action, the whole system freezes. I cannot switch to
the terminal and SysRQ keys also don't work.
If I leave htop open in a terminal and then plug in the device, I can
see that modprobe
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52785684/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52785685/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52785686/BootDmesg.txt
**
You might want to try the fix from here:
http://code.google.com/p/vaio-f11-linux/wiki/EnableMicrophone
#34 here worked for me:
http://code.google.com/p/vaio-f11-linux/issues/detail?id=2can=1
This requires using the HDA anayzer from here:
This is a colossal mess. The bottom line seems to be that one has to
recheck all service configs after an update, whether sysv or upstart.
One also has to know which services have been upstarted in order to
derive their expected behaviour.
Confidence in services' configs at reboot has just been
I use the battery applet mentioned here
http://ubuntuforums.org/showthread.php?p=9271002
gnome-volume-control-applet is fine. Just remove the indicator applet in
its entirely. Job done.
Bluetooth is an app icon in the regular notification area, not one of
the indicator applet entries.
Btw, if
Please close. I no longer use this application.
--
In KDE, adds a file association for every file type
https://bugs.launchpad.net/bugs/410484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Feel free to close.
--
[Acer TravelMate 4650] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/360384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
All a bit of a mess. I've ended up, unconsciously, removing all the new
indicator/status applets and panels, and using replacements. One by one
they fell. I'm even back to Quod Libet to replace Rhythmbox whose
accessibility has been strangled by this change.
I regard this experiment as a failure.
Unfortunately, this problem was with a laptop that I returned last week,
so I'm unable to diagnose further. The problem was still there last
week, though.
--
automatic resume after suspend
https://bugs.launchpad.net/bugs/505190
You received this bug notification because you are a member of
Public bug reported:
(`ubuntu-bug -p linux` performed and sent.)
$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
After upgrading from jaunty to karmic suspend is behaving in the
following manner.
After booting, the first suspend works as normal. Subsequent attempts
result in
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/37648945/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/37648946/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37648947/BootDmesg.txt
**
I think this was an automated submission. I certainly haven't seen for a
long while.
--
[Acer TravelMate 4650] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/360384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30053570/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/30053571/DpkgTerminalLog.txt
--
package envyng-core 2.0.1ubuntu1 failed to install/upgrade: subprocess
post-installation
Public bug reported:
Binary package hint: envyng-core
Description:Ubuntu 9.04
Release:9.04
Install failed as per attached docs. Install script follows:
Setting up envyng-core (2.0.1ubuntu1) ...
Traceback (most recent call
Sorry, my mistake, alternatives messed with my python config and wiped a
symlink causing this problem.
All is now good. Please close.
--
package envyng-core 2.0.1ubuntu1 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
Public bug reported:
Binary package hint: kchmviewer
After installing kchmviewer, I noticed when right-clicking the Open
with... option in any KDE file manager, that there is an KchmViewer
entry.
On closer inpection in KDE System Settings/File Associations, I notice
that there is a KchmViewer
Public bug reported:
Binary package hint: pida
Description:Ubuntu 9.04
Release:9.04
Package: pida
Version: 0.5.1-5ubuntu1
The PdfTex Preview plug-in install, but fails to start due to a missing
dependency on line 40 in pdftex_preview.py:
# other imports
import
Here with kdepim-dbg installed.
As before, this was when doing right-click, Empty wastebin on Local
folders/wastebin.
Application: KMail (kmail), signal SIGABRT
[Current thread is 0 (LWP 4645)]
Thread 2 (Thread 0xabb11b90 (LWP 4661)):
#0 0xb7fad430 in __kernel_vsyscall ()
#1 0xb5bdd7b1 in
Thanks for the feedback. I upgraded to KDE 4.2.4 and things looked good
until:
Application: KMail (kmail), signal SIGABRT
[Current thread is 0 (LWP 29034)]
Thread 2 (Thread 0xac451b90 (LWP 29283)):
#0 0xb8035430 in __kernel_vsyscall ()
#1 0xb5c657b1 in select () from
Public bug reported:
I experience this bug about one in five times when emptying the
wastebin. The problem occurs when right-clicking either Local
Folders/Wastebin or mail account/Trash, and clicking Empty Wastebin.
Notes:
- All my email accounts are IMAP
- I am using the KDE wallet
$
Public bug reported:
Binary package hint: xpn
The sorting column -- set in Prefs/Groups/Visualization -- is not
retained between sessions.
I set this option to Subject (ascending) and it resets to From.
Note that I also have the Threads Pane option set to From.
** Affects: xpn (Ubuntu)
Public bug reported:
Binary package hint: xpn
I would like the option to download headers at start-up. Currently,
headers are only downloaded according to the Minutes between downloads
setting.
** Affects: xpn (Ubuntu)
Importance: Undecided
Status: New
--
xpn doesn't download
Public bug reported:
Binary package hint: xpn
When reading an article, if the periodic header download kicks in, then
xpn clears the article in the article pane.
This is probably due to the fact that I do not display read articles,
and the header download causes a refresh. It shouldn't do this
If I understood the notes I would have tested. The notes make no sense
to me at all. Judging by the lack of feedback, I guess that I'm not
alone!
--
GeForce 6600 not supported
https://bugs.launchpad.net/bugs/313306
You received this bug notification because you are a member of Ubuntu
Bugs, which
1 - 100 of 130 matches
Mail list logo
