[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I'm experiencing the same problem on a fresh install of Ubuntu Mate 20.04 on a Dell XPS 13 9350. Sound works correctly using the internal speakers. If you plug in analog headphones to the 3.5mm jack, there is no sound from the headphones or the internal speakers. All relevant options are unmuted in Sound Settings. The Speaker Test exhibits the same behaviour. Analog headphones worked correctly on this system under 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493083] [NEW] [regression] kmail in Lucid takes extremely long time to show window when restoring from system tray icon
Public bug reported: Binary package hint: kdepim kmail in Ubuntu 9.10 worked for me fine. Typically, I have kmail in the system tray icon which, when clicked, displayed the application full- screen in ~1 second. Since the upgrade to Lucid, kmail now takes (on average) 29 seconds to display the window after clicking the system tray icon. During this time, nothing is printed on the console (if I launch kmail from a console) and kmail doesn't seem to take much (if any) CPU time and the system isn't otherwise under heavy load (both cores of my CPU stay on 1 GHz out of 2.7 GHz). Confusingly, when kmail is first launched from the Applications menu, the window takes only a second or two to appear. ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New ** Tags: lucid regression -- [regression] kmail in Lucid takes extremely long time to show window when restoring from system tray icon https://bugs.launchpad.net/bugs/493083 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 493083] Re: [regression] kmail in Lucid takes extremely long time to show window when restoring from system tray icon
Additional info: using kmail 4.3.3-0ubuntu3 and kernel 2.6.32-6-generic #8-Ubuntu SMP on Ubuntu 10.04 (Lucid). -- [regression] kmail in Lucid takes extremely long time to show window when restoring from system tray icon https://bugs.launchpad.net/bugs/493083 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 398113] [NEW] Gnumeric Doesn't Display Any Data
Public bug reported: Binary package hint: gnumeric On loading gnumeric 1.9.9 on up-to-date Karmic 64-bit, no row numbers appear in the leftmost column but column letters appear in the topmost row. The body of the spreadsheet appears completely blank. If information is typed into any cell, the information is not displayed in the main spreadsheet view but can only be seen in the formula bar at the top. Similarly, when loading an existing spreadsheet, nothing appears in the main spreadsheet view. Cell contents may only be seen in the formula bar when the cell is selected. ** Affects: gnumeric (Ubuntu) Importance: Undecided Status: New -- Gnumeric Doesn't Display Any Data https://bugs.launchpad.net/bugs/398113 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 387896] [NEW] Inkscape crashes immediately on launching
Public bug reported: Binary package hint: inkscape Using up-to-date Kubuntu Karmic 64-bit with Inkscape 0.46-9ubuntu1, Inkscape crashes immediately on opening. If it's launched from the KDE menu, a message box appears: inkscape encountered an internal error and will now close If I launch inkscape from the command line, the following is printed to the terminal: -- Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Segmentation fault -- I don't see a dbg package in the repositories so I don't have any debug symbols, but here is a stack trace from gdb: -- gdb inkscape GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu... (no debugging symbols found) (gdb) run Starting program: /usr/bin/inkscape [Thread debugging using libthread_db enabled] [New Thread 0x7f27065637a0 (LWP 10253)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f27065637a0 (LWP 10253)] 0x007ac329 in ?? () (gdb) bt #0 0x007ac329 in ?? () #1 0x0075bde0 in ?? () #2 0x006e1849 in ?? () #3 0x006e32d5 in ?? () #4 0x7f2702666f77 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 #5 0x7f270264ad6c in ?? () from /usr/lib/libgobject-2.0.so.0 #6 0x7f270264b776 in g_object_newv () from /usr/lib/libgobject-2.0.so.0 #7 0x7f270264c2f5 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 #8 0x7f270264c44c in g_object_new () from /usr/lib/libgobject-2.0.so.0 #9 0x006e134a in ?? () #10 0x00457894 in ?? () #11 0x00457b96 in ?? () #12 0x0044f1bd in ?? () #13 0x0044f591 in ?? () #14 0x7f26fec015e6 in __libc_start_main (main=0x44f220 _zn4glib7ustring6appendep...@plt+2552, argc=1, ubp_av=0x7fffa9000928, init=0x977740, fini=value optimized out, rtld_fini=value optimized out, stack_end=0x7fffa9000918) at libc-start.c:220 #15 0x0044e869 in ?? () #16 0x7fffa9000918 in ?? () #17 0x001c in ?? () #18 0x0001 in ?? () #19 0x7fffa9002572 in ?? () #20 0x in ?? () -- ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New -- Inkscape crashes immediately on launching https://bugs.launchpad.net/bugs/387896 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 380219] Re: Regression: Samba Read/Write Causes System Freeze
Thierry, I can reproduce this systematically using kernel 2.6.30-6-generic . However, this issue appears to be fixed in the kernel 2.6.30-7-generic which was released this morning. Best Regards, David ** Changed in: samba (Ubuntu) Status: Incomplete = Fix Released -- Regression: Samba Read/Write Causes System Freeze https://bugs.launchpad.net/bugs/380219 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 380219] Re: Regression: Samba Read/Write Causes System Freeze
Thierry, I can reproduce this systematically using kernel 2.6.30-6-generic . However, this issue appears to be fixed in the kernel 2.6.30-7-generic which was released this morning. Best Regards, David ** Changed in: samba (Ubuntu) Status: Incomplete = Fix Released -- Regression: Samba Read/Write Causes System Freeze https://bugs.launchpad.net/bugs/380219 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 380219] [NEW] Regression: Samba Read/Write Causes System Freeze
Public bug reported: Binary package hint: smbfs Either reading or writing to a samba share mounted with cifs or smbfs on Karmic causes the system to freeze. I have had significant issues reading writing mounted samba shares for a week or so, and have now produced a minimal test case which demonstrates the issue: Given a 0-byte text file and a Samba share mounted as /media/Media2 : If I run the command... cp /media/Media2/temp.txt ~ ...the process is killed immediately. If I run the command a second time, the process hangs and cp takes up 100% of the CPU and cannot be killed. If I run the command a third time, the system freezes, I can't move the mouse pointer, can't switch Num Lock on or off and can't switch to a virtual terminal. The same behaviour also occurs when writing to a samba share. The same samba share can be accessed fine from a Windows PC and from Xbox Media Center running on an Xbox. My system is an up-to-date Karmic x86_64 with smbfs 2:3.3.4-2ubuntu1 with the samba share mounted automatically using the following line in /etc/fstab: //192.168.0.1/Media2 /media/Media2 cifs username=xxx,password=xxx,iocharset=utf8 0 0 This configuration worked fine with the released Jaunty and earlier versions of Karmic. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: regression -- Regression: Samba Read/Write Causes System Freeze https://bugs.launchpad.net/bugs/380219 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 380219] [NEW] Regression: Samba Read/Write Causes System Freeze
Public bug reported: Binary package hint: smbfs Either reading or writing to a samba share mounted with cifs or smbfs on Karmic causes the system to freeze. I have had significant issues reading writing mounted samba shares for a week or so, and have now produced a minimal test case which demonstrates the issue: Given a 0-byte text file and a Samba share mounted as /media/Media2 : If I run the command... cp /media/Media2/temp.txt ~ ...the process is killed immediately. If I run the command a second time, the process hangs and cp takes up 100% of the CPU and cannot be killed. If I run the command a third time, the system freezes, I can't move the mouse pointer, can't switch Num Lock on or off and can't switch to a virtual terminal. The same behaviour also occurs when writing to a samba share. The same samba share can be accessed fine from a Windows PC and from Xbox Media Center running on an Xbox. My system is an up-to-date Karmic x86_64 with smbfs 2:3.3.4-2ubuntu1 with the samba share mounted automatically using the following line in /etc/fstab: //192.168.0.1/Media2 /media/Media2 cifs username=xxx,password=xxx,iocharset=utf8 0 0 This configuration worked fine with the released Jaunty and earlier versions of Karmic. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: regression -- Regression: Samba Read/Write Causes System Freeze https://bugs.launchpad.net/bugs/380219 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 337912] Re: Freeverb No Longer Adds Reverb
I have now tracked down the source of this problem. The function undenormalise in the file src/freeverb/Components/denormals.h is not working for 64-bit. However, the VLC team also use this function in their code and have fixed this bug in their version: http://www.videolan.org/developers/vlc/doc/doxygen/html/denormals_8h- source.html Simply copying the updated VLC denormals.h into the cmt freeverb folder eliminates compiler warnings for freeverb and makes freeverb work on 64-bit machines. -- Freeverb No Longer Adds Reverb https://bugs.launchpad.net/bugs/337912 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 337912] Re: Freeverb No Longer Adds Reverb
I have now tested the same version on a 32-bit Jaunty machine and the plugin works normally with that configuration. This looks to be 64-bit- related. Upstream v1.16 is also affected by this issue. -- Freeverb No Longer Adds Reverb https://bugs.launchpad.net/bugs/337912 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 337912] [NEW] Freeverb No Longer Adds Reverb
Public bug reported: Binary package hint: cmt I recently installed Ubuntu Jaunty on a new x86_64 PC and have installed cmt version 1.15-3.1. This contains what was previously my most-used LADSPA plugin, Freeverb. However, the plugin no longer adds _any_ reverb at all. It merely seems to boost the volume by a few dbs. It doesn't matter which parameters I adjust, there is still no reverb. Additionally, the plugin allows the user to alter the dry (without reverb) and wet (with reverb) levels. If the dry setting is turned down all the way and the wet setting left as normal, there is no longer any output from the plugin, whereas previously there would have been the raw reverb track output. ** Affects: cmt (Ubuntu) Importance: Undecided Status: New -- Freeverb No Longer Adds Reverb https://bugs.launchpad.net/bugs/337912 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 60656] Incorrect path to default device in jsw.h
Public bug reported: In the package libjsw-dev, the file /usr/include/jsw.h has an error on line 39: it refers to the default device being /dev/js0. In Ubuntu, the correct path is /dev/input/js0. ** Affects: libjsw (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Incorrect path to default device in jsw.h https://launchpad.net/bugs/60656 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58742] Re: [edgy] Important dvb-ttpci modules are missing in edgy!
Video4Linux 1 was replaced by Video4Linux 2. However, quite a number of drivers and applications still rely on the old Video4Linux 1 interface. -- [edgy] Important dvb-ttpci modules are missing in edgy! https://launchpad.net/bugs/58742 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58742] Re: [edgy] Important dvb-ttpci modules are missing in edgy!
Is this a new feature in recent kernels? The kernel in Dapper included support for DVB devices out of the box, so it's quite surprising to see it disappear in Edgy. -- [edgy] Important dvb-ttpci modules are missing in edgy! https://launchpad.net/bugs/58742 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57815] Hard coded path to bzip2 in dh-make is wrong
Public bug reported: The file /usr/bin/dh_make contains hard-coded references to /usr/bin/bzip2 on lines 424 and 426 . However, the correct path is /bin/bzip2 (on Edgy, at least). This causes dh_make to report an error when operating on bz2 files: Source file is a bz2 but bzip2 or gzip not available at /usr/bin/dh_make line 428, STDIN line 2. ** Affects: dh-make (Ubuntu) Importance: Untriaged Status: Unconfirmed ** Description changed: - The file /usr/bin/dh-make contains hard-coded references to + The file /usr/bin/dh_make contains hard-coded references to /usr/bin/bzip2 on lines 424 and 426 . However, the correct path is /bin/bzip2 (on Edgy, at least). This causes dh_make to report an error when operating on bz2 files: Source file is a bz2 but bzip2 or gzip not available at /usr/bin/dh_make line 428, STDIN line 2. -- Hard coded path to bzip2 in dh-make is wrong https://launchpad.net/bugs/57815 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57815] Re: Hard coded path to bzip2 in dh-make is wrong
-- Hard coded path to bzip2 in dh-make is wrong https://launchpad.net/bugs/57815 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
