Bug#850780: linux-image-4.8.0-2-amd64: can't boot on Acer Aspire V5, stuck on initrd
Package: src:linux Version: 4.8.15-2 Severity: critical Justification: breaks the whole system I'm still stuck with linux 4.6 on this laptop. Both the current 4.7 and 4.8 images just hangs on "Loading initramfs". There aren't any further messages. It has similarities to #841883, but I'm submitting a separate report just in case. (After all, perhaps 4.8.7-1 fixed the issue for that submitter, but it certainly didn't for me.) I tried using "earlyprintk=vga" like suggested in #841850, but it had no effect. Maybe that option doesn't work if grub2 boots in graphics mode, but I'm not sure how to disable that without causing other boot errors. Maybe you have some ideas? Not sure what other information would be useful from me. I couldn't use reportbug because it currently seems broken (crashes while collecting information). But here's the /proc/cpuinfo for the first cpu core, at least: processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 19 model name : AMD A10-5757M APU with Radeon(tm) HD Graphics stepping: 1 microcode : 0x6001119 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bugs: fxsave_leak sysret_ss_attrs bogomips: 4990.76 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro
Bug#819884: libz3-dev: shared library in dev package
Package: libz3-dev Version: 4.4.0-5 Severity: serious Justification: Policy 8.1 The libz3-dev package currently contains a shared library, libz3.so.4. According to Debian policy, such a library must be in a package "whose name changes whenever the SONAME of the shared library changes", normally following the pattern "librarynamesoversion" or "libraryname-soversion". In this case, the name for the package containing the shared library might be "libz3-4". Of course, the ".so" symlink should still be in the -dev package, so your .install files should probably contain something like: libz3-4.install: debian/tmp/usr/lib/*/libz3.so.* libz3-dev.install: debian/tmp/usr/include/* debian/tmp/usr/lib/*/libz3.so -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'stable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libz3-dev depends on: ii libc6 2.22-4 ii libgcc1 1:5.3.1-13 ii libgomp15.3.1-13 ii libstdc++6 5.3.1-13 libz3-dev recommends no packages. libz3-dev suggests no packages. -- no debconf information
Bug#639886: [pkg-wine-party] Bug#639886: FTBFS: standard includes have been moved from /usr/lib/* to /usr/bin/{arch directory}/*
If you wanted to know what your *actual* problem might be, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638867 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636210: [pkg-fgfs-crew] Bug#636210: flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory
On 08/01/2011 02:38 PM, Niels Thykier wrote: Hi, flightgear appears to be FTBFS on several architectures with the following: I suppose they need to be built against simgear-dev >= 2.0.0-3, not simgear-dev 2.0.0-2. Will it be necessary to upload new flightgear just to force the build-dep version, or is it enough to just wait for the buildds to build the newest simgear and flightgear after that? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#609439: [pkg-fgfs-crew] Bug#609439: FTBFS: libsgmaterial.so.2.0.0: undefined reference to `simgear::getPropertyRoot()'
On 10. jan. 2011 06:19, Gerardo Esteban Malazdrewicz wrote: I was able to compile it after rebuilding simgear with the attached patch. That patch isn't a proper fix and shouldn't even make a difference, the missing symbol isn't in libdl. (And the thing builds fine on my machines without any patches...) Possibly simply rebuilding simgear (maybe in a different environment) will randomly produce a working binary. After looking at the buildd logs for simgear, I think I've spotted the problem, and I'll try to fix it tonight (along with another mistake I made in the i386 build of simgear). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
