Re: [Bug 1912371] Re: [MIR] flashrom + libftdi
On Wed, 19 May 2021 06:52:55 - Alex Murray <1912...@bugs.launchpad.net> wrote: > These failures of the mocked tests have been reported upstream at > https://github.com/flashrom/flashrom/issues/186 by others but no > response Hi there, I was the flashrom maintainer till a few years ago. While I was using the github repo+tracker, there is currently ~nobody taking care of that. A more promising way to reach the right people is to write an email to flash...@flashrom.org -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876633] Re: cfv not available in 20.04 LTS (focal)
Right, thanks for the pointer. I missed that it was already removed from Debian stable/Buster. It will soon follow in testing. There is some (stalled) effort porting it to Python 3 though: https://github.com/cfv- project/cfv/issues/8 ** Bug watch added: Debian Bug tracker #936288 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936288 ** Also affects: cfv (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936288 Importance: Unknown Status: Unknown ** Bug watch added: github.com/cfv-project/cfv/issues #8 https://github.com/cfv-project/cfv/issues/8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876633 Title: cfv not available in 20.04 LTS (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfv/+bug/1876633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876633] [NEW] cfv not available in 20.04 LTS (focal)
Public bug reported: For some reason cfv did not make it into 20.04, why? It is contained in 19.10 as well as all current Debian suits including testing and unstable. I could not easily find any explanation. ** Affects: cfv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876633 Title: cfv not available in 20.04 LTS (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfv/+bug/1876633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 472426] Re: terminus not available after karmic upgrade - reinstall fixes
That would actually mean that the package now is completely broken. Have you tried restarting your desktop session (e.g., reboot)? Fonts are sometimes not picked up without that... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/472426 Title: terminus not available after karmic upgrade - reinstall fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfonts-terminus/+bug/472426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586753] Re: regression: unusable UI of gitg 3.x
No, it isn't. More appropriately it should be tagged as won't fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586753 Title: regression: unusable UI of gitg 3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitg/+bug/1586753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310307] Re: spamassassin postinst uses a login shell
And I just noticed that this bug is about 5 years old... this is with Ubuntu 18.04 and ubuntu-mate-default-settings version 18.04.17. The actual output is: Installing new version of config file /etc/init.d/spamassassin ... -su: 2: [: x: unexpected operator -su: 2: [: x: unexpected operator -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310307 Title: spamassassin postinst uses a login shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1310307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310307] Re: spamassassin postinst uses a login shell
In my case the culprit is/was '/etc/profile.d/mate-qt.sh' from package 'ubuntu-mate-default-settings'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310307 Title: spamassassin postinst uses a login shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1310307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)
** Also affects: mate-indicator-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)
I ran into this after an update from 16.04. I had a custom panel as well but I found a way to show the notification panel again without resetting the dconf configuration. I had three indicator-application.desktop files (and I IIRC likewise as many probably competing running instances of it): /usr/share/mate/autostart/indicator-application.desktop /etc/xdg/autostart/indicator-application.desktop /usr/share/indicator-application/upstart/xdg/autostart/indicator-application.desktop Only the last one seems to be the current one. I have removed (renamed) the first two. I have not tested if that alone works already but edited the remaining (third) file. I have added MATE to the list of shown-in DEs: OnlyShowIn=Unity;MATE; After a reboot the new notification popped up where it is supposed to including all expected apps. ** Also affects: indicator-application (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager-applet (Ubuntu) Status: Confirmed => Invalid ** Also affects: ubuntu-mate-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)
Possible duplicate/related bug: https://bugs.launchpad.net/ubuntu/+source/indicator- application/+bug/1728449 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90085] Re: When /tmp is mounted noexec, preconfigure fails
My workaround uses a dedicated directory for apt that is noexec as well
but becomes temporally during installs:
/etc/fstab:
tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev,noexec,mode=1777,size=512M 0 0
tmpfs /var/tmp/apt tmpfs
defaults,noatime,nosuid,nodev,noexec,mode=1777,size=512M 0 0
/etc/apt/apt.conf.d/71tmpapt (or whatever):
DPkg
{
Pre-Invoke { "mount /var/tmp/apt -o remount,exec" };
Post-Invoke { "mount /var/tmp/apt -o remount,noexec" };
};
APT::ExtractTemplates::TempDir "/var/tmp/apt";
Since the mount point must(?) exist for any mount point specified in
/etc/fstab I put the apt dir into /var/tmp because its contents are
persistent (unlike /tmp's). It's not very throughly tested yet... ymmv.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/90085
Title:
When /tmp is mounted noexec, preconfigure fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/90085/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742124] [NEW] Missing update-alternatives configuration in 5.0 package for Xenial
Public bug reported: Hi, I did not look at the package metadata but installing clang-5.0 from xenial-updates/universe and afterwards removing clang (and thus clang 3.8) left me without a clang alias while other package provide this alternative. It was fixable via update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-5.0 1000 update-alternatives --install /usr/bin/clang clang /usr/bin/clang-5.0 1000 but I guess it should have happened without that and thus it is a bug in the package(s). ** Affects: llvm-toolchain-5.0 (Ubuntu) Importance: Undecided Status: New ** Tags: packaging ** Description changed: Hi, I did not look at the package metadata but installing clang-5.0 from xenial-updates/universe and afterwards removing clang (and thus clang 3.8) left me without a clang alias while other package provide this alternative. It was fixable via - update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-5.0 1000 - update-alternatives --install /usr/bin/clang clang /usr/bin/clang-5.0 1000 + ~~~ + update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-5.0 1000 + update-alternatives --install /usr/bin/clang clang /usr/bin/clang-5.0 1000 + ~~~ but I guess it should have happened without that and thus it is a bug in the package(s). ** Description changed: Hi, I did not look at the package metadata but installing clang-5.0 from xenial-updates/universe and afterwards removing clang (and thus clang 3.8) left me without a clang alias while other package provide this alternative. It was fixable via - ~~~ update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-5.0 1000 update-alternatives --install /usr/bin/clang clang /usr/bin/clang-5.0 1000 - ~~~ but I guess it should have happened without that and thus it is a bug in the package(s). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742124 Title: Missing update-alternatives configuration in 5.0 package for Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-5.0/+bug/1742124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597740] Re: iwyu 3.7-1 should depend on clang-3.7
libclang-common-3.7-dev would be enough actually -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597740 Title: iwyu 3.7-1 should depend on clang-3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwyu/+bug/1597740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311836] Re: visual glitches when messages are selected with the keyboard
Nope, has been fixed in the mean time. I don't know which version fixed it though. ** Changed in: claws-mail (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/311836 Title: visual glitches when messages are selected with the keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/311836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586753] [NEW] regression: unusable UI of gitg 3.x
Public bug reported: The upstream 3.x branch of gitg is an almost complete rewrite that changes the very nature of the program. For example, the new version packaged for Xenial completely lacks any visible keyboard shortcuts and has many other obstructions for my daily work flow that have been newly introduced - gitg became useless to me (even gitk and git-gui seem to be better(!)). It would be better to deprecate/remove gitg and add the 3.x-based versions of gitg as a new package to communicate this change. I cannot dedicate enough time to maintain a fork on my own but I am more than willing to join anybody who want to cooperate on this... ** Affects: gitg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586753 Title: regression: unusable UI of gitg 3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitg/+bug/1586753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585107] Re: ding only matches words beginning a-i
I can confirm the issue and that both suggestions fix the issue, i.e. adding "-a" to the egrep options or switching to the internal grep implementation. I cannot tell if I have changed this in my 14.04 install before upgrading (if that was possible at all, I cannot remember the GUI at all). I certainly did not change it in 16.04 (updated yesterday). ** Changed in: ding (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585107 Title: ding only matches words beginning a-i To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ding/+bug/1585107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301158] Re: nm-applet icon invisible
I can confirm that the dbus-launch workaround mentioned in #14 also helps when running mate-desktop in 16.04 xenial upgraded from 12.04+14.04 (manually... so this might not be a real bug there). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301158 Title: nm-applet icon invisible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1301158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168518] Re: "The value 'precise' is invalid for APT::Default-Release" when upgrading from precise to quantal via command line
In my case I get it when upgrading to trusty... I presume because precise is no longer supported. Removing the Apt preference/directive «APT::Default-Release "precise";» e.g. in /etc/apt/apt.conf.d/ helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168518 Title: "The value 'precise' is invalid for APT::Default-Release" when upgrading from precise to quantal via command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1168518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558822] Re: [FFe] sync flashrom 0.9.9+r1954-1 from Debian
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558822 Title: [FFe] sync flashrom 0.9.9+r1954-1 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1558822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558822] Re: [FFe] sync flashrom 0.9.9+r1954-1 from Debian
Yes, indeed that was a mistake, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558822 Title: [FFe] sync flashrom 0.9.9+r1954-1 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1558822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558822] Re: [FFe] sync flashrom 0.9.9+r1954-1 from Debian unstable
** Description changed: In bug #1547144 a FFe was granted to merge Debian's package of - flashrom's 0.9.9 release candidate into xenial was granted and the - package has been updated. Upstream has now released 0.9.9 final - including a security fix and I would like to request another exception - (and a sponsored upload) for that. + flashrom's 0.9.9 release candidate into xenial and the package has been + updated. Upstream has now released 0.9.9 final including a security fix + and I would like to request another exception (and a sponsored upload) + for that. The following is a list of changes that followed the RC before the final release: - Fix fscanf format string security bug in layout.c This is the mentioned security bug, cf. https://security-tracker.debian.org/tracker/TEMP-000-C3CEDB Depending on the use case of flashrom the security implications of the correct use might be quite higher than the threat by this bug but it certainly makes sense to include this fix. - Implement serial port shutdown both for regular termination and error condition in pony_spi. pony_spi is one of the numerous programmer modules flashrom supports. This fixes a file descriptor leak. - Add a bunch of new/tested stuff and various small changes 25. In these patches we gather test status updates and other minor fixes. In this particular change there were: status updates, whitespace and typo fixes, a Makefile and manpage patch - partially to make lintian happy. - Fix compilation on SunOS. Building on Solaris-based OSes were tested and two minor related problems fixed. - Rewrite and fix corner case in sb600spi The command line argument handler for AMD chipsets had a minor bug. - Add support for GNU Hurd. We added support to build GNU Hurd because it seems easy enough. - Add support for GD25VQ21B, GD25VQ40C, GD25VQ80C and GD25VQ16C. Some new flash chips were added (regression potential about zero). - Makefile: Fix driver blacklist dependencies The makefile tries to disable some programmers on certain architectures/OSes and was a bit overzealous. - rayer_spi: add support for SPI Tiny Tools-compatible hardware. This adds the definition of a pin mapping for a certain hardware model. - makefile: allow to disable all default-yes config variables with CONFIG_NOTHING=yes. Build/makefile-only change. - Partial architecture support for alpha hppa m68k sh s390 Like for Hurd we decided to add support for these because the changes were mostly trivial and we can now build on all Debian architectures but PS3. This patch also adds support for the s390x architecture that xenial will support for the first time. - dediprog: use ordinary USB devs array. - pickit2_spi: use ordinary USB devs array. These two merely change the output of flashrom -L (that lists all supported devices) and allow for easier future extension of said modules. So to sum up... there were not *only* bug fixes since the RC but also some small feature additions that target new hardware and OSes. Most of these changes are effective at build time only. There are very few imaginable regression possibilities for the x86 and arm versions since the RC IMHO. Logs etc. will follow soon. ** Summary changed: - [FFe] sync flashrom 0.9.9+r1954-1 from Debian unstable + [FFe] sync flashrom 0.9.9+r1954-1 from Debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558822 Title: [FFe] sync flashrom 0.9.9+r1954-1 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1558822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558822] [NEW] [FFe] sync flashrom 0.9.9+r1954-1 from Debian unstable
Public bug reported: In bug #1547144 a FFe was granted to merge Debian's package of flashrom's 0.9.9 release candidate into xenial was granted and the package has been updated. Upstream has now released 0.9.9 final including a security fix and I would like to request another exception (and a sponsored upload) for that. The following is a list of changes that followed the RC before the final release: - Fix fscanf format string security bug in layout.c This is the mentioned security bug, cf. https://security-tracker.debian.org/tracker/TEMP-000-C3CEDB Depending on the use case of flashrom the security implications of the correct use might be quite higher than the threat by this bug but it certainly makes sense to include this fix. - Implement serial port shutdown both for regular termination and error condition in pony_spi. pony_spi is one of the numerous programmer modules flashrom supports. This fixes a file descriptor leak. - Add a bunch of new/tested stuff and various small changes 25. In these patches we gather test status updates and other minor fixes. In this particular change there were: status updates, whitespace and typo fixes, a Makefile and manpage patch - partially to make lintian happy. - Fix compilation on SunOS. Building on Solaris-based OSes were tested and two minor related problems fixed. - Rewrite and fix corner case in sb600spi The command line argument handler for AMD chipsets had a minor bug. - Add support for GNU Hurd. We added support to build GNU Hurd because it seems easy enough. - Add support for GD25VQ21B, GD25VQ40C, GD25VQ80C and GD25VQ16C. Some new flash chips were added (regression potential about zero). - Makefile: Fix driver blacklist dependencies The makefile tries to disable some programmers on certain architectures/OSes and was a bit overzealous. - rayer_spi: add support for SPI Tiny Tools-compatible hardware. This adds the definition of a pin mapping for a certain hardware model. - makefile: allow to disable all default-yes config variables with CONFIG_NOTHING=yes. Build/makefile-only change. - Partial architecture support for alpha hppa m68k sh s390 Like for Hurd we decided to add support for these because the changes were mostly trivial and we can now build on all Debian architectures but PS3. This patch also adds support for the s390x architecture that xenial will support for the first time. - dediprog: use ordinary USB devs array. - pickit2_spi: use ordinary USB devs array. These two merely change the output of flashrom -L (that lists all supported devices) and allow for easier future extension of said modules. So to sum up... there were not *only* bug fixes since the RC but also some small feature additions that target new hardware and OSes. Most of these changes are effective at build time only. There are very few imaginable regression possibilities for the x86 and arm versions since the RC IMHO. Logs etc. will follow soon. ** Affects: flashrom (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Description changed: In bug #1547144 a FFe was granted to merge Debian's package of flashrom's 0.9.9 release candidate into xenial was granted and the package has been updated. Upstream has now released 0.9.9 final including a security fix and I would like to request another exception (and a sponsored upload) for that. The following is a list of changes that followed the RC before the final release: - Fix fscanf format string security bug in layout.c This is the mentioned security bug, cf. https://security-tracker.debian.org/tracker/TEMP-000-C3CEDB Depending on the use case of flashrom the security implications of the correct use might be quite higher than the threat by this bug but it certainly makes sense to include this fix. - Implement serial port shutdown both for regular termination and error condition in pony_spi. pony_spi is one of the numerous programmer modules flashrom supports. This fixes a file descriptor leak. - Add a bunch of new/tested stuff and various small changes 25. In these patches we gather test status updates and other minor fixes. In this particular change there were: status updates, whitespace and typo fixes, a Makefile and manpage patch - partially to make lintian happy. - Fix compilation on SunOS. Building on Solaris-based OSes were tested and two minor related problems fixed. - Rewrite and fix corner case in sb600spi - The command line argument handler for AMD chipsets had a minor bug. + The command line argument handler for AMD chipsets had a minor bug. - Add support for GNU Hurd. We added support to build GNU Hurd because it seems easy enough. - Add support for GD25VQ21B, GD25VQ40C, GD25VQ80C and GD25VQ16C. Some new flash chips were added (regression potential about zero). - Makefile: Fix driver blacklist dependencies The makefile tries to disable some programmers on certain architectures/OSes and was a bit
[Bug 1547144] Re: [FFe] sync flashrom_0.9.9~rc1+r1942-1 from Debian unstable
** Description changed: flashrom has released 0.9.9-rc1 and intends to release 0.9.9 final shortly after xenial beta freeze (around 2016-02-28). Currently Ubuntu still ships 0.9.7+r1852-1.1 due to timing constraints of the respective Debian maintainer. However, said release candidate has now been uploaded to Debian unstable and could probably easily synced with Ubuntu. The current Ubuntu release is missing quite a few critical bugfixes (cf. bug #1404568) and does not build on all Ubuntu supported architectures. - flashrom 0.9.9 compiles and works on all supported architectures (and quite a few more). + flashrom 0.9.9 compiles and works on all supported architectures apart from s390x (although we plan to add that in the final 0.9.9 release). Also, the old version is missing support for some very popular hardware devices. On the other hand we deem regressions very unlikely. The development process of the last 1,5 years was rather slow regarding new features and has focused on improving cross-platform compatibility etc. For a short overview of what has changed from 0.9.7 to the current version please see the attached NEWS file (NB: upstream tagged 0.9.7 at r1711, 0.9.8 at r1888). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547144 Title: [FFe] sync flashrom_0.9.9~rc1+r1942-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1547144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547144] Re: [FFe] sync flashrom_0.9.9~rc1+r1942-1 from Debian unstable
** Description changed: flashrom has released 0.9.9-rc1 and intends to release 0.9.9 final shortly after xenial beta freeze (around 2016-02-28). - Currently Ubuntu still ships 0.9.7+r1852-1.1 which is missing quite a few critical bugfixes (cf. bug #1404568) and does not build on all Ubuntu supported architectures. + Currently Ubuntu still ships 0.9.7+r1852-1.1 due to timing constraints of the respective Debian maintainer. However, said release candidate has now been uploaded to Debian unstable and could probably easily synced with Ubuntu. + The current Ubuntu release is missing quite a few critical bugfixes (cf. bug #1404568) and does not build on all Ubuntu supported architectures. flashrom 0.9.9 compiles and works on all supported architectures (and quite a few more). Also, the old version is missing support for some very popular hardware devices. On the other hand we deem regressions very unlikely. The development process of the last 1,5 years was rather slow regarding new features and has focused on improving cross-platform compatibility etc. For a short overview of what has changed from 0.9.7 to the current version please see the attached NEWS file (NB: upstream tagged 0.9.7 at r1711, 0.9.8 at r1888). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547144 Title: [FFe] sync flashrom_0.9.9~rc1+r1942-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1547144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547144] Re: [FFe] sync flashrom_0.9.9~rc1+r1942-1 from Debian unstable
** Description changed: - flashrom has released 0.9.9-rc1. + flashrom has released 0.9.9-rc1 and intends to release 0.9.9 final + shortly after xenial beta freeze (around 2016-02-28). - Ubuntu is still at 0.9.7+r1852-1.1 which is missing quite a few critical - bugfixes and does not build on all Ubuntu supported architectures. + Currently Ubuntu still ships 0.9.7+r1852-1.1 which is missing quite a few critical bugfixes (cf. bug #1404568) and does not build on all Ubuntu supported architectures. + flashrom 0.9.9 compiles and works on all supported architectures (and quite a few more). + Also, the old version is missing support for some very popular hardware devices. - flashrom 0.9.9 compiles and works on all architectures except - S390/S390x. + On the other hand we deem regressions very unlikely. The development + process of the last 1,5 years was rather slow regarding new features and + has focused on improving cross-platform compatibility etc. + + For a short overview of what has changed from 0.9.7 to the current + version please see the attached NEWS file (NB: upstream tagged 0.9.7 at + r1711, 0.9.8 at r1888). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547144 Title: [FFe] sync flashrom_0.9.9~rc1+r1942-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1547144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311893] Re: kdbg does not start after upgrading to Trusty
This is fixed upstream by this commit http://repo.or.cz/w/kdbg.git/commit/dd2ecd5010070ec7af0a67b1f9dbfcaf58668170 and would be trivial to fix in Ubuntu by including the regenerated image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311893 Title: kdbg does not start after upgrading to Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdbg/+bug/1311893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()
Whoopsie... I completely missed the subject and the stack traces above, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373221 Title: guvcview crashed with SIGSEGV in get_ctrl_by_id() To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()
This is probably more interesting (from running guvcview in gdb): [New Thread 0x7fffe5e44700 (LWP 27177)] Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [Thread 0x7fffe5e44700 (LWP 27177) exited] Program received signal SIGSEGV, Segmentation fault. 0x777b2115 in audio_init_portaudio () from /usr/lib/x86_64-linux-gnu/libgviewaudio-1.0.so.0 (gdb) bt #0 0x777b2115 in audio_init_portaudio () from /usr/lib/x86_64-linux-gnu/libgviewaudio-1.0.so.0 #1 0x777afada in audio_init () from /usr/lib/x86_64-linux-gnu/libgviewaudio-1.0.so.0 #2 0x004084e6 in ?? () #3 0x00407336 in main () My libguvcview-1.0-0:amd64 is version 2.0.1+debian-1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373221 Title: guvcview crashed with SIGSEGV in get_ctrl_by_id() To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()
I doubt that this verbose log helps much, but here you go...
This is with a Trust 17676 webcam (145f:019f) on Debian 8 (guvcview
2.0.1+debian-1).
$ guvcview --verbosity=2
GUVCVIEW: couldn't open /home/.../.config/guvcview2/video0 for read: No such
file or directory
GUVCVIEW: language catalog= dir:/usr/share/locale type:(null) cat:guvcview.mo
GUVCVIEW: main thread (tid: 879)
V4L2_CORE: Device Node Path: /dev/video0
VID/PID: 145f 019f
Novatek
Trust Webcam
serial: (null)
busnum: 3
devnum: 3
V4L2_CORE: language catalog= dir:/usr/share/locale type:(null)
cat:gview_v4l2core.mo
V4L2_CORE: capture method mmap (1)
V4L2_CORE: video device: /dev/video0
V4L2_CORE: mapping control for Pan (relative)
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for Tilt (relative)
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for Pan Reset
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for Tilt Reset
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for Focus
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for LED1 Mode
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for LED1 Frequency
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for Disable video processing
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: mapping control for Raw bits per pixel
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: Init. Trust Webcam (location: usb-:00:1a.7-2)
{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 1280, height = 720 }
Time interval between frame: 1/10, 2/15,
{ discrete: width = 1920, height = 1080 }
Time interval between frame: 1/5,
{ pixelformat = 'MJPG', description = 'MJPEG' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 1280, height = 720 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 1920, height = 1080 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ pixelformat = 'RGB3', description = 'RGB3' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 1280, height = 720 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 1920, height = 1080 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ pixelformat = 'BGR3', description = 'BGR3' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 1280, height = 720 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ discrete: width = 1920, height = 1080 }
Time interval between frame: 1/30, 1/20, 1/15, 1/10, 2/15,
{ pixelformat = 'YU12', description = 'YU12' }
{ discrete: width = 640, height = 480 }
Time interval
[Bug 1404568] [NEW] segfaults with 24 older flash chips
Public bug reported: The flashrom included in ubuntu 14.10 vivid segfaults when running on a computer with any of 24 affected flash chips due to a bug I have added in r1833 (vivid ships r1852). For details please see the attached patch that should fix the issue. ** Affects: flashrom (Ubuntu) Importance: Undecided Status: Confirmed ** Patch added: 0001-Fix-handling-of-write-protection-at-register-space-a.patch https://bugs.launchpad.net/bugs/1404568/+attachment/4284909/+files/0001-Fix-handling-of-write-protection-at-register-space-a.patch ** Changed in: flashrom (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404568 Title: segfaults with 24 older flash chips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1404568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404568] Re: segfaults with 24 older flash chips
** Description changed: - The flashrom included in ubuntu 14.10 vivid segfaults when running on a computer with any of 24 affected flash chips due to a bug I have added in r1833 (vivid ships r1852). - For details please see the attached patch that should fix the issue. + The flashrom included in ubuntu 15.04 vivid segfaults when running on a computer with any of 24 affected flash chips due to a bug I have added in r1833 (vivid ships r1852). + For details please see the attached patch that should fix the issue or the upstream report: http://www.flashrom.org/pipermail/flashrom/2014-December/013038.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404568 Title: segfaults with 24 older flash chips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1404568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307657] Re: UBUNTU_MENUPROXY should not be set in Xfce
** Changed in: unity-gtk-module (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307657 Title: UBUNTU_MENUPROXY should not be set in Xfce To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1307657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1104230] Re: DisplayPort 1.2 MST support seems to be broken in the Intel driver
@ickle: could you please respond as to why this is not an xserver-xorg- video-intel bug? ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104230 Title: DisplayPort 1.2 MST support seems to be broken in the Intel driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1104230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274799] Re: xchat freezes when trying to connect to a server
This is not fixed but quite hard to reproduce. I am quite lucky to be able to reproduce it now quite consistently on my (mostly) 12.04 installation. I am using various packages from quantal, raring, saucy and I think even trusty because I need a lot of different updated texlive packages, but they have relatively few dependencies so they are probably not related (but you can notice that by the harmless Fontconfig warnings in the gdb log attached). I do have some glib packages apparently from quantal too, which might be related but certainly not the cause of my problems - I am very sure I saw this before quantal (probably even before precise) came out. The problem with this bug is that it is very much depending on timing and/or external circumstances. There are many bug reports on other trackers, forums etc. and no one was able to reproduce it consistently. I have experienced the bug in different networks with different probabilities, i.e. it was obviously depending on the network connecting me to the internet and was consistently there on one network and perfectly fine on the other one just 30mins later with no changes whatsoever... repeatedly. The attached log has 3 runs of xchat interrupted after it has entered the endless loop in question (look out for Starting program: /usr/bin/xchat). I have installed libglib2.0-0-dbg (2.34.0-1ubuntu1 from 12.10) after the first run and libgtk2.0-0-dbg (2.24.10-0ubuntu6 from 12.04) after the second run. With someone dares to look at this I am happy to provide more information if need be. ** Attachment added: gdb-xchat.txt https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/274799/+attachment/3943092/+files/gdb-xchat.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/274799 Title: xchat freezes when trying to connect to a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/274799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274799] Re: xchat freezes when trying to connect to a server
Oh and BTW the other thread (there are exactly two at that point) has always the same stack trace (so is probably just blocked at that select call): Thread 2 (Thread 0x7fffe565d700 (LWP 5684)): #0 0x7529d763 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fffe573898a in NotifierThreadProc (clientData=optimized out) at /build/buildd/tcl8.5-8.5.11/unix/../unix/tclUnixNotfy.c:988 #2 0x7662fe9a in start_thread (arg=0x7fffe565d700) at pthread_create.c:308 #3 0x752a43fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #4 0x in ?? () -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/274799 Title: xchat freezes when trying to connect to a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/274799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274799] Re: xchat freezes when trying to connect to a server
** Changed in: xchat (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/274799 Title: xchat freezes when trying to connect to a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/274799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719563] Re: mountall: fatal error: cannot open /dev/mapper/crypthome_unformatted
The situation should definitely be improved. I had some problems already with ubuntu's init (bug #1077650) and this is another case 1) that would make it impossible for a less knowledgeable person to boot and 2) that is rather hard to diagnose even if you have some profound knowledge. I second Thorsten's comments regarding the fstab manpage very much. It was also the first place where I have looked for an answer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719563 Title: mountall: fatal error: cannot open /dev/mapper/crypthome_unformatted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1077650] Re: booting from raid in degraded mode ends in endless loop
this is *not* a duplicate (of bug #728435) as bernd wrote. i am not entirely sure, because in my case i am also suffering from another crypto-related bug, but i think lvm2 might be involved too: mountroot_fail() in /usr/share/initramfs-tools/scripts/init- premount/lvm2 does never return 0 although scanning for new lvs might actually fix things and should restart the search for the root device. but as said i am not sure... initramfs-tools are pretty complicated regarding interoperability of the various scripts/packages. anyway, this needs way more attention... raids should be used to up reliability not downtimes :/ best (as always) would probably to see if debian is also affected and fix it there first then... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1077650 Title: booting from raid in degraded mode ends in endless loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1077650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003309] Re: Boot fails after installing updates, error: “cryptsetup: evms_activate is not available
i had the same problem as the_nipper (robert-wirth-gmx) #58. i migrated a previous root in lvm in luks to root in lvm in luks in raid1 (by creating new block devices incl. a degraded raid1, copying all data over and changing the configuration of crypttab, fstab etc. and updating the initramfs). the solution mentioned in http://forums.debian.net/viewtopic.php?f=5t=74232#p506229 (as linked by #61) did not work for me, probably because of plymouth...? the stdin of cryptsetup was not connected so typing the password had no effect whatsoever, yey... but hey canoncial could get a fancy and completely useless boot screen, that's important! anyway, I resorted to copying lots of the ui logic from /usr/share/initramfs-tools/scripts/local-top/cryptroot into the attached script, which has to be put in /etc/initramfs-tools/scripts/local-top/cryptraid (and made executable!). it is tailored to open /dev/md1, change cryptsource if needed. then run update-initramfs -k all -u it works for me, but it is not much tested, ymmv. ** Attachment added: cryptraid https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309/+attachment/3922004/+files/cryptraid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003309 Title: Boot fails after installing updates, error: “cryptsetup: evms_activate is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255920] Re: Multiple flash chips report, but only one flash chip is installed
The right one ;) flashrom cannot decide which one (yet), so you have to either check the chip visually, or - if you feel lucky - just choose one of the two. The basic definition for both chips is equal, but the (optional) write protection is different. If that is not active it should work with both. This problem is not a bug, hence I have changed it to Invalid. Feel free to contact our mailing list for further support (or even comment here, but be aware that these bugs get read by less people). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255920 Title: Multiple flash chips report, but only one flash chip is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1255920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255920] Re: Multiple flash chips report, but only one flash chip is installed
** Changed in: flashrom (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255920 Title: Multiple flash chips report, but only one flash chip is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1255920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage
Don't expect anybody to read a bug report that has a fix released state since 2011. Either change the state of this bug report or file a new one (I think the latter would be better actually, but i did not read the whole thread in detail). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774071 Title: Indicator-datetime-service renders 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/774071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551382] Re: [needs-packaging] Bring this package back in Karmic and Lucid
Good news: the 2.0 release has been added to Debain sid http://packages.debian.org/changelogs/pool/main/u/usbview/usbview_2.0-1/changelog We can either wait until it hits Debian testing (which will have to wait until the next Debian release because of their freeze AFAIK) and gets automatically synced, or someone needs to sync it manually, see https://wiki.ubuntu.com/SyncRequestProcess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/551382 Title: [needs-packaging] Bring this package back in Karmic and Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbview/+bug/551382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893828] Re: Granting Wireshark capture privileges does not allow USB capture
Similar arguments can be brought up against allowing a user to capture network traffic. So arguing against it - at least if there were a fine- grained option in the kernel - is not convincing, especially if it is disabled by default as the network privilege is ATM. And if there were such a capability then it would be obviously safer and better to run wireshark as non-root if you have to capture USB packets, which isn't too uncommon for hardware developers (I am in that situation right now ;). Hence this is *not* an opinion but a bug (not only in wireshark, but also/mainly in the kernel). Did anybody know what the kernel guys think about adding a finer-grained capability for this? I won't reopen the bug for now mainly because it does not make sense, if the Debian (and an Ubuntu) maintainer just not agrees with the above :) I encourage you to do so and add the kernel though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893828 Title: Granting Wireshark capture privileges does not allow USB capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/893828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893828] Re: Granting Wireshark capture privileges does not allow USB capture
I think if a system uses NAS… I meant it more generally: information leaks on networks are so common that you can compare the thread level to that of a sniffable USB. This opens a security hole on the system as detailed above. That's exactly my point, this should not be needed, because it greatly increases the threat potential due to unnecessarily granted privileges. It is just a poor workaround for the missing capability setting in the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893828 Title: Granting Wireshark capture privileges does not allow USB capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/893828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
hm... I am pretty sure now that this was fixed by linux- image-3.2.0-37-generic (3.2.0-37.58), i can still reproduce the wrong behavior (even with a second bind mount sometimes apparently) with linux-image-3.2.0-36-generic (3.2.0-36.57). can anyone confirm this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
*** This bug is a duplicate of bug 1101666 *** https://bugs.launchpad.net/bugs/1101666 ** This bug has been marked a duplicate of bug 1101666 inotify fd leak -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
lsof -x fl +D /data/home output is empty. losetup -a -v does only show the .iso mounted: /dev/loop0: [fc02]:6162260 (/tftpboot/isos/systemrescuecd-x86-3.0.0.iso) losetup -f returns the first unused loop device, which is loop1. there is no nfs server running. i am running out of ideas... other than compiling umount myself and adding some debug prints... DONOTWANT. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
i have been digging further. REG_MTPTS contains the following values in my setup: /tftpboot/loops/sysrescuecd /tftpboot /data/backup/home-recover /var/cache /home /boot /data i have redirected the output of the umount call (initiated via fstab-decode) to a log file: fstab-decode umount -f -v -r -d $REG_MTPTS /umountfs.log 21 the output is: can't delete device /dev/loop0: No such device or address umount2: Device or resource busy umount: /data/home busy - remounted read-only /dev/loop0 has been unmounted /data/tftpboot has been unmounted /data/backup/home/hourly.0 has been unmounted /data/cache has been unmounted /dev/sda1 has been unmounted /dev/mapper/ssd-data has been unmounted the first line is apparently a problem with umount trying to delete the loop device (umount's -d option) but i dont think that is related. i am not sure about umount2. it is either related to the loop device or to /data/home... which is clearly not cleanly umounted, but remounted as read-only (due to umount's -r option). so... why is it busy? i have no idea. lsof and ps auxf output (called before Unmount local filesystems) attached ** Attachment added: umountfs-lsof.log https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1103416/+attachment/3509715/+files/umountfs-lsof.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
** Attachment added: umountfs-ps.log https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1103416/+attachment/3509716/+files/umountfs-ps.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
grep -v ^# /etc/fstab proc/proc procnodev,noexec,nosuid 0 0 /dev/mapper/ssd-root/ ext4noatime,errors=remount-ro,discard 0 1 UUID=adfae278-b399-446e-8024-77bd1cef5ef0 /boot ext2noatime 0 2 /dev/mapper/ssd-data/data ext4 noatime,discard 0 3 /data/home /home nonebind0 0 /data/cache /var/cache nonebind0 0 /data/backup/home/hourly.0 /data/backup/home-recover/ nonebind,ro /data/tftpboot /tftpboot none bind /tftpboot/isos/systemrescuecd.iso /tftpboot/loops/sysrescuecd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
... autoloop,ro sorry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
I am seeing this too in the last couple of reboots. My / and home are on separate lvm volumes and share the same crypted luks partition. /home is actually bind-mounted from my data partition: /dev/mapper/ssd-root/ ext4noatime,errors=remount-ro,discard 0 1 /dev/mapper/ssd-data/data ext4 noatime,discard 0 3 /data/home /home nonebind0 0 fsck from util-linux 2.20.1 fsck from util-linux 2.20.1 /dev/mapper/ssd-root: clean, … /dev/mapper/ssd-data: Clearing orphaned inode … Kernel is 3.2.0-36-generic #57 amd64. I am have enabled the standard precise repo, precise-updates, precise- backports, precise-security, partner (and all sections in each of them, i.e. main restricted universe multiverse), but *not* precise-proposed. I am also using the official opera and mate-desktop repository (I am running mate as DE). I have also added the quantal repo to use the updated texlive packages, but this should be not related, everything else is pinned back. The purpose of this paragraph is to isolate the offending package. I dont think that the packages named inhere are related; they are just named to derive a timeframe when it broke. I have to admit that I saw this problem earlier (as in months ago) too, but I am quite certain this is something new, i.e. introduced in 2013. The last updates I installed are firefox-globalmenu 18.0.1+build1-0ubuntu0.12.04.1 (automatically, last night), desktop-file-utils 0.20-0ubuntu3 (manually, 2013-01-18). The non-security updates between the two just mentions have not been installed yet, but I will do so now. The problem was certainly introduced by an update *before* them (or a security update). There was a NM update on the 16th: network-manager:amd64 0.9.4.0-0ubuntu4.1 - 0.9.4.0-0ubuntu4.2, at the same time I upgraded xserver and activity-log-manager-common (whatever that is :) and a few others. On the 13th I upgraded mountall:amd64 2.36 - 2.36.3, grub2-common:amd64 1.99-21ubuntu3.4 - 1.99-21ubuntu3.7 (et al) and a few others. I would guess the culprit is one of those above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103416] Re: 12.04 isn't cleanly unmounted
I have added some debug prints to umountfs and umountroot (in /etc/init.d/). Namely: mount /umountrootfs-mount.log lsof /umountrootfs-lsof.log ps auxf /umountrootfs-ps.log and similarly in umountfs before they run their umount sequences. The umountrootfs-mount.log shows, that one of my binded mounts on the /data filesystem is not unmounted cleanly by unmountfs: /data/home on /home type none (ro) /data on the other hand is *not* mentioned anymore(!) The original state of /data/home is this: /data/home on /home type none (rw,bind) as is to be expected with the fstab line i posted in #2. Other bind-mounted directories are unmounted correctly though although they use the same options in fstab, e.g.: /data/tftpboot /tftpboot none bind which shows up in the mount log (before umounting in umountfs) as /data/tftpboot on /tftpboot type none (rw,bind) Neither the ps nor the lsof log indicate any obvious problems. Because of this I have to assume that the initscripts are missing something. ** Package changed: ubuntu = sysvinit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103416 Title: 12.04 isn't cleanly unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1103416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 916948] Re: josm does not always find a valid JVM
i have not looked at how debian does this (we probably better should do that), but FWIW this is my solution... this most probably is not what the original authors wanted though, because this will try to launch josm even on headless-only solutions i think. but it has the advantage, that it uses whatever jvm is available, even if it is only reachable by JAVA_HOME and/or JDK_HOME... ** Patch added: josm-JAVA_HOME.patch https://bugs.launchpad.net/ubuntu/+source/josm/+bug/916948/+attachment/3411954/+files/josm-JAVA_HOME.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/916948 Title: josm does not always find a valid JVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/916948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 916948] Re: josm does not always find a valid JVM
after installing openjdk-7-jdk and removing the following packages: default-jdk openjdk-6-jre-headless default-jre-headless icedtea-6-jre-jamvm openjdk-6-jre openjdk-6-jre-lib icedtea-6-jre-cacao openjdk-6-jdk default-jre openjdk-6-demo the josm start script failed to load it as described above although java -jar /usr/share/josm/josm.jar works fine... ** Summary changed: - Does not default on java runtime (eg. default-jre) + josm does not always find a valid JVM ** Changed in: josm (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/916948 Title: josm does not always find a valid JVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/916948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035051] [NEW] Sync flashrom 0.9.6.1+r1563-1 (universe) from Debian unstable (main)
Public bug reported: affects ubuntu/flashrom subscribe ubuntu-sponsors hi! i am one of the upstream maintainers (without upload rights to Ubuntu) and would like to request the sync of version 0.9.6.1 of our package from Debian. You can read about the changes in our wiki: http://flashrom.org/Flashrom/0.9.6 To summarize: new programmers, new chips, new CLI options, new bugs! Thanks! -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ** Affects: flashrom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035051 Title: Sync flashrom 0.9.6.1+r1563-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1035051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 524407] Re: hibernating wakes up sleeping harddrives
gotta love the bots... this is still an issue on afaik ALL kernels, see upstream bug report... ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/524407 Title: hibernating wakes up sleeping harddrives To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/524407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
mine are either 104 or 0 bytes, but that's just because there are two keys/cookies in them: xauth -f ~/.goutputstream-5X9DGW list hostname/unix:11 MIT-MAGIC-COOKIE-1 key1 hostname/unix:10 MIT-MAGIC-COOKIE-1 key2 (no idea why there are two though...) apart from that i am using mate-desktop but also with lightdm. i am commenting only due to the size/cookie count mismatch, although i dont think it matters, sorry if it is just spam (like 50% of the messages above :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660250] Re: On AC state changes udisks-daemon wakes disks from standby
apparently this issue remains in 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660250 Title: On AC state changes udisks-daemon wakes disks from standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/660250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 961997] Re: *** VTE ***: Failed to load terminal capabilities from '/etc/termcap'
not only the cursor keys dont work, also enter does no longer work in my case and that is pretty bad. it happened today while i was upgrading from 10.10 to 11.04 (via do-release-upgrade in gnome-terminal) (so most probably other versions involved). since such an upgrade takes quite some time it is very annoying because you can no longer work in new terminal windows for that period. a reboot after the upgrade solved it here too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/961997 Title: *** VTE ***: Failed to load terminal capabilities from '/etc/termcap' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte3/+bug/961997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985294] Re: NUnit assembly is not picked up by monodevelop
yes: dpkg -l *nunit* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-==- un libmono-nunit2.2-cil none (no description available) un libmono-nunit2.4-cil none (no description available) un libnunit-cil none (no description available) ii libnunit-cil-dev 2.5.10.11092+dfsg-3Unit test framework for CLI ii libnunit-doc 2.5.10.11092+dfsg-3Unit test framework for CLI un libnunit2.2.6-cil none (no description available) un libnunit2.4-cilnone (no description available) ii libnunit2.5-cil 2.5.10.11092+dfsg-3Unit test framework for CLI ii monodevelop-nunit 2.8.6.3+dfsg-2 NUnit plugin for MonoDevelop ii monodoc-nunit-manual 2.5.10.11092+dfsg-3compiled XML documentation for NUnit ii nunit 2.5.10.11092+dfsg-3Unit test framework for CLI ii nunit-console 2.5.10.11092+dfsg-3Unit test framework for CLI ii nunit-gui 2.5.10.11092+dfsg-3Unit test framework for CLI ** Changed in: monodevelop (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985294 Title: NUnit assembly is not picked up by monodevelop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/985294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985294] Re: NUnit assembly is not picked up by monodevelop
afaik un (unknown, no errors) indicates that they were purged. unpurged packages (i.e. those with left over config files) are rc (remove(d)/conf-files). nevertheless i have purged them with aptitude to no avail. how does monodevelop determine the available references? is there another similar package that does provide assemblies? i could test if the basic mechanism works with that then... do you notice any differences between your test machine and mine? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985294 Title: NUnit assembly is not picked up by monodevelop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/985294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985294] [NEW] NUnit assembly is not picked up by monodevelop
Public bug reported: nothing NUnit-related does show up in the references dialog although i have everything remotely related installed. if i add the assembly by hand it works correctly. the nunit addin works correctly afaik (i.e. the window is there and i can launch test runs). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: monodevelop-nunit 2.8.6.3+dfsg-2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 19 00:58:39 2012 PackageArchitecture: all SourcePackage: monodevelop UpgradeStatus: Upgraded to precise on 2012-03-25 (24 days ago) ** Affects: monodevelop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985294 Title: NUnit assembly is not picked up by monodevelop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/985294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985294] Re: NUnit assembly is not picked up by monodevelop
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985294 Title: NUnit assembly is not picked up by monodevelop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/985294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 976717] [NEW] Sync flashrom 0.9.5.2+r1517-1 (universe) from Debian unstable (main)
Public bug reported: affects ubuntu/flashrom subscribe ubuntu-sponsors hi! i am one of the upstream maintainers (without upload rights to Ubuntu) and would like to request to sync 0.9.5.2 of our package from Debian. The changes since the previous version in precise (0.9.5.1) fixes some programmers using the linux spi module (mostly embedded boards) and some mainboards using the IT87 or W83627 for SPI access. the latter was a regression introduced between 0.9.4 and 0.9.5 (i.e. between oneiric and precise). We regard this release as bugfix-only. Thanks! -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ** Affects: flashrom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976717 Title: Sync flashrom 0.9.5.2+r1517-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/976717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901547] Re: Doesn't work
the updated (see http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651027) package in 12.04 still does not work correctly. ** Bug watch added: Debian Bug tracker #651027 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651027 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901547 Title: Doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlcopyeditor/+bug/901547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966506] [NEW] xsd.exe does not handle default values for xs:decimal correctly
Public bug reported:
when xsd.exe is used with the /c switch to generate c# code from an existing
xml schema (.xsd), it handles attributes like the following incorrectly:
xs:attribute name=setup type=xs:decimal default=123/
this will generate:
[System.ComponentModel.DefaultValue(123m)]
[System.Xml.Serialization.XmlAttributeAttribute(Namespace=)]
public decimal setup {
get {
return this.setupField;
}
set {
this.setupField = value;
}
}
the important thing is the parameter for the DefaultValue constructor: '123m'
is added without quotes. i am not entirely sure that it should actually be
quoted, but if it is not then the compiler bails out with:
error CS0182: An attribute argument must be a constant expression, typeof
expression or array creation expression
defaults for other types (e.g. integer) are quoted correctly.
this is with the latest mono stuff from 12.04
i.e. 2.10.8.1-1ubuntu1
** Affects: mono (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966506
Title:
xsd.exe does not handle default values for xs:decimal correctly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/966506/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941555] [NEW] FFE: Sync flashrom 0.9.5.1+r1508-1 (universe) from Debian unstable (main)
Public bug reported: affects ubuntu/flashrom subscribe ubuntu-release hi! i am one of the upstream maintainers (without upload rights to Ubuntu) and would like to request to sync 0.9.5.1 of our package from Debian. There was a FFE for 0.9.5 already which brought in most of our current development (see bug #938156 https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/938156). 0.9.5.1 was (only) released to fix a few bugs that were shipped with 0.9.5. It fixes accessing of future flash chips that will be supported by querying parameters instead of hardcoding them into our database. So this might become useful in the long term for yet unknown chips and that's the reason i'd like you to push it for the LTS release. Beside those changes only building on Debian/kFreeBsd was fixed. I have not (re)tried building it on ubuntu, but can do so if requested by a sponsor. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ** Affects: flashrom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941555 Title: FFE: Sync flashrom 0.9.5.1+r1508-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/941555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 938156] [NEW] FFE: Sync flashrom 0.9.5+r1503-1 (universe) from Debian unstable (main)
Public bug reported: affects ubuntu/flashrom subscribe ubuntu-release hi! i am one of the upstream maintainers and would like to request to sync 0.9.5 of our package from debian. I have attached the Changelog diff that contains all upstream commits since 0.9.4 (which was packaged for Debian and synced to Ubuntu 11.10 and 12.04 before), but it is rather large. It is probably better to look at our release notes here: http://flashrom.org/Flashrom/0.9.5 Also, the pbuilder-dist precise build log is appended. I have also verified basic operation with our built-in dummy programmer in a precise QEMU VM (i386). I would like to see 0.9.5 in the next LTS release mainly because of two reasons: 1. Newer Intel-based mainboards are often locked down so flashrom can not access the flash chip to update the BIOS (the common use case of flashrom, especially with Ubuntu). The new release adds better support for Intel-based mainboards and prints more precise and easier to understand messages to the user in the case a board is locked down. 2. Support for SFDP was added in 0.9.5 which allows flashrom to support new flash chips without having all properties hard-coded beforehand. So if a user buys a new mainboard with a yet unreleased flash chip holding the BIOS he might be able to update the firmware without getting/building an updated binary. But there are also lots of other useful changes since 0.9.4 which was released last summer. OTOH there are not many reasons to not sync flashrom. There are not many dependencies and afaik no dependents at all. There are no known regressions yet. As mentioned in the release notes above the current SFDP implementation is a bit buggy regarding erase operations. This will be fixed shortly in an exceptional service release tagged 0.9.5.1 (for which i would file another FFE, if this one gets ACKed. It that the correct procedure?). The new Debian package contains a patch that disables (the newly added) support for the Linux kernel's SPI driver, because of dependency problems with non-Linux kernels in Debian. This could be probably dropped and replaced with a dependency on the linux kernel headers for Ubuntu already (will be done so in Debian ASAP), but is not a big issue for most Ubuntu users i guess. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ** Affects: flashrom (Ubuntu) Importance: Undecided Status: New ** Patch added: 0.9.4-0.9.5-Changelog.diff https://bugs.launchpad.net/bugs/938156/+attachment/2767732/+files/0.9.4-0.9.5-Changelog.diff ** Attachment added: last_operation.log https://bugs.launchpad.net/bugs/938156/+attachment/2767733/+files/last_operation.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938156 Title: FFE: Sync flashrom 0.9.5+r1503-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/938156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933484] [NEW] installation fails because $DPKG_MAINTSCRIPT_ARCH is not set
Public bug reported: hi! the upgrade of flashplugin-nonfree 11.1.102.62ubuntu0.10.10.1 (in ubuntu maverick) broke flash for me so i looked into it... dpkg-reconfigure flashplugin-installer Installing from local file /var/cache/flashplugin-installer/adobe-flashplugin_11.1.102.62.orig.tar.gz install: cannot stat `adobe-flashplugin*//libflashplayer.so': No such file or directory the last message comes from the postinst script. the respective command in that script is: install -m 644 adobe- flashplugin*/$DPKG_MAINTSCRIPT_ARCH/libflashplayer.so /usr/lib /flashplugin-installer/ so apparently the $DPKG_MAINTSCRIPT_ARCH is not set correctly. when i exported it from the shell, installation succeeded and the browsers are able to to flash again too: export DPKG_MAINTSCRIPT_ARCH=amd64 ; dpkg-reconfigure flashplugin-installer Installing from local file /var/cache/flashplugin-installer/adobe-flashplugin_11.1.102.62.orig.tar.gz Flash Plugin installed. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: flashplugin-installer 11.1.102.62ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-32.65-generic 2.6.35.14 Uname: Linux 2.6.35-32-generic x86_64 Architecture: amd64 Date: Thu Feb 16 15:07:09 2012 SourcePackage: flashplugin-nonfree ** Affects: flashplugin-nonfree (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933484 Title: installation fails because $DPKG_MAINTSCRIPT_ARCH is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/933484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933484] Re: installation fails because $DPKG_MAINTSCRIPT_ARCH is not set
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933484 Title: installation fails because $DPKG_MAINTSCRIPT_ARCH is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/933484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876001] Re: alsactl store throws /home/(username) not ours errors
probably a duplicate of bug #557016 and hence only a cosmetic problem. i am not changing the bug state (yet), please do so if you agree. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876001 Title: alsactl store throws /home/(username) not ours errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/876001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 822432] Re: dmidecode does falsely use bit 7 when decoding the chassis-type
** Patch added: 0001-Make-dmi_chassis_type-aware-of-the-lock-bit.patch https://bugs.launchpad.net/bugs/822432/+attachment/2260545/+files/0001-Make-dmi_chassis_type-aware-of-the-lock-bit.patch ** Bug watch added: Debian Bug tracker #637028 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637028 ** Also affects: dmidecode (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637028 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/822432 Title: dmidecode does falsely use bit 7 when decoding the chassis-type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/822432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 822432] [NEW] dmidecode does falsely use bit 7 when decoding the chassis-type
Public bug reported: the bug is present in all vanilla versions since at least 2.9. the attached patch was sent upstream and to Debian. for details please see the patch. ** Affects: dmidecode (Ubuntu) Importance: Undecided Status: New ** Affects: dmidecode (Debian) Importance: Unknown Status: Unknown ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/822432 Title: dmidecode does falsely use bit 7 when decoding the chassis-type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/822432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816918] Re: please sync flashrom 0.9.4+r1394-1 from debian unstable
thanks for the ack! regarding the SRU: sorry for using the wrong term. the problem is that there is no single patch/commit that could be ported and we don't have the resources to look at 400 commits to find all corner cases and port them. maybe it would be easier to just remove the package from lucid completely. is that possible? flashrom is exceptional because it can be really, really dangerous, more than about any other package in ubuntu (permanent hardware error...). so please think about a solution for this :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816918 Title: please sync flashrom 0.9.4+r1394-1 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/816918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816918] Re: please sync flashrom 0.9.4+r1394-1 from debian
** Summary changed: - please sync flashrom 0.9.4 from debian + please sync flashrom 0.9.4+r1394-1 from debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816918 Title: please sync flashrom 0.9.4+r1394-1 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/816918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816918] Re: please sync flashrom (0.9.4+r1394-1) from debian unstable
** Summary changed: - please sync flashrom 0.9.4+r1394-1 from debian + please sync flashrom (0.9.4+r1394-1) from debian unstable ** Description changed: - i am one of the upstream maintainers. we have released a new stable - version yesterday (http://www.flashrom.org/Flashrom/0.9.4). one of us is - currently preparing the upload of a new debian package. i'll update this - bug when it is ready. + i am one of the upstream maintainers. we have released a new stable version on 2011-07-26 (http://www.flashrom.org/Flashrom/0.9.4). our Debian maintainer has prepared a new package, which is now in unstable (or on the way there). + please sync! + + a backport for LTS might also be a good idea, because there are many + bugs fixed since the (very old) version in LTS that could brick the + user's PC completely. dunno if that qualifies for a backport though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816918 Title: please sync flashrom (0.9.4+r1394-1) from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/816918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816918] [NEW] please sync flashrom 0.9.4 from debian
Public bug reported: i am one of the upstream maintainers. we have released a new stable version yesterday (http://www.flashrom.org/Flashrom/0.9.4). one of us is currently preparing the upload of a new debian package. i'll update this bug when it is ready. ** Affects: flashrom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816918 Title: please sync flashrom 0.9.4 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/816918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 791335] Re: please sync avr-libc (1:1.7.1-2) from debian unstable
oh. sorry benjamin about that! https://wiki.ubuntu.com/SyncRequestProcess does not mention (changed) dependencies. can you point me to some documentation explaining what i can do to fix this please? the main question for me is: why are those dependencies not available at build(?) time? some of them seem to be easily satisfiable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791335 Title: please sync avr-libc (1:1.7.1-2) from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avr-libc/+bug/791335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 791335] Re: please sync avr-libc (1:1.7.1-2) from debian unstable
how can one test this easily? i would have to (try to) build it myself then i guess? regarding the output you pasted: i was puzzled because as you said most of the dependencies are in place, but it prints them as unmet anyway... for binutils-avr the situation is clear. in oneiric there is currently 2.20.1-1ubuntu2 but = 2.20.1-2 is needed. so this needs to be either synced and the ubuntu changes dropped or merged. thanks for your quick responses! the ubuntu patch for binutils-avr is huge (100MB) and i don't even dare to look at it, so i'll file a merge request. auto merge report can be found at https://merges.ubuntu.com/b/binutils-avr/REPORT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791335 Title: please sync avr-libc (1:1.7.1-2) from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avr-libc/+bug/791335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816957] [NEW] Please merge binutils-avr 2.20.1-2 (universe) from Debian unstable (main)
Public bug reported: this is a dependency for syncing avr-libc see bug 791335 i am new to this stuff, but the mom report looks like it is not a big problem: https://merges.ubuntu.com/b/binutils-avr/REPORT what scares me a bit is the huge ubuntu delta... why is it so huge? ** Affects: binutils-avr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816957 Title: Please merge binutils-avr 2.20.1-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils-avr/+bug/816957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 791335] Re: please sync avr-libc (1:1.7.1-2) from debian unstable
** Summary changed: - avr-libc is terribly out of date + please sync avr-libc (1:1.7.1-2) from debian unstable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791335 Title: please sync avr-libc (1:1.7.1-2) from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avr-libc/+bug/791335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 791335] Re: please sync avr-libc (1:1.7.1-2) from debian unstable
** Description changed: avr-libc 1.6.8 has been released on 2010-02-11 and it's the actual version in Ubuntu 11.04. In the meantime avr-libc 1.7.0 has been released on 2010-06-16 and avr-libc 1.7.1 has been released on 2011-02-16. - I think it's time to update this package. + It has been updated in Debian sid to 1.7.1 and i *think* there are no + changes in Ubuntu, so please sync it. - http://download.savannah.gnu.org/releases/avr-libc/ + This may/will break the arduino package (see http://bugs.debian.org/cgi- + bin/bugreport.cgi?bug=633659) which also needs a sync then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791335 Title: please sync avr-libc (1:1.7.1-2) from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avr-libc/+bug/791335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 791335] Re: avr-libc is terribly out of date
1.7.1 was packaged for debian now (will show up shortly), but because the deadline for the automatic sync of debian packages for 11.10 was already two weeks ago, it will not be in 11.10 without intervention from some ubuntu maintainers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791335 Title: avr-libc is terribly out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avr-libc/+bug/791335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
