*** This bug is a duplicate of bug 1867431 ***
https://bugs.launchpad.net/bugs/1867431
And one more log of my terminal session during the problem.
Was paying attention on IRC; another bug #1867423 pointed out a symlink.
`ln -s /lib/x86_64-linux-gnu/libcrypt.so.1.1.0 libcrypt.so.1`
in another
*** This bug is a duplicate of bug 1867431 ***
https://bugs.launchpad.net/bugs/1867431
Ran into this myself.
Here's my wajig history. Normally I run 'dailyupgrade' when I have a
chance to get this build VM updated, and then rebuild my ISOs with it
after a reboot, on a matching kernel so the
*** This bug is a duplicate of bug 1867431 ***
https://bugs.launchpad.net/bugs/1867431
Ran into this myself.
Last thing I saw in IRC was:
"I bet the affected users all had the bad libcrypt1 installed, from the day
that it incorrectly migrated to the release pocket"
So, here's my wajig log
Hm. After thinking about this a little, perhaps there is a way to have cake and
consume it justly.
Since `ss` is now being used to check ports, I suggest a postinst check with
`ss -6` to see if the icmp6 entry exists or not. If it does not exist, write a
marker file out on disk that
This change would break IPv6 support for nginx on all of my ISO spins.
It's also doubly aggravating that edits to nginx.conf drive apt up the
wall asking for 3 way merges; so I simply stopped editing nginx.conf and
moved to using nginx/conf.d for *everything* because it kept breaking
I'm also getting this from a fresh netinstall of bionic, and picking the
lubuntu desktop (qt) option from tasksel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770801
Title:
Xsession: unable to
"the news server can generate the most relevant message-of-the-day"
So, you promise it's not just going to return the output of GNU fortune
over and over?
And that the serverside will be hardened against exploitation? PS, do me
a favor and make sure it's written in a dynamic scripting language
jeez, and i nearly missed
```
cpu="$(grep -m1 "^model name" /proc/cpuinfo | sed -e "s/.*: //" -e
"s:\s\+:/:g")"
```
So not just uptime, but you get
"Intel(R) Xeon(R) CPU E31230 @ 3.20GHz"
from me too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
```
read up idle < /proc/uptime
uptime="uptime/$up/$idle"
USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime"
```
Uh, okay, I can understand the curl version, the platform and the
cputype; but the uptime of my nodes is nobody's business but my own.
The platform and CPU type are exposed by
Following through on the instructions, "When the package is ready in
Debian, please set this bug status back to "confirmed". Thank you."
** Changed in: xz-utils (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Booted system up and apport wanted to send a crash report from gnome-
disks, so here it is.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-disk-utility 3.18.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic
Public bug reported:
application seems to have segfaulted?
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-disk-utility 3.18.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Some notes -- This seems to happen after creation of the partition, but before
formatting it.
Easiest workaround I have is just relaunch gnome-disks and format the partition
it created just before crashing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Workaround: Stop, and then Start the "Desktop" from the LXQT Session
Settings applet.
** Attachment added: "lxqt-1604-2015-12-10-14-40-06.png"
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1525027/+attachment/4532881/+files/lxqt-1604-2015-12-10-14-40-06.png
** Description
Public bug reported:
VMWare ESXi 5.x (IDE disk) Netinstall of Xenial 2015-12-10, "lxqt-
metapackage openbox qupzilla obconf lubuntu-artwork" following
https://wiki.ubuntu.com/Lubuntu/LXQt#Installing_LXQt_on_fresh_system
Rebooted, First thing I did after logging in was try to change resolutions.
Public bug reported:
Just doing a dist upgrade when systemd freaked out and failed to connect
to the system bus.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: grub-common 2.02~beta2-26ubuntu5
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
Public bug reported:
Wily daily from http://cdimage.ubuntu.com/lubuntu/daily-live/20150817.1
/wily-desktop-amd64.iso fails to install in vmware 11.1.2.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity 2.21.27
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux
I've spent some more time in tracking this down.
If you have a video adapter that is 3D capable and supports KMS, such as
the aforementioned AMD E350 APU, you shouldn't have any issues. IF
you're running some... older hardware, then this might bite you.
Here's the change that made this occur:
Here's an *UNOFFICIAL* ISO based on beta2 (I built it on march 30th) with the
packages corrected.
You may use it to test to see if the specific fix I've played with will work on
other people's hardware.
http://files.sllabs.com/files/long-term/downloads/isos/kamikazi-15.04-beta2-amd64.iso
Your
*** This bug is a duplicate of bug 1441843 ***
https://bugs.launchpad.net/bugs/1441843
the MD5 was asked for, here it is along with the sha1sum.
57949aea7065ea287eeda28821b87543fe95f8b0 kamikazi-15.04-beta2-amd64.iso
894dcc980b19187b1a1be9eb79fa8c8a kamikazi-15.04-beta2-amd64.iso
--
You
This is currently causing some problems for me -- I'm using grub2 to
boot a LiveISO with TORAM=Yes from a DiskOnModule to implement a
hardware appliance.
It's *REALLY* aggravating that tail -f /var/log/filename does not work
as expected.
Could someone bring that overlayfs inotify kernel patch up
Just a note; I've got a lot of experience with the 1068E controller.
Make sure you're running a recent firmware.
I have 1.33.00, Phase 21, flashed on most of my 1068Es of various
vendor brands.
http://lime-technology.com/forum/index.php?topic=12767.0
Versions at Phase 20 (1.32.00 and below) had
Okay, I got this to work a heck of a lot easier.
So, I read startlubuntu.
blah blah blah blah, oh.
Last line.
# Start the LXDE session
exec /usr/bin/lxsession -s Lubuntu -e LXDE
Well, let's try it.
http://puu.sh/69hyP.png
X2Go: Custom Desktop
lxsession -e LXDE -s Lubuntu
Well, that seems
Public bug reported:
Installing to USB memory stick from TORAM=Yes live boot from same device
crashes ubiquity.
I don't know why.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.20
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041128
Title:
Installing to USB memory stick from TORAM=Yes live boot from same
device crashes ubiquity
To manage notifications about this bug go
I'm also having issues with the motherboard indicated by the OP under
Maverick. It was working fine until ~2-3 weeks ago, and I've never heard
my PC make a sound since then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've got the same motherboard, on Maverick.
My onboard sound used to work less than a month ago; but as of a few updates
ago, it also has stopped making output.
Pulseaudio still sees the card, I maxed the mixers for pulseaudio, I checked
alsamixer and every channel is maxed, and yet aplay
Please do report it upstream as well, although I've not seen an update
to u3-tool for a while.
However: I was successfully able to 'burn' a 1.7GB iso to my Contour EX
16GB earlier today using u3-tool 0.3-1 -- Here is my log.
Note: I was *NOT* able to get /dev/sg* or /dev/sr* to work -- I had to
Just a quick note; how does one explicitly exit to the remote shell from
byobu now?
Perhaps an Exit to to this machine's console option would be good in
the F9 menu? Then it's out of the way but accessible; having it below
the profile-autolaunch would be the correct place in my opinion.
Just a
Sorry to break into this bug; but I've been trying to get empathy
working with my work's PBXInAFlash server and I just can't seem to find
any reasonable configuration guide for setting up telepathy-sofiasip.
Can anyone provide a list of resources for configuring empathy with sip?
Right now I'm
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42537977/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42537978/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42537979/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42416514/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42416518/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42416519/Disassembly.txt
** Attachment
Not so off topic. Diakonos' site links here.
I've just finished building ruby 1.9.2 for Diakonos, everything seems to work
just fine for me now.
And with Ralf's 'everybody' workaround, I finally got passenger working in a
couple minutes. (I had previously tried, got frustrated, and gave up.)
Check which clocksource your system is set to:
sudo cat
/sys/devices/system/clocksource/clocksource0/current_clocksource
Check which clocksources are available:
sudo cat /sys/devices/system/clocksource/clocksource0/available_clocksource
I get output like this:
tsc hpet acpi_pm
I'm betting your
Disk quotas are on and you're using EXT4.
Disable quotas to stop the OOPS messages:
sudo quotaoff -a -f
Disable quotas in your /etc/fstab if you're not using them.
Example:
# / was on /dev/sda2 during installation
UUID=acee041c-a2a8-4ca4-9b51-19aa423f122e / ext4
Disk quotas are on and you're using EXT4.
Disable quotas to stop the OOPS messages:
sudo quotaoff -a -f
Disable quotas in your /etc/fstab if you're not using them.
Example:
# / was on /dev/sda2 during installation
UUID=acee041c-a2a8-4ca4-9b51-19aa423f122e / ext4
Public bug reported:
Binary package hint: ubuntuone-client
Removing, cleaning, and reinstalling of the client did not work.
Could not find the authentication token to remove in seahorse (Maybe this is my
problem?)
ProblemType: Bug
.home.kamilion..cache.ubuntuone.log.syncdaemon.exceptions.log:
** Attachment added: .home.kamilion..cache.ubuntuone.log.oauth.login.log.txt
http://launchpadlibrarian.net/35801701/.home.kamilion..cache.ubuntuone.log.oauth.login.log.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35801702/Dependencies.txt
** Attachment added:
** Description changed:
-
The current version in the archive is quite old: 0.12.
eBox 1.3 is already available and takes advantage of new features of the
openLDAP version that is shipped in Karmic.
eBox 1.3 series are the same as 1.2 but with a new great feature. eBox has
gained
This is also causing me a problem in setting up karmic with ebox.
--
ebox-dhcp fails to install on karmic alpha6
https://bugs.launchpad.net/bugs/433788
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It'd be nice to get this commited to the karmic repo before the beta
period finishes up.
--
Please upgrade ebox-dhcp to 1.3
https://bugs.launchpad.net/bugs/411546
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/32842005/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32842006/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/32842007/Disassembly.txt
** Attachment
*** This bug is a duplicate of bug 417430 ***
https://bugs.launchpad.net/bugs/417430
Here's the most recent GDB log.
** Attachment added: gsd-xrandr-crash-gdb-bt-full.log
http://launchpadlibrarian.net/32685261/gsd-xrandr-crash-gdb-bt-full.log
--
gnome-settings-daemon crashed with signal
Just a note, I ran into a similar problem, and I fixed it by running
grub-mkdevicemap then update-grub again.
Something may be amiss with the way the grub2 scripts operate versus the
grub legacy scripts.
--
grub2 boot from lvm Auto-detection of a filesystem module failed
*** This bug is a duplicate of bug 417430 ***
https://bugs.launchpad.net/bugs/417430
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/32126307/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32126308/Dependencies.txt
** Attachment added:
*** This bug is a duplicate of bug 417430 ***
https://bugs.launchpad.net/bugs/417430
Thanks for wiping my full retrace out, apport. I was *JUST* about to
link it to bug 417430.
** Summary changed:
- gnome-settings-daemon crashed with signal 5 in gdk_x_error() (dbgsyms)
+
Just some notes...
The new networking scripts failed to find my br0 defined in
/etc/network/interfaces.
(Fortunately this motherboard has IPMI2 KVM-over-dedicated-IP, otherwise I
would have been up a creek)
couldn't find out how to disable upstart services, so I ended up moving
On Wed, Sep 16, 2009 at 12:05 PM, Scott James Remnant wrote:
On Wed, 2009-09-16 at 06:59 +, Kamilion wrote:
The new networking scripts failed to find my br0 defined in
/etc/network/interfaces.
(Fortunately this motherboard has IPMI2 KVM-over-dedicated-IP, otherwise I
would have been up
The only issue I'm currently having with this series is requesting an
upgrade to 'initscripts' is asking for hostname, rsyslog, and ubuntu-
minimal to be removed at the moment. This scared me enough to cancel
synaptic/update-manager and look at the list of packages a bit closer.
Found the link
Discovered my problem while searching launchpad for similar bugs.
Found some information here:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/190147
Somehow the devicemap was incorrectly generated.
running 'sudo grub-mkdevicemap' and then 'sudo update-grub' fixed my
problems.
Here's a
See #423347 for similar segfaulting.
Supermicro X8-series motherboard, 2xE5520, 16GB ram, 2X WD Black with
mpt2sas JBOD LVM.
--
grub-setup crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/386802
You received this bug notification because you are a member of Ubuntu
Getting this today too after running an update to Aug 31st's latest
karmic packages.
--
update-manager crashed with GError in __init__()
https://bugs.launchpad.net/bugs/417301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Seems to be fixed with 1:0.124.9 for me.
--
update-manager crashed with GError in __init__()
https://bugs.launchpad.net/bugs/417301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Getting bit by this as well.
Have up to date karmic on a fresh new 16 core with no user data on it yet.
Let me know how I can help test.
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
54 matches
Mail list logo
