-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Nov 2014 09:42:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since yesterday I have been doing some research about doing XDMCP over SSH,
which turned
out to be not workable, because SSH does not support tunnelling UDP-connections.
Then, upon looking around some more, I found x2go:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looking at this in more detail, it showed, that XFCE and LXDE-desktops are not
affected,
but it is not a GTK3-exclusive problem, but besides Cinnamon it also shows with
the
E17-desktop and also with KDE-Plasma-Desktop, but it looks different there.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.49
Severity: normal
Dear Maintainer,
Debian-Testing is still not installable for me only expert-installation is
possible
(because of IPv6?) and then it failed at the step of installing tasks, so
I set it up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The graphics-failure only seems to occur when taking the installation from
another AMD64-device and booting it on HP t5735, it is quite strange.
I tried two different installed systems from two different PCs already and saw
the same
problem with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xserver-xorg-video-radeon
Version: 1:7.5.0-1
Severity: normal
Dear Maintainer,
I tried i386 architecture today, which works just fine, so the problem of broken
graphics-output and dead DVI-output is only specific to AMD64-architecture.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: midori
Version: 0.4.3+dfsg-0.1
Severity: normal
Dear Maintainer,
there were two other reports about downloading-problems:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597575
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703210
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This worked for me on my testing-PC, the build went surprisingly fast, the
result is
also workable there. fakeroot really works out of the box, no learning at all
is required
for that, but on my second testing-machine, the resulting kernel-image
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I had used 'make localmodconfig' for testing purposes and forgot about it.
So on the second system missing USB-drivers prevented /root/ from being mounted.
Copying a more general-purpose configuration to .config resolved the problem.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: kernel-package
Version: 13.014
Severity: minor
Dear Maintainer,
I looked at the manpage of make-kpkg, and it said, it was not recommended to
build as
root.
Typically, make-kpkg should be run under fakeroot,
make-kpkg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I tried this image:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
from 2014-10-27
It did not boot from CD, only from USB, apart from this the situation is
unchanged, but
it may be my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[attached,gzipped 'inst-syslog.gz']
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlRJEdAACgkQ5+rBHyUt5wtbDQCfWnfGShvfA5XRCBpo/6U5m7DT
qpcAoKZWLhgmdMdNzrmS7MHB/82O0AXW
=Cnng
-END PGP SIGNATURE-
inst-syslog.gz
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
From: Paul Wise p...@debian.org
To: Andreas Glaeser bugs.andreas.glae...@freenet.de, 763...@bugs.debian.org
Subject: Re: Bug#763426: installation-report: installed system not bootable
by default
Date: Mon, 20 Oct 2014 15:54:59 +0800
X-Mailer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Oct 2014 09:34:49 -0700
Don Armstrong d...@debian.org wrote:
On Mon, 13 Oct 2014, Andreas Glaeser wrote:
I searched for bugs in packages gnome-tweak-tool and audacity, then
src:audacity and
src:gnome-tweak-tool, but currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 2 Oct 2014 09:23:18 -0700
Don Armstrong d...@debian.org wrote:
On Thu, 02 Oct 2014, Andreas Glaeser wrote:
I searched for the term 'Futro S450' in package installation-reports:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: audacity
Version: 2.0.1-1
Severity: normal
Dear Maintainer,
today I want to point out, that recording with 'Software Playthrough' option is
still not workable. Recording audio does not hang anymore and listening to what
you record
works.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The option works in Jessie/testing, also on a low cpu-power machine.
Package: audacity
Version: 2.0.5-2+b1
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I retried this today with XFS and ext4, the former failed very early at
bootstrapping
the base system, the latter failed at setting up the kernel, towards the end of
the
process.
It is also kind of strange, that 'lastlog' and 'faillog' consist of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.49
Severity: minor
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
I searched for the term 'Futro S450' in package installation-reports:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;include=subject%3AFutro+S450;dist=testing;package=installation-reports
and found this archived bug only:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 30 Sep 2014 12:17:52 +0200
Cyril Brulebois k...@debian.org wrote:
Andreas Glaeser bugs.andreas.glae...@freenet.de (2014-09-30):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.57
Severity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.57
Severity: normal
Dear Maintainer,
The installed system was not bootable upon installation, but grub could be
installed
manually:
root@s5:/home/andrew# fdisk -l
.
..
..
.
Disk /dev/sdc: 15.9 GB,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: debbugs
Version: 2.4.1
Severity: minor
Dear Maintainer,
it is not a big issue, but maybe it is worth fixing it.
- -- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried this on another PC today, running Wheezy/stable.
The situation is the same there. GDM3 does not allow any logins via XDMCP,
although
configured accordingly, lightdm allows this with Xnest only, but not with
Xephyr.
Tagging this accordingly.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gdm3
Version: 3.12.2-4
Severity: normal
I use the default desktop on a secondary machine with testing.
Because lightdm does not allow remote logins with Xephyr via XDMCP, I set up
gdm3 today.
This cost about 400 MB of diskspace, because it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xorg
Version: 1:7.7+7
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 effective (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761398
It is almost the same hardware as the box, I reported this from, but GNOME is
not
installed there. I do think, you will have to get your gdm3-dependencies fixed.
It should be able to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please see here:
https://wiki.debian.org/DebianWiki/LicencingTerms
In summary, the wiki should express a clear licence for the content on it,
under which
material can be contributed to and re-used with. This licence should be
DFSG-compliant,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Installation in Virtualbox works now with EFI and UEFI-GPT partitioning, but
the system
is not bootable then. It shows a black screen and a fully loaded CPU instead of
booting
up correctly.
I have no idea, how to fix this, because I have hardly any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The issue seems to be fixed now at least when using the GNOME-desktop:
andrew@s5:~$ aptitude show liferea
Package: liferea
State: installed
Automatically installed: no
Version: 1.10.9-1
Priority: optional
Section: gnome
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 04 Jul 2014 09:29:30 -0500
David Smith sidic...@gmail.com wrote:
On 07/04/2014 05:56 AM, Andreas Glaeser wrote:
Yes dbus-x11 package is installed, I recently re-installed the
whole system, so everything should be pretty much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: nautilus
Version: 3.8.2-3
Severity: normal
Dear Maintainer,
I have not been using Gnome here on my testing-box for quite some time now
because of the
nautilus file-manager. It used to start up with a maximised window and took the
whole
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 28 Jun 2014 10:09:56 -0500
David Smith sidic...@gmail.com wrote:
On 06/24/2014 08:41 AM, Andreas Glaeser wrote:
The problem seemed to be solved, but in fact is is not, the
situation with liferea is
unchanged, so the report
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I leave the workplace, I usually want to lock the screen or log out, but
the
situation here is still unchanged.
I had another look at bug severity levels and now I think it's a normal problem
even,
not minor.
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just tried booting the notebook twice with the experimental build
3.15-trunk-686-pae and
it seems to work now, but I had this impression already earlier, so I am not
closing this
at once, just in case problems reappear.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The problem seemed to be solved, but in fact is is not, the situation with
liferea is
unchanged, so the report was reopened.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see attachments [dmsg.txt.xz] and [hw-rep.txt.xz].
I chose the ICH9-chipset there and ICH6 for storage and enabled bridged
networking in
order to be able to export the information using NFS.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.55
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: liferea
Version: 1.10.8-1
Severity: minor
Dear Maintainer,
* offline-reading RSS-feeds is OK for me, liferea is the application of choice
* On the XFCE-desktop, it needs to be invoked twice from the applications-menu
in order
to start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
See attachments:
[tables.tar.bz2] and [DSDT.dls.xz]
These were ripped from the FSC Futro S450, but this time with the original CPU,
that runs
at 800 MHz or 1600 MHz, depending on the load, but it turned out, that the
board only does
so with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The situation is still unchanged currently,
but as stated there:
linux-source-3.12/Documentation/acpi/initrd_table_override.txt
.
.
..
Alternatively, used ACPI tables can be retrieved via sysfs in latest kernels:
/sys/firmware/acpi/tables
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I submit the ACPI-tables from FSC Futro S500 with Athlon l310 CPU @ 2x1.2 GHz
now, which
has almost the same mainboard as Futro S550. I also disassembled the DSDT-table
and attach
this too.
[tables.tar.bz] and [DSDT.dsl.bz2]
These were read out from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
Date: Mon, 21 Apr 2014 13:30:19 +
From: ow...@bugs.debian.org (Debian Bug Tracking System)
To: Andreas Glaeser bugs.andreas.glae...@freenet.de
Subject: Bug#745416: Acknowledgement (installation-report: setting up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It was reported already there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743360
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlNXaRAACgkQ5+rBHyUt5ws9VQCeOHyLHwFghCGva0JEoLnjufkA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.49
Severity: wishlist
Dear Maintainer,
this installation went fine, not quite as expected.
- -- Package-specific info:
Boot method: USB
Image version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gnome-tweak-tool
Version: 3.12.0-2
Severity: minor
Dear Maintainer,
I wondered for some time, why the desktop-background is grey with my
user-profile and the
normally set background is shown with a new user-profile. Now I found that this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.55
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
Concerning linux-image-3.14-trunk-amd64, I can tell you, that it works and
builds well on
this AMD64-box, but on the Pentium-M notebook it has the same problem as the
3.13-version:
p linux-image-3.13-1-686-pae:i386 - Linux 3.13
, but there might be custom setups with non-threaded Apaches, where the
included
symlink would not work.
On Sat, 29 Mar 2014 22:21:58 +0100
Stefan Fritsch s...@sfritsch.de wrote:
Am Montag, 17. März 2014, 11:19:47 schrieb Andreas Glaeser:
* today I tried out man2html and dwww, both depend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, sorry,
About this line again in conf-enabled/:
root root 36 Mar 17 10:22 serve-cgi-bin.conf -
../conf-available/serve-cgi-bin.conf
It does not point into the void of course, but to
conf-available/serve-cgi-bin.conf
on the same level of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: dwww
Version: 1.12.1
Severity: minor
Dear Maintainer,
* dhelp is defective and not installable
* dwww depends on apache2-bin, which actually does not set up a
webserver
* installing apache2 makes dwww work, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: apache2-bin
Version: 2.4.7-1
Severity: normal
Dear Maintainer,
* today I tried out man2html and dwww, both depend on httpd-cgi
* missing cgi-bin interface leads to broken man2html:
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.55
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
Package: gnome-screensaver
Version: 3.6.1-1
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: qemuctl
Version: 0.3.1-1
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 effective (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When trying this again now, I found, that my settings were not forgotten, they
were only
saved under a different name than 'Default', they were selectable.
I also fail to display the qemu-command-line that was produced, maybe this is
the problem.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: acpidump
Version: 20131115-1.1
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 effective
-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
Package: cairo-dock
Version: 3.3.2-1
Severity: minor
Every time new packages are set up, one has to close the 'Start new
application?'-requester. There does not seem to be any way to disable this, so
please add an option to do so.
Dear Maintainer,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sources:
Our Debian-installation started from Arch-Linux, which could be booted on the
Pogoplug-device already. This was installed following these instructions:
link
http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray
/link
Instructions to
installation-report
Warning: no reportbug configuration found. Proceeding in novice mode.
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'Andreas Glaeser andreas@localhost' as your from address.
Getting status for installation-report...
Checking for newer versions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: soundconverter
Version: 2.0.1-1
Severity: minor
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
Package: installation-reports
Version: 2.55
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
Package: installation-reports
Version: 2.53
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
[see attachments 'dmsg.txt.xz' and 'config-3.11.8caftl.xz']
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlKq/e0ACgkQ5+rBHyUt5wvoBACgr8Xtba4eTibZ1kUtnj5aIsfO
vLoAn03AdiPoFbfTp6D+QAswxGrwXD3/
=R2Fi
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My new Kernel-Configuration is attached.
This one clearly gives the best user-experience so far.
Before this I had a normal desktop-kernel running with 1000Hz timer-frequency.
Now this version has both: 1000 Hz, so it will not be good for running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, this is no bug, you are not using the offical linux-image,
linux-kbuild and linux-headers package.
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andreas@md-ho:~/Documents$ glxgears
1971 frames in 5.0 seconds = 394.131 FPS
2307 frames in 5.0 seconds = 461.212 FPS
2474 frames in 5.0 seconds = 494.774 FPS
^C
#
#The graphics are fast enough, even when running without the proprietary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It showed the same scary flashing screen at boot- and shutdown-time.
[more info attached (Xorg.0.log.xz)]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJ49ZoACgkQ5+rBHyUt5wthPwCeKlfrkV5fbBV18KtqCe/sOzKR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJ4+SYACgkQ5+rBHyUt5wsNtwCfWtj6JM4KhkJRdwH8StuFmtD1
KKgAn1VVOz2wrjFdQHmPidgZAtxSESEt
=OtxG
-END PGP SIGNATURE-
kern.log.xz
Description: application/xz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: firmware-linux-nonfree
Version: 0.36+wheezy.1
Severity: minor
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[see attachment, radeon-info.txt.xz]
Problem also reported there:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728600
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: aptitude
Version: 0.6.8.2-1
Severity: minor
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
Package: dkms
Version: 2.2.0.3-1.2
Severity: normal
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
also see there:
http://www.acpi.info/DOWNLOADS/ACPIspec30b.pdf
Pages 274 ff.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJcHLsACgkQ5+rBHyUt5wupLgCgj7ICIxok+PRsHEBM2ghdjWgb
624AoIMy6UkXFbE0auAnOXEyc6/saamj
=khIu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Removing firmware-linux-nonfree made the initialization- und shutdown-blinking
of my
monitor disappear actually. So I switched to the KDE-desktop now, putting
cairo-dock
towards the top of the screen, so something familiar remains.
This is a viable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This makes it impossible to do anything without X.
I forgot to mention it.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJP+zAACgkQ5+rBHyUt5wsRbwCaAhWdJy8mfhG1qJLmafGE/JJp
tzYAmwT18Ev7J8/bxs+zXjyvCp78NFlb
=ylAa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: browser-plugin-gnash
Version: 0.8.11~git20120629-1
Severity: minor
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
-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
Package: enigmail
Version: 2:1.5.1+id17-3~deb7u1
Severity: normal
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: icedove
Version: 17.0.8-1~deb7u1
Severity: minor
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
Package: gnome-shell
Version: 3.4.2-7+deb7u1
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
overrides
# h01ger | waldi: so which package is providing that firmware? firmware-
# linux?
# jcristau | h01ger: the hardware
thanks
Hi Andreas,
thanks for your installation-report, much appreciated!
On Freitag, 30. August 2013, Andreas Glaeser wrote:
[...] When the original CPU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: seahorse
Version: 3.4.1-2
Severity: normal
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
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
Package: linux-source-3.2
Version: 3.2.46-1
Severity: normal
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
I reported the XFCE-terminal-issue against package xfce4-terminal as
695...@bugs.debian.org, but it was closed very quickly, reopening does not seem
to be
possible now.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
please see attached draft installation-report.txt.gz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlFqakgACgkQ5+rBHyUt5wtBlACgkI1+QwmjLAFtGlDC3qlpQckY
gt4AoI7h+91cMcsJldP0xNcTAQDZrAS2
=Cs5A
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: kernel-package
Version: 12.036+nmu3
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
Yesterday I slightly reconfigured the 3.9 kernel source on this box as
embedded low-latency-desktop and disabled a few unneeded drivers and was a bit
surprised
that this actually built just fine and the result is running more nicely, too.
So my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The situation is now on my 'GNOME-box' as I like to call it, that there is no
dmesg-error
message issued anymore with the most recent 3.2. kernel-version, but
intermittent
blanking still occurs without showing in dmesg-output.
Full-screen blanking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: update-manager-gnome
Version: 0.200.5-2.1
Severity: normal
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
-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
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
Yesterday I tried building the 3.8-series kernel from experimental here:
701...@bugs.debian.org
and it failed. I could not tell initially why this was the case, then upon
restart,
Gnome, i.e. gdm was not able to start up anymore, but told me instead
-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
Today I installed the most recent kernel-version
'linux-image-3.7-trunk-686-pae_3.7.8-1~experimental.1_i386.deb'
from experimental on my
nettop-box and found the issue is really resolved now there.
Probably all I have to do is wait until the
fix is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upon reinstalling today and doing no text-mode configuration at all to Xorg, I
put
'video=LVDS-1:d boot option into /etc/default/grub, 'linux-firmware-nonfree'
was
installed, then 'update-grub' was done. Although it was a bit tricky to guess,
where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upon searching online and finding a similar question here:
http://askubuntu.com/questions/22812/what-does-the-dmesg-error-composite-sync-not-supported-mean
I tried adding the boot-option 'nomodeset' in /etc/default/grub, but neither
did this
make the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 04 Feb 2013 10:27:56 +0100
Michel Dänzer daen...@debian.org wrote:
On Mon, 2013-02-04 at 09:30 +0100, Andreas Glaeser wrote:
The 'firmware-linux-nonfree' package was set up, which made DRI work and
Gnome3 run
in non-fallback mode
101 - 200 of 277 matches
Mail list logo
