It seems I forgot to mention cupsd print-server, printing was not workable upon
upgrading.
au2 = 'aptitude update && aptitude upgrade':
> root@t555:~# au2
> Get: 1 http://security.debian.org stretch/updates InRelease [63.0 kB]
> Ign http://ftp2.de.debian.org/debian stretch InRelease
> Get: 2
In my particular case this is about DSA-signatures in Thunderbird with
Enigmail. These are
very slow to re-check for messages with large attachments. I have a low-end
25-W PC only
some notebooks and other embedded devices may also be affected by this problem.
When there are 3 to 4 compute-cores
go devoid of
their
data-integrity and one might well give away code-reliability for speed. That is
of course
not recommendable.
> Forwarded Message
> Subject: Fwd: Enigmail is very slow to check signatures
> Date: Sat, 14 Oct 2017 09:58:00 +0200
> From: And
Package: enigmail
Version: 2:1.9.8.1-1~deb9u1
Severity: minor
Dear Maintainer,
> Forwarded Message
> Subject: Fwd: Enigmail is very slow to check signatures
> Date: Sat, 14 Oct 2017 09:58:00 +0200
> From: Andreas Glaeser <andreas.glae...@irregulaire.info>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.63
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was
in asymmetric
configurations at least from my own experience.
Please don't try to shine your communication-problems by giving me incorrect
facts.
On Thu, 16 Mar 2017 10:07:05 -0300
Felipe Sateler <fsate...@debian.org> wrote:
> On Thu, Mar 16, 2017 at 5:09 AM, Andreas Glaeser
> <bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now I was sitting down again to install without md-raid and without XFS-root.
I can reconfirm, that the described problem does not appear with BTRFS-raid
only:
> /dev/sda5 btrfs 46872576 2298224 44044944 5% /
> udev devtmpfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk
tible with
> OpenChrome,
> you may want to download, compile, and install the latest OpenChrome code.
> This post I
> made while back is very detailed, so you should not have issues installing
> the latest
> OpenChrome code.
>
> https://lists.freedesktop.org/archives/opench
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is some improvement visible regarding openchrome video-diver,
particularly, there
is no xorg.conf necessary any more in order to make use of the VESA-driver, but
obviously
X falls back to VESA automatically, which is positive in my opinion,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It probably does not make much sense to keep old wishlist-items.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlhSfVYACgkQ5+rBHyUt5wvR4ACgsr4OM0J5nYZika9Ogq2O2qPY
IZQAoKWfcBw47bNdZDEZVQcfRI2yzwE/
=BDAE
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The third possbility is, things remain unfixed, which I do not hope.
Begin forwarded message:
Date: Wed, 14 Dec 2016 16:38:47 +0100
From: Andreas Glaeser <bugs.andreas.glae...@freenet.de>
To: Pedro Beja <altha...@gmail.com>
Subject
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not using this box anymore, since unexpectedly it worked without any major
problem to
port the EWP-appliance to FreeBSD 10.3.
Currently making a clean KVM-image of XEWP in KVM/virt-manager.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey there,
I have been sitting down in front of my PC and this is the result [RECOMPDF]:
> #!/bin/bash
> fname=$1 #take input-arguments
> jqual=$2 #first is the filename, second is the
> JPG-quality-value
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PDFTK also leaves the files unchanged, exactly as libreoffice does, another
possibilty
could be qpdf:
> andrew@a68n:~/Documents/SCAN$ qpdf --help
>
> Usage: qpdf [ options ] { infilename | --empty } [ outfilename ]
>
> An option summary appears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No, idea, what linked or embedded images might be in PDF, I guess, it's rather
the
latter.
I am simply using simple-scan and save a few pages directly as PDF.
But you are right of course, I can just as well use pdftk for re-compressing
the
at 06:16:56PM +0200, Andreas Glaeser wrote:
> > Yeah, anyway, the problem exists in Stretch, it has nothing to do with
> > stable-dependencies vs. testing-dependencies:
>
> Yes, I already said so, basically and marked the bug as-such.
>
> > Now this should really sat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 12 Oct 2016 15:53:48 +0200
Rene Engelhard <r...@debian.org> wrote:
> Hi,
>
> On Wed, Oct 12, 2016 at 03:10:47PM +0200, Andreas Glaeser wrote:
> > If I am getting things correctly, the backported version is identi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.62
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 10 Oct 2016 09:32:34 +0200
Rene Engelhard <r...@debian.org> wrote:
> found 840087 1:5.2.2~rc2-2
> tag 840087 + moreinfo
> thanks
>
> Hi,
>
> On Sat, Oct 08, 2016 at 10:17:20AM +0200, Andreas Glaeser wrote:
> &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: libreoffice-draw
Version: 1:5.2.2~rc2-2~bpo8+1
Severity: minor
Dear Maintainer,
there appeared a new version of the LibreOffice suite from Backports today.
LibreOffice-Draw fails to compress multipage-PDFs, it just makes a copy of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
Date: Tue, 27 Sep 2016 12:11:34 +
From: "nautilus" (GNOME Bugzilla)
To: bugs.andreas.glae...@freenet.de
Subject: [Bug 766557] nautilus: file-manager settings regarding behaviour have
no effect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: e17
Version: 0.17.6-1
Severity: minor
Dear Maintainer,
e17 had filemanager-problems for quite some time, I think they were fixed in
the 32-bit
version first, also seems to work OK in the AMD64-version now, but the problem
is still
there,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://savannah.gnu.org/bugs/?43379
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlcrTssACgkQ5+rBHyUt5wsFmACeMxkpcBkfZaCkzpd7zgS+sAlT
O8IAn05Qp+dUe/mPwk/CrQZf6UA7tPuQ
=am2+
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I retried this with the current netinstall-image from 2016-05-02,
using the internal ATA-flash-memory of the PC as /boot/-partition, but it
doesn't work
either, since GRUB cannot mount the filesystem-root.
It might be related to these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820806
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlcNDUIACgkQ5+rBHyUt5wtdcACgoln5wrsPp2QTy+iZu3jV2XWG
fV4AoJEU7MMMDewbKGv4Pq9LkeZZ71Eu
=QpyN
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since your installation-report was from before the Jessie-release, the issue
has probably
been fixed in the meantime.
If so, then please close the report-ticket yourself by sending e-mail to:
765552-d...@bugs.debian.org
giving a few explanatory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can you retry with the current stable release or with current debian-testing??
Possibly you need to set the BIOS to legacy mode, some UEFI-implementations are
buggy.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What about your report??
Did you still experience any problems, when Jessie was released stable ??
Or with the current testing-branch ??
If you think the problem is resolved in the meanwhile, you can close the ticket
yourself
by sending E-mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Apr 2016 12:15:57 -0700
Andrew Kurn wrote:
> Dear Andreas,
>
> In my turn, I don't understand how to work around a non-bootable
> installer image. Believe me, I booted the way I did because it
> was the only way I could
to the installation-report.
Greetings
Andreas
On Wed, 6 Apr 2016 10:06:34 +0200
Andreas Glaeser <bugs.andreas.glae...@freenet.de> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> Begin forwarded message:
>
> Date: Tue, 5 Apr 2016 12:08:08 -0700
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
Date: Tue, 5 Apr 2016 12:08:08 -0700
From: Andrew Kurn <k...@sfu.ca>
To: bugs.andreas.glae...@freenet.de
Subject: Re: Bug#755230 closed by Andreas Glaeser
Thanks for your attention to this matter.
I agree wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.62
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was
n appeared inDebian-testing
(Andreas Glaeser)
- --
Message: 1
Date: Sat, 26 Mar 2016 16:35:23 +0100
From: Andreas Glaeser <bugs.andreas.glae...@freenet.de>
To: openchrome-us...@lists.freedesktop.org
Subject: [Openc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This obviously has been a low-priority project, but I have the box basically up
and
running now.
If you have a similar scenario as myself, with an external harddisk with data
on it, that
you want to integrate into a RAID and use as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear maintainers,
I closed the issue in the first place in order to tell you, how
extremely disappointed I was about your behaviour, to consistently ignore me.
Now I changed my mind, I think the BTS should actually rather reflect, what's
really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried to use the VESA-driver, putting [xorg.conf.xz] in place, it was not
workable, see
[Xorg.0.log.vesa],
the VIA-driver does not work for me either:
> root@t5550:~/5.76.52.92-l140402_32bit-005f78-20150730# ./vinstall
> error: tool "make"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.58
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: youtube-dl
Version: 2015.06.04.1-1
Severity: minor
Dear Maintainer,
I tried to use youtube-dl on Soundcloud.com:
> andrew@a68n:~$ youtube-dl -v
> https://soundcloud.com/gillespeterson/gilles-peterson-dj-set-precious-hall-japan-5th-oct-2015
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.60
Severity: minor
Dear Maintainer,
graphics are still not workable, see attached file [Xorg.0.log.xz].
I was using a DVI-to-VGA adapter here, because only my main screen is digital,
the others
are VGA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see a new report there:
801...@bugs.debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlYad84ACgkQ5+rBHyUt5wtgZwCcDitk0YeGr5sYrldIJEupWrnm
luAAoKNtre1wLJ/irjJ8KcSQMUZcylyP
=yECd
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 03 Oct 2015 01:06:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:
> This is still not the right place to report bugs in SLOB, nor to ask
> for support with configuring your kernel. Please stop doing this.
>
> Ben.
>
> --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: linux-source-4.1
Version: 4.1.6-1
Severity: normal
Dear Maintainer,
this is the follow-up report to:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800154
I reconfigured and built from linux-source-4.1 now, but the situation actually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I visited the Openchrome-Project Homepage, the Debian-package description
contains a
link there:
> andrew@a68n:~$ aptitude show xserver-xorg-video-openchrome
> Package: xserver-xorg-video-openchrome
> State: installed
> Automatically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.60
Severity: minor
Dear Maintainer,
I still have to use VESA-graphics.
- -- Package-specific info:
Boot method: USB
Image version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800367
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlYJTCsACgkQ5+rBHyUt5wuLRwCff0lVMx0auclOHbxDJj+FdT3B
LZgAnj/0pcIe9wUIbxUKu92GbAGK908o
=8UPa
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
O> This is an automatic notification regarding your Bug report
> which was filed against the linux-source package:
>
> #800154: linux-source: custom built embedded kernel with slob-allocation runs
> too
> unstable, boot-problems
>
> It has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: linux-source
Version: 3.16+63
Severity: normal
Dear Maintainer,
I have been using the custom aedl-kernel [config-3.16.7-ckt11-aedl.xz] on my
dualcore
thin-client and tried to continue using it on my new PC, but it is not really
workable.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.58
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: evolution
Version: 3.12.9~git20141130.241663-1+b1
Severity: normal
Dear Maintainer,
I have been using Evolution for some months, there also sowed up some problems,
that I
reported. Recently I found, that the mail-signatures it makes are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: systemd
Version: 215-17+deb8u1
Severity: minor
Dear Maintainer,
I tried to set a different dns-resolver than the default gateway, but failed:
root@s55:/home/andrew# cat /etc/systemd/network/dns.network
[MATCH]
Name=eth1
HOST=s55
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: debian-reference
Version: 2.58
Severity: minor
Dear Maintainer,
There is no hint about systemd:
https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_network_infrastructure
but it needs to be mentioned there.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.58
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-1+b2
Severity: normal
Dear Maintainer,
I have reported this as an installation report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788337
For the openchrome-driver it's a normal issue. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a minor issue only, because the problem is caused by the quick-resync
option in
the mail-account preferences.
Details see in GNOME-bugzilla.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First I tried to set up fbdev, but it did not work out for me, then I removed
the
openchrome-driver using apt-get and generated a new X-configuration:
# init 1
# cd /etc/X11
# X -configure
# cp /root/xorg.conf.new ./xorg.conf
That's all, graphics
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see attachment [xorg.conf.gz]
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlVofrIACgkQ5+rBHyUt5wvBhwCdHHNfiKjdL2jskolZ1kc3/KyT
PDkAoLMzxig8rvYGsomEBVJSHYE/9N8o
=G1BJ
-END PGP SIGNATURE-
xorg.conf.gz
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When booting up oldstable-live, there is some output on the screen at least.
But it seems to be the wrong display-resolution or graphics-mode.
See attached Xorg-log.
This seems to be the most workable variant, set up oldstable and try to set
things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now with Jessie, I tried to connect an external VGA-monitor and this actually
works.
During the boot-process both displays were mirrored, showing the same things,
but upon
xserver-start there is the login-screen on the external monitor, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.58
Severity: normal
Dear Maintainer,
It's another VIA-device without graphics-output, I wished, it would work by
default, not
the other way around, getting fixes upon request.
- -- Package-specific info:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-1+b2
Severity: normal
Dear Maintainer,
hardware-information about the host-PC can be found in my installation-report
there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786872
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: lxc
Version: 1:1.0.6-6
Severity: minor
Dear Maintainer,
I was trying to make unprivileged user-containers, but failed. I also tried to
make a
container usind 'sudo', then moving it into the home-directory of the user and
changing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: evolution
Version: 3.12.9~git20141130.241663-1+b1
Severity: normal
Dear Maintainer,
Since a few days, there are problems sending mail-messages from the default
account.
Evoltion displays a (ruled out) line saying 'Sending message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I built a kernel-image for this box, it is doing well, as far as I can
tell.
Some research was necessary to find out, how o cross-compile for i386 on AMD64.
This is how I did it:
$ make ARCH=i686-PAE -j6 deb-pkg LOCALVERSION=-es-via-c7
doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: munin-async
Version: 2.0.25-1
Severity: normal
Dear Maintainer,
andrew@s5:~$ sudo munin-check
check /var/cache/munin/www
check /var/lib/munin/cgi-tmp
# /var/lib/munin/cgi-tmp/munin-cgi-graph : Wrong owner (www-data != munin)
#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[see attachments]
First I found, that the netmask was wrong in munin-node.conf this has to be /32
not /24.
Then I thought, it might be due to the network-configuration, because of the
network-bridge, but it was not, the second remote host still does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.58
Severity: wishlist
Dear Maintainer,
this is only a wishlist-item, you may also think of it as a success-story.
- -- Package-specific info:
Boot method: USB
Image version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am using this box currently as a bittorrent-seeder with qbittorrent-nox.
The web-interface is nice. Today I built an embedded-server kernel for it. It
seems to be
doing quite well so far, but there were problems with the Sandisk-Ultra-USB3
(32GB)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.58
Severity: wishlist
Dear Maintainer,
This is wishlist only, just some info.
- -- Package-specific info:
Boot method: USB
Image version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.58
Severity: wishlist
Dear Maintainer,
this wa a flawless installation, wishlist only.
- -- Package-specific info:
Boot method: USB
Image version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I could not reproduce it on my notebook with Intel-graphics and with the 32-bit
version
of Jessie.
The graphics-glitch looks similar to the one I saw there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761358
Please let me know, if more info
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gdm3
Version: 3.14.1-6
Severity: important
Dear Maintainer,
because of security-concerns about lightdm
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781080
I wanted to switch back to GDM3, but found it unusable because of a garbled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: e17
Version: 0.17.6-1
Severity: minor
Dear Maintainer,
the e17-filemanager does not delete any files, it does not matter whether the
context-menu (right-mouse-button) is used or the delete-key on the keyboard, or
shift-delete. This applies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The situation with this problem is currently, that file-management works, when
choosing
'Run' on the desktop for the home-folder, or 'Open' for other folders from the
context-menu, i.e. right-mouse-button menu.
But clicking on the items directly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: nautilus
Version: 3.14.1-2
Severity: minor
Dear Maintainer,
I have been using GNOME3.4, and the settings from there are still in my
home-directory.
Setting the behaviour of the file-manager to opening items/objects
with double-click does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: lightdm
Version: 1.10.3-3
Severity: normal
Dear Maintainer,
until today I had not even tried this, when I typed 'root' and the password
into the
lightdm-mask instead of into VT-4-login.
I was quite surprised, that lightdm allows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I set the file-manager to open items with a single click, crashes do not only
appear on
the desktop, but also in the home-folder for instance.
But apart from this, my impression is good, one can use e17 in order to surf
the web,
etc., just not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 10 Mar 2015 12:38:29 +0100
Holger Levsen hol...@layer-acht.org wrote:
Hi,
when jessie will be released, wheezy will become oldstable and we'll need a
new alias for squeeze, as various tools internally work with aliases. (The
security
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: grub-pc
Version: 2.02~beta2-21
Severity: normal
Dear Maintainer,
I report this from my kernel-build-PC.
The problem there was, that not the last and latest kernel was first in the
grub menu,
but another and there was a new version of .
So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778765
They say it i fixed already upstream.
So you guys might look up there, how to do it.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: libwww-youtube-download-perl
Version: 0.56-1
Severity: important
Dear Maintainer,
say I want to download, that video of motherfucking LADY GAGA:
andrew@s5:~$ youtube-download https://www.youtube.com/watch?v=ohs0a-QnFF4
garbage after JSON
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following 40_custom in /etc/grub.d/ fixed the issue for me:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I tried this out, making a /boot/ partition on the harddisk and changing
/etc/fstab
accordingly. It is workable while the card remains in the
expresscard-cardreader, but not
workable, when it is inserted in the internal mmcblk-cardreader.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.49
Severity: wishlist
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 15 Feb 2015 00:46:50 +
Ben Hutchings b...@decadent.org.uk wrote:
Is this also reproducible with linux-image-3.16.0-4-amd64?
Are any additional patches applied to your custom kernel?
Ben.
Hi, Ben,
actually I cannot tell, if it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't have any problems using e17 desktop with lightdm,
so the issue is probably resolved.
But I can confirm some general instabilities, ie efl-crashes, so one has to
restore the
session quite often.
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Because there were news, that there is actually RC1 out of Debian 8-Jessie, I
retried
installation on i386 architecture today.
It went well, but GRUB would not boot the system upon that, situation mostly
unchanged.
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is the image, I tried today:
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso
On the one hand the upgrade-path from stable needs some testing, too, and I
tried that
already and it worked. On the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The report was reopened, because, the issue was fixed only partially.
Soundconverter links to this page regarding MP3-support:
http://soundconverter.org/gstreamer-mp3-encoding-howto/
The information there is outdated:
Add the deb-multimedia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gtk3-engines-xfce
Version: 3.0.1-2
Severity: normal
Dear Maintainer,
the problem was reported already there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775168
I found now, that it is actually gtk3-engines-xfce's fault.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Evince document-viewer window is also affected for example, this is not
exclusive to
gedit.
libreoffice has also rendering-problems with libreoffice-gtk on XFCE-desktop
with
gtk3-engines-xfce:
Package: libreoffice-gtk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gedit
Version: 3.14.0-3
Severity: minor
Dear Maintainer,
Normally I would use GNOME, but I don't because of these issues:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773627
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738631
So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Drag-and-drop from automounted USB-media seems to work currently, but it seems
to work
only.
The files are not accessible to applications, so the severity of this was
upgraded.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: simple-scan
Version: 3.4.2-1
Severity: minor
Dear Maintainer,
simple-scan does not work over x2go-remote-desktop session.
See there: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761398
It is most probably a problem with user-rights
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gvfs
Version: 1.22.2-1
Severity: minor
Dear Maintainer,
drag-and-drop used to be not workable from gvfs-automounted usb-media, both
with GNOME
and Cinnamon. XFCE-desktop does not show such strange behaviour. This is fixed
already
again,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[see attachment: DSDT.dsl.xz]
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlR5cWgACgkQ5+rBHyUt5wuLOACgnlJknSuh5qw298OlSQD+tnNZ
KOUAoIm4bc5mqk5bFgMNG73FvURMlov+
=3od8
-END PGP SIGNATURE-
DSDT.dsl.xz
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I tried the recipe described there on another system:
http://debian-handbook.info/browse/stable/sect.remote-login.html
[see bottom of the page]
This is not workable on Jessie/testing, both as client and as vnc-host.
I set up GNU-inetd:
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now I tried this recipe:
http://www.ibm.com/developerworks/library/os-multiuserloginsvnc/index.html
[see below]
It works fine for me with tightvncserver, but I had to restart the remote
server once in
order to be able to log in to it with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
Date: Tue, 25 Nov 2014 10:15:29 -0500
From: Andreas Glaeser bugs.andreas.glae...@freenet.de
To: Andreas Glaeser bugs.andreas.glae...@freenet.de
Subject: An IBM message from Andreas Glaeser
Dear Andreas Glaeser,
IBM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trying this out in a bit more detail, it showed, that the identical problem
exists with
Wheezy and 32-bit architecture, it is simply a matter of removing the
proprietary
radeon-firmware in firmware-linux-nonfree, so everything works without
1 - 100 of 277 matches
Mail list logo