Re: [Bug 2066203] [NEW] Libraries compiled without Shadow Stack support
Am Mon, 20 May 2024 23:51:15 - schrieb Marcos Alano <2066...@bugs.launchpad.net>: > [6399376a4e90] main audio output warning: cannot load module `/usr/lib/x86_64-linux-gnu/vlc/plugins/audio_output/libpulse_plugin.so' (/lib/x86_64-linux-gnu/libmpg123.so.0: rebuild shared object with SHSTK support enabled) Regarding libmpg123, you either need to disable assembly optimizations (build with generic decoders only), I presume, or someone provide a patch that adds SHSTK to them. I don't know which implementation of shadow stacks glibc/gcc is using in that setup. I've read up on the concept and so far only figured that this is part of a spiral that complicates ABI and makes providing assembly-optimized functions ever harder. This would be fine if compilers finally would be smart enough to evade the need to do so. Last time I checked, hand-tuned AVX decoding was still a lot more efficient. We already handle IBT, I think, with indirect jumps landing only in C wrapper functions. I wonder if we could also limit the shadow stack impact to those with some compiler/linker flags. The assembly routines are rather strict math, many years old now without much of attack surface. All parsing of input is before them in C. They just do lots of multiplication/addition. One might try to write a set of optimizations using intrinsics for modern CPUs that then also get the treatment of shadow stacks or the next shiny security measure. Porting the AVX code to GCC (and/or other) inline ASM might also work for some platforms. (Still, I am wondering why pulseaudio output should need MPEG decoding.) Alrighty then, Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066203 Title: Libraries compiled without Shadow Stack support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/2066203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1585926] Re: mp3 files decode as crackly noise
Did you try mpg123 -o pulse? I remember that noise under Ubuntu when using pulse via alsa. Using pulse directly worked. As the mpg123 alsa output works fine with standalone alsa, I suppose the alsa-pulse binding is buggy. One could build mpg123 with a changed order of default output modules, so that pulse is tried before alsa. But that might start a pulse daemon where none is wanted. One could drop that alsa plugin that relays to pulse ... mpg123 would skip alsa if there is no default device available. One could fix that alsa plugin ... but then, it's still ugly that mpg123 plays via alsa to pulse that again talks to alsa (kernel) ...when at least mpg123 could talk to pulse directly. Well, I guess audio on Linux is messy. How's OSS4 doing these days? ;-) Alrighty then, Thomas unterwegs ohne Signatur -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585926 Title: mp3 files decode as crackly noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1585926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Oh … this is _another_ bug. We are dealing here with the situation that mdmon controlling rootfs on RAID is not handled at all with Ubuntu initrd, while this new CentOS issue is a bug in said handling in the CentOS initrd … The reference is valuable nevertheless … not least because I have systems about to be upgraded to CentOS 7.4 that might get hit by 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Can we get any reaction from Ubuntu on this? Is the needed reworking of the initrd about to happen for the LTS or is this a WONTFIX and root-on- Intel-Matrix-RAID is simply not supported? It is clear what has to happen to make things work again with systemd and mdadm/mdmon. Will it happen? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Is anyone working on this? I see that the bug is assigned, but apart from that only messages from affected users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Well, of course effects are a pain. The sync is only 256G SSDs im my case. Main point is that the fix is known since many years and should hopefully be quickly adaptible to Ubuntu. Or not … if it is really necessary to switch to a return to the initrd like Fedora. I wonder if 17.04 has this fixed. Can someone comment on that? Is the proper initrd buildup/teardown implemented there? I cannot test this on my servers as they are needed in production. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
So I got a simple fix for being able to reboot again: ``` udpate-rc.d mdadm disable ``` With that, the mdmon instance from the initrd persists (with @sbin/mdmon as argv[0]) and is not killed by systemd. So systemd-reboot does not hang. But: Since mdmon is not killed at all now, the array always gets a fresh resync on each boot. We really, really need to implement the return-to-initrd practice to be able to bring the system down in the proper reverse order of bringing it up. (So initrd filesystem has to be kept in memory for the whole time … wasting some memory with the huge initrds of today's time. It would also be nice if mdmon was just part of the kernel as it should be.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
This very much looks like this ancient issue in RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=752593 It got fixed at some point in 2012 … https://bugzilla.redhat.com/show_bug.cgi?id=785739 Is Ubuntu still running mdmon from inside the root fs and killing it before r/o remount? I am now pondering what to do with a set of file servers running 16.04 and root on an IMSM RAID. I got a number of systems with similar hardware running CentOS 7 just fine with no issue on reboot. I see elaborate handling of mdmon in systemd units on CentOS … including the --offroot command line parameter that I don't see documented anywhere. KillMode=none might also play a role in the mdmon@.service file. ** Bug watch added: Red Hat Bugzilla #752593 https://bugzilla.redhat.com/show_bug.cgi?id=752593 ** Bug watch added: Red Hat Bugzilla #785739 https://bugzilla.redhat.com/show_bug.cgi?id=785739 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585926] Re: mp3 files decode as crackly noise
This is mpg123 upstream here. I do not have a 16.04 system at hand currently, cannot confirm (and I suppose it should be a hardware machine, sound in a VM being possibly a different beast …). So, may I ask: 1. This is only with pulseaudio, right? Things are smooth when disabling it and playing directly via ALSA? 2. Does this persist with current mpg123 built from http://mpg123.org/current (it's 1.23.5)? Minimum receipe: apt-get install build-essentials apt-get libpulse-dev wget https://mpg123.org/current tar -xf mpg123-1.23.5.tar.bz2 cd mpg123-1.23.5 ./configure --disable-shared --with-audio=pulse make src/mpg123 $some_file (Naturally that's my guess, as I did not test on a ubuntu 16.04 system.) This should produce a self-contained mpg123 binary that does run without installing any modules. There was quite some work in the output code going from version 1.22 to 1.23. If the switch fixes things, we at least may have a hint at what fix might apply to the older version in Ubuntu. I am wondering about partial PCM frames being received by pulse, in particular. But that would cause output more like static noise, not what you describe … About the nature of the broken output … it is not just static noise; there is still the initial audio intelligible, just played fast with lots of skippyness? I may test this version of mpg123 on a ubuntu 14.04 box ... can someone tell me if something substantial in pulseaudio changed from that one (it was supposed to be stable now;-)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585926 Title: mp3 files decode as crackly noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1585926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Re: [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk)
The concerned Hardware is gone, so testing is not possible for me anymore. I guess the bug has to be closed ... I don't remember it occuring on other machines, also with integrated Radeon, but different chips. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561301 Title: [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/561301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1082031] [NEW] Package mpg123 for arm with option --with-cpu=generic_fpu
Am Thu, 22 Nov 2012 14:15:39 - schrieb Funatiker 1082...@bugs.launchpad.net: According to the Audacious-Board [2] this happens because has no ARM- assembly code for playing anything else than 16bit. It can be resolved by recompiling mpg123 with option --with-cpu=generic_fpu Right and wrong. 1. There is ARM-assembly code for 16 bit, 32 bit and float, using NEON instructions (Cortex A8). That's the most fun way to play with mpg123 on current ARM machines. 2. The normal ARM code is written for classic ARM CPUs without floating point support, employing integer math, where output of float values would be a bit silly. 3. So, for ARMs without NEON, but sporting decent floating point support, generic_fpu indeed is a good choice. [1] https://wiki.ubuntu.com/ARM/TEGRA/AC100 Too bad that's a Tegra 2 that manages to skip on the NEON part. Note that it would be possible to provide a build of generic_cpu and neon together, deciding at runtime which to use, just like the x86 build. But there is a catch: Someone needs some time to prepare some glue code and test it (the CPU check and setting some function pointers in optimize.c). Currently, I'm not the one. For the record: Combining the integer ARM code with floating point code in a single build is unrealistic. Alrighty then, Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082031 Title: Package mpg123 for arm with option --with-cpu=generic_fpu To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1082031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1072696] [NEW] Issue with Audacious play mp3 on ac100
Am Mon, 29 Oct 2012 12:19:50 - schrieb saturn saturn-...@nm.ru: Attempt to open mp3 return ...mpg123: Error opening file a.mp3: Unable to set up output format! (code 1). This bug with solution discussed already here http://redmine.audacious- media-player.org/boards/2/topics/315 Um, people want everything, eh? Well, there is some wrong and some correct information there. The solution of using generic C code works for getting all output formats, yes (John Lindgren got a wrong impression there about float output being coupled to assembly optimizations). But there also is assembly-optimized decoding to floating point on ARM platforms that feature the NEON instructions (Cortex A8). There is no common build encompassing the different variants like x86 and it is not likely that there will be, as the normal ARM does integer math. There might be a build that combines ARM NEON with generic C fallback code, using floating point math. When audacious insists on floating point data, even on machines that do not feature floating point hardware, you have some options: a) build mpg123 with generic_fpu ... which makes it relatively slow for normal 16-bit playback (or in ARM terms: consuming too much energy), b) patch audacious mpg123 binding to convert 16 bit to float on-the-fly or c) patch mpg123 (or motivate a release) to do that float conversion after decoding, just like 24 bit or unsigned integer types are handled right now. I see a point for the latter one ... it would not be hard to do it. Just a bit pointless in case this is running on a CPU that has working floating point support, or NEON, even. Thoughts from debian? I see this being a problem for packaging as you have to decide for one mpg123 build for stand-alone operation and linking to audacious. Compromises suck. Alrighty then, Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072696 Title: Issue with Audacious play mp3 on ac100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1072696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734889] Re: H5 Compat macros nonfunctional with -DH5_NO_DEPRECATED_SYMBOLS
Well, package maintainers should just remove --with-default-api- version=v16 from the build script. Perhaps some dependent packages need -DH5_USE_16_API following that change, but that is a small price to pay for having a proper build, eh? But looking at the time line of this bug, I fear that there is nobody at ubuntu concerned with HDF5 ... so let's see if poking the debian maintainers of the package brings something. In any case, the broken build is in 12.04 LTS, and probably there to stay. Off I am to building a local HDf5 library install ... this sucks. What also sucks is that the HDF5 lib lacks a sane way to undo the enforced default API, except fixing every individual function mapping macro. This is FAIL* on several levels. *Yeah, sorry for using that childish term. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/734889 Title: H5 Compat macros nonfunctional with -DH5_NO_DEPRECATED_SYMBOLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdf5/+bug/734889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734889] Re: H5 Compat macros nonfunctional with -DH5_NO_DEPRECATED_SYMBOLS
OK, over at debian I see that the package in the next release (HDF 1.8.8) has enforced 1.8 API in the build. I guess this one is WONTFIX for ubuntu 12.04 and will be resolved via an update from the debian package in a newer ubuntu release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/734889 Title: H5 Compat macros nonfunctional with -DH5_NO_DEPRECATED_SYMBOLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdf5/+bug/734889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
About the possibility of getting toshset functionality back, without users hacking stuff themselves: http://marc.info/?l=linux-acpim=123566412407178w=2 This is somewhere into a thread where toshset / toshiba_acpi devs discuss with the ACPI team about getting /dev/toshiba into the kernel, to make toshset work on current laptops. It doesn't look good. Man, am I glad that I gave away my Toshiba machine ... sorry for you folks, Linux sucks sometimes:-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644898 Title: required kernel toshiba support not enabled -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
For the full thread, it starts here: http://marc.info/?l=linux- acpim=123557427716510w=2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644898 Title: required kernel toshiba support not enabled -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589791] Re: apport tries wrong firefox version
Hm, somehow I missed the last question. I can try to reproduce this next week or so, when I have contact to the box again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/589791 Title: apport tries wrong firefox version -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665806] Re: false battery alarm with realtime app running (jackd)
Can't anyone shed some light on this? Isn't there a way to configure this power management frenzy? Seems like I'll have to pull Linux off my peer's machines, since it just behaves badly -- even if it's the machines behaving badly, but this does not count as long as they work in the preinstalled Windows. I don't want to insult people, but I am somewhat loosing my faith in non-geek Linux here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665806 Title: false battery alarm with realtime app running (jackd) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
This problem has been diagnosed to death: People dropped the experimental toshiba patch from the kernel, intending to see if this breaks something for anyone. People noticed that toshset is broken on their machines. People notice that it is trivial to apply the patch (excep the needed change for .37 kernels). Would people please just consider putting the patch back in for 10.04 / 10.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644898 Title: required kernel toshiba support not enabled -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665806] Re: false battery alarm with realtime app running (jackd)
This seems to be a long-known issue in fedora: https://bugzilla.redhat.com/show_bug.cgi?id=509190 But also there, no solution for years. Would be interesting to know why this long-standing problem just started to appear in the recent ubuntu update. ** Bug watch added: Red Hat Bugzilla #509190 https://bugzilla.redhat.com/show_bug.cgi?id=509190 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665806 Title: false battery alarm with realtime app running (jackd) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665806] Re: false battery alarm with realtime app running (jackd)
OK... I've seen those now: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/531190 and the actual https://bugs.freedesktop.org/show_bug.cgi?id=27399 Some how I have to agree with https://bugs.launchpad.net/ubuntu/+source/upower/+bug/531190/comments/55 ... we do a lot of noise on the ubuntu tracker without much information reaching the people who can actually do something about the issue. ** Bug watch added: freedesktop.org Bugzilla #27399 http://bugs.freedesktop.org/show_bug.cgi?id=27399 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665806 Title: false battery alarm with realtime app running (jackd) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632796] Re: battery applet says critical battery when 85-90% charged
Are we talking about this one: https://bugs.freedesktop.org/show_bug.cgi?id=27399 ? Is disconnection of the AC involved? ** Bug watch added: freedesktop.org Bugzilla #27399 http://bugs.freedesktop.org/show_bug.cgi?id=27399 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632796 Title: battery applet says critical battery when 85-90% charged -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
I see that the toshiba_acpi -dev patch has been intentionally dropped, see https://lists.ubuntu.com/archives/kernel-team/2010-June/02.html . Andy wrote: Quote: I therefore suggest we drop this patch and see if anyone notices. Well, I do notice. There is no way anymore to disable the backlight on this nice transflective screen -- or is there an alternative to toshset yet? Please re-integrate that patch. -- required kernel toshiba support not enabled https://bugs.launchpad.net/bugs/644898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665806] [NEW] false battery alarm with realtime app running (jackd)
Public bug reported: Binary package hint: gnome-power-manager When I have the JACK daemon running with realtime priority on this MSI Wind U100 laptop and pull out the wall power, the system tells me that the battery is low and enters hibernation. The battery is full, though. If JACK is not active, nothing happens (just the battery symbol goes gray, which is irritating, but intended, I guess). This forced hibernation is particulary annoying as JACK really does not like going to sleep; it cannot be killed by an ordinary user after resume (meaning: stop it via the button in qjackctl); pkill -9 jackd is needed. But that's another bug in the JACK audio server that one could live with, wouldn't the system -- and I suspect it's called gnome-power- manager here -- force a suspend to disk. I'll check again if it's really just an issue when JACK has realtime priority, after posting this initial report (don't wanna loose it as collateral damage). Even if it is, I suspect some nasty race condition that could occur any time, but is helped by the scheduling schism introduced by JACK. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-power-manager 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sun Oct 24 09:43:17 2010 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 ProcCmdLine: root=UUID=02bb04e6-69d6-4bd4-af6f-cf507b0a0d2d ro quiet splash ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: gnome-power-manager dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- false battery alarm with realtime app running (jackd) https://bugs.launchpad.net/bugs/665806 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665806] Re: false battery alarm with realtime app running (jackd)
-- false battery alarm with realtime app running (jackd) https://bugs.launchpad.net/bugs/665806 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665806] Re: false battery alarm with realtime app running (jackd)
OK, scrap the thing about JACK. It must have been luck before, but now I was able to get the forced hibernation without jackd running at all. The rather infurinating thing is that I get dialog that tells about the fact and offers OK and Cancel buttons... which have no effect on the action being taken. It might be nice if Cancel being pressed withing some time frame would cancel the hibernation process. I even triggered multiple hibernations in a row (unplug, plug, unplug). Causing the laptop to go to sleep again right after waking up. Anyhow: When unplugging from wall power, I get this notification blended onto the desktop about battery state ... and it tells me about 0:02 of battery runtime, 99% .. which somewhat contradicts the information when clicking on the battery applet, there I get 99%, OK, but also the much more sensible estimated runtime of 1:59 or so. Still, this seems to be a timing issue, perhaps the ACPI information doesn't change atomically, or there is just an error in the runtime calculation using an outdated value of whatnot. I suspect, that this might be worked around by waiting some seconds and then recomputing the remaining runtime -- and only triggering the emergency if the situation is confirmed. I do wonder though, if nobody else can reproduce this. Is the MSI Wind U100 BIOS just broken? I'm remined of the strange issues with the webcam and USB, or the Bluetooth/WLAN switch not working correctly by chance (gladly, it works in the Maverick install, as opposed to the live system from USB). -- false battery alarm with realtime app running (jackd) https://bugs.launchpad.net/bugs/665806 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665806] Re: false battery alarm with realtime app running (jackd)
Oh, and I see this issue as rather more serious on observing that I cannot turn off this behaviour. I can only choose between shutdown/standby/hibernate. Nothing like nothing or inform/ask user. Especially since this is not my machine ... so I have to instruct the user to only unplug the wall power when the machine is not running. -- false battery alarm with realtime app running (jackd) https://bugs.launchpad.net/bugs/665806 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556137] Re: kpackagekit fails silently when attempting to install some packages
I see the same general issue on a kubuntu 10.04.1 live system (USB drive). Tell KPackageKit to apply changes ... and wait a few seconds, and nothing got installed. Console output looks the same (ibus stuff). I can install using apt-get just fine. -- kpackagekit fails silently when attempting to install some packages https://bugs.launchpad.net/bugs/556137 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556137] Re: kpackagekit fails silently when attempting to install some packages
Hm sorry ... that ibus stuff is rather irrelevant, I suppose. All I can say is that I had similar non-behaviour of kpackagekit. Now, after doing some installs with apt-get, it suddenly worked. -- kpackagekit fails silently when attempting to install some packages https://bugs.launchpad.net/bugs/556137 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 297080] Re: mpg123 fails playing icecast streams
You might investigate the latest release of mpg123 (1.12.3), which fixes another reading issue of streams with ICY meta info. More people testing that feature would be good to ensure that the mpg123 team got it right now. -- mpg123 fails playing icecast streams https://bugs.launchpad.net/bugs/297080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589791] Re: apport tries wrong firefox version
I did updates, then rebooted into the new kernel. Then, I started firefox and browsed to the bug report in launchpad, pasted the apport-collect command into a terminal... there shouldn't be any trace of the old version by then. Default browser I did not change. -- apport tries wrong firefox version https://bugs.launchpad.net/bugs/589791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589791] [NEW] apport tries wrong firefox version
Public bug reported: Binary package hint: apport I was told to run this command for a different bug: apport-collect -p linux 561301 It tries to run firefox, but, well, not the one I got installed (3.6.3). $ LANG=C apport-collect -p linux 561301 The authorization page: (https://edge.launchpad.net/+authorize-token?oauth_token=8FlQ9bNrqqfkNrXxLv14allow_permission=WRITE_PRIVATE) should be opening in your browser. After you have authorized this program to access Launchpad on your behalf you should come back here and press Enter to finish the authentication process. Error showing url: Failed to execute child process /usr/lib/firefox-3.6.2/firefox (No such file or directory) Simple to fix, I presume. Strange nevertheless. My system is ubuntu 10.04 amd64, updated today. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- apport tries wrong firefox version https://bugs.launchpad.net/bugs/589791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Re: [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk)
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: xserver-xorg-video-ati It is tricky to determine if this issue is the same as one reported in the several bugs about freezes / black screens, so I'm making a new one... I installed a amd64 ubuntu lucid lynx beta1 system on a box with a Foxconn mainboard that features integrated radeon graphics, namely RS690. The system has all current updates as of last saturday. I notice some things, possible related to the final freeze/crash/whatever: 1. Multiple flickering on startup, sortof in intervals of about a second. This includes the plymouth splash screen and the desktop after it appeared (automatic login) for some time. Annoying but not fatal as such, as it seems to stop, generally (maybe reappears once on certain actions, like starting a video player). 2. There is only a VGA connector and there the monitor is connected. The radeon driver complains about bad EDID data for the DVI port, multiple times. Well, there is no physical DVI port. 3. After some undetermined time of usage, the screen suddenty goes black, and I am unable to reach a console. I need to have a second computer to get debugging, I guess. The machine is not frozen, but the screen is gone. This persists with a self-built 2.6.33.2-rt13 kernel (since this is supposed to be an audio workstation) in the same manner, with the linux- rt kernel it was a bit different (for example, I needed to fix the resolution in xorg.conf because with that kernel a wrong one is detected), I did not spend enough time with it to trigger that black screen ... or indeed it does not happen there. - I'll try starting with nomodeset ... then examine if there are still - options like switching back to XAA (that worked in the past for the - buggy intel drivers) ... or resort to VESA. I actually have no time to - debug Xorg issues on that box, but well... do I have a choice? With - another non-ubuntu system (older Xorg at least, kernel version about the - same), this never occured. So it might have to do with the recent enable - of KMS, or acceleration architecture updates. + I'll try starting with nomodeset ... then examine if there are still options like switching back to XAA (that worked in the past for the buggy intel drivers) ... or resort to VESA. I actually have no time to debug Xorg issues on that box, but well... do I have a choice? With another non-ubuntu system (older Xorg at least, kernel version about the same), this never occured. So it might have to do with the recent enable of KMS, or acceleration architecture updates. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/seq:musiker1797 F qjackctl.bin + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'SB'/'HDA ATI SB at 0xfe7f8000 irq 16' +Mixer name : 'Realtek ALC883' +Components : 'HDA:10ec0883,105b0c8c,0012' +Controls : 28 +Simple ctrls : 17 + DistroRelease: Ubuntu 10.04 + Frequency: I don't know. + HibernationDevice: RESUME=UUID=fe1f2b79-1cb9-4b0a-87c3-cd2aecac0d67 + InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + + ppp0 no wireless extensions. + MachineType: FOXCONN RS690M2MA + Package: linux (not installed) + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=1ffb8723-173a-4118-9350-13115ffe0b04 ro quiet splash + ProcEnviron: + PATH=(custom, user) + LANG=C + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 + Regression: Yes + RelatedPackageVersions: linux-firmware 1.34 + Reproducible: No + RfKill: + + Tags: lucid graphics regression-release needs-upstream-testing + Uname: Linux 2.6.32-22-generic x86_64 + UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare video + dmi.bios.date: 05/26/2008 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 080014 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: A690GM2MA/A690VM2MA + dmi.board.vendor: FOXCONN + dmi.board.version: 0A + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd05/26/2008:svnFOXCONN:pnRS690M2MA:pvr0A:rvnFOXCONN:rnA690GM2MA/A690VM2MA:rvr0A:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: RS690M2MA + dmi.product.version: 0A + dmi.sys.vendor: FOXCONN ** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/49673985/AlsaDevices.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk)
[Bug 561301] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/49673992/AplayDevices.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/49673995/ArecordDevices.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/49673996/BootDmesg.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/49673997/Card0.Amixer.values.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Card0.Codecs.codec.3.txt
apport information ** Attachment added: Card0.Codecs.codec.3.txt http://launchpadlibrarian.net/49674006/Card0.Codecs.codec.3.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/49674008/CurrentDmesg.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/49674009/Lspci.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Lsusb.txt
apport information ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/49674010/Lsusb.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/49674014/PciMultimedia.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/49674020/ProcCpuinfo.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/49674021/ProcInterrupts.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] ProcModules.txt
apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/49674022/ProcModules.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] UdevDb.txt
apport information ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/49674033/UdevDb.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] UdevLog.txt
apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/49674045/UdevLog.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] UserAsoundrc.txt
apport information ** Attachment added: UserAsoundrc.txt http://launchpadlibrarian.net/49674052/UserAsoundrc.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/49674064/WifiSyslog.txt -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Re: [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk)
The current ubuntu kernel still flickers around with KMS enabled... the splash screen comes very late and flickers. I didn't wait if a freeze / black screen occurs... need to work now. Maybe the apport info helps. -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Re: [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk)
To make it clear: You suggest booting the final release ISO of ubuntu (29th of april)? I don't see ISOs of a development release. I cannot promise much in the way of testing things... I am working with the machine only at certain intervals, and then it's usually more important to produce something with it. When I come around to test how a new kernel release works, I'll update the bug report -- in the end, people report that the 2.6.33 I am running now might not be the best for firewire audio. -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105586] Re: mpg123 does not support large files
Note that mpg123 supports large files since quite some time now... I just verified that it also writes a WAV file 4G. But there is still a catch: It doesn't change the WAV format it uses... so for sizes 4G, the header information will be wrong, since the WAV header only has 4 bytes for the size field. You could still have software that works around this, but it might be an idea to add support for WAV64 or another container format. In any case, you can always generate raw audio files of any size via the -s switch (possibly piping towards another program that wraps it into a container). -- mpg123 does not support large files https://bugs.launchpad.net/bugs/105586 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Re: [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk)
About my mad monitor EDID ... are you talking about the existing LCD connected to VGA or the non-existing DVI? The physical monitor shouldn't be all that bad since it works without pain using an slightly older Xorg (perhaps about a year or so) without KMS. Should really be the hardware to blame? I hope it's possible to have the KMS code fixed up to work like the old code used to work... and also without KMS, Xorg now detects a sub-optimal mode. This might be due to some well-intended improvements, probably. Oh, and a side note: The splash screen business looks rather pointless in the current setup... after the boot manager menu, there is a delay where nothing happens visually and just a cursor on the top left of a black screen is shown... disk starts clattering in the background... at some time, the ubuntu splash screen comes up, but is replaced by the actual desktop very quickly. Same for shutdown ... it takes some moments to kill the desktop... and then the machine is off after very briefly offering a glimpse on the splash screen. So, some stuff is perhaps too fast (the actual work) ... though I am not sure what the delay at the beginning is about (should re-test with stock kernel and initrd... but I think it was the same there). But then... this is off-topic, just on my mind because of the flickering also hurting the perceived smoothness of the bootup. -- [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk) https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562866] [NEW] too few buttons offered in the dropdown for wheel emulation
Public bug reported: Binary package hint: gpointing-device-settings I have a Logitech TrackMan Marble FX ... a trackball with 4 buttons. They are mapped to 1,2,3 ... and 8 by default. Button 8 is the one I usually use for wheel emulation. This works with xinput or in past times via HAL fdi file... but the GUI of gpointing-device-settings only offers up to button 7, which is a bit frustrating. Besides the question of offering a plain field for manually entering the button number instead of a possibly wrong list for selection (or fixing the list)... what about a simple feature of press the button you'd like to use and detecting the event? ** Affects: gpointing-device-settings (Ubuntu) Importance: Undecided Status: New ** Tags: lucid ** Tags added: lucid -- too few buttons offered in the dropdown for wheel emulation https://bugs.launchpad.net/bugs/562866 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561288] [NEW] linux-rt being based on 2.6.31 seems to cause breakage with lucid
Public bug reported: I noticed that the RT kernel for lucid is based off version 2.6.31, compared to 2.6.32 for the stock ubuntu kernel. It is my suspicion that this is the reason for certain things not working. Most prominent: Network manager does not work. After switching from a base install of lucid beta1 on amd64 to the linux-rt kernel, the nm-applet vanished, and when bringing it back, it did not show my 3G USB modem (or any network device, AFAIR), although the kernel recognized it and I was able to dial up using wvdial. Another issue is wrong detection of the resolution for Xorg ... I have an old 15in XGA TFT connected to VGA, the linux-rt kernel prompted Xorg to try to run with 1366x768 instead of 1024x768. I had to fix this using /etc/X11/xorg.conf (luckily, _some_ parts of this file are not ignored yet). I built an own kernel using make-kpkg, for Opteron/Athlon64 only (http://thomas.orgis.org/ubuntu/linux- image-2.6.33.2-rt13-thorubuntu_2_amd64.deb), starting with vanilla 2.6.33.2-rt13 and off the stock ubuntu kernel config. I had to disable the staging drivers, though, as not all of them build with the RT patch. Using this kernel, everything works as with the stock ubuntu kernel. It is even bug-compatible as in my integrated Radeon graphics (RS690) dying after some time, leaving me staring at a black screen. That is a rather serious showstopper issue, but no regression from the stock ubuntu kernel. ** Affects: linux-rt (Ubuntu) Importance: Undecided Status: New -- linux-rt being based on 2.6.31 seems to cause breakage with lucid https://bugs.launchpad.net/bugs/561288 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] [NEW] [RV690] flicker on startup, dead black screen after some time with lucid
Public bug reported: Binary package hint: xserver-xorg-video-ati It is tricky to determine if this issue is the same as one reported in the several bugs about freezes / black screens, so I'm making a new one... I installed a amd64 ubuntu lucid lynx beta1 system on a box with a Foxconn mainboard that features integrated radeon graphics, namely RS690. The system has all current updates as of last saturday. I notice some things, possible related to the final freeze/crash/whatever: 1. Multiple flickering on startup, sortof in intervals of about a second. This includes the plymouth splash screen and the desktop after it appeared (automatic login) for some time. Annoying but not fatal as such, as it seems to stop, generally (maybe reappears once on certain actions, like starting a video player). 2. There is only a VGA connector and there the monitor is connected. The radeon driver complains about bad EDID data for the DVI port, multiple times. Well, there is no physical DVI port. 3. After some undetermined time of usage, the screen suddenty goes black, and I am unable to reach a console. I need to have a second computer to get debugging, I guess. The machine is not frozen, but the screen is gone. This persists with a self-built 2.6.33.2-rt13 kernel (since this is supposed to be an audio workstation) in the same manner, with the linux- rt kernel it was a bit different (for example, I needed to fix the resolution in xorg.conf because with that kernel a wrong one is detected), I did not spend enough time with it to trigger that black screen ... or indeed it does not happen there. I'll try starting with nomodeset ... then examine if there are still options like switching back to XAA (that worked in the past for the buggy intel drivers) ... or resort to VESA. I actually have no time to debug Xorg issues on that box, but well... do I have a choice? With another non-ubuntu system (older Xorg at least, kernel version about the same), this never occured. So it might have to do with the recent enable of KMS, or acceleration architecture updates. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- [RV690] flicker on startup, dead black screen after some time with lucid https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Re: [RV690] flicker on startup, dead black screen after some time with lucid
** Attachment added: report data generated by apport http://launchpadlibrarian.net/43901346/reportdata -- [RV690] flicker on startup, dead black screen after some time with lucid https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561288] Re: linux-rt being based on 2.6.31 seems to cause breakage with lucid
** Tags added: lucid -- linux-rt being based on 2.6.31 seems to cause breakage with lucid https://bugs.launchpad.net/bugs/561288 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561018] Re: software center destroys system without warning
** Tags added: lucid -- software center destroys system without warning https://bugs.launchpad.net/bugs/561018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561018] Re: software center allows removal of essential and required without extra prompt
I am wondering: The main issue is that it left the system in a unreparable state (out of itself) ... so essential packages should be protected. But, is it generally desired behaviour to silently delete dependent packages? Would a message with This would remove these apps, you really want it? not be a good idea, generally? But then, I might miss the supposed difference the Software Center should have compared to synaptic. -- software center allows removal of essential and required without extra prompt https://bugs.launchpad.net/bugs/561018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561301] Re: [RV690] flicker on startup, dead black screen after some time with lucid
nomodeset kernel option does nothing (at least on my kernel build), but radeon.modeset=0 does help. Worked an evening on the box with disabled modesetting now and didn't see a freeze/crash. Only the mode detection is suboptimal... I have seen that in comparison to another Linux system I have on that box.. the image looked more crisp, less smearing on the LCD (that also covers the mode set using kernel modesetting). After manually fixing ip some tuned mode with slightly increased refresh rate (not 59.9 but rather 61 Hz or so) this is improved. Main message: DIsabling kernel modesetting for RS690 _seems_ to be a good idea so far. -- [RV690] flicker on startup, dead black screen after some time with lucid https://bugs.launchpad.net/bugs/561301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561288] Re: linux-rt being based on 2.6.31 seems to cause breakage with lucid
OK, I have to revert the message about network manager... Today it also failed on me with the 2.6.33-based kernel. I found out that it's not a fault of nm-applet (it is irritating that it just does not show up when there is trouble) ... but rather sometimes the network manager daemon seems to be ill. On some boots it is not properly present. service network-manager restart usually helps to bring the nm-applet icon back and also restores functionality. It is generally frustrating that the system is not very verbose about whatever bothers it... nm-applet should draw an icon and tell me Network Manager is there but does not talk to me. When started from terminal, it prints something about missing dbus service... Shall I make a separate bug report on that? Or should this one here get tagged for network-manager? Concerning the linux-rt kernel, at least the point about default graphics being messed up still applies. But the network-manager thing is apparently not specific to the kernel version. -- linux-rt being based on 2.6.31 seems to cause breakage with lucid https://bugs.launchpad.net/bugs/561288 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561018] [NEW] software center destroys system without warning
Public bug reported: Binary package hint: software-center This is an excerpt out of https://lists.ubuntu.com/archives/ubuntu- studio-users/2010-April/006109.html (trying to get ubuntu (plus studio packages) lucid running)... so sorry for the prose, I had a hard night then. The information bits in it should still be important: quote Now... the crashing plymouth kept nagging me (would a system update really fix this now? -- I need to see if my next visit at the box is long enough for the downloads). It's main function seems to be nagging (and irritate newbies), so I decided to rip plymouth out. Due to a dangerous fling, I clicked on the Software Center menu entry. Searched for plymouth ... removed the daemon... seen that there still is a package for plymouth shared libs... wondered how much stuff might depend on it... figured that one will get warnings about removing dependent stuff (like synaptic does it)... deleted it. B-O-O-M! X11 is killed ... I manage to activate a plain console ... and see that I unwittingly entered a major system fubar. Tried to restart gdm ... there is no gdm ... tried to look after the binary... there is no /bin/ls! Wow. There even is no halt, reboot or shutdown. This system is really ripped apart for good. This is something one really would like to avoid happening to new users, old users ... anyone. This Software Center thingie is supposed to be the bubbly-touchy-feely admin interface for Linux newbies / notcarealots, right? I consider it a serious bug that it hoses the whole install beyond repair for any average ubuntu user (well, except for reinstall). Is this something known? Shall I make a flaming report on launchpad? /quote? I don't think the system information is very important here (I'm on a different box now and on the box I have a new install of ubuntu). It should be easily reproducible by installing ubuntu lucid beta1 from the CD image on amd64 and trying to remove plymouth shared libs in software center. It should try to stop me at least once before accidentally hosing the whole system. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New -- software center destroys system without warning https://bugs.launchpad.net/bugs/561018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278176] Re: disk detection is real slow with some hardware (timout shell drops)
Just want to chime in to confirm what has been said so far. I experienced this some ubuntu releases ago (8.04, perhaps) with my Adaptec 39160. Fails to find root, big rootdelay helps. I initially blamed this on ubuntu because my self-built kernels did not feature this. I always built the scsi driver into the kernel and also used root=/dev/sda2 instead of root=UUID=... . Just recently I observed that the issue vanishes when replacing the dual-channel 39160 with a single-channel 29160 (I only used on channel anyway). So, is there some confusion with the initial scanning of two SCSI channels? Perhaps the kernel reports that it's done only after one channel? But then, it apparently works when the driver is built into the kernel. -- disk detection is real slow with some hardware (timout shell drops) https://bugs.launchpad.net/bugs/278176 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456132] Re: mpg123: breaks 32-bit wine compile on x86_64
How current is this bug now? There have been new mpg123 versions to handle the build issues. -- mpg123: breaks 32-bit wine compile on x86_64 https://bugs.launchpad.net/bugs/456132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
