[Bug 1866844] Re: package libc6:amd64 2.31-0ubuntu3 failed to install/upgrade: installed libc6:amd64 package post-installation script subprocess returned error exit status 127
*** 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 root terminal was enough to get apt to bring things back to sanity. ** Attachment added: "Terminal log of Wajig / Apt session demonstrating failure" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1866844/+attachment/5337113/+files/terminal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866844 Title: package libc6:amd64 2.31-0ubuntu3 failed to install/upgrade: installed libc6:amd64 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1866844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866844] Re: package libc6:amd64 2.31-0ubuntu3 failed to install/upgrade: installed libc6:amd64 package post-installation script subprocess returned error exit status 127
*** 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 right modules get built by dkms and baked into my ISO and it's initramfs. Line 2589: 2020-03-14T20:29:35 remove libc6 2.30-0ubuntu3 is the only occurrence in the log. ** Attachment added: "Wajig log of focal packages installed since January 2020" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1866844/+attachment/5337112/+files/wajig.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866844 Title: package libc6:amd64 2.31-0ubuntu3 failed to install/upgrade: installed libc6:amd64 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1866844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867423] Re: Update to glibc 2.31-0ubuntu5 breaks system
*** 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 of installations. ** Attachment added: "Wajig log of focal packages installed since January 2020" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867423/+attachment/5337111/+files/wajig.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867423 Title: Update to glibc 2.31-0ubuntu5 breaks system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
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 ipv6-appears-disabled. Check the marker during each postinst and select between the two "default" conditions automatically. Duplicate the `sites-available/default` with an additional copy `sites-available/default-ipv6`, with the inverse listen commented out, and the appropriate sites-enabled symlink. If either symlink is removed, the postinst doesn't recreate it. This way `default` remains true to upstream, while the debian/ubuntu ipv6 listen addition is obvious to any operators. A quirk like this could easily be pointed out in the focal release notes as an ubuntuism. As far as I am aware, during deployments of nginx by site operators it is common to remove the `sites-enabled/default` symlink to disable it without apt freaking out about 3 way merges. Currently, I don't even utilize the sites-available or sites-enabled at all with my ISO spins. The last line in my `/etc/nginx/conf.d/autoconfig.conf` is: `include /opt/project/*/resources/latest/config/http/*/*.conf;` It would be no trouble at all for me to add the scripted removal of the `sites-enabled/default-ipv6` symlink alongside my existing scripted removal of `sites-enabled/default`. Means a slightly mungier postinst; but appropriate comments detailing the idea there would go a long way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743592 Title: NGINX fails to start/install/upgrade if IPv6 is completely disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
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 unattended-upgrades. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743592 Title: NGINX fails to start/install/upgrade if IPv6 is completely disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770801] Re: Xsession: unable to launch "/usr/bin/lxsession -s Lubuntu -e LXDE"
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 launch "/usr/bin/lxsession -s Lubuntu -e LXDE" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1770801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637800] Re: add a motd script for news
"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 so at least I know y'all have to waste CPU time on every request... Anyway -- I've got to go make sure my containers run this on every login, and update all of my live USB sticks so all six automatic logins on the VTs in the background ends up hitting your motd server. Y'all don't mind if I patch it to send random uptimes between 4 seconds and 4700 years, and claiming to be a ["Tensilica LX6", "Zilog EZ-80", "Microchip Technology Inc. PIC16F874‑04/P", "EpsonS1C60A16"], right? But seriously -- some comments in the script (actually, your response prefixed with #s would pretty much be spot on) would be appreciated; even if another couple hundred bytes on disk are wasted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637800] Re: add a motd script for news
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637800] Re: add a motd script for news
```
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 normal browser user agent
strings anyway, I'm not really concerned if someone knows I'm amd64 or
arm64; there will be other ways to discover that but my uptime?!
really? REALLY?
And I wouldn't have minded as much if there was a comment describing why
uptime was even being included ("This data is used to improve the graphs
publically available at https://errors.ubuntu.com/";) and some kind of
documentation somewhere that this was occurring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637800
Title:
add a motd script for news
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493999] Re: xz-utils package is really, really old and should be updated to 5.2.2 with multi-core support
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1493999 Title: xz-utils package is really, really old and should be updated to 5.2.2 with multi-core support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1493999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575336] [NEW] gnome-disks crashed
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 x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Apr 26 12:44:07 2016 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2014-06-19 (676 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: gnome-disks ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash TERM=unknown SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to xenial on 2016-03-25 (32 days ago) UserGroups: ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575336 Title: gnome-disks crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1575336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574858] [NEW] gnome-disks crashed
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 CurrentDesktop: LXDE Date: Mon Apr 25 14:14:36 2016 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2014-06-19 (675 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: gnome-disks ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to xenial on 2016-03-25 (31 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574858 Title: gnome-disks crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1574858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547340 Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1547340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525027] [NEW] pcmanfm-qt does not resize root window when desktop size changes
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. The display dimensions change, but pcmanfm-qt's root window does not. Workaround: Open the LXQT Session Settings applet, select "Desktop", press the "Stop" Button, then the "Start" button. Screenshots are attached. ** Affects: pcmanfm-qt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lxqt-1604-2015-12-10-15-09-26.png" https://bugs.launchpad.net/bugs/1525027/+attachment/4532880/+files/lxqt-1604-2015-12-10-15-09-26.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525027 Title: pcmanfm-qt does not resize root window when desktop size changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1525027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525027] Re: pcmanfm-qt does not resize root window when desktop size changes
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 changed: - Netinstall of Xenial 12/10/2015, "lxqt-metapackage openbox qupzilla - obconf lubuntu-artwork" following + VMWare ESXi 5.x (IDE disk) Netinstall of Xenial 12/10/2015, "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. The display dimensions change, but pcmanfm-qt's root window does not. Workaround: Open the LXQT Session Settings applet, select "Desktop", press the "Stop" Button, then the "Start" button. - Will try to attach screenshots in a moment. + Screenshots are attached. ** Description changed: - VMWare ESXi 5.x (IDE disk) Netinstall of Xenial 12/10/2015, "lxqt- + 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. The display dimensions change, but pcmanfm-qt's root window does not. Workaround: Open the LXQT Session Settings applet, select "Desktop", press the "Stop" Button, then the "Start" button. Screenshots are attached. ** Description changed: - VMWare ESXi 5.x (IDE disk) Netinstall of Xenial 2015/12/10, "lxqt- + 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. The display dimensions change, but pcmanfm-qt's root window does not. Workaround: Open the LXQT Session Settings applet, select "Desktop", press the "Stop" Button, then the "Start" button. Screenshots are attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525027 Title: pcmanfm-qt does not resize root window when desktop size changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1525027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492851] [NEW] package grub-common 2.02~beta2-26ubuntu5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 130
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 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Sun Sep 6 12:11:59 2015 DuplicateSignature: package:grub-common:2.02~beta2-26ubuntu5:subprocess new pre-removal script returned error exit status 130 ErrorMessage: subprocess new pre-removal script returned error exit status 130 InstallationDate: Installed on 2015-09-01 (5 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.1.0-3-generic root=UUID=3317e12a-22dc-4059-bf2d-0ef3883e7ede ro rootflags=subvol=@ quiet splash RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: grub2 Title: package grub-common 2.02~beta2-26ubuntu5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 130 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492851 Title: package grub-common 2.02~beta2-26ubuntu5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1492851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1485877] [NEW] Could not install, timezone crashed.
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 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CasperVersion: 1.364 Date: Tue Aug 18 07:19:31 2015 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150817.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lubuntu ubiquity-2.21.27 wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1485877 Title: Could not install, timezone crashed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1485877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432843] Re: Lubuntu failed to boot
*** 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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432843 Title: Lubuntu failed to boot To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432843] Re: Lubuntu failed to boot
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 milage may very, do not rely on this ISO for production purposes, ONLY TESTING! IF you're gonna install, use the official alternate ISOs instead and add the "xserver-xorg-video-all" package (and it's dependencies!) before rebooting. If it breaks, you are advised to keep both pieces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432843 Title: Lubuntu failed to boot To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432843] Re: Lubuntu failed to boot
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:
http://files.sllabs.com/files/long-term/screenshots/kamikazi/vmware-broken-for-lubuntu-and-this-is-the-culprit-commit.jpg
On march 16th, xserver-xorg-video-all was moved from Depends to
Recommends in the xserver-xorg package.
This bug happens to us for two reasons:
One: lubuntu's seed specifies no-follow-recommends.
Two: We do not have an explicit dependency on xserver-xorg-video-all.
I propose that an explicit dependency is added in either lubuntu's seed,
or in one of the metapackages, to follow suit with the rest of the
crowd. They all have the packages installed, one way or another, and we
are the odd-man-out.
ubuntu-mate seems to have added their explicit dependency in the vivid cycle.
edubuntu had the explicit dependency in utopic, so they never noticed.
Xubuntu does not have no-follow-recommends, so they never noticed.
The others (ubuntu+Unity, kubuntu, etc) are all primarily based on GL
compositors these days, and simply barf on the simple 2D cards that most
of these remaining packages support.
Specifically:
xserver-xorg-video-vmware
xserver-xorg-video-vesa
xserver-xorg-video-mga
xserver-xorg-video-cirrus
xserver-xorg-video-mach64
xserver-xorg-video-trident
MGA is required to support the Matrox G200e-compatible VGA adapter found in
Nuvoton and ASPEED baseboard management controllers on various supermicro X8
and X9 series motherboards.
Mach64 is required to support some older supermicro X7-series on-motherboard
VGA adapter.
cirrus and trident are required for some emulation environments like qemu.
Most of the pieces of actual hardware that these drivers were built for
are no longer used; but they are old enough to be "the popular virtual
devices to emulate".
I am not sure if these drivers will ever be updated to support DRM or
KMS, or even if it is worth it for them to be changed, with the progress
on wayland+pixman.
This comment is found in several of the seeds, and no longer seems to apply as
of the march 16th commit to xserver-xorg.
# this includes xserver-xorg->xserver-xorg-{input|video}-* (no need to add
specific drivers manually)
Here is my factual corroboration of the above set of opinions.
[code]
ubuntu@kamikazi-builder:~/seedfinder/seeds$ grep -r "xserver-xorg" | grep -v
"xserver-xorg-input" | grep -v "dbg" | grep -v "geode"
edubuntu.utopic/desktop-gnome: * (xserver-xorg-video-all)
edubuntu.vivid/desktop-gnome: * (xserver-xorg-video-all)
kubuntu.utopic/active: * xorg # this includes
xserver-xorg->xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
kubuntu-active.utopic/active: * xorg # this includes
xserver-xorg->xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
kubuntu-active.vivid/active: * xorg # this includes
xserver-xorg->xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
platform.utopic/desktop-common: * xorg # this includes
xserver-xorg->xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
platform.utopic/installer-gtk: * xserver-xorg-core-udeb
platform.utopic/installer-gtk: * xserver-xorg-video-fbdev-udeb
platform.vivid/desktop-common: * xorg # this includes
xserver-xorg->xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
platform.vivid/installer-gtk: * xserver-xorg-core-udeb
platform.vivid/installer-gtk: * xserver-xorg-video-fbdev-udeb
ubuntu-mate.vivid/core: * xserver-xorg
ubuntu-mate.vivid/core: * xserver-xorg-video-all
ubuntu@kamikazi-builder:~/seedfinder/seeds$ grep -r "no-follow-recommends"
lubuntu.utopic/STRUCTURE:feature no-follow-recommends
lubuntu.utopic/core: * Feature: no-follow-recommends
lubuntu.utopic/desktop: * Feature: no-follow-recommends
lubuntu.vivid/STRUCTURE:feature no-follow-recommends
lubuntu.vivid/core: * Feature: no-follow-recommends
lubuntu.vivid/desktop: * Feature: no-follow-recommends
platform.utopic/build-essential: * Feature: no-follow-recommends
platform.utopic/required: * Feature: no-follow-recommends
platform.vivid/build-essential: * Feature: no-follow-recommends
platform.vivid/required: * Feature: no-follow-recommends
ubuntu.utopic/system-image: * Feature: no-follow-recommends
ubuntu.vivid/system-image: * Feature: no-follow-recommends
ubuntu-mate.vivid/STRUCTURE:feature no-follow-recommends
ubuntu-mate.vivid/cloudtop: * Feature: no-follow-recommends
ubuntu-mate.vivid/core: * Feature: no-follow-recommends
ubuntu-mate.vivid/desktop: * Feature: no-follow-recommends
ubuntu-mate.vivid/live: * Feature: no-follow-recommends
ubuntu-mate.vivid/live:# 'no-follow-recommends' is used in the seed to prevent
the following
ubuntu-mate.vivid/live:== no-follow-recommends hacks ==
ubuntu-mate.vivid/live:# software when 'no-follow-recommends' is u
[Bug 882147] Re: overlayfs does not implement inotify interfaces correctly
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/ does not work as expected. Could someone bring that overlayfs inotify kernel patch up to date against vivid before alpha2 strikes so we can kill this annoying little problem once and for all for 15.04 and beyond? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882147 Title: overlayfs does not implement inotify interfaces correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/882147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
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 significant issues while negotiating link speeds for me, I could either get everything running fine at 1.5/3Gbit and all the drives worked, or I would get 6Gbit and all the older drives would be missing. I believe the latest dell-branded firmware is: http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=8R2N4&fileId=3098294144&osCode=LNUX&productCode=poweredge-r300&languageCode=EN&categoryId=SF Unfortunately, it seems to come only as an .exe, but I didn't try to download it. I've got two 1068Es paired up with HP SAS Expanders: http://www.amazon.com/HP-468406-B21-Sas-Expander-Card/dp/B0025ZQ16K At one point I tried to connect I think about 60 drives (If I recall correctly, I got up to /dev/sdbd) Getting that working properly was another firmware hassle story involving purchasing a used HP server just to flash it; but I won't bore you with it in a LP bug# comment. But still -- out of date firmware can lead to wacky results. Good luck convincing Kay to raise the udev timeout from 30sec! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241958] Re: startlubuntu missing from 13.10 for x2go
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 to work! http://puu.sh/69hqX.png (using ubuntustudio-installer on top of lubuntu-core) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241958 Title: startlubuntu missing from 13.10 for x2go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1241958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041128] Re: Installing to USB memory stick from TORAM=Yes live boot from same device crashes ubiquity
-- 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 to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1041128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041128] [NEW] Installing to USB memory stick from TORAM=Yes live boot from same device crashes ubiquity
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 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 CasperVersion: 1.315 Date: Fri Aug 24 03:04:03 2012 InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/lubuntu.seed boot=casper initrd=/casper/initrd.lz TORAM=Yes -- LiveMediaBuild: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423) ProcEnviron: TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ubiquity-2.10.16 -- 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 to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1041128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 822244] Re: [M4A88TD V/EVO, Realtek ALC892] sound only at my video card hdmi output
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 /user/share/sounds/alsa/Noise.wav still makes no output. I can post my apport details in a moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/822244 Title: [M4A88TD V/EVO, Realtek ALC892] sound only at my video card hdmi output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/822244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692029] Re: [Realtek ALC892] ALSA test tone not correctly played back
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. https://bugs.launchpad.net/bugs/692029 Title: [Realtek ALC892] ALSA test tone not correctly played back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/692029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534070] Re: u3-tool 0.3 fails on cruzer 2GB stick
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 address the disk as /dev/sdf to get it to work. kamil...@sonyra840g:~$ sudo u3-tool -i /dev/sr2 Error opening device: Read-only file system kamil...@sonyra840g:~$ sudo u3-tool -i /dev/sdf Total device size: 14.95 GB (16051601408 bytes) CD size: 7.69 MB (8060928 bytes) Data partition size: 14.94 GB (16043474944 bytes) kamil...@sonyra840g:~$ sudo u3-tool -D /dev/sdf Partition info: - Partition count: 0x02 - Data partition size: 14177271808 byte(0x01a68400) - Unknown1: 0x0002 - CD size: 1874329600 byte(0x0037dc00) - Unknown2: 0x0103 Data partition info: - Data partition size: 14177271808 byte(0x01a68400) - Secured zone size: 0 byte(0x) - Unlocked: 0x - Password try: 0x Chip info: - Manufacturer: SanDisk - Revision: 84210020 Property page 0x03: - Device size: 16051601408 byte(0x01de6000) - Device serial: 32482307E3811C16 - Full record length: 0x0077 - Unknown1: 0x0b - Unknown2: 0x540e0781 - Unknown3: 0x540e0781 Property page 0x0C: - Max. pass. try: 5 kamil...@sonyra840g:~$ sudo u3-tool -l UbuntuLucid3264.iso /dev/sdf CD image(1874288640 byte) is to big for current cd partition(8060928 byte), please repartition device. kamil...@sonyra840g:~$ sudo u3-tool -p 1874288640 /dev/sdf WARNING: Loading a new cd image causes the whole device to be whiped. This INCLUDES the data partition. I repeat: ANY EXCISTING DATA WILL BE LOST! Are you sure you want to continue? [yn] y kamil...@sonyra840g:~$ sudo u3-tool -l UbuntuLucid3264.iso /dev/sdf |**| 100% OK So that all worked just fine for me. I did some testing on the /dev/sg? stuff a minute ago just to see if it would work, here's the results: kamil...@sonyra840g:~$ cd /dev/ kamil...@sonyra840g:/dev$ ls sg* sg0 sg1 sg2 sg3 sg4 sg5 sg6 sg7 sg8 kamil...@sonyra840g:/dev$ sudo u3-tool -D /dev/sg0 u3_partition_info() failed: Device reported command failed: status 1 u3_data_partition_info() failed: Device reported command failed: status 1 u3_chip_info() failed: Device reported command failed: status 1 u3_read_device_property() failed for property 0x03: Header of property 0x0003 could not be read. u3_read_device_property() failed for property 0x0C: Header of property 0x000C could not be read. kamil...@sonyra840g:/dev$ sudo u3-tool -D /dev/sg1 Partition info: - Partition count: 0x00 - Data partition size: 837131066880 byte(0x6174732f) - Unknown1: 0x6300 - CD size: 0 byte(0x) - Unknown2: 0x Data partition info: - Data partition size: 0 byte(0x) - Secured zone size: 1000297383424 byte(0x74732f63) - Unlocked: 0x03007461 - Password try: 0x001700b1 Chip info: - Manufacturer: at - Revision: Length of property 0x03 is not the expected length. (len=12131) Length of property 0x0C is not the expected length. (len=12131) kamil...@sonyra840g:/dev$ sudo u3-tool -D /dev/sg2 u3_partition_info() failed: Device reported command failed: status 1 u3_data_partition_info() failed: Device reported command failed: status 1 u3_chip_info() failed: Device reported command failed: status 1 u3_read_device_property() failed for property 0x03: Header of property 0x0003 could not be read. u3_read_device_property() failed for property 0x0C: Header of property 0x000C could not be read. kamil...@sonyra840g:/dev$ sudo u3-tool -D /dev/sg3 u3_partition_info() failed: Device reported command failed: status 1 u3_data_partition_info() failed: Device reported command failed: status 1 u3_chip_info() failed: Device reported command failed: status 1 u3_read_device_property() failed for property 0x03: Header of property 0x0003 could not be read. u3_read_device_property() failed for property 0x0C: Header of property 0x000C could not be read. kamil...@sonyra840g:/dev$ sudo u3-tool -D /dev/sg4 u3_partition_info() failed: Device reported command failed: status 1 u3_data_partition_info() failed: Device reported command failed: status 1 u3_chip_info() failed: Device reported command failed: status 1 u3_read_device_property() failed for property 0x03: Header of property 0x0003 could not be read. u3_read_device_property() failed for property 0x0C: Header of property 0x000C could not be read. kamil...@sonyra840g:/dev$ sudo u3-tool -D /dev/sg5 u3_partition_info() failed: Device reported command failed: status 1 u3_data_partition_info() failed: Device reported command failed: status 1 u3_chip_info() failed: Device reported command failed: status 1 u3_read_device_property() failed for property 0x03: Header of property 0x0003 could not be read. u3_read_device_property() failed for property 0x0C: Header of property 0x000C could not be read. kamil...@sonyra8
[Bug 597233] Re: inbound video calls broken
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 'stuck' using the sflphone.org deb packages to get a working softphone on lucid because I've never gotten ekiga to work properly with my audio. SFLPhone works really decently, just what I needed, they just got into debian unstable a few days ago; so I'd love to see it end up in ubuntu's repos. It would be my preference to get proper docs for a empathy, as we've a lot of lucid boxes that already have empathy & telepathy-sofiasip deployed but unconfigured. -- inbound video calls broken https://bugs.launchpad.net/bugs/597233 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568306] Re: Double-exit counterintuitive when running byobu at login
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 non-zero exit, I guess? -- Double-exit counterintuitive when running byobu at login https://bugs.launchpad.net/bugs/568306 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552008] Re: gnome-keyring-daemon crashed with SIGSEGV
** 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 added: "ProcMaps.txt" http://launchpadlibrarian.net/42537980/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/42537981/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/42537982/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/42537983/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/42537984/ThreadStacktrace.txt ** Visibility changed to: Public -- gnome-keyring-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/552008 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551169] Re: apport-gtk crashed with SIGFPE in g_signal_handler_unblock()
** 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 added: "ProcMaps.txt" http://launchpadlibrarian.net/42416521/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/42416522/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/42416524/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/42416526/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/42416528/ThreadStacktrace.txt ** Visibility changed to: Public -- apport-gtk crashed with SIGFPE in g_signal_handler_unblock() https://bugs.launchpad.net/bugs/551169 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 393888] Re: Ruby 1.9.0 curses Alt-key handling broken
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.) Two birds with one stone. -- Ruby 1.9.0 curses Alt-key handling broken https://bugs.launchpad.net/bugs/393888 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483316] Re: after upgrade to karmic with clocksource tsc drifts over 7.25 sec every 10 minutes
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 current clocksource is tsc, which the kernel seems to favor as default on some systems, but just doesn't keep track of time all that well. Append clocksource=acpi_pm or clocksource=hpet to your kernel options depending on what available_clocksource returns. If you have Grub2, you would edit the GRUB_CMDLINE_LINUX="" line in /etc/default/grub, then run sudo update-grub. For GRUB legacy, you can add clocksource=acpi_pm or clocksource=hpet to defoptions (for "normal" entries) or altoptions (for all entries) and then run sudo update-grub. GRUB will then append it to all of your future kernel entries. -- after upgrade to karmic with clocksource tsc drifts over 7.25 sec every 10 minutes https://bugs.launchpad.net/bugs/483316 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 442799] Re: WARNING: at /build/buildd/linux-2.6.31/fs/quota/dquot.c:964 dquot_claim_space+0x84/0x130()
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 errors=remount-ro,usrquota,grpquota 0 1 Remove usrquota and grpquota if they exist. # / was on /dev/sda2 during installation UUID=acee041c-a2a8-4ca4-9b51-19aa423f122e / ext4 errors=remount-ro 0 1 -- WARNING: at /build/buildd/linux-2.6.31/fs/quota/dquot.c:964 dquot_claim_space+0x84/0x130() https://bugs.launchpad.net/bugs/442799 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456069] Re: WARNING: at /build/buildd/linux-2.6.31/net/mac80211/rc80211_minstrel.c:69 minstrel_tx_status+0x66/0xd0 [mac80211]()
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 errors=remount-ro,usrquota,grpquota 0 1 Remove usrquota and grpquota if they exist. # / was on /dev/sda2 during installation UUID=acee041c-a2a8-4ca4-9b51-19aa423f122e / ext4 errors=remount-ro 0 1 -- WARNING: at /build/buildd/linux-2.6.31/net/mac80211/rc80211_minstrel.c:69 minstrel_tx_status+0x66/0xd0 [mac80211]() https://bugs.launchpad.net/bugs/456069 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484475] Re: Refuses to connect, unable to reinstall
** 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: "UbuntuoneClientPackages.txt" http://launchpadlibrarian.net/35801703/UbuntuoneClientPackages.txt -- Refuses to connect, unable to reinstall https://bugs.launchpad.net/bugs/484475 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484475] [NEW] Refuses to connect, unable to reinstall
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: 2009-11-17 14:05:21,389 - dbus.proxies - ERROR - Introspect error on org.freedesktop.NetworkManager:/org/freedesktop/NetworkManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files 2009-11-17 14:05:21,502 - ubuntuone.SyncDaemon.DBus - ERROR - Error while getting the NetworkManager state org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files .home.kamilion..config.ubuntuone.ubuntuone.client.conf: [ubuntuone] show_applet = 1 connected = True connect = 0 bookmarked = True Architecture: amd64 Date: Tue Nov 17 14:05:28 2009 DistroRelease: Ubuntu 9.10 Package: ubuntuone-client 1.0.2-0ubuntu2 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-15.50-server SourcePackage: ubuntuone-client Uname: Linux 2.6.31-15-server x86_64 ** Affects: ubuntuone-client (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Refuses to connect, unable to reinstall https://bugs.launchpad.net/bugs/484475 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411546] Re: Please upgrade ebox-dhcp to 1.3
** 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 the ability to be set up in a master-slave architecture, allowing several slave eBoxes to use a master eBox's LDAP to keep their users. This way you can set up a master eBox to hold all your users and groups and then have a few slave eBoxes with different services such as Samba, Asterisk, Jabber or Mail using these users that are available in the master one. Each of these services is configured individually and just will share the users. It also manages the LDAP directory more nicely. It does not wipe it out when the module is installed for first time and uses your current configuration. ** Tags added: upgrade -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411546] Re: Please upgrade ebox-dhcp to 1.3
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 433788] Re: ebox-dhcp fails to install on karmic alpha6
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440307] Re: seahorse-agent crashed with SIGSEGV in IA__gdk_window_enable_synchronized_configure()
** 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 added: "ProcMaps.txt" http://launchpadlibrarian.net/32842008/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/32842009/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/32842010/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/32842011/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/32842012/ThreadStacktrace.txt ** Visibility changed to: Public -- seahorse-agent crashed with SIGSEGV in IA__gdk_window_enable_synchronized_configure() https://bugs.launchpad.net/bugs/440307 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 433713] Re: gnome-settings-daemon crashed with signal 5 in gdk_x_error() (dbgsyms backtrace)
*** 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 5 in gdk_x_error() (dbgsyms backtrace) https://bugs.launchpad.net/bugs/433713 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385428] Re: grub2 boot from lvm Auto-detection of a filesystem module failed
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 https://bugs.launchpad.net/bugs/385428 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 433713] Re: gnome-settings-daemon crashed with signal 5 in gdk_x_error() (dbgsyms backtrace)
*** 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) + gnome-settings-daemon crashed with signal 5 in gdk_x_error() (dbgsyms backtrace) ** Description changed: Binary package hint: gnome-settings-daemon - gsd crash with dev & dbgsyms packages installed. + gsd crash backtrace with dev & dbgsyms packages installed. + Ubuntu karmic server, up to date as of 4:30PM PST Sept 20. + X session is FreeNX from a Windows 7 Client running latest NXClient 3.3.0-6 + Server is latest FreeNX from http://ppa.launchpad.net/freenx-team/ppa/ubuntu karmic main + No other PPAs are configured other than ddebs. + Themes over FreeNX are not working likely due to this. ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Sun Sep 20 15:32:59 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon Package: gnome-settings-daemon 2.27.92-0ubuntu2 ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-server Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: gdk_x_error (display=, _XError (dpy=0xbe7a00, rep=0xc12e70) _XReply (dpy=0xbe7a00, rep=, doGetScreenResources (dpy=0xbe7a00, window=87, fill_out_screen_info (screen=0xc130b0, Title: gnome-settings-daemon crashed with signal 5 in gdk_x_error() Uname: Linux 2.6.31-10-server x86_64 UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare -- gnome-settings-daemon crashed with signal 5 in gdk_x_error() (dbgsyms backtrace) https://bugs.launchpad.net/bugs/433713 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 433713] Re: gnome-settings-daemon crashed with signal 5 in gdk_x_error() (dbgsyms)
*** 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: "Disassembly.txt" http://launchpadlibrarian.net/32126309/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/32126310/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/32126311/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/32126312/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/32126313/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/32126314/ThreadStacktrace.txt ** Visibility changed to: Public -- gnome-settings-daemon crashed with signal 5 in gdk_x_error() (dbgsyms) https://bugs.launchpad.net/bugs/433713 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 427356] Re: Boot Performance Updates
On Wed, Sep 16, 2009 at 12:05 PM, Scott James Remnant wrote: > On Wed, 2009-09-16 at 06:59 +0000, 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 a creek) >> > You should file a separate bug for this. Never mind, it was my fault. Missed a package. Haven't had the problem since the initial reboot. After a package update this morning and a reboot, it works fine. >> couldn't find out how to disable upstart services, so I ended up moving >> /etc/init/gdm.conf to /etc/init-disabled/gdm.conf, >> Any better ways? > Rename them to .conf-disabled is another. So it's looking in any directory under /etc/init for ".conf" files, correct? What's the best trigger to get upstart to log all events as early as possible? I'd like to figure out the path the new setup follows. > I tend to just comment out the "start on" line. yeah, I ended up doing the same, to keep 'start gdm' working, > Better methods are planned in future Upstart releases which will find > their way into future Ubuntu releases. Where's the discussion for this type of stuff currently centered? >> Some simple upstart jobs I'd like to see quickly: >> opensshd, postfix, bootlogd, kvm/libvirt > I think we'll largely stick with the current set for karmic; though > don't be surprised if karmic+1 work appears in the ubuntu-boot PPA > sooner rather than later. I've got some time to kill, and I'd like to see at least opensshd make the jump before karmic+1, mainly because it's one of the single most important dependencies on a remote system to have properly tied to network events being emitted. Better to debug this now and have it solid and reliable before ubuntu-server goes out. How can I help? (Just send me an email) -- Boot Performance Updates https://bugs.launchpad.net/bugs/427356 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 427356] Re: Boot Performance Updates
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 /etc/init/gdm.conf to /etc/init-disabled/gdm.conf, Any better ways? sysvconfig has gone away, but sysv-rc-conf works fine for poking at the remaining rc?.d sysv links. Some simple upstart jobs I'd like to see quickly: opensshd, postfix, bootlogd, kvm/libvirt -- Boot Performance Updates https://bugs.launchpad.net/bugs/427356 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 427356] Re: Boot Performance Updates
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 here, deselected the packages listed above and installed everything else. Still waiting on a few more packages to make the switch, but I'm definitely looking forward to it. Thanks for the hard work, Robbie, Scott, and Steve! Let us know when it's safe to proceed, if you would be so kind. -- Boot Performance Updates https://bugs.launchpad.net/bugs/427356 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386802] Re: grub-setup crashed with SIGSEGV in __libc_start_main()
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 properly generated entry now:
### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-10-server" {
set quiet=1
insmod lvm
insmod ext2
set root=(BigBlock-KarmicRoot)
search --no-floppy --fs-uuid --set 8679421a-df8d-4e61-a88d-e0cae0d9a202
linux /boot/vmlinuz-2.6.31-10-server root=/dev/mapper/BigBlock-Karmic$
initrd /boot/initrd.img-2.6.31-10-server
}
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386802] Re: grub-setup crashed with SIGSEGV in __libc_start_main()
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417301] Re: update-manager crashed with GError in __init__()
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417301] Re: update-manager crashed with GError in __init__()
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409621] Re: The program 'gnome-settings-daemon' received an X Window System error. During on a FreeNX server suring a session.
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
