Re: Re: Recommended way to use Debian?
Thanks everyone for your help, it does indeed look like I'm having graphics issues thanks to Optimus. Plasma suddenly died on me just now (or atleast that's what I thought happened) and after looking into Xorg.0.log I saw that actually my Intel GPU had crashed! Hence why I couldn't see Plasma decorations. So I'll email that pkg-nvidia-devel list, maybe the Bumblebee guys are interested and if not I'll send my crash report to Intel. Even though it was my Intel GPU that was crashing every day, not my NVIDIA GPU, I switched to Bumblebee in wheezy-backports 2 weeks ago and now my computer hasn't crashed at all since then! I even re-installed PulseAudio successfully, so I'm now a very happy Debian Stable KDE user! Thanks everyone for your help 2 weeks ago! Cheers, Shervin Emami.
Re: Re: Recommended way to use Debian?
On Monday 15 July 2013 11:24:28 Shervin Emami wrote: I'm using the NVIDIA driver from Debian Stable, but since I have Optimus (both an Intel NVIDIA GPU), it would be using the Intel driver for normal display, and I made it use Mesa as the default GL library for this reason. So maybe my problems are related to Optimus, I wouldn't be surprised :-( I wouldn't be surprised if Optimus is indeed one/the source of your problems. To determine whether that is indeed the case, you'd probably want to write an email to the nvidia devel ML (http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-nvidia-devel) for that. AFAIK the bumblebee maintainers are also subscribed to that list. HTH -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Re: Re: Recommended way to use Debian?
Thanks everyone for your help, it does indeed look like I'm having graphics issues thanks to Optimus. Plasma suddenly died on me just now (or atleast that's what I thought happened) and after looking into Xorg.0.log I saw that actually my Intel GPU had crashed! Hence why I couldn't see Plasma decorations. So I'll email that pkg-nvidia-devel list, maybe the Bumblebee guys are interested and if not I'll send my crash report to Intel. Cheers, Shervin Emami. http://www.shervinemami.info/openCV.html On Wed, Jul 17, 2013 at 4:36 AM, Diederik de Haas didi.deb...@cknow.orgwrote: On Monday 15 July 2013 11:24:28 Shervin Emami wrote: I'm using the NVIDIA driver from Debian Stable, but since I have Optimus (both an Intel NVIDIA GPU), it would be using the Intel driver for normal display, and I made it use Mesa as the default GL library for this reason. So maybe my problems are related to Optimus, I wouldn't be surprised :-( I wouldn't be surprised if Optimus is indeed one/the source of your problems. To determine whether that is indeed the case, you'd probably want to write an email to the nvidia devel ML ( http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-nvidia-devel) for that. AFAIK the bumblebee maintainers are also subscribed to that list. HTH -- GPG: 0x138E41915C7EFED6
Re: Recommended way to use Debian?
I use skype and pulseaudio in Debian Wheezy. I just recently started using pulseaudio and I like it, especially since I have 2 sound cards and I like to have System and Skype sounds go through my analog output while my music going through a digital output. What I have observed, however, is that sometimes pulseaudio just stops working, and when that happens any other program that needs sound just freezes instead of making sounds. It becomes a cascading effect of frozen apps that won't work even after restarting them. It happens often when I receive an IM (which results in a system sound) while I am talking on Skype. I believe this is a bug in how Skype uses Pulse, or a bug in Pulse, but in either case, there is an instability in this particular combination of software that forces me to either logout/login again to KDE, or to reboot. Restarting pulse doesn't do it for me. I did not observe this instability until I started using pulseaudio. If Skype uses Alsa directly, it seems to be more stable. On Mon, Jul 15, 2013 at 11:24 AM, Shervin Emami shervin.em...@gmail.comwrote: I'm using the NVIDIA driver from Debian Stable, but since I have Optimus (both an Intel NVIDIA GPU), it would be using the Intel driver for normal display, and I made it use Mesa as the default GL library for this reason. So maybe my problems are related to Optimus, I wouldn't be surprised :-( I work for NVIDIA and yet even I have numerous software hardware troubles due to Optimus! I'll try using the latest NVIDIA driver, supposedly it has some Optimus support now so it doesn't need Bumblebee anymore. Cheers, Shervin Emami. http://www.shervinemami.info/openCV.html On Mon, Jul 15, 2013 at 10:51 AM, Facundo Aguilera budin...@gmail.comwrote: On Mon, Jul 15, 2013 at 2:14 AM, Shervin Emami shervin.em...@gmail.com wrote: I'm even using the Debian Stable packages for NVIDIA GPU and CUDA toolkit and OpenGL. ... Are you using the nvidia driver or nouveau? I had similar problems with nouveau and desktop effects enabled. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPYB0ABaVE=yg5jjy6ruhbfuksg_794oc6psznku0va+da_...@mail.gmail.com
Re: Recommended way to use Debian?
On 07/15/2013 01:14 PM, Shervin Emami wrote: Hi, Any recommendations on how to get more stability? Because I really want to stick with Debian KDE for long-term. As far as iceweasel crashing, I think that's really bizarre.. I use it everyday for years on lots of different hardware and it's *never* crashed for me. To add to that, the Mozilla/Iceweasel/Firefox team have been very good at blacklisting graphics drivers that don't support hardware accelerated webgl, etc. So you really shouldn't be getting crashes for any reason. I would suggest investigating the possibility of hardware failure (memtest86+, cpu/gpu stress tests, etc). I've also found repeatable bugs that crash apps such as Kate and Inkscape but when I start to file bug reports I realize I shouldn't because Debian Stable is using old versions of the software and these bugs were fixed in later versions Yes, I've had repeatable crashes with Kate related to collapsing/expanding sections of code in .patch files which I found and reported to upstream back before Debian Wheezy was even frozen. It took almost a year and 50+ duplicate bug reports before it was fixed by Kate devs, and the fix missed the Wheezy freeze window. That's just the way things are sometimes with upstream, you either learn to use the software in a way that doesn't cause it to crash until they fix it, you learn to fix it yourself and submit a patch, or you use something else because there are about a million great alternatives to Kate. As a Debian user for 10+ years, I would suggest just running Debian stable for now and grab newer versions of software if you need it from wheezy-backports (if available). Sometimes you can apt-get source the package source from unstable and recompile it yourself for stable. I did that just now for Inkscape 0.48.4-1 (unstable) and the package installs and runs perfectly fine on Wheezy. If your troubles in inkscape still aren't fixed, make sure you get them reported to upstream. -David -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51e3995d.5050...@gmail.com
Re: Recommended way to use Debian?
Thanks Rubin David for the replies. Unfortunately I need Skype, VirtualBox, Oracle JDK and NVIDIA CUDA Toolkit, I need those many times each day for my work as a remote developer. I'd love to get rid of Flash, so just now I switched YouTube to use WebM instead (go to http://www.youtube.com/html5;) as a start. But when I experience browser crashes, it's not while doing anything strange like watching youtube so I don't think Flash is my problem. Maybe when Dolphin or Plasma or Iceweasel crash it really is a problem with my RAM hardware (I put 16GB RAM in my laptop since i often build Android from source and often use WinXP through VirtualBox), possibly related to the fact I use 5GB of RAM as a ramdisk where I do lots of my temp stuff in. For the repeatable bugs I found in Kate Inkscape, you guys convinced me I should file the bug reports and then find ways to live around the bugs for the near future. I sent a message to this group recently about the Kate crash because I wasn't sure how to report it, but no-one replied: http://lists.debian.org/debian-kde/2013/06/msg00014.html;. For the Inkscape crash i tested it on Mint KDE 14, Mint KDE 13 and ArchLinux and none of those crashed, only Debian Stable, and only while using OpenGL as the KWin renderer (ie: it doesn't crash while using XRender), so I'm also a bit confused about whether to file a bug to Debian or to Inkscape, since it seems to have been fixed in recent versions of Inkscape. I haven't looked into back-porting packages yet since I read on the Debian FAQ that you shouldn't mix both Stable and Testing in your apt source list, but now I realize back-porting is a way to compile new Testing or SID software packages into the equivalent of Stable packages without modifying my apt sources (or am I wrong?). So from you guys it sounds like I should back-port Inkscape Skype NVIDIA driver CUDA Toolkit, since it is possible that my sudden Plasma crashes or Inkscape crashes are related to the Wheezy's older NVIDIA display driver interacting strangely with Optimus technology (dual GPU). Cheers, Shervin Emami. http://www.shervinemami.info/openCV.html On Sun, Jul 14, 2013 at 11:40 PM, David Smith sidic...@gmail.com wrote: On 07/15/2013 01:14 PM, Shervin Emami wrote: Hi, Any recommendations on how to get more stability? Because I really want to stick with Debian KDE for long-term. As far as iceweasel crashing, I think that's really bizarre.. I use it everyday for years on lots of different hardware and it's *never* crashed for me. To add to that, the Mozilla/Iceweasel/Firefox team have been very good at blacklisting graphics drivers that don't support hardware accelerated webgl, etc. So you really shouldn't be getting crashes for any reason. I would suggest investigating the possibility of hardware failure (memtest86+, cpu/gpu stress tests, etc). I've also found repeatable bugs that crash apps such as Kate and Inkscape but when I start to file bug reports I realize I shouldn't because Debian Stable is using old versions of the software and these bugs were fixed in later versions Yes, I've had repeatable crashes with Kate related to collapsing/expanding sections of code in .patch files which I found and reported to upstream back before Debian Wheezy was even frozen. It took almost a year and 50+ duplicate bug reports before it was fixed by Kate devs, and the fix missed the Wheezy freeze window. That's just the way things are sometimes with upstream, you either learn to use the software in a way that doesn't cause it to crash until they fix it, you learn to fix it yourself and submit a patch, or you use something else because there are about a million great alternatives to Kate. As a Debian user for 10+ years, I would suggest just running Debian stable for now and grab newer versions of software if you need it from wheezy-backports (if available). Sometimes you can apt-get source the package source from unstable and recompile it yourself for stable. I did that just now for Inkscape 0.48.4-1 (unstable) and the package installs and runs perfectly fine on Wheezy. If your troubles in inkscape still aren't fixed, make sure you get them reported to upstream. -David
Re: Recommended way to use Debian?
On Monday, 2013-07-15, Shervin Emami wrote: I experience crashes around once per day, either as a software like Iceweasel or Kate or Dolphin crashing or as KDE/Plasma crashing requiring me to hit Alt+PrtSc+K to close X log back in to KDE. I've also found If Plasma Desktop crashes it can usually be restarted using Alt-F2 and typing plasma-desktop. Hasn't happend for me in ages, so maybe it is one of the applets you are using? Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Re: Recommended way to use Debian?
Shervin Emami wrote, On 2013-07-15 00:25: Unfortunately I need Skype, VirtualBox, Oracle JDK and NVIDIA CUDA Toolkit, I need those many times each day for my work as a remote developer. I'd love to get rid of Flash, so just now I switched YouTube to use WebM instead (go to http://www.youtube.com/html5;) as a start. But when I experience browser crashes, it's not while doing anything strange like watching youtube so I don't think Flash is my problem. Maybe when Dolphin or Plasma or Iceweasel crash it really is a problem with my RAM hardware (I put 16GB RAM in my laptop since i often build Android from source and often use WinXP through VirtualBox), possibly related to the fact I use 5GB of RAM as a ramdisk where I do lots of my temp stuff in. First option is since you've already got VirtualBox setup, setup a VM for Skype and other tricky software. Flash is EVERYWHERE, no joke. When you're running your web browser, open up a terminal window and run top (or better yet htop) and sort by CPU usage. You'll see Flash pop up a bunch, not just YouTube vids. There are some great plugins that'll ask you before starting up any Flash content, might be worth checking out. If you want to test your ram, apt-get install memtest86+, reboot, select it in GRUB, and let that thing run over night. For the repeatable bugs I found in Kate Inkscape, you guys convinced me I should file the bug reports and then find ways to live around the bugs for the near future. I sent a message to this group recently about the Kate crash because I wasn't sure how to report it, but no-one replied: http://lists.debian.org/debian-kde/2013/06/msg00014.html;. For the Inkscape crash i tested it on Mint KDE 14, Mint KDE 13 and ArchLinux and none of those crashed, only Debian Stable, and only while using OpenGL as the KWin renderer (ie: it doesn't crash while using XRender), so I'm also a bit confused about whether to file a bug to Debian or to Inkscape, since it seems to have been fixed in recent versions of Inkscape. Unless told specifically to do so by a project community, file bugs in a tracker over sending an issue to a mailing list. Mailing lists are good for disucssing current thing, bug trackers are good for recording a history and it's eventually resolution (or ignorance). Unless you want to ask a community if you shouldn't file a bug (never ask if you should, because you'll fall into that no one will reply trap). -- Rubin ru...@starset.net signature.asc Description: OpenPGP digital signature
Re: Recommended way to use Debian?
Yes I do this to restart Plasma when it crashes every few days. I am using the NetworkManager applet, and that is well known to have many issues, so that might be partly to blame. But other times when my computer crashes, not even Ctrl+Alt+Del or Ctrl+Alt+BkSpace work, and sometimes Ctrl+Alt+1 works so I can kill a bad app, but often the only key combo that works at all is Alt+PrtSc+K! Cheers, Shervin Emami. http://www.shervinemami.info/openCV.html On Mon, Jul 15, 2013 at 12:28 AM, Kevin Krammer kevin.kram...@gmx.atwrote: On Monday, 2013-07-15, Shervin Emami wrote: I experience crashes around once per day, either as a software like Iceweasel or Kate or Dolphin crashing or as KDE/Plasma crashing requiring me to hit Alt+PrtSc+K to close X log back in to KDE. I've also found If Plasma Desktop crashes it can usually be restarted using Alt-F2 and typing plasma-desktop. Hasn't happend for me in ages, so maybe it is one of the applets you are using? Cheers, Kevin
Re: Recommended way to use Debian?
Hoi: I'd say the problem may well be somewhere in the graphics stack. Once you have a crash it's quite convenient knowing exactly where it happenned and getting a backtrace of it. Check ~/.xsession-erros and also Xorg log (/var/log/Xorg.[01].log or /var/log/Xorg.[01].log.old if a new X instance already fired up), sometimes kdm.log also helps. If you want further information, install relevant -dbg packages: xserver, x video driver, mesa and drm. Once you have this installed make sure you enabled core dumps. I do this adding ulimit -c unlimited somewhere at the begginning of /etc/init.d/kdm script. If X crashes you'll get a core dump at /etc/X11/core which you can later analyze with gdb /etc/X11/core $(which Xorg) Good luck with this. Regards, On Mon, Jul 15, 2013 at 01:39:07AM -0700, Shervin Emami wrote: Yes I do this to restart Plasma when it crashes every few days. I am using the NetworkManager applet, and that is well known to have many issues, so that might be partly to blame. But other times when my computer crashes, not even Ctrl+Alt+Del or Ctrl+Alt+BkSpace work, and sometimes Ctrl+Alt+1 works so I can kill a bad app, but often the only key combo that works at all is Alt+PrtSc+K! Cheers, Shervin Emami. http://www.shervinemami.info/openCV.html On Mon, Jul 15, 2013 at 12:28 AM, Kevin Krammer kevin.kram...@gmx.at wrote: On Monday, 2013-07-15, Shervin Emami wrote: I experience crashes around once per day, either as a software like Iceweasel or Kate or Dolphin crashing or as KDE/Plasma crashing requiring me to hit Alt+PrtSc+K to close X log back in to KDE. I've also found If Plasma Desktop crashes it can usually be restarted using Alt-F2 and typing plasma-desktop. Hasn't happend for me in ages, so maybe it is one of the applets you are using? Cheers, Kevin -- Raúl Sánchez Siles -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130715090040.GA11306@trismegisto.universo
Re: Recommended way to use Debian?
In data domenica 14 luglio 2013 22:14:41, Shervin Emami ha scritto: Any recommendations on how to get more stability? Did you try to create a new account? regards -- Marco Valli -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6608449.cqbAgz0cB6@debian
Re: Recommended way to use Debian?
First option is since you've already got VirtualBox setup, setup a VM for Skype and other tricky software. I already tried following numerous forums about getting microphone webcam to work in VirtualBox, some people have been successful but I just couldn't get it to work for WinXP or Ubuntu guests, maybe since I'm using ALSA instead of PulseAudio. So I'll give up for now and stick with native Skype on Linux. Flash is EVERYWHERE, no joke. Yeah I know, I use Flashblock in my browser to keep Flash at bay. file bugs in a tracker over sending an issue to a mailing list. No worries, but should I report the bug to Debian or to the apps (Inkscape and KDE/Kate), since I am technically using outdated versions of these software? Cheers, Shervin Emami. http://www.shervinemami.info/openCV.html On Mon, Jul 15, 2013 at 12:36 AM, Rubin Abdi ru...@starset.net wrote: Shervin Emami wrote, On 2013-07-15 00:25: Unfortunately I need Skype, VirtualBox, Oracle JDK and NVIDIA CUDA Toolkit, I need those many times each day for my work as a remote developer. I'd love to get rid of Flash, so just now I switched YouTube to use WebM instead (go to http://www.youtube.com/html5;) as a start. But when I experience browser crashes, it's not while doing anything strange like watching youtube so I don't think Flash is my problem. Maybe when Dolphin or Plasma or Iceweasel crash it really is a problem with my RAM hardware (I put 16GB RAM in my laptop since i often build Android from source and often use WinXP through VirtualBox), possibly related to the fact I use 5GB of RAM as a ramdisk where I do lots of my temp stuff in. First option is since you've already got VirtualBox setup, setup a VM for Skype and other tricky software. Flash is EVERYWHERE, no joke. When you're running your web browser, open up a terminal window and run top (or better yet htop) and sort by CPU usage. You'll see Flash pop up a bunch, not just YouTube vids. There are some great plugins that'll ask you before starting up any Flash content, might be worth checking out. If you want to test your ram, apt-get install memtest86+, reboot, select it in GRUB, and let that thing run over night. For the repeatable bugs I found in Kate Inkscape, you guys convinced me I should file the bug reports and then find ways to live around the bugs for the near future. I sent a message to this group recently about the Kate crash because I wasn't sure how to report it, but no-one replied: http://lists.debian.org/debian-kde/2013/06/msg00014.html;. For the Inkscape crash i tested it on Mint KDE 14, Mint KDE 13 and ArchLinux and none of those crashed, only Debian Stable, and only while using OpenGL as the KWin renderer (ie: it doesn't crash while using XRender), so I'm also a bit confused about whether to file a bug to Debian or to Inkscape, since it seems to have been fixed in recent versions of Inkscape. Unless told specifically to do so by a project community, file bugs in a tracker over sending an issue to a mailing list. Mailing lists are good for disucssing current thing, bug trackers are good for recording a history and it's eventually resolution (or ignorance). Unless you want to ask a community if you shouldn't file a bug (never ask if you should, because you'll fall into that no one will reply trap). -- Rubin ru...@starset.net
Re: Recommended way to use Debian?
On Mon, Jul 15, 2013 at 2:14 AM, Shervin Emami shervin.em...@gmail.com wrote: I'm even using the Debian Stable packages for NVIDIA GPU and CUDA toolkit and OpenGL. ... Are you using the nvidia driver or nouveau? I had similar problems with nouveau and desktop effects enabled. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPYB0ABaVE=yg5jjy6ruhbfuksg_794oc6psznku0va+da_...@mail.gmail.com
Re: Recommended way to use Debian?
I'm using the NVIDIA driver from Debian Stable, but since I have Optimus (both an Intel NVIDIA GPU), it would be using the Intel driver for normal display, and I made it use Mesa as the default GL library for this reason. So maybe my problems are related to Optimus, I wouldn't be surprised :-( I work for NVIDIA and yet even I have numerous software hardware troubles due to Optimus! I'll try using the latest NVIDIA driver, supposedly it has some Optimus support now so it doesn't need Bumblebee anymore. Cheers, Shervin Emami. http://www.shervinemami.info/openCV.html On Mon, Jul 15, 2013 at 10:51 AM, Facundo Aguilera budin...@gmail.comwrote: On Mon, Jul 15, 2013 at 2:14 AM, Shervin Emami shervin.em...@gmail.com wrote: I'm even using the Debian Stable packages for NVIDIA GPU and CUDA toolkit and OpenGL. ... Are you using the nvidia driver or nouveau? I had similar problems with nouveau and desktop effects enabled. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPYB0ABaVE=yg5jjy6ruhbfuksg_794oc6psznku0va+da_...@mail.gmail.com
Recommended way to use Debian?
Hi, I switched to Debian 7.0 Wheezy Stable (KDE) AMD64 as my main OS for work home for the past 2 months, because I love KDE but was annoyed with how often Linux Mint KDE would suddenly crash and need me to logout log back in to KDE. I chose Debian Stable as the most stable KDE option, and yet it still seems unstable for me. Perhaps its the combination of some software I'm often using (Skype, Oracle Java, Adobe Flash, VirtualBox) or my Ghost-Deco KDE Window Decoration or my laptop's NVIDIA/Intel Optimus GPU. But I've used the official Debian stable package for everything I'm using except Skype, Oracle JDK, Flash and Truecrypt. I'm even using the Debian Stable packages for NVIDIA GPU and CUDA toolkit and OpenGL. I also had initial problems with audio until I removed every possible piece of PulseAudio I could find while still allowing Skype, so I'm not sure exactly what is causing my instability but it feels like multiple bugs, not just one. I experience crashes around once per day, either as a software like Iceweasel or Kate or Dolphin crashing or as KDE/Plasma crashing requiring me to hit Alt+PrtSc+K to close X log back in to KDE. I've also found repeatable bugs that crash apps such as Kate and Inkscape but when I start to file bug reports I realize I shouldn't because Debian Stable is using old versions of the software and these bugs were fixed in later versions, so I assume nothing else can be done. So I get the impression I would have more stability if I used Debian Testing in the hope that newer software drivers have fixed the bugs I'm often experiencing, but I've only used Debian for 2 months so I'm not sure if I should be back-porting newer versions to my system or what. Any recommendations on how to get more stability? Because I really want to stick with Debian KDE for long-term. Cheers, Shervin Emami.
Re: Recommended way to use Debian?
First off I would say simply try apt-get removing most of the odd 3rd party peices of software you listed in your email. Particularly Skype and Flash. See if you can go a few days without either of them. Next step would be simply to try a more recenter kernel (though honestly 3.2.0 is fairly stable on most of the machine I've got Wheezy running on right now). You can read up about Debian Backports or simply learn about compiling your own. Google should provide a multitude of guides on either subject. I would not recommend jumping to Jessie (Debian Testing) just yet, maybe hold off another month or two for folks to get past the fanfare of a new stable release happening. I think you'll find much of the same as Stable except with the few newer things being slightly broken in some special way. Keep in mind that Stable was Testing as of a few months ago, it's still fairly fresh or so they say. Currently I'm running Debian Sid (no Flash, Oracle Java, Skype), which in all honesty has provided me with less stability problems over the past year, but more ho crap apt-get dist-upgrade just puked all over everything! issues to deal with than you'll find in Jessie or less so with Wheezy. Your milage and want to sysadmin your own machine may vary. Also a note about bugs, you should always file bugs, always always always, regardless of what version you're running, always. But only after you do a quick search to make sure your issue hasn't already been filed. Always file bugs, even for the old stuff. Noting it down is better than not, it might help with fixing a similar bug in the future. And remember kids, filing good bug reports is half the contributing to FOSS battle! -- Rubin ru...@starset.net signature.asc Description: OpenPGP digital signature
