** Changed in: lnr
Assignee: (unassigned) => Lubuntu Packages Team (lubuntu-packaging)
** Project changed: lnr => plymouth
--
package ubuntustudio-plymouth-theme 0.38 failed to install/upgrade:
ErrorMessage: под процеса инсталиран е скрипта post-installation върна грешка
за състояние за и
I just came across this issue while trying out the lubuntu-desktop
packages. Same condition exists in the postinst and postrm calls for the
lubuntu-plymouth-theme package.
** Also affects: ubuntustudio
Importance: Undecided
Status: New
** Project changed: ubuntustudio => lnr
--
packag
Marking as invalid as it appears my issues stemmed from a failing hard
drive. It's quite possible that system files were corrupted and causing
the havoc I was experiencing. With a new, and tested, hard drive
installed, we've been rock solid so far. I'll open a new report lest I
come across the same
At this moment in time, yes, this is the first occurrence and I have not
been able to reproduce it in any way. Is there anything from the log
entry that might give a clue as to its origin that I may be able to
trigger a response in order to reproduce it?
--
kernel BUG at /build/buildd/linux-2.6.2
If anything else is needed, please don't hesitate to ask.
Like I said, other than the log entry I am at a loss to what caused it.
You can see from the timestamps from the log that it was a bit over two
hours before the kernel bug and the final entry before the reboot. I had
walked away from the ma
Architecture: amd64
Dependencies:
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dial
Public bug reported:
First, I apologize for how vague this bug report may be. I'm not quite
sure how one goes about reporting kernel bugs. All I have to offer is
the fact that the machine locked up, and assuming a kernel panic of some
kind, I checked the kern.log and came across the following righ
This is still an unresolved issue.
a...@obsidian:~$ apt-cache policy pidgin
pidgin:
Installed: 1:2.5.5-1ubuntu7
Candidate: 1:2.5.5-1ubuntu7
Version table:
*** 1:2.5.5-1ubuntu7 0
500 http://us.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
a...@obsidian:~$
*** This bug is a duplicate of bug 357949 ***
https://bugs.launchpad.net/bugs/357949
** Attachment added: "gdb-pidgin.txt"
http://launchpadlibrarian.net/25083773/gdb-pidgin.txt
--
pidgin crashed with SIGSEGV in __xmlRaiseError()
https://bugs.launchpad.net/bugs/358085
You received this bu
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/25083325/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25083326/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/25083327/ProcMaps.txt
** Attachment ad
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/24817360/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24817361/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/24817362/Disassembly.txt
** Attachm
System Testing crashed with this bug on first attempt with the below
criteria. It happen while the "Gathering information from your
system..." dialog box was visible. Subsequent attempts to use System
Testing finished with no errors.
a...@osiris:~$ lsb_release -a
No LSB modules are available.
Dist
For a fresh Hardy 64-bit install, with updates and multiverse enabled,
you should be able to grab 9.0.152.0ubuntu1~hardy1 which still pulls the
binary from the download.macromedia.com location. Or, just grab the deb
file from http://packages.ubuntu.com/hardy-updates/flashplugin-nonfree
and install
I was able to restore what appeared to be a broken Jaunty installation
after receiving this error. In my case, the system would freeze waiting
for the gdm login to appear. In order to gain access to another terminal
or login prompt, I had to have it boot without the splash, either by
removing it as
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/20005831/DpkgTerminalLog.gz
--
package gnome-session-canberra None [modified:
/var/lib/dpkg/info/gnome-session-canberra.list] failed to install/upgrade:
trying to overwrite
`/usr/share/gnome/autostart/libcanberra-login
Public bug reported:
Binary package hint: gnome-session-canberra
[EMAIL PROTECTED]:~$ lsb_release -rd
Description:Ubuntu jaunty (development branch)
Release:9.04
[EMAIL PROTECTED]:~$ sudo apt-cache policy gnome-session-canberra
[sudo] password for adam:
gnome-session-canberra:
Inst
Just got this crash reported via apport alert after trying to use the
Guest session on a fully updated Ubuntu 8.10. The alert was waiting for
me when I switched back to my normal session. It reported that the Gnome
login sound crashed, but the sound played as normal when switching over
to Guest.
-
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/18360184/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18360185/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/18360186/Disassembly.txt
** Attachm
Wow. What a pain this was to remove. Raymond Slieff's idea worked, but
in my case I had to first reinstall kio-umountwrapper to make sure it
wasn't set for removal when trying to reinstall the dependent packages
of dolphin and konqueror. Each time I tried to get dolphin and konqueror
installed, apt
Sorry. After making the change I mentioned above, you'll need to restart
the server.
sudo /etc/init.d/ssh restart
--
sshd seems to be run multiple times at startup
https://bugs.launchpad.net/bugs/129789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I found this fix elsewhere.
Open /etc/ssh/sshd_config for editing. Uncomment the listening address
for 0.0.0.0.
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Change to:
# Use these options to restrict which interfaces/proto
And here's a little additional backtrace for you. During this backtrace
I can't even get nautilus to respond, not even to open a browser window,
when initiating the backtrace. As soon as I attach the PID, I can't get
nautilus to do anything. I initiate the final steps of the backtrace and
quit gdb.
I've been having the same kind of issues but with folders containing
audio clips. I have seen no ill effects when browsing folders with video
files. After some initial trial and error learning how to perform a
backtrace, the one for Nautilus I have attached here. Hope it helps. I
don't know enough
23 matches
Mail list logo
