Bug#945814: audacity: various segfaults of audacity on startup
Dear Bernhard, thanks for the efforts. Best regards, Tjeerd Pinkert On 1/27/20 15:26, Bernhard Übelacker wrote: > Control: reassign -1 zynaddsubfx-dssi 3.0.3-1 > Control: affects -1 + audacity > > > Hello Tjeerd, > >> Thanks for coming back, I'm not in a hurry... >> >> The problem is that I can not trigger specific bugs (they seem to happen >> somewhat random). So a made some more valgrinds: valgrind.dat > > Because the error des not manifest each run in the same location > this might be thread related e.g. two threads are working on the > same memory. > > >> I had zynaddsubfx installed to try it out and see if I like it, but did >> not uninstall after the tries (sufficient diskspace luxury). I could >> uninstall zynadd, zynsaddsubfx and zynaddsubfx-dssi, the data package is >> depended on by the lmms-common package. > > I tried to install some more lv2 plugins and bridges and after enabling > all in audacity I got the shared library loaded libzynaddsubfx_dssi.so > by just starting audacity - but still cannot reproduce a crash. > (Details attached.) > > >> And audacity runs without crashing (thanks for the hint) but still gives >> a lot of debug output: audacity_debug.dat > > Most of the remaining output seems gui related - seems to be harmless. > > >> So at least the the source of all evil is now clear... and the bug >> "resolved". Do you have contact with the zynaddsubfx devs and file a bug >> there? Devs amongst each other might talk clearer? Otherwise I'm happy >> to do it. > > It might not be that clear - depending on e.g. libzynaddsubfx_dssi.so > is intended to work multi threaded ... > > When I did run audacity in my test environment I get some > "Possible data race" with valgrind's helgrind tool. > > At least it might be related to some plugins, either direct or > via some bridges, therefore I hope it is ok to reassign. > > Bringing the issue upstream might also not be a bad idea. > > Kind regards, > Bernhard signature.asc Description: OpenPGP digital signature
Bug#945814: audacity: various segfaults of audacity on startup
Package: audacity Version: 2.2.2-1+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, thanks for creating a normally very stable and properly functioning system. * What led up to the situation? I tried to start the program audacity $ audacity * What exactly did you do (or not do) that was effective (or ineffective)? Nothing unusual * What was the outcome of this action? various responces follow: :~$ audacity lo server running on 15889 ../src/common/debugrpt.cpp(453): assert "IsOk()" failed in AddContext(): use IsOk() first [in thread 7f6f3c5f1700] Segmentation fault :~$ audacity -v lo server running on 15901 munmap_chunk(): invalid pointer Aborted :~$ audacity lo server running on 15907 Warning: failed to load part<>! Segmentation fault :~$ audacity lo server running on 15911 ../src/common/debugrpt.cpp(453): assert "IsOk()" failed in AddContext(): use IsOk() first [in thread 7f76eb92d700] Segmentation fault :~$ audacity lo server running on 15918 Segmentation fault :~$ audacity lo server running on 15923 Segmentation fault :~$ audacity --version lo server running on 15942 double free or corruption (fasttop) Aborted :~$ audacity lo server running on 15947 malloc_consolidate(): invalid chunk size Aborted :~$ audacity lo server running on 15950 ../src/common/debugrpt.cpp(453): assert "IsOk()" failed in AddContext(): use IsOk() first [in thread 7f70fa1a0700] Segmentation fault :~$ audacity lo server running on 15953 ../src/common/debugrpt.cpp(453): assert "IsOk()" failed in AddContext(): use IsOk() first [in thread 7f0f2862d700] Segmentation fault * What outcome did you expect instead? I expected audacity to start I was not able to resolve the problem. I hope the problem may be solved... Best regards, Tjeerd Pinkert -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages audacity depends on: ii audacity-data 2.2.2-1 ii libasound2 1.1.8-1 ii libavcodec-extra58 [libavcodec58] 7:4.1.4-1~deb10u1 ii libavformat58 7:4.1.4-1~deb10u1 ii libavutil567:4.1.4-1~deb10u1 ii libc6 2.28-10 ii libexpat1 2.2.6-2+deb10u1 ii libflac++6v5 1.3.2-3 ii libflac8 1.3.2-3 ii libgcc11:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk2.0-02.24.32-3 ii libid3tag0 0.15.1b-14 ii liblilv-0-00.24.2~dfsg0-2 ii libmad00.15.1b-10 ii libmp3lame03.100-2+b1 ii libogg01.3.2-1+b1 ii libportaudio2 19.6.0-1 ii libportsmf00.1~svn20101010-5 ii libsndfile11.0.28-6 ii libsoundtouch1 2.1.2+ds1-1 ii libsoxr0 0.1.2-3 ii libstdc++6 8.3.0-6 ii libsuil-0-00.10.0~dfsg0-1 ii libtwolame00.3.13-4 ii libvamp-hostsdk3v5 2.7.1~repack0-1 ii libvorbis0a1.3.6-2 ii libvorbisenc2 1.3.6-2 ii libvorbisfile3 1.3.6-2 ii libwxbase3.0-0v5 3.0.4+dfsg-8 ii libwxgtk3.0-0v53.0.4+dfsg-8 audacity recommends no packages. Versions of packages audacity suggests: ii amb-plugins [ladspa-plugin] 0.8.1-7 ii ambdec [ladspa-plugin]0.7.1-1 ii autotalent [ladspa-plugin]0.2-5 ii blepvco [ladspa-plugin] 0.1.0-3+b1 ii blop [ladspa-plugin] 0.2.8-6.1 ii bs2b-ladspa [ladspa-plugin] 0.9.1-3 ii caps [ladspa-plugin] 0.9.26-1 ii cmt [ladspa-plugin] 1.16-2 ii csladspa [ladspa-plugin] 1:6.11.1-1 ii fil-plugins [ladspa-plugin] 0.3.0-6 ii guitarix-ladspa [ladspa-plugin] 0.36.1-1+b1 ii invada-studio-plugins-ladspa [ladspa-plugin] 0.3.1-5 ii ladspa-sdk [ladspa-plugin]1.13-3 ii mcp-plugins [ladspa-plugin] 0.4.0-6 ii omins [ladspa-plugin]
Bug#623539: Takes over GPG and SSH agents from gnupg-agent and ssh-agent
Dear all, I came across this issue after an update of the 8 series (jessie) with backports. Seems to be introduced there (or maybe it was already present and popped back up, I vaguely remember something in the past). Most annoying is that none of the proposed solutions work. I'm usign the MATE desktop, and somehow, although I completely removed the /etc/xdg/autostart/gnome-keyring-gpg.desktop and -ssh equivalent, also in the ~/.config folder, even while adding the --disable-gpg-agent to the remaining gnome-keyring files, gnome-keyring keeps interfering. And stubbornly loads the gpg and ssh parts. remaining entries have the end of the file now as follows: - Exec=/usr/bin/gnome-keyring-daemon --start --components=secrets --disable-gpg-agent OnlyShowIn=GNOME;Unity;MATE; X-GNOME-Autostart-Phase=Initialization X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=true X-GNOME-Bugzilla-Bugzilla=GNOME X-GNOME-Bugzilla-Product=gnome-keyring X-GNOME-Bugzilla-Component=general X-GNOME-Bugzilla-Version=3.14.0 - GnuPG v 2.0.26-6+deb8u gnome-keyring 3.14.0-1+b1 pinentry-gtk2 0.9.7-5~bpo8+1 Although the help option of gnome-keyring-daemon shows that the gpg and ssh parts are optional, they simply load during session start (gdm3 as display manager). I could not find any other places where the gnome-keyring-daemon is configured, any hints are welcome. - Solution (not very handy though): $ killall gnome-keyring-daemon after the gnome-keyring has been killed pinentry takes over in thunderbird + gnupg. Best regards, Tjeerd On Fri, 11 Mar 2016 23:19:48 +0100 Luca Capello <l...@pca.it> wrote: > block 623539 by 773304 > block 623539 by 760102 > affects 623539 + gnupg-agent > affects 623539 + libpam-ssh > user luca.cape...@infomaniak.com > usertag 623539 + infomaniak.com-authentication > thanks > > Hi there! > > On Fri, 22 Apr 2011 17:02:45 -0700, Josh Triplett wrote: > > retitle 623539 Takes over GPG and SSH agents from gnupg-agent and ssh-agent > > At least the GnuPG part of this bug has been fixed: > > - upstream[1][2][3] since gnome-keyring_3.17.4 together with > pinentry_0.9.5 and gnupg_2.1.6 > > - in Debian[4] since gnome-keyring_3.16.0-3 > > [1] <https://bugs.debian.org/773304> > [2] <https://bugzilla.gnome.org/show_bug.cgi?id=644415#c10> > [3] > <https://mail.gnome.org/archives/distributor-list/2015-August/msg0.html> > [4] <https://bugs.debian.org/760102> > > This means that the bug should already been fixed in stretch > (gnome-keyring_3.18.3-1, pinentry_0.9.7-5 and gnupg_2.1.11-6). > > For jessie, you still need to avoid gnome-keyring-gpg and -ssh startup > as explained in the README.Debian, either with 'Hidden=true' as > explained on Simon Josefsson's blog[5] or, better, with (works on Ubuntu > 14.04 as well, gnome-keyring_3.10.1-1ubuntu4): > = > $ mkdir -p ~/.config/autostart > $ echo 'X-GNOME-Autostart-enabled=false' \ > | cat /etc/xdg/autostart/gnome-keyring-gpg.desktop - \ > >>~/.config/autostart/gnome-keyring-gpg.desktop > $ echo 'X-GNOME-Autostart-enabled=false' \ > | cat /etc/xdg/autostart/gnome-keyring-ssh.desktop - \ > >>~/.config/autostart/gnome-keyring-ssh.desktop > = > > [5] <https://blog.josefsson.org/2015/01/02/openpgp-smartcards-and-gnome/> > > Thx, bye, > Gismo / Luca -- graag antwoord via: t.j.pink...@alumnus.utwente.nl T.J.Pinkert --- Wij zijn per 1 april 2017 naar Duitsland verhuisd. Omdat we eerst tijdelijk wonen de post graag naar: Tjeerd Pinkert Stegerensallee 43 7701 PK Dedemsvaart The Netherlands Ons nieuwe tijdelijke adres is (achternaam vermelden!): Tjeerd Pinkert Rheinring 4b 38120 Braunschweig Germany telefoonnummers: vast: +49 531 50835195 (voorkeur) mob: +49 1 5901154868 (voorkeur) mob: +31 6 41924439 signature.asc Description: OpenPGP digital signature
Bug#853149: Extension Manager: exception in synchronize
Dear Rene, thank you for the quick reply and checks. I think it can be closed, see below. On 01/30/2017 12:09 PM, Rene Engelhard wrote: > reassign 853149 libreoffice-core > tag 853149 + unreproducible > tag 853149 + moreinfo > thanks > > On Mon, Jan 30, 2017 at 11:00:07AM +0100, Tjeerd Pinkert wrote: >> Package: libreoffice-base > > Obviously not. It's not a bug in the Database application, is it? > Please report against correct packages (and in this case the package > description > of libreoffice-base is clear what it is) I'm sorry, this is my fault, realised only after sending it should have been another package, would have chosen libreoffice-common or -core I think, still wrong, -base sounds like it (in Dutch) but is not :~ >> Version: 4.3.3-2+deb8u5 >> >> After an update I found that LibreOffice did not start anymore. It gave >> an error dialog saying: > > When and what and how? I restarted my machine last friday after a longer time with multiple updates done in the mean time (it partially acts as a server), but not as long ago as mid-2016. > 1:4.3.3-2+deb8u5 is there since months (mid-2016), as is > libreoffice-lightproof-en (from jessie release onwards) > (which would be the correct package to file it in if it was a bug in th > packages' file permissions) > >> After searching the web I found that this might happen if the user >> profile is defunct (that was not the case) or the Extention Manager has >> no access to some of the shared library locations: >> >> I found that including all rX on the following directories solved the bug. >> >> user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath$ >> ls -l >> total 44 >> -rw-r--r-- 1 root root 4078 May 15 2014 >> lightproof_handler_lightproof_en.py >> -rw-r--r-- 1 root root 14966 May 15 2014 lightproof_impl_lightproof_en.py >> -rw-r--r-- 1 root root 13965 May 15 2014 lightproof_lightproof_en.py >> -rw-r--r-- 1 root root 260 May 15 2014 lightproof_opts_lightproof_en.py >> drwxr-x--- 2 root root 4096 Jan 24 10:58 __pycache__ >> user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath$ >> sudo chmod a+rX __pycache__/ >> user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath$ >> cd __pycache__/ >> user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath/__pycache__$ >> ls -l >> total 28 >> -rw-r- 1 root root 4938 Jan 24 10:58 >> lightproof_handler_lightproof_en.cpython-34.pyc >> -rw-r- 1 root root 14624 Jan 24 10:58 >> lightproof_impl_lightproof_en.cpython-34.pyc >> -rw-r- 1 root root 435 Jan 24 10:58 >> lightproof_opts_lightproof_en.cpython-34.pyc >> user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath/__pycache__$ >> sudo chmod a+rX * > > After installing libreoffice-lightproof-en and libreoffice-writer in a clean > jessie and proofchecking a simple wrong sentence and closing I get: > > drwxr-xr-x 2 root root 4096 Jan 30 11:04 __pycache__ > > So it's ok. (And normal files don't need to be +x) X is not x. Interesting that the clean install is OK. >> After this it still did not work, I also changed: >> >> user@pudding:/var/spool/libreoffice/uno_packages/cache$ ls -l >> total 4 >> drwxr-x--- 2 root root 4096 Jan 24 10:58 uno_packages >> user@pudding:/var/spool/libreoffice/uno_packages/cache$ sudo chmod a+rX * > > (cowbuilder-stable)root@frodo:/var/spool/libreoffice/uno_packages/cache# ls -l > total 4 > drwxr-xr-x 2 root root 4096 Jan 30 11:04 uno_packages Interesting... Looks like something on my machine went wrong, but what... > without doing anything. Did you loose directories and recreated them on your > own? > fs problems? No directories lost as far as I know. The latter might have been the case although I had a clean fs on reboot as far as I know/have seen? I also had some other old trouble back today, so it might have been an unclean fs restored to some previous state... Let's keep it on that. > In any case, I can't see any bug in any of the involving packages. OK, I accept your verdict, thank you for the efforts, my excuses for the false report. I hope then this will at the least serve as a lead to other users getting this error (since SSE is not the problem here, but that is what many searches refer to). Best regards, Tjeerd
Bug#853149: Extension Manager: exception in synchronize
Package: libreoffice-base Version: 4.3.3-2+deb8u5 After an update I found that LibreOffice did not start anymore. It gave an error dialog saying: Extension Manager: exception in synchronize After searching the web I found that this might happen if the user profile is defunct (that was not the case) or the Extention Manager has no access to some of the shared library locations: I found that including all rX on the following directories solved the bug. user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath$ ls -l total 44 -rw-r--r-- 1 root root 4078 May 15 2014 lightproof_handler_lightproof_en.py -rw-r--r-- 1 root root 14966 May 15 2014 lightproof_impl_lightproof_en.py -rw-r--r-- 1 root root 13965 May 15 2014 lightproof_lightproof_en.py -rw-r--r-- 1 root root 260 May 15 2014 lightproof_opts_lightproof_en.py drwxr-x--- 2 root root 4096 Jan 24 10:58 __pycache__ user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath$ sudo chmod a+rX __pycache__/ user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath$ cd __pycache__/ user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath/__pycache__$ ls -l total 28 -rw-r- 1 root root 4938 Jan 24 10:58 lightproof_handler_lightproof_en.cpython-34.pyc -rw-r- 1 root root 14624 Jan 24 10:58 lightproof_impl_lightproof_en.cpython-34.pyc -rw-r- 1 root root 435 Jan 24 10:58 lightproof_opts_lightproof_en.cpython-34.pyc user@pudding:/usr/lib/libreoffice/share/extensions/lightproof_en/pythonpath/__pycache__$ sudo chmod a+rX * After this it still did not work, I also changed: user@pudding:/var/spool/libreoffice/uno_packages/cache$ ls -l total 4 drwxr-x--- 2 root root 4096 Jan 24 10:58 uno_packages user@pudding:/var/spool/libreoffice/uno_packages/cache$ sudo chmod a+rX * Then it worked. I did not try to undo the first change. I'm using repos: deb http://ftp.nl.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.nl.debian.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free deb http://ftp.debian.org/debian jessie-backports main contrib non-free Yours, Tjeerd
Bug#839706: redmine: wrong version of rake installed
Package: redmine Version: 3.0~20140825-8~deb8u3 Severity: important Dear maintainer, on installing the redmine package, all seems to go well. However, when enabling the apache virtual host (with and without passenger) I get an internal server error: The apache error log shows: [Tue Oct 04 09:33:16.327586 2016] [core:error] [pid 6703:tid 139721459033856] [client ::1:44268] End of script output before headers: dispatch.fcgi /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:92:in `block in materialize': Could not find rake-11.3.0 in any of the sources (Bundler::GemNotFound) from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:85:in `map!' from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:85:in `materialize' from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:132:in `specs' from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:177:in `specs_for' from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:166:in `requested_specs' from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:18:in `requested_specs' from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:13:in `setup' from /usr/lib/ruby/vendor_ruby/bundler.rb:121:in `setup' from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:17:in `' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/share/redmine/config/boot.rb:4:in `' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/share/redmine/public/dispatch.fcgi:3:in `' [Tue Oct 04 09:42:26.674066 2016] [fcgid:warn] [pid 6703:tid 139721442248448] (104)Connection reset by peer: [client ::1:44352] mod_fcgid: error reading data from FastCGI server [Tue Oct 04 09:42:26.674101 2016] [core:error] [pid 6703:tid 139721442248448] [client ::1:44352] End of script output before headers: dispatch.fcgi This might be due to our inexperience with Ruby and the horribleness of the many "tutorials" found on the web however. I have tried to deinstall all packages related to redmine and reinstall them fresh, but the issue remains. Best regards, Tjeerd Pinkert -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages redmine depends on: ii bundler 1.7.4-1 ii dbconfig-common 1.8.47+nmu3+deb8u1 ii debconf [debconf-2.0] 1.5.56 ii libjs-scriptaculous 1.9.0-2 ii redmine-pgsql 3.0~20140825-8~deb8u3 ii ruby1:2.1.5+deb8u2 ii ruby-actionpack-action-caching 1.1.1-3 ii ruby-awesome-nested-set 3.0.0-1 ii ruby-coderay1.1.0-2 ii ruby-i18n 0.6.9-2 ii ruby-jquery-rails 3.1.2-2 ii ruby-mime-types 1.25-2 ii ruby-net-ldap 0.8.0-1 ii ruby-openid 2.5.0debian-1 ii ruby-protected-attributes 1.0.8-2 ii ruby-rack 1.5.2-3+deb8u1 ii ruby-rack-openid1.4.2-1 ii ruby-rails 2:4.1.8-1+deb8u4 ii ruby-rails-observers0.1.1-1 ii ruby-redcarpet 3.1.2-1 ii ruby-request-store 1.1.0-1 ii ruby-rmagick2.13.2-4+b1 ii ruby2.1 [ruby-interpreter] 2.1.5-2+deb8u3 Versions of packages redmine recommends: ii libfcgi-ruby1.9.1 0.9.2.1-1 ii ruby-fcgi [libfcgi-ruby1.9.1] 0.9.2.1-1+b3 ii ruby-passenger 4.0.53-1 Versions of packages redmine suggests: ii bzr 2.6.0+bzr6595-6 ii cvs 2:1.12.13+real-15 ii darcs 2.8.5-2 ii git 1:2.1.4-2.1+deb8u2 ii mercurial 3.1.2-2+deb8u3 ii subversion 1.8.10-6+deb8u4
Bug#837091: firefox-esr: EME DRM extention present and enabled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: firefox-esr
Version: 45.3.0esr-1~deb8u1
Severity: serious
Tags: security upstream
Justification: Policy 2.2.1 must comply with the DFSG
Dear Maintainer,
after reading up a bit (late(ly)) on the W3C EME proposed standard for
embedding of DRM managed content in web pages, I decided to have a
look if it is present in the firefox browser. about:config shows the
following:
media.eme.apiVisible;true
media.eme.enabled;true
I think the presence of code that requires closed source components to
function, might violate the DFSG for the main section? On the other
hand, no package relation is available in the non-free section as far
as I see that is actively depended on. If a decision has been taken on
this already, then please close.
I have not found this in the system for the firefox-esr package, I did
find bug 748342 (iceweasel), and the upstream bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1011459
and a discussion at:
http://forums.debian.net/viewtopic.php?f=20=114687
First of all I disabled the function by setting the above values to:
false.
It would be better to have support for EME removed altogether to be free
of any possible legal issues arising from DRM enabled software.
Yours,
Tjeerd Pinkert
P.S. yes I know, having flash installed as a plugin is as bad as
having EME enabled... Trying to block as much as possible though...
- -- Package-specific info:
- -- Extensions information
Name: Adblock Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{d1
0d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Package: xul-ext-adblock-plus
Status: enabled
Name: Cookie Monster
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{45
d8ff86-d909-11db-9705-005056c8}
Package: xul-ext-cookie-monster
Status: enabled
Name: Default theme
Location:
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198
ce6fd}.xpi
Package: firefox-esr
Status: enabled
Name: DOM Inspector
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ins
pec...@mozilla.org
Package: xul-ext-dom-inspector
Status: enabled
Name: Element Hiding Helper for Adblock Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ele
mhidehel...@adblockplus.org
Package: xul-ext-adblock-plus-element-hiding-helper
Status: enabled
Name: English (GB) Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack-en-GB@firefox-esr.mozil
la.org.xpi
Package: firefox-esr-l10n-en-gb
Status: enabled
Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled
Name: Flashblock
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{3d
7eb24f-2740-49df-8937-200b1cc08f8a}
Package: xul-ext-flashblock
Status: enabled
Name: FlashGot
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{19
503e42-ca3c-4c27-b1e2-9cdb2170ee34}
Package: xul-ext-flashgot
Status: enabled
Name: Lightbeam
Location: ${PROFILE_EXTENSIONS}/jid1-f9uj2thwoam...@jetpack.xpi
Status: enabled
Name: Nederlands (NL) Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack-nl@firefox-esr.mozilla.
org.xpi
Package: firefox-esr-l10n-nl
Status: enabled
Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.x
pi
Status: enabled
- -- Plugins information
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: disabled
Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: disabled
Name: Shockwave Flash (11.2.202.632)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled
- -- Addons package information
ii firefox-esr45.3.0esr-1~ amd64Mozilla Firefox web
browser - Ext
ii firefox-esr-l1 45.3.0esr-1~ all English (United Kingdom)
language
ii firefox-esr-l1 45.3.0esr-1~ all Dutch language package
for Firefo
ii gnome-shell3.14.4-1~deb amd64graphical shell for the
GNOME des
ii rhythmbox-plug 3.1-1amd64plugins for rhythmbox
music playe
ii xul-ext-adbloc 2.6.6+dfsg-1 all advertisement blocking
extension
ii xul-ext-adbloc 1.3-1all companion for Adblock
Plus to cre
ii xul-ext-cookie 1.2.0-1 all manage cookies in a
whitelist-bas
ii xul-ext-dom-in 1:2.0.14-1 all tool for inspecting the
DOM of we
ii xul-ext-flashb 1.5.18-1 all Mozilla extension to
block Adobe
ii xul-ext-flashg 1.5.6.7+dfsg all Extension to handle
downloads wit
- -- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG
Bug#826896: still not fixed or pops up again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just saw that I missed the NoScript addon in Firefox, I ran all security updates and it is still missing. In about:addons it is disabled and tells me: NoScript is incompatible with Firefox 45.2.0 I don't know if this is a new issue or that this issue is still not fixed in stable. packages involved: xul-ext-noscript 2.6.9.3-1 firefox-esr 45.2.0esr-1~de Yours, Tjeerd Pinkert -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlec0UcACgkQ9xQaBfeouaoqFwCfcqge0SU5PWF16QUv3Fwv6Fvi LUcAn2gz1bPe/+z5pBK/TLJ7VnGbv0SF =Co86 -END PGP SIGNATURE-
Bug#685436: cheese: CRITICAL **: cheese_camera_device_get_uuid: assertion `CHEESE_IS_CAMERA_DEVICE (device)' failed
Dear maintainers, we had the same bug on our system. It turns out that adding the user to the group video resolves the problem. I think cheese should not crash but report (as one of the other programs did) that the user has no access to the video devices found. Best regards, Tjeerd Pinkert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720107: [cheese] (cheese:20940): Clutter-CRITICAL
Dear maintainers, we get this bug when starting cheese via SSH with X support on a Ubuntu 12.04 LTS machine. The machine where cheese runs is a Debian Stable machine. cheese version: (= 3.4.2-2) Best regards, Tjeerd Pinkert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721763: brltty grabs tty from CP2102/CP2109 device disconnecting default kernel driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15-09-13 21:22, Samuel Thibault wrote: Tjeerd Pinkert, le Tue 03 Sep 2013 22:30:18 +0200, a ￩crit : brltty unexpectedly replaced the default kernel driver with it's own USB Braille terminal driver. Since the Seika Braille reader uses the CP2102/CP2109 default vid/pid, brltty addressed the SPEC board as such. Yes, this is unfortunately *expected*, actually. I conclude, only if the user installed brltty (which is assumed to be on purpose). To resolve the issue I uninstalled the brltty package. Yes, that's the proper way currently. What we would need to understand is how brltty got installed on your system. We don't expect systems without a braille device to have brltty installed. That way, we can make some of these nasty devices actually work easily without workarounds. The bug really is why brltty ended up being installed on your computer. Uhm, yes, good question (blush). There are two possible answers. I have machines running Ubuntu and as a quick way of installing the bulk of the software I use, I have simply installed the packages on my Debian system that dpkg --get-selections gave on the Ubuntu system. While uninstalling brltty on the Ubuntu system I got the message: - --- The following actions will resolve these dependencies: Remove the following packages: 1) brltty-x11 Leave the following dependencies unresolved: 2) ubuntu-desktop recommends brltty - --- so it might have been installed by default on Ubuntu 12.04 LTS? A second Ubuntu system had the brltty package installed too, no *brl* processes running, no ubuntu-desktop dependency complaint on removal. A second possibility is that I might have pulled the package in (having to install new systems lately, going through the huge package list and installing all what seems usefull) myself on the Ubuntu side and then having applied the above copy action. To be sure about this I would need to either reinstall, or find a way of seeing what Ubuntu installs as a minimum. Most probably I'm the fault here. So this means the bug could be closed for Debian, since it is not a fault in the distro, and most probably caused by myself installing something I should not have done, although there is a real problem with some devices which would have solved this on forehand in an ideal world. I have had contact with: The devellopers, among others Eric van der Bij and Tomasz Wlostowski, of the SPEC board, whose strong conviction is that the default kernel driver should be used to yield a ttyUSB device, and that changing to a custom vid/pid for this harware will cause confusion. Why would this cause confusion? This vid/pid designates a serial port converter. Using another vid/pid to more precisely describe the device would be useful. The chip (on the SPEC) is used as serial port, so the defaults are correct. Anyway, the SPEC board is not an isolated case. Whatever serial device, which a user would connect through a USB-to-serial converter, would have just the same issue. Which is crazily crazy. USB has *given* us a way for a device to identify itself in a perfectly safe way, and thus permits to have real safe plugplay support, which was an extremely great addition for the accessibility of the debian installer, for instance. Indeed, one could say it is a manufacturer induced problem, if a device is not meant to be a serial port. Yes, we can't do anything for the already-produced devices, we'll have to live with them. It'd however be really good to manage to convince Seika such that having a separate vid/pid is a really important detail for accessibility everywhere on the long term. That would be best indeed... I have notified them of the bug report here. I hope it is picked up. Maybe active contact from the actual user community would help here? My expectation of the outcome is: the default kernel driver being respected for the default vid/pid of USB to serial convertors, but a possibility to enable the use of brltty if needed will be provided. If possible, clear communication to the blind users of brltty is given on forehand, that specific devices will become disabled because of this issue. This is actually already what we have: brltty is not supposed to be installed on usual systems, and blind users know that they have to install brltty (or get it automatically installed by the installer run in braille mode) in order to get their braille device working. I would argue differently, it can get installed somehow... However, the (Debian?) view on the issue is more clear and I think the bug can thus be closed. Tjeerd -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlI41GoACgkQ9xQaBfeouapDaQCfc2IMZ7WQ9EiOE/7bbU7yVHSy p3cAnixaq8s71iWzEJ4CbCURb0Dc1tA6 =HnXY -END PGP SIGNATURE
Bug#721763: brltty grabs tty from CP2102/CP2109 device disconnecting default kernel driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: brltty Severity: critical Tags: upstream Justification: breaks unrelated software Dear Maintainer, On connecting a CERN SPEC board (see www.ohwr.org White Rabbit project) through it's USB to serial convertor (CP2102/CP2109, vid=10C4h, pid=EA60h) to the system, expecting a ttyUSB device to be installed using the default kernel driver, brltty unexpectedly replaced the default kernel driver with it's own USB Braille terminal driver. Since the Seika Braille reader uses the CP2102/CP2109 default vid/pid, brltty addressed the SPEC board as such. The output of dmesg is given here: [ 3548.128782] usb 3-1.5: new full-speed USB device number 7 using ehci_hcd [ 3548.222649] usb 3-1.5: New USB device found, idVendor=10c4, idProduct=ea60 [ 3548.222654] usb 3-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3548.222657] usb 3-1.5: Product: CP2102 USB to UART Bridge Controller [ 3548.222660] usb 3-1.5: Manufacturer: Silicon Labs [ 3548.222662] usb 3-1.5: SerialNumber: 0001 [ 3548.223562] cp210x 3-1.5:1.0: cp210x converter detected [ 3548.296321] usb 3-1.5: reset full-speed USB device number 7 using ehci_hcd [ 3548.389167] usb 3-1.5: cp210x converter now attached to ttyUSB0 [ 3548.389243] usb 3-1.5: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 3548.389670] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 3548.389691] cp210x 3-1.5:1.0: device disconnected To resolve the issue I uninstalled the brltty package. Withholding brltty from connecting by default to the conflicting USB to serial convertors involved, solves this problem, but seems not easily possible at the moment. As far as the sources concern, the vid/pid combination is found in Drivers/Braille/Seika/braille.c connectResource() function, but also in the Hotplug/udev.rules file. I cannot find the latter installed, and thus assume that the c-code is used. Furtheron I read that alls supported USB devices are enabled by default in the /usr/share/doc/brltty/NEWS.Debian.gz file. If I look at the udev.rules file in the source the news means that this bug presumably also holds for the following devices: # Device: 10C4:EA80 # Generic Identifier # Vendor: Cygnal Integrated Products, Inc. # Product: CP210x UART Bridge # Seika [Note Taker] # Device: 0403:6001 # Generic Identifier # Vendor: Future Technology Devices International, Ltd # Product: FT232 USB-Serial (UART) IC # Albatross [all models] # Cebra [all models] # HIMS [Sync Braille] # HandyTech [FTDI chip] it holds for my device: # Device: 10C4:EA60 # Generic Identifier # Vendor: Cygnal Integrated Products, Inc. # Product: CP210x UART Bridge / myAVR mySmartUSB light # Seika [Braille Display] I had hoped to be able to disable the conflicting device by disabling the brltty udev rules for these devices, which is alas not possible at the moment, since it seems not to be used. I have had contact with: The devellopers, among others Eric van der Bij and Tomasz Wlostowski, of the SPEC board, whose strong conviction is that the default kernel driver should be used to yield a ttyUSB device, and that changing to a custom vid/pid for this harware will cause confusion. Not to mention the problems this would possibly cause in Windows land, since this means programming (and certification) of a custom serial port driver. A develloper, Dave Mielke, of brltty, whose conviction is that the SPEC usage of the default vid/pid is correct, but that brltty should enable as many devices as possible for ease of use by blind people, the Braille devices are their screen. A standpoint that can be understood from his perspective. Dave is investigating if the device can be distinghuished from the default chip via other/additional USB descriptors. The manufacturer, Seika, of the Braille reader, who says the reader can identify itself over the serial bus. No outcome on what is possible with the vid/pid is given up to this moment. Programming a custom serial port driver (and having it certified) on the Windows platform might be a problem in this case too (this is speculative from my side). Although the CP210x chips in principle allow reprogramming, it seems not so easy to solve this problem on the hardware side of the Braille readers, since existing Braille displays are not easily replaced because of their high cost and users might not understand why they should update vid/pid if it could be done in a proper way. My expectation of the outcome is: the default kernel driver being respected for the default vid/pid of USB to serial convertors, but a possibility to enable the use of brltty if needed will be provided. If possible, clear communication to the blind users of brltty is given on forehand, that specific devices will become disabled because of this issue. Yours, Tjeerd Pinkert - -- System Information: Debian Release: jessie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'testing
Bug#673049: gnome-panel: Workspace switcher applet: single colour, no workspaces visible
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have made a screenshot to show the problem. It is attached. The screenshot shows in the rightmost corner (the shell icon) the application switcher and next to it the desktop switcher with 4 desktops. 2 desktops are in use. on the leftmost desktop 2 windows were open (square corner eaten out of the iceweasel icon) and on the one next to it one window. As can be seen, this is somewhat unclear. No difference in colour (the background of my desktop is blue like) between the panel bar and desktops can be seen, thus one has to know that there are 2 more desktops to switch to. The icon backgrounds are somehow ugly black, which I don't care too much about but there is no line around the window representation so it can be unclear how windows are arranged on the workspace switcher. I hope this makes the oddity more clear... Yours, Tjeerd Pinkert -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/CUHYACgkQ9xQaBfeouaoEmQCeL4EzpY6Fusz5Q0VBqi+h06S3 fxEAoJgkiRCGt8Sx4MiQ/dPbL/Zh7mnc =gL4W -END PGP SIGNATURE- attachment: workspace_switcher.png workspace_switcher.png.sig Description: PGP signature
Bug#673049: gnome-panel: Workspace switcher applet: single colour, no workspaces visible
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear package maintainer, The issue is resolved. It appeared that no GTK+ theme was installed causing this issue. After installation of some of the gnome 3 theme packages and selecting a theme via the advanced settings editor (the Adwaita theme) the window switcher has contrasts again. Yours, Tjeerd Pinkert -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/ChgsACgkQ9xQaBfeouarC7QCfSLCvDhAD/NKNevxkQorrHCTd ddEAn02DfBcolvqcjRkNzPOn2CrIkplw =cmnT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648394: gnome: allow workspaces allocation in a static way
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I agree fully with the author of this bug. Static workspaces, quick launch buttons, applets etc. as one used to have in the Gnome 2 panel should in my oppinion be supported by default before the Gnome 3 desktop can move on to Stable release. The standard reply that it will not be supported because of a religious kind of desktop philosophy that must be adhered to according to the Gnome authors, will in my opinion not work for many people who are used to years of Gnome 2 with an in my opinion very well working panel and desktop philosophy attached. To add my whishlist then: - - ability to move stuff around in the top panel bar. - - ability to remove stuff from the top panel bar. - - ability to add things like a desktop switcher applet and window list applet (these do not have to be applets but I liked the functionality) - - ability to run one's own WM (always had sawfish with the handy close button on the left of the window) I think I will get used to the visual bling bling of the new thing but the basic behaviour of Gnome 2 should be there and relatively easily to access (or even copied from one's Gnome 2 configuration?) off topic: - -- The reason I reply to this, after an unheeded update of Testing my desktop looks and feels very different to what I was used to the last approx. 6 years. This has taken now already three afternoons of my valuable (fortuanately holiday) time to sort out that there is no choice to change the behaviour as far as the Gnome team is concerned. Very disappointing because Gnome was actually the first properly working and easily configurable desktop environment that I encountered on Linux and I have stuck to it almost from the beginning (just as the Debian distro, good work!). yours, Tjeerd Pinkert -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk71U6EACgkQ9xQaBfeouaqCswCaAliYBqmcrpzX7YL33pp2lKlj sz4AnA90rsy0oR4S8CboL5hyCdW1w7hi =Dhih -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#381109: Check dependencies and code?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I find that sawfish-ui does not start. Initially exec rep $0 $@ (line 8 of /usr/bin/sawfish-ui script) failed, I needed to install the rep package (is not in dependencies) After that: $ sawfish-ui *** Unbound variable: gtk-preview-new (You're accessing an undefined variable or function `gtk-preview-new') So I confirm the report of Ian Zimmerman. Yours, Tjeerd Pinkert -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyLaA4ACgkQ9xQaBfeouaqcdQCdE5Bj8CZ0OmccDs/5xK0W3rET H5gAoIznBj9dKSrcW+4hHADs63fHncPt =4cK0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571714: apache 2.2.14 doesn't parse php5 in public_html
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I noticed the same (already a while ago, but had no pressing need to fix it, until today I had some time). For me the problem still exists after commenting out the lines in /etc/apache2/mods-available/php5.conf. I restarted the server, php works in the wwwroot /var/www/ but not in the userdirs. I purged all apache2 stuff, did a fresh install of only the server and the libapache2-mod-php5 package. I enabled userdirs to work and commented the lines in /etc/apache2/mods-available/php5.conf. again the same result, php works in wwwroot but not in the user dirs. Did I overlook anything? or what could go wrong here? Yours, Tjeerd -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvhrt8ACgkQ9xQaBfeouaosOACfWFaRuB4jNTu2pUe5yx0SHPzA rXwAnipSIgA9Y7Orn2tkG0oRd2Y3VKwk =0Ah0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#431661: although mounted as root I could write to the fs on existing files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I experienced the same problem that the fs was mounted as root although smbmount was called as user. I noted also that I could make changes to the files being on the mounted fs, although they were r-x for group and world... I could however not make files or directories. The fileserver here is Windows 2003 server, but I have no further control over it since I'm only a user. Yours, Tjeerd -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGkhCZ1BoqZaj+NmYRAgc1AJ48xT0Y4eiezkc0wvlAOo2hTW7RagCeJD+u uU3aENZosipRDjyXMmysIR4= =7dBy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366552: not due to compiler
Hello, Ran into this as well. Looking in the older kernel tree header files we see that the call MODULE_PARM is depricated. I found: http://www.uwsg.iu.edu/hypermail/linux/kernel/0410.1/0248.html in which the following replacements are made: - MODULE_PARM(any, i); + module_param(any, int, 0644); also for the others... this appears to work. Groetjes, Tjeerd -BEGIN GEEK CODE BLOCK- Version: 3.1 GE/FA/MU/S d-(++)/!x/!!@ s+: a-/? C UL+ P L+++ E--- W++(+++)-- N+++ o? K-/!+ w- O? M V? PS(---)@ PE Y+++ PGP--+++ t+ 5 X-- R-- !tv b+ DI(+) D-- G++ e+ h/-- r--+++ y- --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315339: update to lvm2 2.02.05-1 renders striped vg unusable
Package: lvm2
Version: 2.02.05-1
Installing version 2.02.05-1 from the lvm2 package makes my striped VG
unreadable (the other vg does well), downgrading to 2.01.04-5 fixes the
problem.
I can not give you the exact outcome of the vgdisplay but it gave about
the same outcome as in the report of Igor Belyi, Tue, 28 Jun 2005
19:11:49 -0400 (this appears to be the same problem), but some other name
of the volume and other counter numbers (most probably 547 != 1094).
I would say it looked like (i can get you this but than I have to render
my system 'unusable' first):
# vgdisplay datavolume
LV backup: inconsistent LE count 547 != 1094
Internal error: LV segments corrupted in backup.
Volume group datavolume doesn't exist
now it says (with 2.01.04-5):
# vgdisplay datavolume
--- Volume group ---
VG Name datavolume
System ID muziekje1075727894
Formatlvm1
VG Access read/write
VG Status resizable
MAX LV256
Cur LV1
Open LV 1
Max PV256
Cur PV2
Act PV2
VG Size 34.19 GB
PE Size 32.00 MB
Total PE 1094
Alloc PE / Size 1094 / 34.19 GB
Free PE / Size 0 / 0
VG UUID elbhhh-3TS6-Qhju-ie78-13sj-rGG4-euaOEr
Attached is the /etc/lvm/backup/datavolume config file.
Tjeerd Pinkert# Generated by LVM2: Fri Jun 9 20:23:34 2006
contents = Text Format Volume Group
version = 1
description = Created *after* executing '/sbin/vgcfgbackup'
creation_host = 171-248 # Linux 171-248 2.4.27-2-686 #1 Wed Nov 30
21:55:37 JST 2005 i686
creation_time = 1149877414 # Fri Jun 9 20:23:34 2006
datavolume {
id = elbhhh-3TS6-Qhju-ie78-13sj-rGG4-euaOEr
seqno = 0
status = [RESIZEABLE, READ, WRITE]
system_id = muziekje1075727894
extent_size = 65536 # 32 Megabytes
max_lv = 256
max_pv = 256
physical_volumes {
pv0 {
id = Ush8FJ-H4LE-xbKX-0fJw-Xc4Y-56RK-4qhBiw
device = /dev/sdb # Hint only
status = [ALLOCATABLE]
pe_start = 65920
pe_count = 547 # 17.0938 Gigabytes
}
pv1 {
id = Xi1Ige-rycC-LUjf-NKwb-snYC-1s48-OdwCYU
device = /dev/sdc # Hint only
status = [ALLOCATABLE]
pe_start = 65920
pe_count = 547 # 17.0938 Gigabytes
}
}
logical_volumes {
dataschijf {
id = 00------00
status = [READ, WRITE, VISIBLE]
allocation_policy = normal
read_ahead = 64
segment_count = 1
segment1 {
start_extent = 0
extent_count = 1094 # 34.1875 Gigabytes
type = striped
stripe_count = 2
stripe_size = 256 # 128 Kilobytes
stripes = [
pv0, 0,
pv1, 0
]
}
}
}
}
