[Ubuntustudio-bugs] [Bug 1909022] Re: Ardour crashes when using the Calf Limiter LV2 plugin and tying to raise the Oversampling parameter to 4
Little tip to the workaround from Erich Eickmeyer I found out the the same... Ardour crashes when parameter "Oversampling" has the value "4" Because of this i was unable to open my Ardour and Mixbus files anymore. To save the work with enabling/disabling all plugins open the affected .ardour file in a text-editor and search for "Calf Limiter". under "active" change the value "1" to "0" and save and close. Now you can open the file in Ardour/Mixbus again and change the parameter "Oversampling" from 4 to to a value between 1 and 3. After this you can enable the Calf Limiter plugin again. You will do this on our own risk! you should make a backup before manipulating the .ardour file. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to calf in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1909022 Title: Ardour crashes when using the Calf Limiter LV2 plugin and tying to raise the Oversampling parameter to 4 Status in calf package in Ubuntu: Invalid Bug description: About my system: It's a new KDE Slimbook with KDE neon pre-installed, which itself is based on Ubuntu focal. I used aptitude to install ardour, calf-plugins, and some other stuff I need to do my audio work. All installed packages are up-to-date, there are no pending updates. List of relevant installed packages: ii ardour 1:5.12.0-3ubuntu4 amd64the digital audio workstation ii calf-plugins 0.90.3-1build2amd64Calf Studio Gear ... Steps to reproduce 1: - Open a new/blank Ardour workspace - Add the "Calf Limiter" plugin (LV2) to the Master bus - Double-click on the plugin to see its GUI - Try to raise the "Oversampling" value to 4 using the knob => crash Steps to reproduce 2: - Open an existing Ardour workspace where the Calf Limiter plugin is present already having an Oversampling value of 4. - In this case Ardour will crash right during the startup. - Workaround: - start Ardour with the '-B' option - activate all plugins (except the Limiter, which also would lead to an immediate crash) - open the Limiter and turn "Oversampling" down to 1. - then the Limiter plugin can be activated and everything works fine. PS: I noticed this bug after I was rsync'ing my audio workspaces from my PC (based on Debian/buster) to the new laptop. All workspaces and plugins (whether Calf, Guitarix, whatever) worked fine, except for my "mastering" workspace which is using the Calf Limiter plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calf/+bug/1909022/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1877155] [NEW] gimp crashes on first login ang starts on second login
Public bug reported:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx
--enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)
using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.62.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Speicherzugriffsfehler
Stack trace:
```
# Stack traces obtained from PID 3658 - Thread 3658 #
[New LWP 3660]
[New LWP 3661]
[New LWP 3662]
[New LWP 3663]
[New LWP 3664]
[New LWP 3665]
[New LWP 3666]
[New LWP 3667]
[New LWP 3668]
[New LWP 3669]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7fff79ae8c90, fd=13) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f2785e75e00 (LWP 3658) "gimp-2.10" __libc_read
(nbytes=256, buf=0x7fff79ae8c90, fd=13) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f27855ee700 (LWP 3660) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f2784ded700 (LWP 3661) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7f277c5ec700 (LWP 3662) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f277f28e700 (LWP 3663) "gmain" 0x7f2786e17c2f in
__GI___poll (fds=0x55b8763e7a60, nfds=1, timeout=4704) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7f277e654700 (LWP 3664) "gdbus" 0x7f2786e17c2f in
__GI___poll (fds=0x55b8763fe380, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7f2763fff700 (LWP 3665) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f27637fe700 (LWP 3666) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7f2762ffd700 (LWP 3667) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
10 Thread 0x7f275bfff700 (LWP 3668) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
11 Thread 0x7f27627fc700 (LWP 3669) "pool-gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 11 (Thread 0x7f27627fc700 (LWP 3669)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f278710aea6 in g_cond_wait_until () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f278708f3e1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7f278708fa06 in g_async_queue_timeout_pop () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f27870e8969 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7f27870e8181 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x7f2786efe669 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139807132993280,
-776773280171938494, 140735234873502, 140735234873503, 140735234873648,
139807132989696, 826019304206380354, 826222579432041794}, mask_was_saved = 0}},
priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev =
[Ubuntustudio-bugs] [Bug 1874441] [NEW] Move appdata.xml file to main package
Public bug reported: The file /usr/share/metainfo/org.kde.kdenlive.appdata.xml is in the package "kdenlive-data", but should be in the package "kdenlive" (like Debian does it), to prevent having two entries in plasma-discover when the flatpak backend is enabled. ** Affects: kdenlive (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to kdenlive in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1874441 Title: Move appdata.xml file to main package Status in kdenlive package in Ubuntu: New Bug description: The file /usr/share/metainfo/org.kde.kdenlive.appdata.xml is in the package "kdenlive-data", but should be in the package "kdenlive" (like Debian does it), to prevent having two entries in plasma-discover when the flatpak backend is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1874441/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1865272] [NEW] ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAP
Public bug reported:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
9.2.1-17ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none,hsa --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20191102 (Ubuntu 9.2.1-17ubuntu1)
using babl version 0.1.74 (compiled against version 0.1.72)
using GEGL version 0.4.18 (compiled against version 0.4.18)
using GLib version 2.63.5 (compiled against version 2.62.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Speicherzugriffsfehler
Stack trace:
```
# Stack traces obtained from PID 52883 - Thread 52883 #
[New LWP 52884]
[New LWP 52885]
[New LWP 52886]
[New LWP 52887]
[New LWP 52888]
[New LWP 52889]
[New LWP 52890]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffe6480cd10, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7ff974a17e00 (LWP 52883) "gimp-2.10" __libc_read
(nbytes=256, buf=0x7ffe6480cd10, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7ff971ce3700 (LWP 52884) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7ff9714e2700 (LWP 52885) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7ff970ce1700 (LWP 52886) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7ff963dfb700 (LWP 52887) "gmain" 0x7ff975a0fc3f in
__GI___poll (fds=0x558250d06cf0, nfds=1, timeout=3501) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7ff9635fa700 (LWP 52888) "gdbus" 0x7ff975a0fc3f in
__GI___poll (fds=0x558250d12f00, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7ff954db3700 (LWP 52889) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7ff94bfff700 (LWP 52890) "pool-gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (Thread 0x7ff94bfff700 (LWP 52890)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7ff975d044e6 in g_cond_wait_until () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7ff975c87511 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7ff975c87b36 in g_async_queue_timeout_pop () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7ff975ce1219 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7ff975ce08d1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x7ff975af6669 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140708698650368,
-4907943033698399510, 140730584586446, 140730584586447, 140730584586592,
140708698646784, 4904961158509611754, 4904860411942128362}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
#7 0x7ff975a1c333 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 7 (Thread 0x7ff954db3700 (LWP 52889)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No
[Ubuntustudio-bugs] [Bug 1576977] Re: Lots of GEGL-gegl-operation.c-WARNING on starting gimp
I have the identical issue under Mint 18. Google works fine, but they just fill up my console :-) They're only warnings, but it would be nice if someone could clean up the code. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to gimp in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1576977 Title: Lots of GEGL-gegl-operation.c-WARNING on starting gimp Status in gimp package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 gimp: 2.8.16-1ubuntu1 rm ~/.gimp-2.8/ LANG=en gimp (gimp:413): GLib-GObject-WARNING **: g_object_set_valist: object class 'GeglConfig' has no property named 'cache-size' (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A3410 from "gimp:point-layer-mode" to "gimp :dissolve-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A39B0 from "gimp:point-layer-mode" to "gimp :behind-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A4090 from "gimp:point-layer-mode" to "gimp :multiply-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A43A0 from "gimp:point-layer-mode" to "gimp :screen-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A4790 from "gimp:point-layer-mode" to "gimp :overlay-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A4BC0 from "gimp:point-layer-mode" to "gimp :difference-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A5800 from "gimp:point-layer-mode" to "gimp :addition-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A5BC0 from "gimp:point-layer-mode" to "gimp :subtract-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A5F80 from "gimp:point-layer-mode" to "gimp :darken-only-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A63D0 from "gimp:point-layer-mode" to "gimp :lighten-only-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A68E0 from "gimp:point-layer-mode" to "gimp:hue- mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A6B40 from "gimp:point-layer-mode" to "gimp :saturation-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A6F70 from "gimp:point-layer-mode" to "gimp:color- mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A73E0 from "gimp:point-layer-mode" to "gimp:value- mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A7760 from "gimp:point-layer-mode" to "gimp :divide-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A7BE0 from "gimp:point-layer-mode" to "gimp:dodge- mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A7F50 from "gimp:point-layer-mode" to "gimp:burn- mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A83A0 from "gimp:point-layer-mode" to "gimp :hardlight-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A8740 from "gimp:point-layer-mode" to "gimp :softlight-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A8B40 from "gimp:point-layer-mode" to "gimp:grain- extract-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A90A0 from "gimp:point-layer-mode" to "gimp:grain- merge-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A93C0 from "gimp:point-layer-mode" to "gimp:color- erase-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20A9730 from "gimp:point-layer-mode" to "gimp:erase- mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20AA080 from "gimp:point-layer-mode" to "gimp :replace-mode" (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of operation class 0x20AA450 from "gimp:point-layer-mode" to "gimp:anti- erase-mode" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1576977/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 574342] Re: GIMP set as default pdf viewer
This bug is still present in Arch Linux. Since Gimp has been installed, both Firefox and Thunderbird open PDFs with Gimp instead of Okular. Furthermore, editing /usr/share/applications/mimeinfo.cache only helped temporarily. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to gimp in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/574342 Title: GIMP set as default pdf viewer Status in gimp package in Ubuntu: Confirmed Bug description: Binary package hint: gimp After installing GIMP on Lucid, GIMP became the default application to open PDF files, instead of evince. While GIMP can open PDF files, this surely is not what most people want. Please fix this. May be related to debian bug #525077, but I am not sure. In any case, /usr/share/applications/mimeinfo.cache contains application/pdf=gimp.desktop;evince.desktop; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/574342/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
Re: [Ubuntustudio-bugs] [Bug 1400470] Re: cannot download photos using shotwell via usb
On 09/07/18 17:27, SunBear wrote: > I see the following message from Shotwell 0.22.0 in Ubuntu 16.04 > every time a iPhone4s is plugged in to my computer usb: > > Shotwell Unable to fetch previews from the camera: Could not claim > the USB device (-53) > > I have to click "Ok" to remove this message before I can access > Shotwell. This warning has always appeared for a few years. Annoying. > It will be great that this warning be removed. You are very lucky that clicking OK enables you to proceed like that. This is a well-known and pervasive bug which has remained unfixed for many years, for some unknown reason. "Could not claim the USB device (-53)" means that some other process (I believe a driver of some kind) has already grabbed the device without authorization, and will not let go of it. This kind of usurpation is not really something we want in an operating system. We need to get to the bottom of it, and delete the process which is apparently jumping in where it is not wanted. I am guessing — because I cannot find any concrete information — that it is a kernel driver installed for some other, perfectly authentic, reason, which is doing this as an unwanted side-effect, so the author may be completely unaware that this is happening. I have already recommended elsewhere that the correct interim solution is for camera applications (in your case, Shotwell, but in fact almost anything that needs access to the camera, even a plain file manager) to be able (with sudo authentication) to kill the current claiming process, break the lock, and give the application the access it needs. Long term, it should be possible to identify to the user *what* process has claimed the USB device uninvited, and allow the user to kill the process permanantly (ie remove it from whatever autostart procedure it was spawned from). Until that happens, camera software usage is largely crippled. ///Peter -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to shotwell in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb Status in shotwell package in Ubuntu: Fix Committed Bug description: I get error message "Unable to fetch previews from the camera: Could not claim the USB device (-53)" when I try to connect my camera and download photos to the PC using Shotwell. I have also installed gThumb and still same message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1400470] Re: cannot download photos using shotwell via usb
This problem is still present: Shotwell cannot access the camera although it is aware of its existence (it is correctly listed in the LH side menu, in my case a Kodak EZ200). The recommended method of unmounting the device in a file manager seems to be bogus for many people: no device is mounted, so there's nothing to unmount. Something, somewhere, is grabbing the device when it is plugged in, and nothing seems to be able to detect *what* process is responsible. I'm attaching the syslog from when I plug it in. Perhaps someone with better usb-fu can make sense of it. ** Attachment added: "syslog of plugging in Kodak EZ200 under Mint 18" https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+attachment/5146822/+files/ez200 -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to shotwell in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb Status in shotwell package in Ubuntu: Fix Committed Bug description: I get error message "Unable to fetch previews from the camera: Could not claim the USB device (-53)" when I try to connect my camera and download photos to the PC using Shotwell. I have also installed gThumb and still same message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1577494] Re: application dies with 'VMware: vmw_ioctl_command error Invalid argument.'
apt-file search vmwgfx libdrm-dev: /usr/include/libdrm/vmwgfx_drm.h libgl1-mesa-dri: /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so ... ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to blender in Ubuntu. Matching subscriptions: ubuntustudio-bugs: blender https://bugs.launchpad.net/bugs/1577494 Title: application dies with 'VMware: vmw_ioctl_command error Invalid argument.' Status in ROS: New Status in Stellarium: New Status in blender package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: running stellarium in ubuntu 16.04 in a VMWare 12.1.1 virtual machine. thanks. jstokes@ubuntu1604:~$ stellarium ** (stellarium:1768): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-6Rt5CAvHFy: Connection refused --- [ This is Stellarium 0.14.3 - http://www.stellarium.org ] [ Copyright (C) 2000-2016 Fabien Chereau et al. ] --- Writing log file to: "/home/jstokes/.stellarium/log.txt" File search paths: 0 . "/home/jstokes/.stellarium" 1 . "/usr/share/stellarium" Config file is: "/home/jstokes/.stellarium/config.ini" Detected: OpenGL "3.0" Driver version string: "3.0 Mesa 11.2.0" GL vendor is "VMware, Inc." GL renderer is "Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;" GL Shading Language version is "1.30" MESA Version Number detected: 11.2 Mesa version is fine, we should not see a graphics problem. GLSL Version Number detected: 1.3 GLSL version is fine, we should not see a graphics problem. Cache directory is: "/home/jstokes/.cache/stellarium/stellarium" Sky language is "en_US" Application language is "en_US" Loading Solar System data ... Loading star data ... "Loading \"/usr/share/stellarium/stars/default/stars_0_0v0_5.cat\": 0_0v0_2; 4963" "Loading \"/usr/share/stellarium/stars/default/stars_1_0v0_5.cat\": 1_0v0_2; 21598" "Loading \"/usr/share/stellarium/stars/default/stars_2_0v0_5.cat\": 2_0v0_2; 150090" "Loading \"/usr/share/stellarium/stars/default/stars_3_1v0_3.cat\": 3_1v0_3; 428466" Finished loading star catalogue data, max_geodesic_level: 3 navigation/preset_sky_time is a double - treating as jday: "2451514.25001" Reloading DSO data... Loaded 10756 DSO records Loading DSO name data ... Loaded 221 / 297 DSO name records successfully Loading star names from "/usr/share/stellarium/skycultures/western/star_names.fab" Loaded 339 / 339 common star names Loading star names from "/usr/share/stellarium/stars/default/name.fab" Loaded 4506 / 4506 scientific star names Loading variable stars from "/usr/share/stellarium/stars/default/gcvs_hip_part.dat" Loaded 6916 / 6916 variable stars Loading cross-index data from "/usr/share/stellarium/stars/default/cross-index.dat" Loaded 108279 / 108279 cross-index data records Loaded 88 / 88 constellation records successfully for culture "western" Loaded 85 / 85 constellation art records successfully for culture "western" Loaded 88 / 88 constellation names Loading constellation boundary data ... Loaded 782 constellation boundary segments Initializing basic GL shaders... Creating GUI ... Loaded plugin "Exoplanets" Exoplanets: version of the format of the catalog: 1 Exoplanets: loading catalog file: "/home/jstokes/.stellarium/modules/Exoplanets/exoplanets.json" Loaded plugin "FOV" Loaded plugin "MeteorShowers" MeteorShowersMgr: Loading catalog file: "/home/jstokes/.stellarium/modules/MeteorShowers/showers.json" Loaded plugin "Novae" Novae: version of the catalog: 1 Novae: loading catalog file: "/home/jstokes/.stellarium/modules/Novae/novae.json" Loaded plugin "Oculars" Ocular plugin - press Command-O to toggle eyepiece view mode. Press ALT-o for configuration. Oculars::validateIniFile ocular.ini exists at: "/home/jstokes/.stellarium/modules/Oculars/ocular.ini" . Checking version... Oculars::validateIniFile found existing ini file version 3 Loaded plugin "Satellites" Satellites: loading catalog file: "/home/jstokes/.stellarium/modules/Satellites/satellites.json" Satellite has invalid orbit: "FLOCK 1B-27" "40422" Satellite has invalid orbit: "FLOCK 1B-22" "40428" Satellite has invalid orbit: "FLOCK 1B-10" "40429" Satellite has invalid orbit: "FLOCK 1B-5" "40453" Satellite has invalid orbit: "FLOCK 1B-6" "40454" Satellite has invalid orbit: "FLOCK 1B-12" "40460" Loaded plugin "SolarSystemEditor" Using the ssystem.ini file that already exists in the user directory... Unable to find module called "TimeZoneConfiguration" Loaded plugin "TimeZoneConfiguration" VMware:
[Ubuntustudio-bugs] [Bug 1577494] Re: application dies with 'VMware: vmw_ioctl_command error Invalid argument.'
Blender, Ubuntu 16.04 package (or the original from blender.org) frequently crashes in the VMware 12.1.1 with the same error message: VMware: vmw_ioctl_command error Invalid argument. see also https://communities.vmware.com/thread/537924?start=0=0 -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to blender in Ubuntu. Matching subscriptions: ubuntustudio-bugs: blender https://bugs.launchpad.net/bugs/1577494 Title: application dies with 'VMware: vmw_ioctl_command error Invalid argument.' Status in ROS: New Status in Stellarium: New Status in blender package in Ubuntu: Confirmed Bug description: running stellarium in ubuntu 16.04 in a VMWare 12.1.1 virtual machine. thanks. jstokes@ubuntu1604:~$ stellarium ** (stellarium:1768): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-6Rt5CAvHFy: Connection refused --- [ This is Stellarium 0.14.3 - http://www.stellarium.org ] [ Copyright (C) 2000-2016 Fabien Chereau et al. ] --- Writing log file to: "/home/jstokes/.stellarium/log.txt" File search paths: 0 . "/home/jstokes/.stellarium" 1 . "/usr/share/stellarium" Config file is: "/home/jstokes/.stellarium/config.ini" Detected: OpenGL "3.0" Driver version string: "3.0 Mesa 11.2.0" GL vendor is "VMware, Inc." GL renderer is "Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;" GL Shading Language version is "1.30" MESA Version Number detected: 11.2 Mesa version is fine, we should not see a graphics problem. GLSL Version Number detected: 1.3 GLSL version is fine, we should not see a graphics problem. Cache directory is: "/home/jstokes/.cache/stellarium/stellarium" Sky language is "en_US" Application language is "en_US" Loading Solar System data ... Loading star data ... "Loading \"/usr/share/stellarium/stars/default/stars_0_0v0_5.cat\": 0_0v0_2; 4963" "Loading \"/usr/share/stellarium/stars/default/stars_1_0v0_5.cat\": 1_0v0_2; 21598" "Loading \"/usr/share/stellarium/stars/default/stars_2_0v0_5.cat\": 2_0v0_2; 150090" "Loading \"/usr/share/stellarium/stars/default/stars_3_1v0_3.cat\": 3_1v0_3; 428466" Finished loading star catalogue data, max_geodesic_level: 3 navigation/preset_sky_time is a double - treating as jday: "2451514.25001" Reloading DSO data... Loaded 10756 DSO records Loading DSO name data ... Loaded 221 / 297 DSO name records successfully Loading star names from "/usr/share/stellarium/skycultures/western/star_names.fab" Loaded 339 / 339 common star names Loading star names from "/usr/share/stellarium/stars/default/name.fab" Loaded 4506 / 4506 scientific star names Loading variable stars from "/usr/share/stellarium/stars/default/gcvs_hip_part.dat" Loaded 6916 / 6916 variable stars Loading cross-index data from "/usr/share/stellarium/stars/default/cross-index.dat" Loaded 108279 / 108279 cross-index data records Loaded 88 / 88 constellation records successfully for culture "western" Loaded 85 / 85 constellation art records successfully for culture "western" Loaded 88 / 88 constellation names Loading constellation boundary data ... Loaded 782 constellation boundary segments Initializing basic GL shaders... Creating GUI ... Loaded plugin "Exoplanets" Exoplanets: version of the format of the catalog: 1 Exoplanets: loading catalog file: "/home/jstokes/.stellarium/modules/Exoplanets/exoplanets.json" Loaded plugin "FOV" Loaded plugin "MeteorShowers" MeteorShowersMgr: Loading catalog file: "/home/jstokes/.stellarium/modules/MeteorShowers/showers.json" Loaded plugin "Novae" Novae: version of the catalog: 1 Novae: loading catalog file: "/home/jstokes/.stellarium/modules/Novae/novae.json" Loaded plugin "Oculars" Ocular plugin - press Command-O to toggle eyepiece view mode. Press ALT-o for configuration. Oculars::validateIniFile ocular.ini exists at: "/home/jstokes/.stellarium/modules/Oculars/ocular.ini" . Checking version... Oculars::validateIniFile found existing ini file version 3 Loaded plugin "Satellites" Satellites: loading catalog file: "/home/jstokes/.stellarium/modules/Satellites/satellites.json" Satellite has invalid orbit: "FLOCK 1B-27" "40422" Satellite has invalid orbit: "FLOCK 1B-22" "40428" Satellite has invalid orbit: "FLOCK 1B-10" "40429" Satellite has invalid orbit: "FLOCK 1B-5" "40453" Satellite has invalid orbit: "FLOCK 1B-6" "40454" Satellite has invalid orbit: "FLOCK 1B-12" "40460" Loaded plugin "SolarSystemEditor" Using the ssystem.ini file that already exists in the user directory... Unable to find module called "TimeZoneConfiguration" Loaded plugin "TimeZoneConfiguration" VMware:
[Ubuntustudio-bugs] [Bug 1577494] Re: application dies with 'VMware: vmw_ioctl_command error Invalid argument.'
** Also affects: blender (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to blender in Ubuntu. Matching subscriptions: ubuntustudio-bugs: blender https://bugs.launchpad.net/bugs/1577494 Title: application dies with 'VMware: vmw_ioctl_command error Invalid argument.' Status in ROS: New Status in Stellarium: New Status in blender package in Ubuntu: Confirmed Bug description: running stellarium in ubuntu 16.04 in a VMWare 12.1.1 virtual machine. thanks. jstokes@ubuntu1604:~$ stellarium ** (stellarium:1768): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-6Rt5CAvHFy: Connection refused --- [ This is Stellarium 0.14.3 - http://www.stellarium.org ] [ Copyright (C) 2000-2016 Fabien Chereau et al. ] --- Writing log file to: "/home/jstokes/.stellarium/log.txt" File search paths: 0 . "/home/jstokes/.stellarium" 1 . "/usr/share/stellarium" Config file is: "/home/jstokes/.stellarium/config.ini" Detected: OpenGL "3.0" Driver version string: "3.0 Mesa 11.2.0" GL vendor is "VMware, Inc." GL renderer is "Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;" GL Shading Language version is "1.30" MESA Version Number detected: 11.2 Mesa version is fine, we should not see a graphics problem. GLSL Version Number detected: 1.3 GLSL version is fine, we should not see a graphics problem. Cache directory is: "/home/jstokes/.cache/stellarium/stellarium" Sky language is "en_US" Application language is "en_US" Loading Solar System data ... Loading star data ... "Loading \"/usr/share/stellarium/stars/default/stars_0_0v0_5.cat\": 0_0v0_2; 4963" "Loading \"/usr/share/stellarium/stars/default/stars_1_0v0_5.cat\": 1_0v0_2; 21598" "Loading \"/usr/share/stellarium/stars/default/stars_2_0v0_5.cat\": 2_0v0_2; 150090" "Loading \"/usr/share/stellarium/stars/default/stars_3_1v0_3.cat\": 3_1v0_3; 428466" Finished loading star catalogue data, max_geodesic_level: 3 navigation/preset_sky_time is a double - treating as jday: "2451514.25001" Reloading DSO data... Loaded 10756 DSO records Loading DSO name data ... Loaded 221 / 297 DSO name records successfully Loading star names from "/usr/share/stellarium/skycultures/western/star_names.fab" Loaded 339 / 339 common star names Loading star names from "/usr/share/stellarium/stars/default/name.fab" Loaded 4506 / 4506 scientific star names Loading variable stars from "/usr/share/stellarium/stars/default/gcvs_hip_part.dat" Loaded 6916 / 6916 variable stars Loading cross-index data from "/usr/share/stellarium/stars/default/cross-index.dat" Loaded 108279 / 108279 cross-index data records Loaded 88 / 88 constellation records successfully for culture "western" Loaded 85 / 85 constellation art records successfully for culture "western" Loaded 88 / 88 constellation names Loading constellation boundary data ... Loaded 782 constellation boundary segments Initializing basic GL shaders... Creating GUI ... Loaded plugin "Exoplanets" Exoplanets: version of the format of the catalog: 1 Exoplanets: loading catalog file: "/home/jstokes/.stellarium/modules/Exoplanets/exoplanets.json" Loaded plugin "FOV" Loaded plugin "MeteorShowers" MeteorShowersMgr: Loading catalog file: "/home/jstokes/.stellarium/modules/MeteorShowers/showers.json" Loaded plugin "Novae" Novae: version of the catalog: 1 Novae: loading catalog file: "/home/jstokes/.stellarium/modules/Novae/novae.json" Loaded plugin "Oculars" Ocular plugin - press Command-O to toggle eyepiece view mode. Press ALT-o for configuration. Oculars::validateIniFile ocular.ini exists at: "/home/jstokes/.stellarium/modules/Oculars/ocular.ini" . Checking version... Oculars::validateIniFile found existing ini file version 3 Loaded plugin "Satellites" Satellites: loading catalog file: "/home/jstokes/.stellarium/modules/Satellites/satellites.json" Satellite has invalid orbit: "FLOCK 1B-27" "40422" Satellite has invalid orbit: "FLOCK 1B-22" "40428" Satellite has invalid orbit: "FLOCK 1B-10" "40429" Satellite has invalid orbit: "FLOCK 1B-5" "40453" Satellite has invalid orbit: "FLOCK 1B-6" "40454" Satellite has invalid orbit: "FLOCK 1B-12" "40460" Loaded plugin "SolarSystemEditor" Using the ssystem.ini file that already exists in the user directory... Unable to find module called "TimeZoneConfiguration" Loaded plugin "TimeZoneConfiguration" VMware: vmw_ioctl_command error Invalid argument. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ros/+bug/1577494/+subscriptions --
[Ubuntustudio-bugs] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages
*** This bug is a duplicate of bug 1573408 *** https://bugs.launchpad.net/bugs/1573408 Please fix this bug!!! This has not been fixed despite what has been claimed. I have done a clean install of both 16.04 and 16.04.1 and the bug persists. Come on guys, this is a LTS release, and this should be addressed. Work-arounds is not a solution for faulty software. It looks to me that when you try to install some package from the Software Centre, it starts the install then hangs. I believe this is because a dialog box should appear asking for admin credentials to install the software, but since that dialog box does not appear it just sits there waiting. My set up is a Dell Precision M4500 (but this isn't a hardware issue - it is most definitely a software problem). My installation is a fully encrypted hard drive with encrypted home directory if that makes a difference. Please mark this bug as not fixed. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to The Ubuntu Studio Project. Matching subscriptions: UbuntuStudio Bugs https://bugs.launchpad.net/bugs/1573206 Title: GNOME Software does not install third-party .deb packages Status in GNOME Software: New Status in Ubuntu GNOME: Triaged Status in Ubuntu Studio: Triaged Status in gnome-software package in Ubuntu: Triaged Bug description: Ubuntu 16.04 LTS (clean install). 64-bit. Final release. Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 Version table: *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500 500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I intended to install MEGA Sync Client, Google Chrome and Dropbox by downloading the needed packages from their websites (respectively https://mega.nz/#sync and https://www.google.com/chrome/ and https://www.dropbox.com/install?os=lnx ). I opened the packages one by one with gnome-software and pressed Install - nothing, except for a super-quick progress bar animation, happened. No matter how many times I tried, same result. Also, an icon pops up on the panel saying "Waiting to install", but nothing seems to happen. This only seems to happen with third-party packages; installing a random deb from packages.ubuntu.com/xenial worked. I even tried to reinstall the system to make this work, but same problem. Gdebi, however, installs the packages as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 21 21:01:52 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2016-04-21 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nn_NO.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1573206/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1492623] Re: Revision doesn't match upstream v2.0.2
Thanks, Actually, I fixed it ;) Tracking bugs by revision number works very well for upstream, and if that interferes with Debian packaging then they would see that as Debian's problem. In any case, I was given commit access to the Debian repository recently, and made the fix in such a way that the revision will be set automatically each time new upstream code gets imported via uscan, so there is no chance of somebody forgetting to do it. Unfortunately I haven't been given access to the Debian archive so I can't upload the package into Debian, but hopefully the actual maintainer will get around to doing it soon. Peter -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1492623 Title: Revision doesn't match upstream v2.0.2 Status in musescore package in Ubuntu: Fix Committed Bug description: This bug applies to musescore (2.0.2+dfsg-1) [universe] in the Wily repo. Go to Help -> About. The following is displayed in the dialog: Version: 2.0.2 Revision: 3543170 But the revision should be: f51dc11 The revision number should correspond to the first 7 digits of git commit code corresponding to the v2.0.2 tagged release: https://github.com/musescore/MuseScore/tree/2.0.2 The revision number is specified in the code in the file mscore/revision.h. Simply change the number in this file to fix the bug. Note to maintainer - updating the revision number automatically: There is a Makefile target called "revision" (i.e. "make revision") that sets the revision number. Adding the appropriate command to debian/rules would set revision automatically. However, note the following: - "make revision" only works in a git repository - If using a downstream git repo you MUST use "make revision" BEFORE committing to a downstream repository. (i.e. "revision" should match the upstream git revision, not the downstream git revision). I help maintain the MuseScore PPA on Launchpad (https://launchpad.net /~mscore-ubuntu) and regularly contribute to the upstream code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1492623/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1565380] Re: LADI (control center, log file viewer) doesn't work
p13rrot@p13rrot-Inspiron-3543:~$ uname -a Linux p13rrot-Inspiron-3543 3.19.0-56-lowlatency #62~14.04.1-Ubuntu SMP PREEMPT Fri Mar 11 12:05:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to Ubuntu Studio. Matching subscriptions: UbuntuStudio Bugs https://bugs.launchpad.net/bugs/1565380 Title: LADI (control center, log file viewer) doesn't work Status in Ubuntu Studio: New Bug description: Opening settings manager and clicking on LADI Control Center or LADI Log File Viewer does nothing. Running "ladi-control-center" and "ladi-system-log" yields similar results: p13rrot@p13rrot-Inspiron-3543:~$ ladi-control-center Traceback (most recent call last): File "/usr/bin/ladi-control-center", line 28, in from laditools import _gettext_domain File "/usr/lib/python2.7/dist-packages/laditools/__init__.py", line 27, in from .ladish import LadishProxy, LadishStatusType, LadishProxyError, check_ladish File "/usr/lib/python2.7/dist-packages/laditools/ladish.py", line 34, in "STUDIO_RUNNING") File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 325, in __call__ return cls._create_(value, names, module=module, type=type) File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 433, in _create_ enum_class = metacls.__new__(metacls, class_name, bases, classdict) File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 154, in __new__ member_type, first_enum = metacls._get_mixins_(bases) File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 467, in _get_mixins_ issubclass(base, Enum) and TypeError: issubclass() arg 1 must be a class and p13rrot@p13rrot-Inspiron-3543:~$ ladi-system-log Traceback (most recent call last): File "/usr/bin/ladi-system-log", line 32, in from laditools import _gettext_domain File "/usr/lib/python2.7/dist-packages/laditools/__init__.py", line 27, in from .ladish import LadishProxy, LadishStatusType, LadishProxyError, check_ladish File "/usr/lib/python2.7/dist-packages/laditools/ladish.py", line 34, in "STUDIO_RUNNING") File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 325, in __call__ return cls._create_(value, names, module=module, type=type) File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 433, in _create_ enum_class = metacls.__new__(metacls, class_name, bases, classdict) File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 154, in __new__ member_type, first_enum = metacls._get_mixins_(bases) File "/usr/lib/python2.7/dist-packages/enum/__init__.py", line 467, in _get_mixins_ issubclass(base, Enum) and TypeError: issubclass() arg 1 must be a class To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio/+bug/1565380/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1248174] Re: Update the Ubuntu colour palette to fit the spec
marking as invalid for design.ubuntu.com as we have no inkscape pallets, if there is a specific thing to do on this site, please file a new bug referencing this one. ** Changed in: ubuntu-brand-guidelines Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to gimp in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Triaged Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1492629] [NEW] patch to remove manual is obsolete
Public bug reported: This bug applies to musescore (2.0.2+dfsg-1) [universe] in the Wily repo. The patch debian/01-do-not-install-manual-pdf.patch no longer applies. The patch comment reads: # Description: Don't install PDF manual as it is removed for DFSG compliance However, the PDF manual is no longer included in the upstream code. I help maintain the MuseScore PPA on Launchpad (https://launchpad.net /~mscore-ubuntu) and regularly contribute to the upstream code. ** Affects: musescore (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1492629 Title: patch to remove manual is obsolete Status in musescore package in Ubuntu: New Bug description: This bug applies to musescore (2.0.2+dfsg-1) [universe] in the Wily repo. The patch debian/01-do-not-install-manual-pdf.patch no longer applies. The patch comment reads: # Description: Don't install PDF manual as it is removed for DFSG compliance However, the PDF manual is no longer included in the upstream code. I help maintain the MuseScore PPA on Launchpad (https://launchpad.net /~mscore-ubuntu) and regularly contribute to the upstream code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1492629/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1463975] Re: Update to MuseScore 2.0.1
** Changed in: musescore (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1463975 Title: Update to MuseScore 2.0.1 Status in musescore package in Ubuntu: Fix Committed Bug description: MuseScore 2.0.1 is out for a month now. It would be great if Ubuntu and Debian could have a new package. Tarball is here http://musescore.org/download/musescore.tar.bz2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1463975/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1478931] Re: stable PPA refused by Mint17
Try it doing it from the command line. i.e: sudo add-apt-repository ppa:mscore-ubuntu/mscore-stable And then to install MuseScore: sudo apt-get update sudo apt-get install musescore -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1478931 Title: stable PPA refused by Mint17 Status in musescore package in Ubuntu: New Bug description: In Mint17 Quiana, Rebecca, Raphaela, all based upon Ubuntu 14.04 , trying to add this PPA deb http://ppa.launchpad.net/mscore-ubuntu/mscore-stable/ubuntu trusty main one get a pop upmessage Impossible d'ajouter le ppa no JSON obect could be decoded However this PPA can be added to Lubuntu vivid (but with a GPG error) So I will also file a bug in Mint To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1478931/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1473724] Re: MIDI Keyboard Input do not works in Musescore 2 and Ubuntu 14.4
I am using a MIDI keyboard with MuseScore 2.0.0 on Ubuntu 15.04 just fine, but I can't speak for 14.04. Try this... in Edit -> Preferences: - Under "Note Input" tick the "Enable MIDI Input" checkbox. - Under "I/O" select "ALSA audio". Now restart MuseScore and then plug in the keyboard and switch it on. IMPORTANT NOTE: You must always start MuseScore BEFORE you plug in and switch on the MIDI keyboard. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1473724 Title: MIDI Keyboard Input do not works in Musescore 2 and Ubuntu 14.4 Status in musescore package in Ubuntu: New Bug description: My system: Ubuntu 14.4 Musescore 2.0.0 Keyboard: MIDISTART 2 After upgrade to 2.0: Musescore are not more listed in aconnectgui and MIDI keyboard input is not working anymore.. Any ideas how to work out this problem? Thank you in advance, Marco p.s.: removing 2.0 and installing 1.3 solve the problem, MIDI is working without problems with the old version of Musescore. My solution at the moment ist to work with 1.3 in Ubuntu and to use 2.0.1 with Wine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1473724/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1348045] [NEW] blender crashes on start with Segmentation fault when reading /dev/urandom
Public bug reported:
-If you start blender from the CLI you get this info:
ubuntu@tegra-ubuntu:~$ blender
Color management: using fallback mode for management
connect failed: No such file or directory
Writing: /tmp/blender.crash.txt
Segmentation fault
ubuntu@tegra-ubuntu:~$ cat /tmp/blender.crash.txt
# Blender 2.69 (sub 0), Revision: unknown
# backtrace
-If you start blender via strace you get this info:
strace -e open blender
open(/dev/urandom, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 16
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x54} ---
Is there a problem with the urandom device ?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: blender 2.69-4ubuntu2
Uname: Linux 3.10.24-gf455cd4 armv7l
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: armhf
CurrentDesktop: Unity
Date: Thu Jul 24 07:52:47 2014
SourcePackage: blender
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: blender (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug armhf trusty
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to blender in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/1348045
Title:
blender crashes on start with Segmentation fault when reading
/dev/urandom
Status in “blender” package in Ubuntu:
New
Bug description:
-If you start blender from the CLI you get this info:
ubuntu@tegra-ubuntu:~$ blender
Color management: using fallback mode for management
connect failed: No such file or directory
Writing: /tmp/blender.crash.txt
Segmentation fault
ubuntu@tegra-ubuntu:~$ cat /tmp/blender.crash.txt
# Blender 2.69 (sub 0), Revision: unknown
# backtrace
-If you start blender via strace you get this info:
strace -e open blender
open(/dev/urandom, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 16
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x54} ---
Is there a problem with the urandom device ?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: blender 2.69-4ubuntu2
Uname: Linux 3.10.24-gf455cd4 armv7l
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: armhf
CurrentDesktop: Unity
Date: Thu Jul 24 07:52:47 2014
SourcePackage: blender
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1348045/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1347914] Re: Audacity crashes on startup while trying to read /proc/cpuinfo
Please read here: http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/178645.html Could someone talk with Will Deacon from arm.com about removing Bogomips ? Whats your opinion ? -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to audacity in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1347914 Title: Audacity crashes on startup while trying to read /proc/cpuinfo Status in “audacity” package in Ubuntu: New Bug description: root@tegra-ubuntu:~# audacity ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports only playback stream ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave FATAL: cannot locate cpu MHz in /proc/cpuinfo It looks like audacity requires the Bogomips value from /proc/cpuinfo which is no more present in modern kernels. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: audacity 2.0.5-1ubuntu3.2 Uname: Linux 3.10.24-gf455cd4 armv7l ApportVersion: 2.14.1-0ubuntu3.2 Architecture: armhf CurrentDesktop: Unity Date: Wed Jul 23 22:44:22 2014 SourcePackage: audacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1347914/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1338062] [NEW] libav-tools throws warnings while installing
Public bug reported: Kubuntu 14.04 updated through 7/4/14 Libav version: 6:9.13-0ubuntu0.14.04.1 During the installation of libav-tools, dpkg complains as follows: Preparing to unpack .../libav-tools_6%3a9.13-0ubuntu0.14.04.1_i386.deb ... dpkg: error: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! Unpacking libav-tools (6:9.13-0ubuntu0.14.04.1) ... As far as I can tell, the software is correctly installed despite these complaints. ** Affects: libav (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to libav in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1338062 Title: libav-tools throws warnings while installing Status in “libav” package in Ubuntu: New Bug description: Kubuntu 14.04 updated through 7/4/14 Libav version: 6:9.13-0ubuntu0.14.04.1 During the installation of libav-tools, dpkg complains as follows: Preparing to unpack .../libav-tools_6%3a9.13-0ubuntu0.14.04.1_i386.deb ... dpkg: error: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! Unpacking libav-tools (6:9.13-0ubuntu0.14.04.1) ... As far as I can tell, the software is correctly installed despite these complaints. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1338062/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
