[Bug 554009] Re: Resume from disk (swapfile) fails

[Ryo Onodera]

As this bug was closed with "fix-released", I'm re-opening as another
bug report: https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/1644975

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554009

Title:
  Resume from disk (swapfile) fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/554009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644975] Re: Resume from disk (swapfile) fails

[Ryo Onodera]

Hi! Some time passed...

Will this bug be addressed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644975

Title:
  Resume from disk (swapfile) fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644975] Re: Resume from disk (swapfile) fails

[Ryo Onodera]

I'm marking this status to confirmed because this is a re-open of
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/554009

** Changed in: initramfs-tools (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/1644975

Title:
  Resume from disk (swapfile) fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1522563] Re: hangs on packages libfm4 and libfm-extra4

[Ryo Onodera]

Thanks for fixing this!!!

So, when is this released to xenial??

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522563

Title:
  hangs on packages libfm4 and libfm-extra4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debsums/+bug/1522563/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644975] [NEW] Resume from disk (swapfile) fails

[Ryo Onodera]

Public bug reported:

Well, hibernation with swap file doesn't work while hibernation with
swap partition works perfectly fine with the exactly same configuration
and hardware.

The reason is that when resuming from swap file, initramfs script can't
correctly detect the machine are hibernated from the last shut down.

And I investigated the issue and found this patch solved
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
hibernate to work.

And it isn't applied to the package. I'd like to help this is really
applied to the official package.

In short, my setup is swapfile inside the system filesystem (LUKS + LVM2
+ ext4).

Also, I roughly followed this tutorial to prepare this configurartion
that: https://ubuntuforums.org/showthread.php?t=1042946

I've opening this bug because the original bug report is closed and
getting no response...

** Affects: initramfs-tools (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/1644975

Title:
  Resume from disk (swapfile) fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 554009] Re: Resume from disk (swapfile) fails

[Ryo Onodera]

Oops, I pasted wrong URL for the patch...

This is the URL I intended to quote:
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/554009/+attachment/1366060/+files/resume.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554009

Title:
  Resume from disk (swapfile) fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/554009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 554009] Re: Resume from disk (swapfile) fails

[Ryo Onodera]

Well, my setup needed this patch
(https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/554009/+attachment/1368963/+files/probe.c) for the hibernate
to work.

And it isn't applied to the package.
I'd like to help this is really fixed.

In short, my setup is swapfile inside the system filesystem (LUKS + LVM2
+ ext4).

I roughly followed this tutorial to achive that:
https://ubuntuforums.org/showthread.php?t=1042946

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554009

Title:
  Resume from disk (swapfile) fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/554009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1522563] Re: hangs on packages libfm4 and libfm-extra4

[Ryo Onodera]

I've encountered with similar problem for the package libfuse2.

After some investigation, it seems that this is caused by an infinite
loop inside resolve_path.

After this tiny hack, it finished to work:

```
ryoqun@miyako:~$ diff -u /usr/bin/debsums{?*,}
--- /usr/bin/debsums.backup 2016-10-26 13:12:30.157544031 +0900
+++ /usr/bin/debsums2016-10-26 13:33:01.565480144 +0900
@@ -427,7 +427,9 @@
 my $path = shift;
 my @tokens = split(/\//, $path);
 my @parts = ();
-while (@tokens) {
+my $loop_count = 0;
+while (@tokens && $loop_count < 2000) {
+$loop_count++;
 my $token = shift @tokens;
 next if $token eq '.' || $token eq '';
 if ($token eq '..') {
@@ -443,6 +445,9 @@
 push @parts, $token;
 }
 }
+if ($loop_count >= 2000) {
+  warn "maybe infinite loop: $path  ";
+}
 return join('/', @parts);
 }
 

```

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522563

Title:
  hangs on packages libfm4 and libfm-extra4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debsums/+bug/1522563/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1633865] [NEW] zfs-doc is needlessly depended by zfsutils-linux

[Ryo Onodera]

Public bug reported:

Not minor bug.

However as far as I'm aware, usually *-doc packages aren't depended by
really actual packages. They should be optional for disk space savings.
However the zfs package doesn't follow the convention as follows:

ryoqun@miyako:~$ aptitude show zfsutils-linux
Package: zfsutils-linux
New: yes
State: installed
Automatically installed: no
Version: 0.6.5.6-0ubuntu8
Priority: extra
Section: universe/admin
Maintainer: Ubuntu Developers 
Architecture: amd64
Uncompressed Size: 720 k
Depends: init-system-helpers (>= 1.18~), zfs-doc (= 0.6.5.6-0ubuntu8), 
libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), 
libuutil1linux, libzfs2linux, libzpool2linux
Recommends: zfs-dkms, zfs-zed
Suggests: samba-common-bin (>= 3.0.23), nfs-kernel-server, zfs-initramfs
Conflicts: zfs, zfs-fuse, zfs-fuse:i386, zfs:i386, zfsutils-linux:i386
Replaces: zfs, zfs:i386
Provides: zfs
Description: Native OpenZFS management utilities for Linux
 This package provides the zpool and zfs commands that are used to manage 
OpenZFS filesystems.
Homepage: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.6

** Affects: zfs-linux (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Not minor bug.
  
  However as far as I'm aware, usually *-doc packages aren't depended by
  really actual packages. They should be optional for disk space savings.
- However the zfs packages doesn't follow the convention as follows:
+ However the zfs package doesn't follow the convention as follows:
  
  ryoqun@miyako:~$ aptitude show zfsutils-linux
- Package: zfsutils-linux  
+ Package: zfsutils-linux
  New: yes
  State: installed
  Automatically installed: no
  Version: 0.6.5.6-0ubuntu8
  Priority: extra
  Section: universe/admin
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Uncompressed Size: 720 k
  Depends: init-system-helpers (>= 1.18~), zfs-doc (= 0.6.5.6-0ubuntu8), 
libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), 
libuutil1linux, libzfs2linux, libzpool2linux
  Recommends: zfs-dkms, zfs-zed
  Suggests: samba-common-bin (>= 3.0.23), nfs-kernel-server, zfs-initramfs
  Conflicts: zfs, zfs-fuse, zfs-fuse:i386, zfs:i386, zfsutils-linux:i386
  Replaces: zfs, zfs:i386
  Provides: zfs
  Description: Native OpenZFS management utilities for Linux
-  This package provides the zpool and zfs commands that are used to manage 
OpenZFS filesystems.
+  This package provides the zpool and zfs commands that are used to manage 
OpenZFS filesystems.
  Homepage: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.6

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633865

Title:
  zfs-doc is needlessly depended by zfsutils-linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1633865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1083038] Re: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS

[Ryo Onodera]

Maybe related to this:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1514120

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083038

Title:
  Encrypted LVM in Ubiquity unavailable when installing alongside an
  existing OS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1083038/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1514120] Re: Encrypted Ubuntu on dual boot

[Ryo Onodera]

This should be really fixed...

Encrypted ubuntu installation SHOULD be treated equally as plain-text
installation.

It seems that encrypted installation can be chosen only if the whole
system disk is overwritten... I think Ubiquity just can use the free
area of the system disk I've prepared for Ubuntu..

Note that I CAN INSTALL Ubuntu in that way when I forgo encryption by
choosing "Alongside...". That's not fair for security-inclined people..

So, I'm forced to go manual disk trickery like this:
https://www.jayway.com/2015/11/22/ubuntu-full-disk-encrypted-macosx/ And
there is plenty other similar tutorials on the Internet.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514120

Title:
  Encrypted Ubuntu on dual boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1514120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1160352] [NEW] Still reachable leak is reported with dlopen and pthread

[Ryo Onodera]

Public bug reported:

Valgrind reports still reachable leaks in dlopen()/dlclose() only when
linked with -lpthread with the following code:

$ cat /tmp/valgrind-dlopen-pthread-leak.c
#include stdio.h
#include dlfcn.h

int main() {
  char *error = 0;

  void *handle = dlopen(NULL, RTLD_NOW | RTLD_GLOBAL);

  if((error = dlerror())) {
printf(dlopen failed: %s\n, error);
return 1;
  }
  printf(%p\n, handle);

  dlclose(handle);

  if((error = dlerror())) {
printf(dlclose failed: %s\n, error);
return 1;
  }

  return 0;
}

This code correctly dlopen()s and dlclose()s, so there should be no leak
whatsoever. And this can be confirmed from the result of valgrind
without -lpthread:

$ gcc /tmp/valgrind-dlopen-pthread-leak.c -ldl
$ valgrind ./a.out
...
==31371== All heap blocks were freed -- no leaks are possible
...

But this doesn't hold once I compile the sample code with -lpthread:

$ gcc /tmp/valgrind-dlopen-pthread-leak.c -ldl -lpthread
$ valgrind ./a.out
...
==31363== LEAK SUMMARY:
==31363==definitely lost: 0 bytes in 0 blocks
==31363==indirectly lost: 0 bytes in 0 blocks
==31363==  possibly lost: 0 bytes in 0 blocks
==31363==still reachable: 32 bytes in 1 blocks
==31363== suppressed: 0 bytes in 0 blocks
...

I've created a suppresion for this:

$ valgrind --gen-suppressions=all --leak-check=full --show-reachable=yes ./a.out
...
==31414== 32 bytes in 1 blocks are still reachable in loss record 1 of 1
==31414==at 0x4C29DB4: calloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==31414==by 0x4E3359F: _dlerror_run (dlerror.c:142)
==31414==by 0x4E32FC0: dlopen@@GLIBC_2.2.5 (dlopen.c:88)
==31414==by 0x400662: main (in 
/home/ryoqun/dev/rubinius/rubinius-master/a.out)
...
{
   Still-reachable leak in dlopen/dlclose when linked to libpthread
   Memcheck:Leak
   fun:calloc
   fun:_dlerror_run
   fun:dlopen@@GLIBC_2.2.5
   fun:main
}
...

I don't know this should rather be fixed at libc...

** Affects: valgrind (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/1160352

Title:
  Still reachable leak is reported with dlopen and pthread

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1160352/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1160352] Re: Still reachable leak is reported with dlopen and pthread

[Ryo Onodera]

** Description changed:

  Valgrind reports still reachable leaks in dlopen()/dlclose() only when
  linked with -lpthread with the following code:
  
- $ cat /tmp/valgrind-dlopen-pthread-leak.c 
+ $ cat /tmp/valgrind-dlopen-pthread-leak.c
  #include stdio.h
  #include dlfcn.h
  
  int main() {
-   char *error = 0;
+   char *error = 0;
  
-   void *handle = dlopen(NULL, RTLD_NOW | RTLD_GLOBAL);
+   void *handle = dlopen(NULL, RTLD_NOW | RTLD_GLOBAL);
  
-   if((error = dlerror())) {
- printf(dlopen failed: %s\n, error);
- return 1;
-   }
-   printf(%p\n, handle);
+   if((error = dlerror())) {
+ printf(dlopen failed: %s\n, error);
+ return 1;
+   }
+   printf(%p\n, handle);
  
-   dlclose(handle);
+   dlclose(handle);
  
-   if((error = dlerror())) {
- printf(dlclose failed: %s\n, error);
- return 1;
-   }
+   if((error = dlerror())) {
+ printf(dlclose failed: %s\n, error);
+ return 1;
+   }
  
-   return 0;
+   return 0;
  }
  
  This code correctly dlopen()s and dlclose()s, so there should be no leak
  whatsoever. And this can be confirmed from the result of valgrind
  without -lpthread:
  
  $ gcc /tmp/valgrind-dlopen-pthread-leak.c -ldl
  $ valgrind ./a.out
  ...
  ==31371== All heap blocks were freed -- no leaks are possible
  ...
  
  But this doesn't hold once I compile the sample code with -lpthread:
  
  $ gcc /tmp/valgrind-dlopen-pthread-leak.c -ldl -lpthread
  $ valgrind ./a.out
  ...
  ==31363== LEAK SUMMARY:
  ==31363==definitely lost: 0 bytes in 0 blocks
  ==31363==indirectly lost: 0 bytes in 0 blocks
  ==31363==  possibly lost: 0 bytes in 0 blocks
  ==31363==still reachable: 32 bytes in 1 blocks
  ==31363== suppressed: 0 bytes in 0 blocks
  ...
  
  I've created a suppresion for this:
  
- $ valgrind --gen-suppressions=yes --leak-check=full --show-reachable=yes 
./a.out
+ $ valgrind --gen-suppressions=all --leak-check=full --show-reachable=yes 
./a.out
  ...
  ==31414== 32 bytes in 1 blocks are still reachable in loss record 1 of 1
  ==31414==at 0x4C29DB4: calloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==31414==by 0x4E3359F: _dlerror_run (dlerror.c:142)
  ==31414==by 0x4E32FC0: dlopen@@GLIBC_2.2.5 (dlopen.c:88)
  ==31414==by 0x400662: main (in 
/home/ryoqun/dev/rubinius/rubinius-master/a.out)
  ...
  {
-Still-reachable leak in dlopen/dlclose when linked to libpthread
-Memcheck:Leak
-fun:calloc
-fun:_dlerror_run
-fun:dlopen@@GLIBC_2.2.5
-fun:main
+    Still-reachable leak in dlopen/dlclose when linked to libpthread
+    Memcheck:Leak
+    fun:calloc
+    fun:_dlerror_run
+    fun:dlopen@@GLIBC_2.2.5
+    fun:main
  }
  ...
  
  I don't know this should rather be fixed at libc...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160352

Title:
  Still reachable leak is reported with dlopen and pthread

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1160352/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1148529] Re: OProfile support is disabled

[Ryo Onodera]

Thanks for replying!

First of all, Ubuntu started to provide the latest OProfile (0.9.8)
again after some inactivity of packaging. I'm really happy about that.
Thank you very mcuh!!

Because now LLVM depends on libopagent, this bug is blocked by these
following libopagent-related bugs:

Bug 1154025 Install PIC version of libbfd.a
Bug 1148682 symbol lookup error: /usr/lib/libopagent.so: undefined symbol: 
bfd_init

Could you also take a look at these? By resolving them, we can avoid to
add the linking option -lbfd to configure.

Turning back to this bug, the side effects or permance issues should be
minimal.

When LLVM's users aren't using OProfile related C++ LLVM classes
explitly, nothing happens at runtime. Thus, thre is no performance
degragation at all. Starting from LLVM 3.1, linking to libopagent is
delayed by using dlopen as much as possible until when we absoluteby
have to do it.

In a sense, as a side effect, we have new dependancy. Also, the binary
size will be bigger a bit.

Note that I didn't but we should make libllvm3.1 and llvm-3.1-dev depend
on libopagent1.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148529

Title:
  OProfile support is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-3.1/+bug/1148529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1154025] [NEW] Install PIC version of libbfd.a

[Ryo Onodera]

Public bug reported:

Like Bug #50512, there should be the PIC version of libbfd.a.

The reason is as follows:

1. As required, we need to link statically to libbfd (see linux-tools:
perf should link statically to libbfd Bug #783660)

2. we need to build libopagent correctly, which uses libbfd with static
link (see oprofile: symbol lookup error: /usr/lib/libopagent.so:
undefined symbol: bfd_init Bug #1148682)

3. But currently, libopagent aren't built correctly causing the symbol
lookup error. That's because OProfile's patches/static-libbfd-
libopagnet-makefile.patch disables static linking to libbfd (possibly,
as a quick work around):

--- a/libopagent/Makefile.am
+++ b/libopagent/Makefile.am
@@ -15,7 +15,7 @@ libopagent_la_CPPFLAGS = -I ${top_srcdir
  -I ${top_srcdir}/libutil \
  @OP_CPPFLAGS@

-libopagent_la_LIBADD = $(BFD_LIBS)
+libopagent_la_LIBADD =

 # Do not increment the major version for this library except to
 # intentionally break backward ABI compatability.  Use the

When I build OProfile with the preceeding work-around patch removed, I
get following error. I want to fix this error.

/bin/bash ../libtool --tag=CC   --mode=link x86_64-linux-gnu-gcc -fPIC
-g -O2 -version-info  1:0:0 -Wl,--version-
script=../libopagent/opagent_symbols.ver   -o libopagent.la -rpath
/usr/lib/oprofile libopagent_la-opagent.lo /usr/lib/libbfd.a -lz
-liberty -ldl  -liberty -lpopt  -ldl -lz

*** Warning: Linking the shared library libopagent.la against the
*** static library /usr/lib/libbfd.a is not portable!
libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  
.libs/libopagent_la-opagent.o   /usr/lib/libbfd.a -liberty 
/usr/lib/x86_64-linux-gnu/libpopt.so -ldl -lz  -O2 
-Wl,--version-script=../libopagent/opagent_symbols.ver   -Wl,-soname 
-Wl,libopagent.so.1 -o .libs/libopagent.so.1.0.0
/usr/bin/ld: /usr/lib/libbfd.a(archures.o): relocation R_X86_64_32S against 
`_sch_istable' can not be used when making a shared object; recompile with -fPIC
/usr/lib/libbfd.a: could not read symbols: Bad value
collect2: error: ld returned 1 exit status
make: *** [libopagent.la] Error 1

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Like LP #50512, there should be the PIC version of libbfd.a.
  
  The reason is as follows:
  
  1. As required, we need to link statically to libbfd (see linux-tools:
- perf should link statically to libbfd LP #783660)
+ perf should link statically to libbfd Bugs #783660)
  
  2. we need to build libopagent correctly, which uses libbfd with static
  link (see oprofile: symbol lookup error: /usr/lib/libopagent.so:
  undefined symbol: bfd_init LP #1148682)
  
  3. But currently, libopagent aren't built correctly causing the symbol
  lookup error. That's because OProfile's patches/static-libbfd-
  libopagnet-makefile.patch disables static linking to libbfd (possibly,
  as a quick work around):
  
  --- a/libopagent/Makefile.am
  +++ b/libopagent/Makefile.am
  @@ -15,7 +15,7 @@ libopagent_la_CPPFLAGS = -I ${top_srcdir
-   -I ${top_srcdir}/libutil \
-   @OP_CPPFLAGS@
-  
+   -I ${top_srcdir}/libutil \
+   @OP_CPPFLAGS@
+ 
  -libopagent_la_LIBADD = $(BFD_LIBS)
  +libopagent_la_LIBADD =
-  
-  # Do not increment the major version for this library except to
-  # intentionally break backward ABI compatability.  Use the
+ 
+  # Do not increment the major version for this library except to
+  # intentionally break backward ABI compatability.  Use the
  
  When I build OProfile with the preceeding work-around patch removed, I
  get following error. I want to fix this error.
  
  /bin/bash ../libtool --tag=CC   --mode=link x86_64-linux-gnu-gcc -fPIC
  -g -O2 -version-info  1:0:0 -Wl,--version-
  script=../libopagent/opagent_symbols.ver   -o libopagent.la -rpath
  /usr/lib/oprofile libopagent_la-opagent.lo /usr/lib/libbfd.a -lz
  -liberty -ldl  -liberty -lpopt  -ldl -lz
  
  *** Warning: Linking the shared library libopagent.la against the
  *** static library /usr/lib/libbfd.a is not portable!
  libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  
.libs/libopagent_la-opagent.o   /usr/lib/libbfd.a -liberty 
/usr/lib/x86_64-linux-gnu/libpopt.so -ldl -lz  -O2 
-Wl,--version-script=../libopagent/opagent_symbols.ver   -Wl,-soname 
-Wl,libopagent.so.1 -o .libs/libopagent.so.1.0.0
  /usr/bin/ld: /usr/lib/libbfd.a(archures.o): relocation R_X86_64_32S against 
`_sch_istable' can not be used when making a shared object; recompile with -fPIC
  /usr/lib/libbfd.a: could not read symbols: Bad value
  collect2: error: ld returned 1 exit status
  make: *** [libopagent.la] Error 1

** Description changed:

  Like LP #50512, there should be the PIC version of libbfd.a.
  
  The reason is as follows:
  
  1. As required, we need to link statically to libbfd (see linux-tools:
- perf should link statically to libbfd Bugs #783660)
+ perf should link statically to libbfd Bug #783660)
  
  2. we need to build libopagent correctly, which uses libbfd with static
  

[Bug 1148682] Re: symbol lookup error: /usr/lib/libopagent.so: undefined symbol: bfd_init

[Ryo Onodera]

As reported at Bug 1154025, my original patch wasn't correct. We need to
link statically to libbfd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148682

Title:
  symbol lookup error: /usr/lib/libopagent.so: undefined symbol:
  bfd_init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/1148682/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1148529] [NEW] OProfile support is disabled

[Ryo Onodera]

Public bug reported:

OProfile suppot for LLVM is disabled. It is used for profiling JIT-ed
code by LLVM.

Please enable OProfile. I created a rough patch for it. Please review.

** Affects: llvm-3.1 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: llvm-oprofile.patch
   
https://bugs.launchpad.net/bugs/1148529/+attachment/3559640/+files/llvm-oprofile.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148529

Title:
  OProfile support is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-3.1/+bug/1148529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1148682] [NEW] symbol lookup error: /usr/lib/libopagent.so: undefined symbol: bfd_init

[Ryo Onodera]

Public bug reported:

libopagent.so have to be linked to libbfd.

I just created a tiny patch for it. However, I'm not sure if this is the
right way to fix it..

Please review this.

ryoqun@rrm:~/rubinius/ryoqun$ ldd /usr/lib/libopagent.so
linux-vdso.so.1 =  (0x7fff0c39a000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7fb3cfc55000)
/lib64/ld-linux-x86-64.so.2 (0x7fb3d0238000)
ryoqun@rrm:~/rubinius/ryoqun$ ldd /usr/lib/libopagent.so
linux-vdso.so.1 =  (0x7fff5f1ff000)
libbfd-2.22.90-system.20120924.so = 
/usr/lib/libbfd-2.22.90-system.20120924.so (0x7f88dc80b000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f88dc44c000)
libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f88dc247000)
libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f88dc03)
/lib64/ld-linux-x86-64.so.2 (0x7f88dcd3d000)

** Affects: oprofile (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: oprofile-link-libbfd.patch
   
https://bugs.launchpad.net/bugs/1148682/+attachment/3559675/+files/oprofile-link-libbfd.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148682

Title:
  symbol lookup error: /usr/lib/libopagent.so: undefined symbol:
  bfd_init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/1148682/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1148682] Re: symbol lookup error: /usr/lib/libopagent.so: undefined symbol: bfd_init

[Ryo Onodera]

** Patch added: oprofile-link-libbfd.patch
   
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/1148682/+attachment/3559676/+files/oprofile-link-libbfd.patch

** Attachment removed: oprofile-link-libbfd.patch
   
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/1148682/+attachment/3559675/+files/oprofile-link-libbfd.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148682

Title:
  symbol lookup error: /usr/lib/libopagent.so: undefined symbol:
  bfd_init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/1148682/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1071683] Re: error while loading shared libraries

[Ryo Onodera]

Could you try again after install this package?:

  apt-get install binutils

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071683

Title:
  error while loading shared libraries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/1071683/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1148682] Re: symbol lookup error: /usr/lib/libopagent.so: undefined symbol: bfd_init

[Ryo Onodera]

** Description changed:

  libopagent.so have to be linked to libbfd.
  
  I just created a tiny patch for it. However, I'm not sure if this is the
  right way to fix it..
  
  Please review this.
  
+ ldd's change:
+ 
+ Before:
+ 
  ryoqun@rrm:~/rubinius/ryoqun$ ldd /usr/lib/libopagent.so
- linux-vdso.so.1 =  (0x7fff0c39a000)
- libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7fb3cfc55000)
- /lib64/ld-linux-x86-64.so.2 (0x7fb3d0238000)
+ linux-vdso.so.1 =  (0x7fff0c39a000)
+ libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7fb3cfc55000)
+ /lib64/ld-linux-x86-64.so.2 (0x7fb3d0238000)
+ 
+ After:
+ 
  ryoqun@rrm:~/rubinius/ryoqun$ ldd /usr/lib/libopagent.so
- linux-vdso.so.1 =  (0x7fff5f1ff000)
- libbfd-2.22.90-system.20120924.so = 
/usr/lib/libbfd-2.22.90-system.20120924.so (0x7f88dc80b000)
- libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f88dc44c000)
- libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f88dc247000)
- libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f88dc03)
- /lib64/ld-linux-x86-64.so.2 (0x7f88dcd3d000)
+ linux-vdso.so.1 =  (0x7fff5f1ff000)
+ libbfd-2.22.90-system.20120924.so = 
/usr/lib/libbfd-2.22.90-system.20120924.so (0x7f88dc80b000)
+ libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f88dc44c000)
+ libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f88dc247000)
+ libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f88dc03)
+ /lib64/ld-linux-x86-64.so.2 (0x7f88dcd3d000)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1148682

Title:
  symbol lookup error: /usr/lib/libopagent.so: undefined symbol:
  bfd_init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/1148682/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1069214] Re: no package named `libtiff5' is installed, cannot configure

[Ryo Onodera]

Hi, fortunately, this bug is fixed now! I confirmed.

This bug is similar to the now-fixed bug: Bug #1062503

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069214

Title:
  no package named `libtiff5' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1069214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1068555] Re: Quantal upgrade says no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Hi, fortunately, this bug is fixed now! I confirmed.

This bug is similar to the now-fixed bug: Bug #1062503

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068555

Title:
  Quantal upgrade says no package named `libjbig0' is installed, cannot
  configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1068555/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1065722] Re: Upgrade to quantal fails: libqtgui4:i386 depends on libtiff5

[Ryo Onodera]

Hi, fortunately, this bug is fixed now! I confirmed.

This bug is similar to the now-fixed bug: Bug #1062503

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065722

Title:
  Upgrade to quantal fails: libqtgui4:i386 depends on libtiff5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1065722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Hi, fortunately, this bug is fixed now! I confirmed.

This bug is similar to the now-fixed bug:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1062503

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025405] Re: package libtiff5 4.0.2-1ubuntu1 failed to install/upgrade: no package named `libtiff5' is installed, cannot configure

[Ryo Onodera]

Hi, fortunately, this bug is fixed now! I confirmed.

This bug is similar to the now-fixed bug: Bug #1062503

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025405

Title:
  package libtiff5 4.0.2-1ubuntu1 failed to install/upgrade: no package
  named `libtiff5' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1025405/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1062503] Re: apt fails to install libglapi-mesa-lts-quantal correctly on switching x stacks

[Ryo Onodera]

Hi, for your information, this was affecting following bugs too:

Bug #1065722
Bug #1025408
Bug #1025405
Bug #1068555
Bug #1069214

I was separately investigating this issue. The following comments are my
report of the investigation (including reproduciable steps):

https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/comments/10
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/comments/11

All of these bugs are due to an upgrade failure with multi-arch
packages.

Thanks very much for fixing this bug!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062503

Title:
  apt fails to install libglapi-mesa-lts-quantal correctly on switching
  x stacks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1062503/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1062503] Re: apt fails to install libglapi-mesa-lts-quantal correctly on switching x stacks

[Ryo Onodera]

Oops, I forgot one thing to say.

Could you confirm these bugs are really fixed now and close them?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062503

Title:
  apt fails to install libglapi-mesa-lts-quantal correctly on switching
  x stacks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1062503/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1068555] Re: Quantal upgrade says no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Graeme, this bug can be happened even if Skype isn't installed. Skype
depends on i386 library packages and those library packages actually
cause this bug. So, if you installed some of those i386 library packages
for some other reason, it's possible this bug is happened.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068555

Title:
  Quantal upgrade says no package named `libjbig0' is installed, cannot
  configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1068555/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1068555] Re: Quantal upgrade says no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Please take a look into this.

I've tracked down that this ALWAYS happens when AMD64 Precise Ubuntu
with Skype installed is upgraded to Quantal.

I've investigated this problem as much as possible. Please see Bug
#1025408

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068555

Title:
  Quantal upgrade says no package named `libjbig0' is installed, cannot
  configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1068555/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Today, I investigated this problem again.

I found another fact: when qdbus:amd64 isn't installed this problem does
NOT occur.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Btw, I think it's a good idea for do-release-upgrade to run apt-get
--dry-run to ckeck there is any problem before hand.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1065722] Re: Upgrade to quantal fails: libqtgui4:i386 depends on libtiff5

[Ryo Onodera]

This is related Bug #1025408

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065722

Title:
  Upgrade to quantal fails: libqtgui4:i386 depends on libtiff5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1065722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1068555] Re: Quantal upgrade says no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

This is also related to Bug #1065722

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068555

Title:
  Quantal upgrade says no package named `libjbig0' is installed, cannot
  configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1068555/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

OK, I did tested after restoring my backup.

Now, I'm fairly certain this upgrade failure is caused by
libqtgui4:i386, which is required by Skype. Actually this bug is not
caused by Skype itself. Ubuntu pacakaging for Qt 4 has some problem.
When libqtgui4:i386 is installed, the upgrade fails.

Reproducible steps:

1. Install Ubuntu 12.04 (amd64)
2. Install libqtgui4:i386
3. Upgrade to Ubuntu 12.10

So, the proper upgrade step is to ensure to remove libqtgui4 (thereby
Skype too) before starting the upgrade itself.

But this is less of importance to us...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

I'm attaching apt-get dry-run results indicating libqtgui4 issue.

To be specific, it seems that unpacking libjbig0:amd64 and
libtiff5:amd64 is skipped for some reason. Then configuring those
packages is started and failed. On the other hand, processing
libjbig0:i386 and libtiff5:i386 is fine, it seems...

** Attachment added: succeeded-libqtgui4-dry-run-install.txt
   
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+attachment/3432062/+files/succeeded-libqtgui4-dry-run-install.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

** Attachment added: failed-libqtgui4-dry-run-upgrade.txt
   
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+attachment/3432063/+files/failed-libqtgui4-dry-run-upgrade.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Tristan Schmelcher (tschmelcher) and WDMARKPC (wdmarkpc), thanks for
answering!

My guess isn't still cetain, but I came it up from the fact that Skype
requires this particular package. Usually it isn't required. My ubuntu
was freshly installed recently. And it wasn't contomized a lot and had
really plain setup other than Skype.

When I was upgrading, libtiff5 also failed to install like this package.
Technically, I'm guessing that there may be a multiarch-related  problem
in libjbig0 or libtiff5. When upgrading amd64 Ubuntu with Skype i386
package installed, both amd64 and i386 versions of those packages must
correctly be installed. But this didn't work due to some kind of lib
package dependancy relation problem..

Utkarsh Ray (utkarshray), did your ubuntu have  some third-party
software packages at time of upgrading?

Also, I forgot to mention that this bug only occurs on amd64 not on i386
probably.

Fortunately, I backed my system disk up before upgrading. I'll test if
upgrading works after removing Skype tomorrow.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025408] Re: package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Hmm, I just looked into this bug.

Maybe, this is related to skype..

I want to ask other people affected by this bug.

Was skype installed at the time of upgrades?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025408

Title:
  package libjbig0 2.0-2ubuntu1 failed to install/upgrade: no package
  named `libjbig0' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1025408/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1068555] Re: Quantal upgrade says no package named `libjbig0' is installed, cannot configure

[Ryo Onodera]

Hi, I eccountered this bug...

This is related to #1025408 and #1025405

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068555

Title:
  Quantal upgrade says no package named `libjbig0' is installed, cannot
  configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1068555/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs