Changed Status from to "VERIFIED - WONTFIX" to "RESOLVED - FIXED" after
Leland applied a patch to Menus.cpp in r12639 that fixes this.
Leland wrote:
> This should be removed with wxWidgets 2.8.13 is released.
Does the Widgets fix
http://trac.wxwidgets.org/changeset/67929?format=diff&new=67929 al
(In reply to comment #9)
Sorry not had much time to test this but will do so. One problem found - Winamp
can't see the TYER frame if TDRC is written as well. I've reported it to Winamp
here:
http://forums.winamp.com/showthread.php?t=36
I'd tend to call this a limitation in Winamp, and doubt
(In reply to comment #10)
RESOLVED - FIXED despite id3 on Ubuntu now can't see the Audacity Year tag when
it could before the committed fix.
Tested exported MP3 and MP2 containing Year tag (TYER and TDRC) on all
three platforms (including WMP, VLC, Foobar and iTunes on Windows,
iTunes on Mac and
Command-line export "(external program)" is also affected. I tested
exporting 16-bit silence to Apple Lossless and WMA Lossless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608964
Title:
Select-al
I tested opening further files as below which I think may not have been
(fully) tested. I used HEAD "0ceae62".
Windows 10:
* "Open with" set up to open 2.0.6 when HEAD was already running (HEAD took the
file, correctly)
* "Open with" set up to open HEAD when HEAD was already running
* "Send to"
Public bug reported:
Observed in Audacity r13166 in Ubuntu 14.04 using Unity with Ambience or
Radiance theme. Only the shortcuts for Edit > Undo and Redo are visible
in the menus. I do not experience inactive menus mentioned in
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1312625 .
Ini
(In reply to Paul L from comment #14)
> Perhaps, then, this bug should be left open but with less priority until
> further performance improvements can be found?
Is it this bug or a more general one that typing in a label is too CPU
expensive?
On the 1 GHz machine typing a character into one of
Thanks, Paul. RESOLVED-FIXED but see my comment at the end about CPU use
in case it is important.
Yes with 3000 labels on Win 7 64-bit (2.4 GHz) I see the difference
between 2.1.2 release and HEAD when Karaoke is open.
Tested on Ubuntu 14.04 32-bit (Atom 1 GHz processor) with 1500 labels.
In 2.1.
(In reply to comment #5)
> What FFmpeg libraries do you have installed and where?
2.2.2 installed in /usr/local/lib.
> Can you run these commands to shed some light on it?
> find /usr/ -name avcodec.h
/usr/include/libavcodec/avcodec.h
/usr/local/include/libavfilter/avcodec.h
/usr/local/include/l
(In reply to Benjamin Drung from comment #7)
Don't know at the moment, Benjamin, I am on Ubuntu 14.04 now on the 32-bit
machine, and I don't have a problem with compiling Audacity against self-built
FFmpeg 2.2.2 installed into /usr/local and using dynamic loading (i.e. default
Audacity ./configu
This appears to have been fixed by Audacity moving to wx3, which it will
support from Audacity 2.1.2 onwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007737
Title:
cursor volume tooltip is un
This appears to have been fixed by Audacity moving to wx3. I do not see
the issue now in HEAD on Ubuntu 14.04 in either "Unity" or "Gnome
Flashback".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10077
(In reply to comment #5)
Gale wrote:
> Multiple files are still a problem. With the patch, multiple files can be now
> be imported with all the above methods if Audacity is not running. But if
> Audacity is already running, only one of the multiple files will import (no
> error ap
(In reply to comment #13)
Leland's modified patch committed at r13692.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615307
Title:
opening a file from file manager when audacity is open gives error
> I tested the patch on Ubuntu 14.04, but the running audacity process crashes
> when a second audacity process is launched
Hi Benjamin,
I can't reproduce that on Ubuntu 14.04 in a release build of Audacity.
Did you patch a debug build? What are the exact steps by which you
opened a second process
(In reply to comment #13)
Leland wrote:
> It definitely wouldn't hurt to validate both Linux AND Windows since they
> now share the same code.
On Win 7 (audacity.cfg and plugin*.cfg files deleted before launching HEAD),
using Explorer "Open with" to open an AUP file or to import an associated file
(In reply to comment #6)
Benjamin wrote:
> The patch looks good to me with just one minor change: The socket file
> shouldn't be placed in "/tmp/audacity.sock", but in "/var/run/audacity.sock"
> instead.
Can you explain more? Is it to preserve the file between reboots?
Will every Linux distro hav
HEAD),
>> using Explorer "Open with" to open an AUP file or to import an associated
>> file
>> type displays a Windows dialogue "Audacity... has stopped working".
>>
> I can't make this happen Gale. Can you try again?
It's still 10
(In reply to comment #11)
As there has been no response from Benjamin about how to reproduce the crash
and given using "/tmp/audacity.sock" appears to be the most practical solution,
I suggest we apply this patch as is so we can get more testing on it.
Moved back to patch_ready.
--
You receive
A workaround has been committed at
https://code.google.com/p/audacity/source/detail?r=13894 so that
src/audacity.desktop.in is set to UBUNTU_MENUPROXY=0. Audacity compiled
from source will thus show shortcuts in the menus and will have its own
menu bar in the application. It will remain up to Ubunt
Fixes have recently been committed to support libav 0.8 to 0.10 and FFmpeg 1.2
to 2.2. There are still known issues, see Steps to Reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076928
Title
I just tried now with Audacity HEAD built with system libsbsms 2.0.1-1
on Ubuntu 14.04, and there is no crash.
However I could not reproduce the bug in Audacity HEAD built with system
libsbsms 2.0.1-1 on Ubuntu 13.10, until I installed the 2.0.3 package
of Audacity. The 2.0.3 package crashed eve
(In reply to comment #3)
Gale wrote:
> --disable-dynamic-loading still fails to compile on Ubuntu 13.10 against
> self-compiled FFmpeg 2.2.2 (even on fresh Audacity checkout).
That is, it fails with --disable-dynamic-loading the only argument, so using
FFMPEG="system".
Created an attachment (id=497)
Tobias Platen's patch to allow passing subsequent files to Audacity on Linux
Tested on Win and Mac that patch builds and does not affect current
functionality.
Tested on Ubuntu 13.10 dragging audio files to Audacity icon, using file
manager Open (with association se
Created an attachment (id=492)
make log Ubuntu 13.10 with --disable-dynamic-loading
(In reply to comment #2)
@Benjamin, Audacity compiles for me at r13196 against self-compiled FFmpeg
2.2.2 on Ubuntu 14.04 with --disable-dynamic-loading. --disable-dynamic-loading
still fails to compile on Ubuntu 1
Is this an Audacity or an Ubuntu bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325110
Title:
Audacity HEAD shows almost no shortcuts in menus using Unity
To manage notifications about this bu
Is this an Audacity or an Ubuntu bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325110
Title:
Audacity HEAD shows almost no shortcuts in menus using Unity
To manage notifications about this bu
Public bug reported:
Steps to reproduce crash in Audacity built from system sbsms
1 Download Lola.mp3 from
https://drive.google.com/file/d/0B7u-ChIr3ATUeXh4Ql9BQ2pMNEtSNGlUS3pUTkExY3JPb0VB/edit?usp=sharing
.
2 Import Lola.mp3 into Audacity and apply Sliding Time Scale to the whole
track at se
IMPORTANCE changed to P5, Repeatable.
Confirmed on Windows 7 but the file is corrupt.
oggdec.exe crashes trying to play it, hence probably why the import
aborts.
oggenc.exe reports:
New logical stream (#1, serial: 3d051edb): type vorbis
S
Vorbis headers parsed for stream 1, information follows.
(In reply to comment #2)
Rated as P3 and added release note. Please adjust the note if inaccurate.
Added comments from the launchpad report...
Comment from David Henningsson on
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/687689 comment 8 on
2011-03-21:
> Christal wrote on 2011-03-20
Bug 74 suggests we should incorporate these values in the hover tooltips
instead, so you don't have to click-to-see.
A workaround for now is to double-click the slider to open the fine adjustment
dialogue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Rated as P5 at the moment (about half a dozen requests noted so far). There is
only limited player support on Windows (Firefox - output level cannot be
controlled except for mute - and Foobar2000). If we're going to add support we
should do it for all three platforms, I think.
Export support alr
(In reply to comment #1)
VLC actually supports Opus now, but their features page does not say so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064030
Title:
Need to add Opus Support to Audacity
T
Changed title to "Exporting from integer internal formats to files in same
format or higher adds unwanted dither noise". Just about every format is
affected (including FFmpeg formats) except OGG.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
(In reply to comment #9)
> 1) Import a 24 bit file into Audacity with the default settings (creates a
> 32-bit float track).
> 2) Export the track as a 24 bit WAV file.
> The audio in the exported file is identical to the original.
So we are downsampling, but *not* dithering?
--
You received this
You can work round it if your build of Audacity supports FFmpeg.
1 open the Extended Import Preferences
2 create a rule for *.OGV
3 drag "FFmpeg-compatible files" to the top of the list
4 uncheck "Attempt to use filter in OpenFile dialog first"
5 click OK.
Audio from the OGV files should now be i
On Ubuntu 10.10 using Ubuntu-distributed FFmpeg, this seems to be fixed by
applying the patch in bug 176 comment 10 which includes the patch attached
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Thanks, Leland. Changed Status to "DEVEL-FIXED MADE".
Note we have a general Linux bug 264 that Benjamin started "Some apps do not
see exported MP3 metadata". Should we apply the idea of this fix to all our
named tags to address that? Could that ever fix all cases e.g where user writes
a custom ta
Also see bug 313 comment 1. Import of any formats (even non-FFmpeg) is
generally flaky after applying the patch in comment 10 here. WMA imports will
always
segfault, but so will WAV, MP3 and FLAC imports (most, but not all of the
time). I have to suspect this patch in comment 10, because:
* If I u
(In reply to comment #14)
> I tested the patch from comment 10 with the system FFmpeg and it works on my
> system.
> Exporting and importing ac3, flac, ogg, wav, wma worked.
> System: Ubuntu 11.04 (natty) development version
> Audacity: trunk configured to use all system libraries
Hmm. Is this the
(In reply to comment #17)
> did you happen to a "make dep" in the "src" directory before/after applying?
>(would be a good idea to do it.)
As per comment 15 I applied the patch then did make clean, then ./configure;
make dep; make. Did not do "make dep" before the patch (except that I did it
befo
(In reply to comment #19)
> builds ok with system FFMpeg on Ubuntu 10.10
> (c)an import WAV, MP3 and FLAC with FFmpeg, but importing WMA segfaults.
Have you tried the patch in bug 317 for FFmpeg import crashes? That needs to be
applied on top of the patch attached here.
--
You received this bug n
Leland wrote:
> Should I regenerate the above patch with the fix from bug #317?
Yes, I think that would make it easier for others to test.
> What are the outstanding issues?
All FFmpeg bugs "should" have the "FFmpeg" keyword:
http://bugzilla.audacityteam.org/buglist.cgi?keywords=FFmpeg&resolutio
OK on fresh checkout and make dep before and after applying attached patch then
make dep before and after bug 317 patch, on Ubuntu 10.10 with the Ubuntu
FFmpeg...
* I seem to get consistently safe exports of AC3, WMA and AAC. However AAC
export is far too slow.
* I seem to get consistently safe
(In reply to comment #26)
> Created an attachment (id=125) [details]
> Just a combination of 0.6.1 support and the import crash fix
Actually this patch lacks the three new files in lib-src\ffmpeg\libavutil
attributes.h
avconfig.h
error.h
which you will need to grab from the original patch:
htt
(In reply to comment #26)
> I have been unable to pin down why M4A imports are silenced. Actually, I no
> longer see this, so if y'all can attach a file to this bug that consistently
> imports as silence that'd be great.
For me, the same file will sometimes import as silence and sometimes not. The
(In reply to comment #36)
> if everyone is also satisfied, I'd like to go ahead and commit it and move
> on to the detection simplification.
If you're OK I'd still like to try with SVN FFmpeg, since that gave endless
trouble before. I assume you have done this, but since I'm inexperienced there
is
(In reply to comment #31)
>> I think you will be able to repro it on Windows (and I assume on FFmpeg 0.6.1
>> too, but I have not tried with 0.6.1 yet). What happens on Mac?
>
> Same sort of thing. If I create a mono M4A file using 0.6.1 and then try to
> import it using a v0.5 library, it will
(In reply to comment #39)
> use libfaac for encoding (Windows and OSX) and use the native FFmpeg aac
> decoder instead of libfaad
OK, I think we could get away with that on Windows and OS X without a release
note if there are no technical issues with it. I assume you have
libfaac-encoded a native-
(In reply to comment #33)
> 1) No extreme time differences between m4a and other ffmpeg formats.
> 2) The native exporter is faster than faac
> 3) Faac exported files sound better
> 4) Any file imported with faad gets imported as stereo
> This was all done on the Mac...
Thanks for your tests,
Only tested so far on Ubuntu 10.10. Ubuntu-distributed FFmpeg is listed on
opening Prefs on initialised or non-existent .cfg.
Should be tested with self-compiled FFmpeg.
Side issue for discussion: although FFmpeg version number is listed in Prefs,
when you click "Locate...", then "Yes" in "Succe
See bug 141 comment 3 - undefined symbol match_ext in HEAD after running 1.3.12
Ubuntu package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602934
Title:
ffmpeg import/export not working with ffmp
Is the new FFmpeg support in these patches backwards-compatible beyond 0.5? So
if someone on Win went from 1.3.6 Beta to 1.3.13 Beta, they would not need to
update their FFmpeg? I don't think it matters if not, just asking.
--
You received this bug notification because you are a member of Ubuntu
Leland
Applied v11 on Windows and Ubuntu (uninstalled FFmoeg HEAD so back to Ubuntu
FFmpeg).
Only minor WMA problem left is visibility of exported metadata to other apps -
see http://bugzilla.audacityteam.org/show_bug.cgi?id=134#c5 .
32-bit WAV files come in OK via FFmpeg as 32-bit on Win and
> What I want to do now to complete testing is to generate AMR/AC3/M4A/WMA files
> outside Audacity and try those on Audacity on Win and Ubuntu.
This did not provide any problems in terms of correct audio being imported.
All the residual issues from this AFAICT are now at bug 317, bug 338, bug 339
(In reply to comment #80)
>> AAC export on Ubuntu (native encoder using "M4A files") is still wrong -
>> seems to be a silent file - "playable" but very small file size.
> I'm pretty sure the small file size is expected, but the silent file is not.
> Can you send me one of those via email?
I hav
(In reply to comment #84)
> Is this supposed to wait until after 1.3.13 is released? Or should it get
> committed now?
I would agree to committing it because I think it would reduce the number of
Linux complaints about FFmpeg, and it's been pretty well tested on my systems.
But you need someone el
Tried v12 on win 7 x64 so far. Main finding so far is that exported bit rates
are not correct. Exporting a stereo music track, both with FFmpeg 0.5 and 0.6
and according to Medianfo and iTunes,
24 kbps exports as 60 kbps
96 and 256 kbps both export as 150 kbps (the exported files are the same
si
(In reply to comment #93)
> I totally agree that the Quality method should be used. But, I think LRN had
> it right when he used a slider. We wouldn't be able to provide an accurate
> value if we tried to assign a bitrate to a specific quality value.
Of the three apps I know about, SUPER (using F
The only point about backwards-compatibility as I see it is to save people
coming from 1.3.6 and 1.3.7 (which had our earliest version of FFmpeg) having
to get the latest FFmpeg when they upgrade Audacity. Even without this patch
those 1.3.6/1.3.7 users would have to upgrade to the current FFmpeg a
(In reply to comment #97)
> I'm going to go ahead and commit the version 11
Agreed. M4A quality slider issue is now at bug 344.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602934
Title:
ffmpeg imp
Leland committed as r11055 so Status changed to DEVEL - FIX MADE, though I have
tested as much as I can. Would Bill like to test this on Mac?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602934
Title
Are we providing FFmpeg 0.6 binaries for Win/Mac for 1.3.13 Beta?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602934
Title:
ffmpeg import/export not working with ffmpeg version in maverick
--
ub
(From update of attachment 147)
this version was committed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602934
Title:
ffmpeg import/export not working with ffmpeg version in maverick
--
ubuntu-b
> Gale's comment #8 seems it does fix the crash
Yes it still works in HEAD, so changed to RESOLVED-FIXED.
The hang/crash if you exceed libsamplerate's limits is now at bug 333.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
(In reply to comment #42)
Thanks for your further patch. Likely to take a little while before I get round
to it.
> How important is HEAD support?
I would say most who are interested in compiling and not just using the distro
package of Audacity will "head straight for HEAD". They see no need fo
(In reply to comment #46)
Thanks for confirming the import crashing has gone, Steve.
> AMR narrowband appear to be exported correctly, but when imported the file is
> double the original length and at half the original frequency.
I was wondering, how do you get AMR NB support with Ubuntu's FFmpeg?
(In reply to comment #48)
> newer FFmpegs include a native amr decoder and the default sample format for
> them is float whereas the default for the opencore amr decoder it 16-bit.
Thanks for the new patch. Yes I recall now about FFmpeg only supporting 16-bit
input. But you mean the native "encod
I ran into
ImportFFmpeg.cpp
..\..\..\src\import\ImportFFmpeg.cpp(874) : error C3861: 'lrintf': identifier
not found
..\..\..\src\import\ImportFFmpeg.cpp(878) : error C3861: 'lrint': identifier
not found
on Windows Unicode Release.
--
You received this bug notification because you are a member o
(In reply to comment #53)
> Actually, there isn't a native AMR encoder, just a native decoder. And that
> decoder returns to Audacity as floats. I "think" AMR files are always 8-bit
> 8000Hz, but I could be entirely wrong about that.
Sorry but I got confused by discussion of two decoders. So the
at FFmpeg.h:529)
make[1]: *** [FFmpeg.o] Error 1
make[1]: Leaving directory `/home/gale/audacityc/src'
I won't be trying v7 for a while so if you are around please let me know what
you think about the above error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Thanks Leland, I built Audacity against your v8 patch and am using
FFmpeg HEAD.
WMA and AMR NB export and import OK (at least Audacity's own files).
AC3 import OK. AC3 export gives a zero byte file but the same happens with
standalone ffmpeg at the command line "LIBAVUTIL_50 not defined in file
l
(In reply to comment #69)
Thanks Leland. Will try v10. For those who try the patches one after the other,
is there an easier way to apply the patch than manually deleting then restoring
the affected files before patch? E.g. could I actually apply your v10 patch
over an earlier patch version?
--
Y
Thanks for the tips, Benjamin.
Leland, I applied v10 and I exported all four FFmpeg formats using FFmpeg HEAD
and all three available formats (amr is not available) uing the Ubuntu FFmpeg.
I imported the seven files using both versions of FFmpeg.
My only issue was with the stereo m4a I exported
(In reply to comment #102)
> This might be something that the devel subscribers would like to discuss.
> Personally, I say go for it...
It's expected FFmpeg 0.6.2 will be released for Win/Mac users when 1.3.13 is
released. A cursory test of 0.6.2 on Win XP suggests 0.6.2 is OK.
This is RESOLV
Fixed by patch for bug 176.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695648
Title:
audacity crashed with SIGSEGV in memcpy() on WMA export
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
I can confirm this behaviour on a T60 and can without a doubt say it's
due to the iwl3945 driver. Bug 275227 is similar. The workaround for me
as been to blacklist iwl3945 for a successful boot then modprobe it.
--
(some) thinkpads hard hang at boot
https://bugs.launchpad.net/bugs/263330
You rece
I can confirm this behaviour on a T60 and can without a doubt say it's
due to the iwl3945 driver. Bug 275227 is similar. The workaround for me
as been to blacklist iwl3945 for a successful boot then modprobe it.
--
Slow to recover from suspend
https://bugs.launchpad.net/bugs/218700
You received t
Whoops, wrong thread. Apologies.
--
Slow to recover from suspend
https://bugs.launchpad.net/bugs/218700
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/ma
Confirmed here too except I'm running Intrepid.
--
In hardy, sshfs /etc/mtab and /etc/fstab do not match, umount and unmount
through "Disk Mounter" applet do not work
https://bugs.launchpad.net/bugs/243298
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Thanks Sebastian, I didn't think to look over there. I can't believe the
discussion has been dragging on for over 2 months now.
--
Nautilus not preserving timestamps
https://bugs.launchpad.net/bugs/215499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
Timestamps are not preserved when copying files/directories via
Nautilus. Reproducible by mounting an ext3 partition and copying to
local home directory. This behavior worked as expected in 7.10 by
preserving timestamps, whether cross-partition or the same partition.
** Affec
Oops, this is 8.04 beta up-to-date as of April 10
--
Nautilus not preserving timestamps
https://bugs.launchpad.net/bugs/215499
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
http
Public bug reported:
Using Hardy 64 beta alternate install CD on Asus P5E WS Pro with Intel
Q6600.
DVD drives are connected via IDE but these are controlled by Marvell 88SE6145
SATA/PATA controller. CD boots OK but when starting the install the DVD drive
is not recognised. Am prompted to instal
Brian
Unless I have completely lost the plot this is impossible to do any of
this as this is during install.
This is happening when booting Hardy x64 beta CDROM to carry out an
install on the hardware already detailed in the bug report.
--
[Install] Marvell 88SE6145 PATA - CDROM not recognised
Public bug reported:
Binary package hint: diveintopython
Upgrade failed from 6.10 + automatix to herd 5: online update disabled
as needed to replace repositories. Fixed with online update while
filling bug report.
ProblemType: Package
Date: Thu Mar 8 20:22:24 2007
ErrorMessage:
ErrorMessage: p
Public bug reported:
manual sudo apt-get install sofa apps.
Failed. Karmic 9.10 as upgrade so using old grub and I have nvidia
installed
ProblemType: Package
Architecture: amd64
Date: Mon Nov 9 13:19:03 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: trying to overwrite '/usr/share/applications/s
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/35390526/AptOrdering.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/35390527/Dmesg.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/35390528/DpkgTerminalLog.gz
--
packag
Mine is a desktop, and no suspend occurs, ever. Are you (Kai-Heng Feng)
asking me to suspend it and wake it up and see if it goes away?
On Mon, Sep 24, 2018 at 10:45 AM Kai-Heng Feng
wrote:
> Do you see this after S3?
>
> --
> You received this bug notification because you are subscribed to the
It is not HDMI specific. I have a similar problem: every start up,
output is selected on (usb) headphones, but actual audio comes out my
motherboard line out. Volume control adjusts headphones, so apparently
has no effect. I have to go change it to line out, then the volume
control works.
Should I
I'm not sure if this is actually the same bug, but I fixed an issue with
the same symptoms, documenting here for the sake of those who come after
me:
The NetworkManager tool asks you to input a subnet mask in "dotted-quad"
format, however, if you look at the config file created for the
connection
Still happens on 237-3ubuntu10.31
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813400
Title:
systemctl doesn't respect --dry-run
To manage notifications about this bug go to:
https://bugs.launchp
#26 solution is the only one that worked for me.
NUC7i7BNH on Juno (Ubuntu 18.04.2 LTS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304067
Title:
Mouse cursor changes size in some GTK2 applicati
I have an APC UPS too. Great find. Who would have guessed an IRQ handling
problem message from the kernel was due to a serial or USB device. Wow.
On Thu, Apr 18, 2019 at 7:16 AM Kai-Heng Feng
wrote:
> Thanks for the info. Have anyone filed a bug against upstream apcupsd?
>
> --
> You received th
Exactly. It never happened in ubuntu 17.10. Started happening after
installing ubuntu 18.04. Can't say I know exactly what kernel version
17.10 was up to, sorry. It was the standard one, whatever dist-upgrade
would have gave me.
I'll try the kernel version you proposed and update this bug after I
Still happening:
doug@doug-dt:~$ uname -a
Linux doug-dt 4.18.0-041800rc5-generic #201807152130 SMP Sun Jul 15 21:32:10
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
doug@doug-dt:~$ dmesg | tail
[ 169.701341] usb 1-4: Warning! Unlikely big volume range (=4096), cval->res
is probably wrong.
[ 169.7013
Public bug reported:
Every few seconds I get something like this in my dmesg:
[44984.933221] do_IRQ: 1.34 No irq handler for vector
[44986.933976] do_IRQ: 1.34 No irq handler for vector
[44991.935614] do_IRQ: 1.34 No irq handler for vector
[45004.938590] do_IRQ: 1.34 No irq handler for vector
[45
*** This bug is a duplicate of bug 1551886 ***
https://bugs.launchpad.net/bugs/1551886
The automated link to bug 1551886 does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564997
Title
The updated clock settings have already been published upstream, at
http://www.iana.org/time-zones. Version 2013d of the time zone database,
released 2013-07-05, contains this update. That version has already been
incorporated in Debian unstable and testing.
It is urgent to propagate that version
@Tomer Cohen: You seem to be using Raring, which at this moment is on
version 2013b of the time zone database. That is why you will only be
hit on October 6. All other supported Ubuntu releases are on earlier
versions, so all those users were already hit today by this bug. (I am
using Quantal, so I
1 - 100 of 138 matches
Mail list logo
