Bug#1003398: After distribution upgrade many mails are "tainted" and not delivered
Package: exim4-daemon-heavy
Version: 4.94.2-7
Severity: important
Hello Maintainer,
after upgrading the server from Debian 9 to 11 there is a problem with (actual)
no solution.
Here is an example from the paniclog:
2022-01-06 14:13:56 1n4NwM-00ASE5-Py == sys...@example.com R=mysql_user
T=local_mysql_delivery defer (-1): Tainted '/srv/ma
il/example.com/system/' (file or directory name for local_mysql_delivery
transport) not permitted
2022-01-06 14:13:56 1n3cy0-008N8T-By == karsten@example-com R=mysql_user
T=local_mysql_delivery defer (-1): Tainted '/srv/m
ail/example.com/karsten/' (file or directory name for local_mysql_delivery
transport) not permitted
The mainlog is full of messages like this for every local delivery:
2022-01-09 14:53:39 1n5pDL-000Z0k-OR == sys...@example.com R=mysql_user
T=local_mysql_delivery defer (-1): Tainted '/srv/ma
il/example.com/system/' (file or directory name for local_mysql_delivery
transport) not permitted
The research of this error message leads to a big discussion without an
solution here:
https://www.mail-archive.com/exim-users@exim.org/msg54866.html (another example)
This seems to be introduced in exim V 4.94:
https://www.mail-archive.com/exim-users@exim.org/msg54868.html
The documentation is not understandable:
https://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_appendfile_transport.html#SECTfildiropt
What must be done to get the mails de-tainted?
When there is no simple understandable solution an server version < 4.94 must
be used.
The config for this part is this:
local_mysql_delivery:
driver = appendfile
directory = /srv/mail/${domain}/${local_part}/
maildir_format
delivery_date_add
envelope_to_add
return_path_add
user = Debian-exim
group = mail
mode = 0660
Thank you for any hint to solve the problem.
Best regards
karsten
-- Package-specific info:
Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DANE DKIM DNSSEC
Event I18>
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql
nis nis>
Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#992592: lightdm does not start / work any more after system upgrade
Am 08.01.22 um 03:10 schrieb xiao sheng wen(肖盛文): If you want use nodm, only run apt-get install nodm in enough. lightdm and nodm can co-exist in the same machine. When install nodm after lightdm, It'll display a prompt let user choise "Default display manager". You may choice nodm to use. Yes - thanks. But a package that does not work and is useless can be purged.
Bug#992592: lightdm does not start / work any more after system upgrade
There seems no solution in sight. When there is only one user that can be automatically logged in the nodm display manager can solve the problem. Use: agt-get purge lightdm apget install nodm Best regards karsten
Bug#928509: Firefox extensions can be used again
I upgraded the Firefox packages for Debian 8 (Jessie) and Debian 9 (Stretch) now and in both Releases Firefox can use the extensions again. Thanks for your great work! Besides - Debian 8 is used for desktop use, because it is running with less problems. Like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926066 or https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910494
Bug#856842: symbol hackrf_device_list seems to exist
undefined symbol: hackrf_device_list But the symbol seems to be defined! The error is not understandable? $ nm -D /usr/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.1.4 U hackrf_board_id_name U hackrf_board_id_read U hackrf_close U hackrf_compute_baseband_filter_bw -> U hackrf_device_list U hackrf_device_list_free U hackrf_device_list_open U hackrf_error_name U hackrf_exit U hackrf_init U hackrf_is_streaming U hackrf_open U hackrf_open_by_serial U hackrf_set_amp_enable U hackrf_set_antenna_enable U hackrf_set_baseband_filter_bandwidth U hackrf_set_freq U hackrf_set_lna_gain U hackrf_set_sample_rate U hackrf_set_txvga_gain U hackrf_set_vga_gain U hackrf_start_rx U hackrf_start_tx U hackrf_stop_rx U hackrf_stop_tx U hackrf_usb_board_id_name U hackrf_version_string_read
Bug#856842: GQRX does not start
Package: gqrx-sdr Version: 2.6-1~bpo8+1 Severity: important Hello, i tried to update my gqrx from the standard repositories (2.3.1) to 2.6, because there are bug in V 2.3.1. aptitude -t jessie-backports install gqrx-sdr The installation works, but after the installation gqrx does not start. I can see the following messages by starting from the bash: $ gqrx linux; GNU C++ version 4.9.2; Boost_105500; UHD_003.009.005-0-unknown Controlport disabled No user supplied config file. Using "default.conf" gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10 built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy redpitaya FM demod gain: 1.52789 IQ DCR alpha: 1.04166e-05 Using audio backend: auto BookmarksFile is /home/karsten/.config/gqrx/bookmarks.csv gqrx: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.1.4: undefined symbol: hackrf_device_list Regards Karsten -- System Information: Debian Release: 8.7 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gqrx-sdr depends on: ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libc6 2.19-18+deb8u7 ii libgcc1 1:4.9.2-10 ii libgnuradio-analog3.7.103.7.10.1-1~bpo8+1 ii libgnuradio-audio3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-blocks3.7.103.7.10.1-1~bpo8+1 ii libgnuradio-digital3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-fft3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-filter3.7.103.7.10.1-1~bpo8+1 ii libgnuradio-osmosdr0.1.40.1.4-11~bpo8+1 ii libgnuradio-pmt3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-runtime3.7.10 3.7.10.1-1~bpo8+1 ii libpulse0 5.0-13 ii libqt5core5a5.3.2+dfsg-4+deb8u2 ii libqt5gui5 5.3.2+dfsg-4+deb8u2 ii libqt5network5 5.3.2+dfsg-4+deb8u2 ii libqt5svg5 5.3.2-2 ii libqt5widgets5 5.3.2+dfsg-4+deb8u2 ii libstdc++6 4.9.2-10 ii libvolk1.3 1.3-1~bpo8+1 ii libgnuradio-audio3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-blocks3.7.103.7.10.1-1~bpo8+1 ii libgnuradio-digital3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-fft3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-filter3.7.103.7.10.1-1~bpo8+1 ii libgnuradio-osmosdr0.1.40.1.4-11~bpo8+1 ii libgnuradio-pmt3.7.10 3.7.10.1-1~bpo8+1 ii libgnuradio-runtime3.7.10 3.7.10.1-1~bpo8+1 ii libpulse0 5.0-13 ii libqt5core5a5.3.2+dfsg-4+deb8u2 ii libqt5gui5 5.3.2+dfsg-4+deb8u2 ii libqt5network5 5.3.2+dfsg-4+deb8u2 ii libqt5svg5 5.3.2-2 ii libqt5widgets5 5.3.2+dfsg-4+deb8u2 ii libstdc++6 4.9.2-10 ii libvolk1.3 1.3-1~bpo8+1 ii pulseaudio 5.0-13 gqrx-sdr recommends no packages. gqrx-sdr suggests no packages. -- no debconf information
Bug#851997: [Pkg-xmpp-devel] Bug#851997: No TLS encryption possible
Hello Simon, Am 07.02.2017 um 10:12 schrieb Simon Josefsson: > You need to provide more details for this to be a useful bug report. > Your statements above can easily be disproved. I'm using > 2.4.0-1~bpo8+1 and TLS works just as I want it to work, see for example: > > https://www.xmpp.net/result.php?domain=josefsson.org&type=server > https://www.xmpp.net/result.php?domain=josefsson.org&type=client I don't know what is tested there - but all i can test is $ openssl s_client -connect chat.josefsson.org:5222 -starttls xmpp CONNECTED(0003) There is no TLS connection established! But when i test the same to my prosody server i get ... --- SSL handshake has read 1946 bytes and written 627 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384 Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1.2 Cipher: ECDHE-RSA-AES256-GCM-SHA384 ... This is an working TLS connection! > > All of my configurations are available here: > > https://gitlab.com/jas/sjd-cosmos/tree/master/chat.josefsson.org/overlay/etc/jabberd2 So at least you use |josefsson.org | That's what i already tested. > As far as I can tell, what you are looking for is help to configure > jabberd2. To get help, you need to find someone to help you and you > need to explain what you have tried and what happenes, and what you > expect to happen. I have written all this information in the linked bug reports. There is nothing more that could be find out. The developer doesn't support help or more information. Sorry. It's just a warning to users who want's to have a secure XMPP server. Best regards Karsten
Bug#851997: TLS and jabberd2
> I have clients running with a Jabberd2 server using LetsEncrypt certifcate > for the Jabber server. > Wireshark shows the communication between client and server is using TLS. Please tell me the secret howto get a working encryption with jabberd2 ? Maybe you are using an older version ? I couldn't master it including let's encrypt. Here you can read about my experiments to get it working. https://community.letsencrypt.org/t/understanding-certification/25952 As client i only tried it with pidgin and psi. Both clients couldn't connect in a secure way with jabberd2. But now with prosody it is no problem. Regards Karsten
Bug#851997: Secure alternative server
For the users who are searching for an alternative secure XMPP server: I have installed prosody now as debian package. https://prosody.im/ The configuration is well documented and very easy in comparison to jabberd. I can use a self-signed certificate or let's encrypt without problem. All the communication and file transfer is encrypted with ECDHE-RSA-AES256-GCM-SHA384. I have verified this in an wireshark session. It's simply perfect.
Bug#851997: No TLS encryption possible
Package: jabberd2 Version: 2.4.0-1~bpo8+1 Justification: user security hole Severity: grave Tags: security I am sorry to report this, but the users of jabberd2 should now that there is no encryption possible with this package. An configuration with encryption settings is ignored and an unencrypted connection is opened without warnings. I could verify this in an wireshark session. Wasting many time to get it running with a working TLS i had to give up. There is no interest from the developer to solve the problem. Please refer to this bugs that include further links: https://github.com/jabberd2/jabberd2/issues/137 https://github.com/jabberd2/jabberd2/issues/141 Regards Karsten
Bug#850434: Package for Debian Jessie
Sorry - i have forgotten to write that this package is for Debian Jessie (Stable). I didn't know how to address this to Backports. At least i want to make this packages public available. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850433 Regards Karsten
Bug#850433: Package for Debian Jessie
Sorry - i have forgotten to write that this package is for Debian Jessie (Stable). I didn't know how to address this to Backports. At least i want to make this packages public available. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850434 Regards Karsten
Bug#847064: KGPG does not start
Hola Maximilio, Am 13.12.2016 um 16:01 schrieb Maximiliano Curia: > ¡Hola Karsten! > > I guess that it either failed to show the configuration wizard or it tried to > migrate some configuration from a > previous version. I've tested this in a clean vm, using stable and the wizard > worked fine, so maybe you had a left > over configuration from an older version? Yes - i migrated my running Debian several times. I didn't use KGPG before - so this will be an explanation. Thanks for your support! Karsten
Bug#847064: KGPG does not start
Package: kgpg Version: 4:4.14.2-1 Justification: renders package unusable Severity: grave When i try to start KGPG i can see the following messages in the console: $ kgpg QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Regards Karsten -- System Information: Debian Release: 8.6 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kgpg depends on: ii gnupg1.4.18-7+deb8u3 ii gnupg2 2.0.26-6+deb8u1 ii kde-runtime 4:4.14.2-2 ii kdepim-runtime 4:4.14.2-3 ii libakonadi-contact4 4:4.14.2-2+deb8u2 ii libakonadi-kde4 4:4.14.2-2+deb8u2 ii libc62.19-18+deb8u6 ii libkabc4 4:4.14.2-2+deb8u2 ii libkdecore5 4:4.14.2-5+deb8u1 ii libkdeui54:4.14.2-5+deb8u1 ii libkio5 4:4.14.2-5+deb8u1 ii libkpimutils44:4.14.2-2+deb8u2 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libsolid44:4.14.2-5+deb8u1 ii libstdc++6 4.9.2-10 kgpg recommends no packages. kgpg suggests no packages. -- no debconf information
Bug#845094: Storing the settings is not working correct
Package: gqrx-sdr Version: 2.3.1-2 Severity: important I have the problem that the storing of the settings ist not working correct. It seems that the last opened settings are always overwritten again. The settings are changing when storing them. This is really annoying. I really does not understand why this bug occurs, because it should be fixed in version 2.3. "Gqrx 2.3.0 released" http://gqrx.dk/category/news "Properly store settings when using Save As function." There are more functions in the actual 2.6 version. It would be a good idea to update. Thanks. Karsten -- System Information: Debian Release: 8.6 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gqrx-sdr depends on: ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libc6 2.19-18+deb8u6 ii libgcc1 1:4.9.2-10 ii libgnuradio-analog3.7.5 3.7.5-5 ii libgnuradio-blocks3.7.5 3.7.5-5 ii libgnuradio-fft3.7.53.7.5-5 ii libgnuradio-filter3.7.5 3.7.5-5 ii libgnuradio-osmosdr0.1.30.1.3-2 ii libgnuradio-pmt3.7.53.7.5-5 ii libgnuradio-runtime3.7.53.7.5-5 ii libpulse0 5.0-13 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libstdc++6 4.9.2-10 ii libvolk0.0.03.7.5-5 gqrx-sdr recommends no packages. gqrx-sdr suggests no packages.
Bug#839935: MySQL server has wrong dependencies and is not installable
Package: mysql-common
Version: 5.5.50-0+deb8u1
Justification: renders package unusable
Severity: grave
Hello,
i want to install a LAMP server but MySQL will not install.
# aptitude install mysql-server-5.6
Die folgenden NEUEN Pakete werden zusätzlich installiert:
mysql-server-5.6{b} mysql-server-core-5.6{a}
0 Pakete aktualisiert, 2 zusätzlich installiert, 0 werden entfernt und 0 nicht
aktualisiert.
10,9 MB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden
80,3 MB zusätzlich belegt sein.
Die folgenden Pakete haben verletzte Abhängigkeiten:
mysql-server-5.6 : Hängt ab von: mysql-common (>= 5.6.22-1~) aber
5.5.52-0+deb8u1 ist installiert.
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Beibehalten der folgenden Pakete in ihrer aktuellen Version:
1) mysql-server-5.6 [Nicht installiert]
Diese Lösung akzeptieren? [Y/n/q/?] y
Es werden keine Pakete installiert, aktualisiert oder entfernt.
0 Pakete aktualisiert, 0 zusätzlich installiert, 0 werden entfernt und 0 nicht
aktualisiert.
0 B an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 0 B
zusätzlich belegt sein.
The problem is that a corresponding package mysql-common (>= 5.6.22-1~) does
not exist!
It does not helpe to purge the old 5.5.52 package.
Please give a solution.
Cheers
Karsten
-- System Information:
Debian Release: 8.5
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
Bug#782353: closed by Stefan Hornburg (Racke) (Bug#782353: fixed in pure-ftpd 1.0.43-1)
Am 07.09.2016 um 13:36 schrieb Stefan Hornburg (Racke): > > Hello Karsten, > > ok so let's reopen the bug and I'll ask the Pure-FTPd author for advice. > > Regards > Racke > That's perfect - thank you! Maybe this problem was not realized by the author. Regards Karsten
Bug#782353: closed by Stefan Hornburg (Racke) (Bug#782353: fixed in pure-ftpd 1.0.43-1)
Am 07.09.2016 um 11:20 schrieb Stefan Hornburg (Racke): > Hello Karsten, > I think your report says it might be a bug in Pure-FTPd but I can't see really > a justification to that. > > Fixed security problem: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791420 > > Regards > Racke > Hello Racke, i reported definitely a security hole, because i could determine a hacker intrusion over this FTP server. After the FTP was disabled completely there was no security problem again. This FTP-server is used as standard FTP server in ISPConfig 3. I never had any problems like this with ProFTPD. So my security advice for every user is to use another FTP server or only activate Pure-FTPd for the use within a session. Regards Karsten
Bug#782353: closed by Stefan Hornburg (Racke) (Bug#782353: fixed in pure-ftpd 1.0.43-1)
Hello Stefan, why do you believe that this bug is fixed? My report to the developers seems to be ignored and i can't read anything about fixes of security holes !? https://www.pureftpd.org/project/pure-ftpd/news Regards Karsten Am 05.09.2016 um 15:21 schrieb Debian Bug Tracking System: > This is an automatic notification regarding your Bug report > which was filed against the pure-ftpd-common package: > > #782353: Security hole in server version 1.0.36 > > It has been closed by Stefan Hornburg (Racke) . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Stefan Hornburg (Racke) > by > replying to this email. > >
Bug#830723: When X server start fails it ends up in an endless loop
Package: xserver-xorg Version: 1:7.7+7 Severity: important Hello, for more than one time i have the problem that when the X server fails to start it ends up in an loop to try to start! When you have a damaged vga card and change it you never get a simple console again. Sometimes the system doesn't react any more because it is somehow locked by the X server. Why this loop? In the past the X server tried to start and when it fails it prompted the error and you land on the console. Now the system behaviour is like in windows where the system get's unusable without an graphical frontend! Cheers Karsten -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jun 21 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 2015 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u2 (2015-07-17) Xorg X server log files on system: -- -rw-r--r-- 1 root root 42479 Dec 4 2010 /var/log/Xorg.2.log -rw-r--r-- 1 root root 35553 Jun 19 12:29 /var/log/Xorg.1.log -rw-r--r-- 1 root root 8004 Jul 10 21:04 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 309.595] X.Org X Server 1.16.4 Release Date: 2014-12-20 [ 309.595] X Protocol Version 11, Revision 0 [ 309.595] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 309.595] Current Operating System: Linux PC8 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u2 (2015-07-17) x86_64 [ 309.595] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=22e85ef8-276b-4cdd-bfd9-bc76e4f12e56 ro quiet [ 309.595] Build Date: 11 February 2015 12:32:02AM [ 309.596] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [ 309.596] Current version of pixman: 0.32.6 [ 309.596]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 309.596] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 309.597] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 10 21:04:34 2016 [ 309.597] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 309.598] (==) No Layout section. Using the first Screen section. [ 309.598] (==) No screen section available. Using defaults. [ 309.598] (**) |-->Screen "Default Screen Section" (0) [ 309.598] (**) | |-->Monitor "" [ 309.598] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 309.598] (==) Automatically adding devices [ 309.598] (==) Automatically enabling devices [ 309.598] (==) Automatically adding GPU devices [ 309.598] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 309.598]Entry deleted from font path. [ 309.598] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 309.598] (==) ModulePath set to "/usr/lib/xorg/modules" [ 309.598] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 309.598] (II) Loader magic: 0x7fe8ba921d80 [ 309.598] (II) Module ABI versions: [ 309.598]X.Org ANSI C Emulation: 0.4 [ 309.598]X.Org Video Driver: 18.0 [ 309.598]X.Org XInput driver : 21.0 [ 309.598]X.Org Server Extension : 8.0 [ 309.598] (II) xfree86: Adding drm device (/dev/dri/card0) [ 309.600] (--) PCI:*(0:2:0:0) 10de:0de1:: rev 161, Mem @ 0xfd00/16777216, 0xf000/134217728, 0xfa00/33554432, I/O @ 0xe800/128, BIOS @ 0x/524288 [ 309.600] (II) LoadModule: "glx" [ 309.600] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 309.601] (II) Module glx: vendor="X.Org Foundation" [ 309.601]compiled for 1.16.4, module version = 1.0.0 [ 309.601]ABI class: X.Org Server Extension, version 8.0 [ 309.601] (==) AIGLX enabled [ 309.601] (==) Matched nouveau as autoconfigured driver 0 [ 309.601] (==) Matched nv as
Bug#830721: Failed to load module "nv" (module does not exist, 0)
Package: nvidia-driver Version: 340.96-1 Severity: normal Hello, i changed the card from ATI to NVIDIA after the ATI card died. After that i uninstalled all ATI stuff. Then i reinstalled the xserver and the nvidia-driver. It says it was compiling the nvidia driver and did report no error. But it is not working - there is no driver! Why graphics is such a pain in original Debian? When i boot Knoppix i always have a running X! Cheers Karsten -- Package-specific info: uname -a: Linux PC8 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1 (2016-07-04) x86_64 GNU/Linux /proc/version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.36-1 (2016-07-04) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: gcc version 4.8.4 (Debian 4.8.4-1) lspci 'VGA compatible controller [0300]': 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 Kernel driver in use: nvidia dmesg: [0.00] AGP: No AGP bridge found [0.00] AGP: Checking aperture... [0.00] AGP: No AGP bridge found [0.00] AGP: Node 0: aperture [bus addr 0x4d9a00-0x4d9bff] (32MB) [0.00] Console: colour VGA+ 80x25 [0.201784] vgaarb: setting as boot device: PCI::02:00.0 [0.201784] vgaarb: device added: PCI::02:00.0,decodes=io+mem,owns=io+mem,locks=none [0.201784] vgaarb: loaded [0.201784] vgaarb: bridge control possible :02:00.0 [0.926641] Linux agpgart interface v0.103 [4.832218] snd_hda_intel :02:00.1: Handle VGA-switcheroo audio client [4.962472] nvidia: module license 'NVIDIA' taints kernel. [4.986801] vgaarb: device changed decodes: PCI::02:00.0,olddecodes=io+mem,decodes=none:owns=none [4.987257] [drm] Initialized nvidia-drm 0.0.0 20140818 for :02:00.0 on minor 0 [4.987263] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 [5.620508] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:02:00.1/sound/card0/input7 [5.620575] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:02:00.1/sound/card0/input8 [5.620637] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:02:00.1/sound/card0/input9 [5.620695] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:02:00.1/sound/card0/input10 Device node permissions: crw-rw+ 1 root video 226, 0 Jul 10 20:11 /dev/dri/card0 crw-rw+ 1 root video 195, 0 Jul 10 20:11 /dev/nvidia0 crw-rw+ 1 root video 195, 255 Jul 10 20:11 /dev/nvidiactl video:x:44:karsten,multimedia OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jul 10 19:56 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 44 Jul 10 19:56 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 41 Jul 10 19:56 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 41 Jul 10 19:56 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jul 10 19:56 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jul 10 19:56 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 50 Jul 10 19:56 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 50 Jul 10 19:56 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 47 Jul 10 19:56 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 root root 47 Jul 10 19:56 /etc/alternati
Bug#827650: system crashes using HDMI
I agree that the real problem have to be searched not in this library. Maybe there is a problem in the driver. The crashing of the system maybe a defect of the hardware of the vga card. After i changed the card the system is running stable. Thanks.
Bug#827650: system crashes using HDMI
Package: libglib2.0-data Version: 2.42.1-1 Severity: important Please also refer to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751670 On an multimedia system i am using this VGA card: http://www.powercolor.com/br/products_features.asp?id=371#PowerColorRadeon%E2%84%A2HD65702GBDDR32 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device 2308 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at d000 (64-bit, prefetchable) [size=256M] Memory at fe9e (64-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=256] Expansion ROM at fe9c [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon There is a monitor (vga port) and a beamer connected (HDMI) to it - both using full HD resolution. When i use the monitor the system is running stable without problems. But when the beamer on the HDMI port is active, the system is crashing after a while! This can end up in a reboot loop! Everytime the system activates the graphic mode it crashes again. Disconnecting the HDMI the system can boot normal. I only found this error messages in the syslog: console-kit-daemon[1810]: console-kit-daemon[1810]: GLib-CRITICAL: Source ID 44 was not found when attempting to remove it console-kit-daemon[1810]: GLib-CRITICAL: Source ID 44 was not found when attempting to remove it I will try to make a copy of the running system to another parition and upgrade it to testing. -- System Information: Debian Release: 8.4 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#823403: Getting the STM32F10x standard peripheral library
I think i understand the problem. The standard library is published under the LIBERTY V2 - Software license agreement. So you must download and install the library for your own. You can do that at http://www2.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32-standard-peripheral-libraries/stsw-stm32054.html or you go to http://www2.st.com and search for STSW-STM32054. As registered user (email) you can download the library (21.1 MB). The USB-library (5.4 MB) can be found with STSW-STM32121 or here http://www2.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32-standard-peripheral-libraries-expansions/stsw-stm32121.html The next problem is howto install and use the libraries ? All standard search path can be shown with $ arm-none-eabi-gcc -print-search-dirs | grep libraries | sed 's/:/\n/g' results in: libraries =/usr/lib/gcc/arm-none-eabi/4.8/ /usr/lib/gcc/arm-none-eabi/4.8/../../../arm-none-eabi/lib/arm-none-eabi/4.8/ /usr/lib/gcc/arm-none-eabi/4.8/../../../arm-none-eabi/lib/ When i copy the complete structure of STM32F10x_StdPeriph_Driver to one of the above paths containing header files it does not work. Some help would be usefull to get it working. Is there any way to get the compiler working without any IDE like Eclipse? Regards Karsten
Bug#823403: gcc-arm-none-eabi: Missing header files for cortex microcontroller
Package: gcc-arm-none-eabi Version: 4.8.4-1+11-1 Severity: normal Hello, i want to do some programming with ARM STM32F103 microcontroller. So i installed gcc-arm-none-eabi. But when i try to compile something i get "fatal error: stm32f10x_conf.h: No such file or directory" So all the header files are missing! :-( I don't know if the path is not set correctly, but i can't find the files anywhere. I only found this header that only include "bigger" cpu's. /usr/lib/arm-none-eabi/include/c++/4.8/arm-none-eabi drwxr-xr-x 10 root root 4,0K Apr 10 12:58 . drwxr-xr-x 12 root root 4,0K Apr 10 12:58 .. drwxr-xr-x 4 root root 4,0K Apr 10 12:58 armv6-m drwxr-xr-x 3 root root 4,0K Apr 10 12:58 armv7-ar drwxr-xr-x 6 root root 4,0K Apr 10 12:58 armv7e-m drwxr-xr-x 4 root root 4,0K Apr 10 12:58 armv7-m drwxr-xr-x 2 root root 4,0K Apr 10 12:58 bits drwxr-xr-x 2 root root 4,0K Apr 10 12:58 ext drwxr-xr-x 4 root root 4,0K Apr 10 12:58 fpu drwxr-xr-x 4 root root 4,0K Apr 10 12:58 thumb How can i solve this problem? The avr-gcc package can be used for compiling immediately, why not this package? Maybe you can refer to this bug too: https://bugs.launchpad.net/gcc-arm-embedded/+bug/1309060 Best regards Karsten -- System Information: Debian Release: 8.3 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcc-arm-none-eabi depends on: ii binutils-arm-none-eabi 2.25-5+5+b1 ii libc6 2.19-18+deb8u2 ii libcloog-isl4 0.18.2-1+b2 ii libgcc1 1:4.9.2-10 ii libgmp102:6.0.0+dfsg-6 ii libisl100.12.2-2 ii libmpc3 1.0.2-1 ii libmpfr43.1.2-2 ii libstdc++6 4.9.2-10 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages gcc-arm-none-eabi recommends: ii libnewlib-arm-none-eabi 2.1.0+git20140818.1a8323b-2 gcc-arm-none-eabi suggests no packages. -- no debconf information
Bug#813105: nouveau driver freezing the system intermittently
Package: linux-image-3.16.0-4-amd64 Version: 3.16.7-ckt20-1+deb8u2 Severity: normal There is a problem with old graphic cards now, because the driver NVidida 96.43.23 is not maintained any more. I know - you will say: "Why you are using such an old graphic card?" :-) The problem is that the system fits the needs and you must throw away everything when you want to upgrade. I could not find any other AGP card with a driver that is maintained. The system works - but freezes intermittently and after waiting about one minute it will come back again. In the freeze time you can login remote over ssh and you see that the system is alive and not busy. So the nouveau driver is definitely blocking the complete X-server and desktop. I attach some additional logs i found in other logfiles. ** Kernel log: [ 2444.780065] nouveau E[Xorg[1577]] jmp_space: -16 [ 2444.920096] nouveau E[Xorg[1577]] jmp_space: -16 [ 2445.060333] nouveau E[Xorg[1577]] jmp_space: -16 [ 2445.201301] nouveau E[Xorg[1577]] jmp_space: -16 [ 2445.344187] nouveau E[Xorg[1577]] jmp_space: -16 [ 2445.486470] nouveau E[Xorg[1577]] jmp_space: -16 [ 2445.626545] nouveau E[Xorg[1577]] jmp_space: -16 [ 2445.766814] nouveau E[Xorg[1577]] jmp_space: -16 [ 2445.906794] nouveau E[Xorg[1577]] jmp_space: -16 [ 2446.047018] nouveau E[Xorg[1577]] jmp_space: -16 [ 2446.187153] nouveau E[Xorg[1577]] jmp_space: -16 [ 2446.327953] nouveau E[Xorg[1577]] jmp_space: -16 [ 2446.478885] nouveau E[Xorg[1577]] jmp_space: -16 [ 2446.627398] nouveau E[Xorg[1577]] jmp_space: -16 [ 2446.769086] nouveau E[Xorg[1577]] jmp_space: -16 [ 2446.911374] nouveau E[Xorg[1577]] jmp_space: -16 [ 2447.052038] nouveau E[Xorg[1577]] jmp_space: -16 [ 2447.192485] nouveau E[Xorg[1577]] jmp_space: -16 [ 2447.335349] nouveau E[Xorg[1577]] jmp_space: -16 [ 2447.477759] nouveau E[Xorg[1577]] jmp_space: -16 [ 2447.619030] nouveau E[Xorg[1577]] jmp_space: -16 [ 2447.759054] nouveau E[Xorg[1577]] jmp_space: -16 [ 2447.900906] nouveau E[Xorg[1577]] jmp_space: -16 [ 2448.043214] nouveau E[Xorg[1577]] jmp_space: -16 [ 2448.183871] nouveau E[Xorg[1577]] jmp_space: -16 [ 2448.329252] nouveau E[Xorg[1577]] jmp_space: -16 [ 2448.473382] nouveau E[Xorg[1577]] jmp_space: -16 [ 2448.615237] nouveau E[Xorg[1577]] jmp_space: -16 [ 2448.755767] nouveau E[Xorg[1577]] jmp_space: -16 [ 2448.896203] nouveau E[Xorg[1577]] jmp_space: -16 [ 2449.039829] nouveau E[Xorg[1577]] jmp_space: -16 [ 2449.180021] nouveau E[Xorg[1577]] jmp_space: -16 [ 2449.319917] nouveau E[Xorg[1577]] jmp_space: -16 [ 2449.465706] nouveau E[Xorg[1577]] jmp_space: -16 [ 2449.606445] nouveau E[Xorg[1577]] jmp_space: -16 [ 2449.746298] nouveau E[Xorg[1577]] jmp_space: -16 [ 2449.892729] nouveau E[Xorg[1577]] jmp_space: -16 [ 2450.035774] nouveau E[Xorg[1577]] jmp_space: -16 [ 2450.176489] nouveau E[Xorg[1577]] jmp_space: -16 [ 2450.316505] nouveau E[Xorg[1577]] jmp_space: -16 [ 2450.462322] nouveau E[Xorg[1577]] jmp_space: -16 [ 2450.618877] nouveau E[Xorg[1577]] jmp_space: -16 [ 2450.759495] nouveau E[Xorg[1577]] jmp_space: -16 [ 2450.906189] nouveau E[Xorg[1577]] jmp_space: -16 [ 2451.046154] nouveau E[Xorg[1577]] jmp_space: -16 [ 2451.187436] nouveau E[Xorg[1577]] jmp_space: -16 [ 2451.328375] nouveau E[Xorg[1577]] jmp_space: -16 [ 2451.468396] nouveau E[Xorg[1577]] jmp_space: -16 [ 2451.609581] nouveau E[Xorg[1577]] jmp_space: -16 [ 2451.749636] nouveau E[Xorg[1577]] jmp_space: -16 [ 2451.889852] nouveau E[Xorg[1577]] jmp_space: -16 [ 2452.030453] nouveau E[Xorg[1577]] jmp_space: -16 [ 2452.171342] nouveau E[Xorg[1577]] jmp_space: -16 [ 2452.311317] nouveau E[Xorg[1577]] jmp_space: -16 [ 2452.451588] nouveau E[Xorg[1577]] jmp_space: -16 [ 2452.594432] nouveau E[Xorg[1577]] jmp_space: -16 [ 2452.735198] nouveau E[Xorg[1577]] jmp_space: -16 [ 2452.876073] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.016838] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.157556] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.298711] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.438509] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.578319] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.719807] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.859896] nouveau E[Xorg[1577]] jmp_space: -16 [ 2453.999793] nouveau E[Xorg[1577]] jmp_space: -16 [ 2454.139701] nouveau E[Xorg[1577]] jmp_space: -16 [ 2454.280186] nouveau E[Xorg[1577]] jmp_space: -16 [ 2454.420377] nouveau E[Xorg[1577]] jmp_space: -16 [ 2454.560727] nouveau E[Xorg[1577]] jmp_space: -16 [ 2454.700667] nouveau E[Xorg[1577]] jmp_space: -16 [ 2454.841558] nouveau E[Xorg[1577]] jmp_space: -16 [ 2454.981553] nouveau E[Xorg[1577]] jmp_space: -16 [ 2455.122365] nouveau E[Xorg[1577]] jmp_space: -16 [ 2455.351780] nouveau E[Xorg[1577]] jmp_space: -16 [ 2455.492125] nouveau E[Xorg[1577]] jmp_space: -16 [ 2455.644351] nouveau E[Xorg[1577]] jmp_space: -16 [ 2455.784106] nouveau E[Xorg[1577]] jmp_space: -16 [ 2455.924521] nouveau E[Xorg[1577]] jmp_space: -16 [ 2456.066058] nouveau E[Xorg[1577]] jmp_space: -16 [ 2456.206568] nouveau E[Xo
Bug#808240: guvcview not running anymore after system upgrade
Package: guvcview Version: 2.0.1+debian-1 Severity: important Hello, guvcview was running perfect on my laptop. But after the last upgrade it is unusable. When i try to start it then the windows open and closes directly. Starting from a shell shows the following errors: $ guvcview V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden Failed to create secure directory (/run/user/1000/pulse): Keine Berechtigung ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map Failed to create secure directory (/run/user/1000/pulse): Keine Berechtigung ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Verbindung verweigert Failed to create secure directory (/run/user/1000/pulse): Keine Berechtigung ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Verbindung verweigert Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden Cannot connect to server request channel jack server is not running or cannot be started Speicherzugriffsfehler dmesg shows guvcview[5365]: segfault at c ip 7f4ecbde4940 sp 7f4eb8649800 error 4 in libSDL2-2.0.so.0.2.0[7f4ecbd2d000+f9000] Please also have a look at this thread: http://ubuntuforums.org/showthread.php?t=2251286 Regards Karsten -- System Information: Debian Release: 8.2 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages guvcview depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-18+deb8u1 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u4 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1+deb8u1 ii libguvcview-1.0-02.0.1+debian-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 Versions of packages guvcview recommends: ii uvcdynctrl 0.2.4-1.1 guvcview suggests no packages. -- no debconf information
Bug#805352: closed by Michael Biebl (Bug#805352: fixed in avrdude 6.2-1)
Hello, i believe that my relevant bug is not fixed! http://savannah.nongnu.org/bugs/?41561 Is the release >= r1343 ? Am 17.11.2015 um 16:36 schrieb Debian Bug Tracking System: > We believe that the bug you reported is fixed in the latest version of > avrdude, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 805...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Michael Biebl (supplier of updated avrdude package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) >
Bug#805352: avrdude 6.2 released
Package: avrdude Version: 6.1-2 Severity: normal Hello, yesterday a new release of avrdude was released by Joerg Wunsch. http://download.savannah.gnu.org/releases/avrdude/avrdude-6.2.tar.gz With this release some important bugs has been fixed. It would be excellent to make an update and a new package for it. When you have not the time - how can i make a package for it? Maybe it can be released at the download page of avrdude instead. Regards Karsten -- System Information: Debian Release: 8.2 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages avrdude depends on: ii libc6 2.19-18+deb8u1 ii libelf1 0.159-4.2 ii libftdi1 0.20-2 ii libncurses5 5.9+20140913-1+b1 ii libreadline6 6.3-8+b3 ii libtinfo5 5.9+20140913-1+b1 ii libusb-0.1-4 2:0.1.12-25
Bug#799207: Kate C++ Helper Plugin
Package: kate Version: 4:4.14.2-2 Severity: wishlist Hello, i want to suggest to add this really nice plugin to the kate package. With this plugin you have extended functionality in developing C++ programs, you only find in big development environments. Just have a look at the description and screenshots on the homepage: http://zaufi.github.io/kate-cpp-helper-plugin.html You can find the KDE homepage here: http://kde-apps.org/content/show.php?content=148606 Up to now there was the problem to get this plugin compiled. But today i get support from the author and it is working now in Debian 8.2 (jessie). The complete discussion can be found here: https://github.com/zaufi/kate-cpp-helper-plugin/issues/24 Here a short description how to compile it successfull. Install the following packages: kdelibs5-dev libclang-3.5-dev libclang-common-3.5-dev libclang1-3.5 xapian libxapian22 libxapian-dev libboost-all-dev clang-3.5 (I can't say if all of them are needed) Then you download and compile the sources with this commands: $ git clone https://github.com/zaufi/kate-cpp-helper-plugin.git $ cd kate-cpp-helper-plugin $ git fetch $ git checkout issue-23 $ mkdir build $ cd build $ cmake .. $ make $ make install Currently i have not tested to install the files in the Debian directories i found in /usr/share/kde4/apps/kate/plugins/ Regards Karsten
Bug#799204: Kate C++ Helper Plugin
Package: kate Version: 4:15.08.0-1 Severity: wishlist Hello, i want to suggest to add this really nice plugin to the kate package. With this plugin you have extended functionality in developing C++ programs, you only find in big development environments. Just have a look at the description and screenshots on the homepage: http://zaufi.github.io/kate-cpp-helper-plugin.html You can find the KDE homepage here: http://kde-apps.org/content/show.php?content=148606 Up to now there was the problem to get this plugin compiled. But today i get support from the author and it is working now in Debian 8.2 (jessie). The complete discussion can be found here: https://github.com/zaufi/kate-cpp-helper-plugin/issues/24 Here a short description how to compile it successfull. Install the following packages: kdelibs5-dev libclang-3.5-dev libclang-common-3.5-dev libclang1-3.5 xapian libxapian22 libxapian-dev libboost-all-dev clang-3.5 (I can't say if all of them are needed) Then you download and compile the sources with this commands: $ git clone https://github.com/zaufi/kate-cpp-helper-plugin.git $ cd kate-cpp-helper-plugin $ git fetch $ git checkout issue-23 $ mkdir build $ cd build $ cmake .. $ make $ make install Currently i have not tested to install the files in the Debian directories i found in /usr/share/kde4/apps/kate/plugins/ Regards Karsten
Bug#791603: GUVCVIEW: couldn't open ~/.config/guvcview2/video0 for read
Package: guvcview Version: 2.0.1+debian-1 Severity: important Hello, it seems that an old bug is back in this newer package https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761230 When i try to start guvcview the window is opening and then direct closing again. So i am doing the same in a shell and get the following output: $ guvcview GUVCVIEW: couldn't open /home/karsten/.config/guvcview2/video0 for read: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden Cannot connect to server request channel jack server is not running or cannot be started Speicherzugriffsfehler With Debian Wheezy guvcview was working on the same hardware. Cheers Karsten -- System Information: Debian Release: 8.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages guvcview depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-18 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libguvcview-1.0-02.0.1+debian-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 Versions of packages guvcview recommends: ii uvcdynctrl 0.2.4-1.1 guvcview suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#790045: The ppd version 5.2 9 is not compatible with gutenprint 5.2.3
Package: cups-driver-gutenprint Version: 5.2.10-3 Severity: important Hello, after upgrading my system i run into the problem that i could not print anymore. But i could find a solution for the problem here: https://bbs.archlinux.org/viewtopic.php?id=102892 Running /usr/sbin/cups-genppdupdate solved the problem. This should be added to the installation script of the package. Cheers Karsten -- System Information: Debian Release: 8.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cups-driver-gutenprint depends on: ii dpkg 1.17.25 ii printer-driver-gutenprint 5.2.10-3 cups-driver-gutenprint recommends no packages. cups-driver-gutenprint suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782353: Security hole in server version 1.0.36
Maybe there are some additional ideas from the developers of ISPConfig. I have written my question here: https://www.howtoforge.com/community/threads/security-hole-in-ftp-server-version-1-0-36.69684/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782353: Security hole in server version 1.0.36
Am 11.04.2015 um 12:05 schrieb Stefan Hornburg (Racke): > OK, can you please tell me the contents of thefiles in /etc/pure-ftpd/auth so > we make sure that only MySQL > authentication is enabled? Regards Racke This file does not exist. They used a different configuration. I attached the complete tared directory. Of course the password is modified again. I would say PAM and MySQL authentification is used. Cheers Karsten etc.pure-ftpd.tgz Description: application/compressed-tar
Bug#782353: Security hole in server version 1.0.36
Am 11.04.2015 um 11:45 schrieb Stefan Hornburg (Racke):
> Hello Karsten, we need more information to conclude this is really a security
> hole in Pure-FTP. Which authentication
> methods are allowed? Can you send me the contents of the /etc/pure-ftpd
> directory? Regards Racke
At least there is only 1 configuration file with content.
I attached it with altered password.
This is the standard configuration generated by ISPConfig.
Regards
Karsten
##
##
# Sample Pure-FTPd Mysql configuration file. #
# See README.MySQL for explanations. #
##
##
# Optional : MySQL server name or IP. Don't define this for unix sockets.
MYSQLServer 127.0.0.1
# Optional : MySQL port. Don't define this if a local unix socket is used.
# MYSQLPort 3306
# Optional : define the location of mysql.sock if the server runs on this host.
# MYSQLSocket /var/run/mysqld/mysqld.sock
# Mandatory : user to bind the server as.
MYSQLUser ispconfig
# Mandatory : user password. You must have a password.
MYSQLPassword 0b482e3800421b833fab372df58d
# Mandatory : database to open.
MYSQLDatabase dbispconfig
# Mandatory : how passwords are stored
# Valid values are : "cleartext", "crypt", "md5" and "password"
# ("password" = MySQL password() function)
# You can also use "any" to try "crypt", "md5" *and* "password"
MYSQLCrypt crypt
# In the following directives, parts of the strings are replaced at
# run-time before performing queries :
#
# \L is replaced by the login of the user trying to authenticate.
# \I is replaced by the IP address the user connected to.
# \P is replaced by the port number the user connected to.
# \R is replaced by the IP address the user connected from.
# \D is replaced by the remote IP address, as a long decimal number.
#
# Very complex queries can be performed using these substitution strings,
# especially for virtual hosting.
# Query to execute in order to fetch the password
MYSQLGetPW SELECT password FROM ftp_user WHERE active = 'y' AND server_id
= '1' AND username="\L"
# Query to execute in order to fetch the system user name or uid
MYSQLGetUID SELECT uid FROM ftp_user WHERE active = 'y' AND server_id = '1'
AND username="\L"
# Optional : default UID - if set this overrides MYSQLGetUID
#MYSQLDefaultUID 1000
# Query to execute in order to fetch the system user group or gid
MYSQLGetGID SELECT gid FROM ftp_user WHERE active = 'y' AND server_id = '1'
AND username="\L"
# Optional : default GID - if set this overrides MYSQLGetGID
#MYSQLDefaultGID 1000
# Query to execute in order to fetch the home directory
MYSQLGetDir SELECT dir FROM ftp_user WHERE active = 'y' AND server_id = '1'
AND username="\L"
# Optional : query to get the maximal number of files
# Pure-FTPd must have been compiled with virtual quotas support.
MySQLGetQTAFS SELECT quota_files FROM ftp_user WHERE active = 'y' AND
server_id = '1' AND quota_files != '-1' AND username="\L"
# Optional : query to get the maximal disk usage (virtual quotas)
# The number should be in Megabytes.
# Pure-FTPd must have been compiled with virtual quotas support.
MySQLGetQTASZ SELECT quota_size FROM ftp_user WHERE active = 'y' AND server_id
= '1' AND quota_size != '-1' AND username="\L"
# Optional : ratios. The server has to be compiled with ratio support.
MySQLGetRatioUL SELECT ul_ratio FROM ftp_user WHERE active = 'y' AND server_id
= '1' AND ul_ratio != '-1' AND username="\L"
MySQLGetRatioDL SELECT dl_ratio FROM ftp_user WHERE active = 'y' AND server_id
= '1' AND dl_ratio != '-1' AND username="\L"
# Optional : bandwidth throttling.
# The server has to be compiled with throttling support.
# Values are in KB/s .
MySQLGetBandwidthUL SELECT ul_bandwidth FROM ftp_user WHERE active = 'y' AND
server_id = '1' AND ul_bandwidth != '-1' AND username="\L"
MySQLGetBandwidthDL SELECT dl_bandwidth FROM ftp_user WHERE active = 'y' AND
server_id = '1' AND dl_bandwidth != '-1' AND username="\L"
# Enable ~ expansion. NEVER ENABLE THIS BLINDLY UNLESS :
# 1) You know what you are doing.
# 2) Real and virtual users match.
# MySQLForceTildeExpansion 1
# If you upgraded your tables to transactionnal tables (Gemini,
# BerkeleyDB, Innobase...), you can enable SQL transactions to
# avoid races. Leave this commented if you are using the
# traditionnal MyIsam databases or old (< 3.23.x) MySQL versions.
MySQLTransactions On
Bug#774283: Solution for other users
> But you should think about an solution for the problem, because after the upgrade you did not have the chance to see anything, because the graphic card was dead. > When you have not another PC, network and a running SSH-Server on the system, you can't do anything to get it working again. This is really fatal! Here is an idea for other users who encounter the problem: When you are booting with grub you can manually edit the boot options in grub. https://www.gnu.org/software/grub/manual/html_node/gfxpayload.html Add "text" at the end of the kernel parameters to boot in a text console so that the X system will not be started. Then you can download and install the ATI driver in text mode. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774283: Problem identified and solved
Hello together, i did not install the backup and found the problem now. The ATI driver from March 2014 did not fit together with the updated X-Server package. I downloaded and installed the newest Catalyst driver from here and X is running now again: http://support.amd.com/de-de/download/desktop?os=Linux+x86 Version Omega (14.12) from 09.12.2014. So this bug can be closed now. But you should think about an solution for the problem, because after the upgrade you did not have the chance to see anything, because the graphic card was dead. When you have not another PC, network and a running SSH-Server on the system, you can't do anything to get it working again. This is really fatal! From my experience in the last year it is getting more and more difficult to get an working desktop system with running X and sound with Debian. There are problems with ATI and NVidia, such as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767678 Is there really no chance to get this problems covered? A failsafe system that has the possibilty to have X with a standard VGA resolution would be a milestone for Debian. I wish you a happy new year! Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774283: Failed to start X after system upgrade
Package: xserver-xorg-core Version: 2:1.12.4-6+deb7u5 Severity: important Hello, i simply made an system update yesterday and after restart X does not start anymore! The system is in usage so i have to wipe it and install an backup from the beginning of the month where everything was fine. I suppose the XServer is broken, because the Xorg.0.log stops without an error message. The main system is running and i can connect to it via SSH. But the screen is only black and also a TTY1 cannot be accessed locally! If this problem does not belong to the XServer, please move it to the correct package. Thanks. Here the packages that where updated. Start-Date: 2014-12-30 19:52:20 Upgrade: libsox-fmt-all:amd64 (14.4.0-3, 14.4.0-3+deb7u1), bind9-host:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), libsox-fmt-mp3:amd64 (14.4.0-3, 14.4.0-3+deb7u1), libsox-fmt-base:amd64 (14.4.0-3, 14.4.0-3+deb7u1), dnsutils:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), libdbus-1-3:amd64 (1.6.8-1+deb7u4, 1.6.8-1+deb7u5), libdbus-1-3:i386 (1.6.8-1+deb7u4, 1.6.8-1+deb7u5), unzip:amd64 (6.0-8, 6.0-8+deb7u1), apache2-suexec:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), apache2-mpm-worker:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), xserver-xorg-core:amd64 (1.12.4-6+deb7u2, 1.12.4-6+deb7u5), libsox-fmt-oss:amd64 (14.4.0-3, 14.4.0-3+deb7u1), libsox-fmt-pulse:amd64 (14.4.0-3, 14.4.0-3+deb7u1), linux-compiler-gcc-4.6-x86:amd64 (3.16.7-2~bpo70+1, 3.16.7-ckt2-1~bpo70+1), xserver-common:amd64 (1.12.4-6+deb7u2, 1.12.4-6+deb7u5), libsox-fmt-alsa:amd64 (14.4.0-3, 14.4.0-3+deb7u1), libdns88:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), subversion:amd64 (1.6.17dfsg- 4+deb7u6, 1.6.17dfsg-4+deb7u8), libsox2:amd64 (14.4.0-3, 14.4.0-3+deb7u1), linux-image-3.2.0-4-amd64:amd64 (3.2.63-2+deb7u1, 3.2.63-2+deb7u2), linux-headers-3.2.0-4-amd64:amd64 (3.2.63-2+deb7u1, 3.2.63-2+deb7u2), libisccc80:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), apache2-utils:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), iucode-tool:amd64 (0.8.3-1, 0.8.3-2), apache2:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), libsvn1:amd64 (1.6.17dfsg-4+deb7u6, 1.6.17dfsg-4+deb7u8), dbus:amd64 (1.6.8-1+deb7u4, 1.6.8-1+deb7u5), apache2.2-common:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), linux-headers-3.2.0-4-common:amd64 (3.2.63-2+deb7u1, 3.2.63-2+deb7u2), liblwres80:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), cpio:amd64 (2.11+dfsg-0.1, 2.11+dfsg-0.1+deb7u1), apache2.2-bin:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), libsox-fmt-ao:amd64 (14.4.0-3, 14.4.0-3+deb7u1), libbind9-80:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), ntp:amd64 (4.2.6.p5+dfsg-2, 4.2.6. p5+dfsg-2+deb7u1), sox:amd64 (14.4.0-3, 14.4.0-3+deb7u1), mime-support:amd64 (3.52-1, 3.52-1+deb7u1), libjasper1:amd64 (1.900.1-13+deb7u1, 1.900.1-13+deb7u2), libisccfg82:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), apache2-doc:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), bsd-mailx:amd64 (8.1.2-0.2006cvs-1, 8.1.2-0.2006cvs-1+deb7u1), libsox-fmt-ffmpeg:amd64 (14.4.0-3, 14.4.0-3+deb7u1), linux-libc-dev:amd64 (3.2.63-2+deb7u1, 3.2.63-2+deb7u2), host:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), intel-microcode:amd64 (1.20140624.1, 1.20140913.1), dbus-x11:amd64 (1.6.8-1+deb7u4, 1.6.8-1+deb7u5), libisc84:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), deb-multimedia-keyring:amd64 (2012.05.10-dmo4, 2014.2) End-Date: 2014-12-30 19:53:50 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jul 3 2013 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2048760 Dec 9 22:22 /usr/bin/Xorg Diversions concerning libGL are in place diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions VGA-compatible devices on PCI bus: -- 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Devic
Bug#767678: system upgrade
Am 01.11.2014 um 22:26 schrieb Vincent Cheng: I will have a look at this bugs. Thanks. But i am using the standard kernel 3.2.0 !? The newer kernel is only installed additionally for test purposes. Your attached reportbug logs show: uname -a: Linux PC10 3.13-0.bpo.1-amd64 #1 SMP Debian 3.13.10-1~bpo70+1 (2014-04-23) x86_64 GNU/Linux i.e. your running kernel was 3.13 when you hit this bug. O.K. This opens my eyes. Installing the kernel update did an update of the grub configuration. So the newer kernel was booted instead of the standard kernel and i did not realize it. Easy and embarrassing. I think it will work doing this right - I will test it. Do you think the problems with newer kernels will be solved? Maybe it is helpfull that i bug this against NVidia? Thank you. Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767678: system upgrade
Am 01.11.2014 um 22:14 schrieb Vincent Cheng: Hi Karsten, On Sat, Nov 1, 2014 at 1:41 PM, Karsten Malcher wrote: Hello, when i only upgrade all packages without the kernel package X still works. So linux-image-3.2.0-4-amd64 3.2.57-3+deb7u2 is the last one to get a running X with the NVidia driver. Anyhow for a GF108 [GeForce GT 430]. Why? Because you're attempting to use a backported kernel, and it's a known bug that linux >= 3.13 (i.e. wheezy-backports) doesn't work with the nvidia packages in wheezy/wheezy-backports (see #754108, #749703). I will have a look at this bugs. Thanks. But i am using the standard kernel 3.2.0 !? The newer kernel is only installed additionally for test purposes. Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767678: system upgrade
Hello, when i only upgrade all packages without the kernel package X still works. So linux-image-3.2.0-4-amd64 3.2.57-3+deb7u2 is the last one to get a running X with the NVidia driver. Anyhow for a GF108 [GeForce GT 430]. Why? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767678: nvidia-glx: xserver fails to start after last package upgrade
Package: nvidia-glx Version: 304.117-1 Severity: important Hello, i simply made an package upgrade and the start of X fails now. :-( This will be somehow a continuation of this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735424 After this i also tried to purge all nvidia* packages and to reinstall only nvidia-glx. But it does not help - X is dead! See the attached upgrade bugreport. I am very frustrated now, because Debian becomes unusable for me after many lucky years with it. But a working PC without X is not usable at all! After the upgrade i was thrown back into the stone age. The nouveau driver seems not to be able to drive big screen resolutions of 1920 X 1080 and the picture is bad. So this also makes no sense. In the other bugs you can see that it is not possible to make a new installation with testing, because i have no working X in another way. Now i can't make an upgrade of my last working system any more. :-( I was careful and made an backup before the upgrade. This i could extract to have a working PC again now. Is there really no hope for Debian and NVidia any more? Cheers Karsten Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: karsten To: Debian Bug Tracking System Subject: nvidia-glx: xserver does not start after reinstallation of nvidia-glx X-Debbugs-Cc: deb...@dct.mine.nu Package: nvidia-glx Version: 304.117-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 ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: uname -a: Linux PC10 3.13-0.bpo.1-amd64 #1 SMP Debian 3.13.10-1~bpo70+1 (2014-04-23) x86_64 GNU/Linux /proc/version: Linux version 3.13-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.13.10-1~bpo70+1 (2014-04-23) lspci 'VGA compatible controller [0300]': 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.00] Console: colour VGA+ 80x25 [0.418772] vgaarb: device added: PCI::02:00.0,decodes=io+mem,owns=io+mem,locks=none [0.418774] vgaarb: loaded [0.418775] vgaarb: bridge control possible :02:00.0 [1.116180] PCI-DMA: Disabling AGP. [1.116263] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture [1.195290] Linux agpgart interface v0.103 [4.015977] hda-intel :02:00.1: Handle VGA-switcheroo audio client [4.028311] nvidia: module license 'NVIDIA' taints kernel. [4.038080] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0) [4.823404] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:02:00.1/sound/card1/input16 [4.823609] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:02:00.1/sound/card1/input15 [4.823761] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:02:00.1/sound/card1/input14 [4.823907] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:02:00.1/sound/card1/input13 [8.752184] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0) OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Nov 1 19:25 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 41 Nov 1 19:25 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 41 Nov 1 19:25 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Nov 1 19:25 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Nov 1 19:25 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux
Bug#749264: No nvidia-driver working
Hello Vincent, thank you for your explanations! I suggest to add them to the Debian Wiki, because this system is not explained there. Shall i try to add it? When you google for specific problems you will find to much wrong hints. But here you see how many people have problems with this theme. ;-) Am 21.09.2014 11:44, schrieb Vincent Cheng: It's no surprise that X won't load, given that you're trying to use the nvidia 304.xx driver series with hardware that doesn't support it. O.K. - but why the 304.117 driver is installed when i install dkms? It would be better that there is a dependency that announces a conflict when i want to have a 173xx driver. Assuming you're just an uninformed user with no idea what dkms is and just want a working X server + nvidia driver...why would you care to install nvidia-kernel-dkms? All you would reasonably be expected to do is to run nvidia-detect and install whatever package it told you to install. Or if you were a new user with no knowledge of nvidia-detect, you would instead google for "nvidia debian" or similar, hit this wiki page [1] as your first search result, and then proceed to install the correct package. I assumed i need the dkms package to automatically recompile the display driver. Now i understand the differences. As i have written nouveau failed because it does not support this hardware. But the nouveau driver from Knoppix is doing it. Probably because Knoppix is using a newer kernel? I think so (should be /kernel/ 3.0.4) - but this is not a big difference. It is crazy that you need a newer kernel to support older hardware? As i said - there are to much much dependencies that are not understandable. Experiments with new kernels in an stable working environment is causing more problems than solving it. Then you have X but you loose sound or some interface hardware ... File bug reports against the kernel for specific issues. Also, you seem to have no issues using Knoppix (which AFAIK packages newer kernels than what is typically found in Debian stable...). Yes - but AFAIK there are no AMD64 versions of it. Debian has the best support for so many different CPU's. That's one of many reasons to use it. It is the base for so many other distributions. So it would be wonderful if the X-problems could be minimized at the base. Best regards Karsten [1] https://wiki.debian.org/NvidiaGraphicsDrivers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749264: No nvidia-driver working
Am 21.09.2014 11:08, schrieb Vincent Cheng: Hi Karsten, Fix your smtp server so that it stops timing out. The DSL was burned after a lightning bolt abd the server not reachable. So i installed # aptitude install nvidia-glx-legacy-173xx nvidia-kernel-dkms No, just install nvidia-glx-legacy-173xx (as suggested by nvidia-detect); its dependencies will ensure that you have a working nvidia 173.xx driver installed. Installing nvidia-kernel-dkms on wheezy will actually pull in the default 304.xx driver series, which is obviously not what you want. If you take a look at the log file you attached in your followup message... [42.428] (II) NVIDIA GLX Module 304.117 Tue Nov 26 21:45:09 PST 2013 [42.445] (WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is [42.445] (WW) NVIDIA(0): supported through the NVIDIA 173.14.xx Legacy drivers. [42.445] (WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for [42.445] (WW) NVIDIA(0): more information. The 304.117 NVIDIA driver will ignore [42.445] (WW) NVIDIA(0): this GPU. Continuing probe... [42.445] (EE) No devices detected. It's no surprise that X won't load, given that you're trying to use the nvidia 304.xx driver series with hardware that doesn't support it. O.K. - but why the 304.117 driver is installed when i install dkms? It would be better that there is a dependency that announces a conflict when i want to have a 173xx driver. That's what i am meaning - it is really hard to keep an overview what you must install and what dependencies exist. nouveau should work, yes; if it doesn't, please file a bug against the kernel. Have you tried fetching a kernel from wheezy-backports and seeing if you can run nouveau using a newer kernel? Regards, Vincent As i have written nouveau failed because it does not support this hardware. But the nouveau driver from Knoppix is doing it. Experiments with new kernels in an stable working environment is causing more problems than solving it. Then you have X but you loose sound or some interface hardware ... Best regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762271: This driver is not usable for the FX5200
Hello, i am sorry to say this and you will damn me for my bug report - but - the original driver from NVidia works! So this package is not usable. For other users with the same problem: Purge all nvidia packages from Debian and install the original driver. Let it generate a xorg.conf. Then you have a running X system. :-) Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762271: Legacy driver is not working with NVidia FX5200
Package: nvidia-glx-legacy-173xx Version: 173.14.35-4 Severity: normal Hello, please refer to my initial description at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749264#65 I will try to install the latest original NVidia driver now: NVIDIA-Linux-x86_64-173.14.39-pkg2.run Best regards Karsten -- Package-specific info: uname -a: Linux PC12 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux /proc/version: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 173.14.35 Fri Jun 8 00:07:59 PDT 2012 GCC version: gcc version 4.6.3 (Debian 4.6.3-14) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:9980] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: nvidia dmesg: [0.00] AGP bridge at 00:00:00 [0.00] Aperture from AGP @ ec00 old size 32 MB [0.00] Aperture from AGP @ ec00 size 32 MB (APSIZE 0) [0.00] Nvidia board detected. Ignoring ACPI timer override. [0.00] AGP bridge at 00:00:00 [0.00] Aperture from AGP @ ec00 old size 32 MB [0.00] Aperture from AGP @ ec00 size 32 MB (APSIZE 0) [0.00] Console: colour VGA+ 80x25 [0.164625] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.164625] vgaarb: loaded [0.164625] vgaarb: bridge control possible :01:00.0 [0.982094] agpgart-amd64 :00:00.0: AGP bridge [10de/00e1] [0.982103] agpgart-amd64 :00:00.0: aperture size 4096 MB is not right, using settings from NB [0.982109] agpgart-amd64 :00:00.0: setting up Nforce3 AGP [0.985127] agpgart-amd64 :00:00.0: AGP aperture is 64M @ 0xec00 [0.985205] PCI-DMA: Warning: Small IOMMU 32MB. Consider increasing the AGP aperture in BIOS [0.985213] PCI-DMA: Reserving 32MB of IOMMU area in the AGP aperture [1.188214] Linux agpgart interface v0.103 [6.827531] nvidia: module license 'NVIDIA' taints kernel. [7.614577] nvidia :01:00.0: PCI INT A -> Link[LNKD] -> GSI 17 (level, low) -> IRQ 17 [7.614586] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [7.615247] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 173.14.35 Fri Jun 8 00:07:59 PDT 2012 OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Sep 20 12:01 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 43 Sep 20 12:01 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Sep 20 12:01 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Sep 20 12:01 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 59 Sep 20 12:01 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 51 Sep 20 12:01 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Sep 20 12:01 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 29 Sep 20 12:01 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 23 Sep 20 12:01 /etc/alternatives/nvidia -> /usr/lib/nvidia/current lrwxrwxrwx 1 root root 51 Sep 20 12:01 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 51 Sep 20 12:01 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 59 Sep 20 12:01 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 67 Sep 20 12:01 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 33 Sep 20 12:01 /etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/current/libglx.so lrwxrwxrwx 1 root root 59 Sep 20 12:01 /etc/alternatives/nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 37
Bug#749264: No nvidia-driver working
Hello Vincent, maybe i always find the combination of hardware that is not running? For this PC the FX5200 is directly connected with DVI to the monitor. I tried to get a running X with the nouveau driver - but it does not work! For me it seems that a FX5200 is simply not supported: [ 1362.592] (II) NOUVEAU driver for NVIDIA chipset families : [ 1362.592]RIVA TNT(NV04) [ 1362.592]RIVA TNT2 (NV05) [ 1362.592]GeForce 256 (NV10) [ 1362.592]GeForce 2 (NV11, NV15) [ 1362.592]GeForce 4MX (NV17, NV18) [ 1362.592]GeForce 3 (NV20) [ 1362.592]GeForce 4Ti (NV25, NV28) [ 1362.592]GeForce FX (NV3x) [ 1362.592]GeForce 6 (NV4x) [ 1362.592]GeForce 7 (G7x) [ 1362.593]GeForce 8 (G8x) [ 1362.593]GeForce GTX 200 (NVA0) [ 1362.593]GeForce GTX 400 (NVC0) [ 1362.593] (--) using VT number 7 [ 1362.921] (EE) [drm] failed to open device [ 1362.921] (EE) No devices detected. So i booted Knoppix 6.7 and it works directly perfect!? What is the secret of Knoppix using Debian as underlaying distribution? I attached the log and xorg.conf from Knoppix. When i tried the Knoppix xorg.conf in Wheezy the screen cannot be found. The last thing i can try is to install the original driver from NVidia ... (Or simply use Knoppix). But before i will open a new bug against the legacy driver. Cheers Karsten [21.768] X.Org X Server 1.11.0 Release Date: 2011-08-26 [21.768] X Protocol Version 11, Revision 0 [21.768] Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian [21.768] Current Operating System: Linux Microknoppix 3.0.4 #12 SMP PREEMPT Thu Sep 8 05:27:05 CEST 2011 i686 [21.768] Kernel command line: ramdisk_size=10 lang=de vt.default_utf8=0 apm=power-off initrd=minirt.gz nomce libata.force=noncq hpsa.hpsa_allow_any=1 loglevel=1 tz=localtime BOOT_IMAGE=linux [21.768] Build Date: 28 August 2011 11:30:31AM [21.768] xorg-server 2:1.11.0-1 (Cyril Brulebois ) [21.768] Current version of pixman: 0.22.2 [21.768] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [21.768] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [21.768] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 20 11:32:37 2014 [21.770] (==) Using config file: "/etc/X11/xorg.conf" [21.770] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [21.771] (==) ServerLayout "XFree86 Configured" [21.771] (**) |-->Screen "Screen0" (0) [21.771] (**) | |-->Monitor "Monitor0" [21.774] (**) | |-->Device "Card0" [21.774] (**) Option "AllowMouseOpenFail" "true" [21.774] (**) Option "AIGLX" "true" [21.774] (==) Automatically adding devices [21.774] (==) Automatically enabling devices [21.778] (WW) The directory "/usr/share/fonts/X11/Speedo" does not exist. [21.778] Entry deleted from font path. [21.778] (WW) The directory "/usr/share/fonts/X11/PEX" does not exist. [21.778] Entry deleted from font path. [21.778] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [21.778] Entry deleted from font path. [21.778] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/truetype". [21.778] Entry deleted from font path. [21.778] (Run 'mkfontdir' on "/usr/share/fonts/truetype"). [21.778] (WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist. [21.778] Entry deleted from font path. [21.778] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [21.778] Entry deleted from font path. [21.779] (**) FontPath set to: /usr/share/fonts/X11/misc:unscaled, /usr/share/fonts/X11/75dpi:unscaled, /usr/share/fonts/X11/100dpi:unscaled, /usr/share/fonts/X11/Type1, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [21.779] (**) ModulePath set to "/usr/lib/xorg/modules" [21.779] (**) Extension "Composite" is enabled [21.779] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [21.780] (II) Loader magic: 0x822b800 [21.780] (II) Module ABI versions: [21.780] X.Org ANSI C Emulation: 0.4 [21.780] X.Org Video Driver: 11.0 [21.780] X.Org XInput driver : 13.0 [21.780] X.Org Server Extension : 5.0 [21.781] (--) PCI:*(0:1:0:0) 10de:0322:1462:9980 rev 161, Mem @ 0xfd00/16777216, 0xf000/134217728, BIOS @ 0x/131072 [21.781] (II) Open ACPI successful (/var/run/acpid.socket) [21.781
Bug#749264: No nvidia-driver working
Maybe I should add the attached log file for my example. [42.377] X.Org X Server 1.12.4 Release Date: 2012-08-27 [42.377] X Protocol Version 11, Revision 0 [42.378] Build Operating System: Linux 3.11-2-amd64 x86_64 Debian [42.378] Current Operating System: Linux PC12 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 [42.378] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 root=UUID=9df2eaa9-df3c-4638-bc44-9b0a80754178 ro quiet [42.378] Build Date: 17 December 2013 07:37:58PM [42.378] xorg-server 2:1.12.4-6+deb7u2 (Julien Cristau ) [42.378] Current version of pixman: 0.26.0 [42.379] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [42.379] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [42.380] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 20 12:41:35 2014 [42.380] (==) Using config file: "/etc/X11/xorg.conf" [42.380] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [42.381] (==) ServerLayout "Layout0" [42.381] (**) |-->Screen "Screen0" (0) [42.381] (**) | |-->Monitor "Monitor0" [42.381] (**) | |-->Device "Device0" [42.381] (**) |-->Input Device "Keyboard0" [42.381] (**) |-->Input Device "Mouse0" [42.381] (==) Automatically adding devices [42.381] (==) Automatically enabling devices [42.381] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [42.381] Entry deleted from font path. [42.382] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [42.382] (==) ModulePath set to "/usr/lib/xorg/modules" [42.382] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [42.382] (WW) Disabling Keyboard0 [42.382] (WW) Disabling Mouse0 [42.382] (II) Loader magic: 0x7f46afb95ae0 [42.382] (II) Module ABI versions: [42.382] X.Org ANSI C Emulation: 0.4 [42.382] X.Org Video Driver: 12.1 [42.382] X.Org XInput driver : 16.0 [42.382] X.Org Server Extension : 6.0 [42.383] (--) PCI:*(0:1:0:0) 10de:0322:1462:9980 rev 161, Mem @ 0xfd00/16777216, 0xf000/134217728, BIOS @ 0x/131072 [42.383] (II) Open ACPI successful (/var/run/acpid.socket) [42.383] (II) LoadModule: "extmod" [42.384] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [42.385] (II) Module extmod: vendor="X.Org Foundation" [42.385] compiled for 1.12.4, module version = 1.0.0 [42.385] Module class: X.Org Server Extension [42.385] ABI class: X.Org Server Extension, version 6.0 [42.385] (II) Loading extension SELinux [42.385] (II) Loading extension MIT-SCREEN-SAVER [42.385] (II) Loading extension XFree86-VidModeExtension [42.385] (II) Loading extension XFree86-DGA [42.385] (II) Loading extension DPMS [42.385] (II) Loading extension XVideo [42.385] (II) Loading extension XVideo-MotionCompensation [42.385] (II) Loading extension X-Resource [42.385] (II) LoadModule: "dbe" [42.386] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so [42.386] (II) Module dbe: vendor="X.Org Foundation" [42.386] compiled for 1.12.4, module version = 1.0.0 [42.386] Module class: X.Org Server Extension [42.386] ABI class: X.Org Server Extension, version 6.0 [42.386] (II) Loading extension DOUBLE-BUFFER [42.386] (II) LoadModule: "glx" [42.386] (II) Loading /usr/lib/xorg/modules/linux/libglx.so [42.428] (II) Module glx: vendor="NVIDIA Corporation" [42.428] compiled for 4.0.2, module version = 1.0.0 [42.428] Module class: X.Org Server Extension [42.428] (II) NVIDIA GLX Module 304.117 Tue Nov 26 21:45:09 PST 2013 [42.428] (II) Loading extension GLX [42.428] (II) LoadModule: "record" [42.429] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so [42.429] (II) Module record: vendor="X.Org Foundation" [42.429] compiled for 1.12.4, module version = 1.13.0 [42.429] Module class: X.Org Server Extension [42.429] ABI class: X.Org Server Extension, version 6.0 [42.429] (II) Loading extension RECORD [42.429] (II) LoadModule: "dri" [42.430] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so [42.430] (II) Module dri: vendor="X.Org Foundation" [42.430] compiled for 1.12.4, module version = 1.0.0 [42.430] ABI class: X.Org Server Extension, version 6.0 [42.431] (II) Loading extension XFree86-DRI [42.431] (II) LoadModule: "dri2" [42.431] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so [42.431] (II) Module dri2: vendor="X.Org Found
Bug#749264: No nvidia-driver working
Hello Vincent, i didn't get your email from Sat, 9 Aug 2014 or from the debian bug system. So i see it today in the bug system. Ok, I think the discussion has derailed quite a bit from the original bug report... Yes - sorry - but the problem is still alive. Karsten, I can sympathize with you, but to address your concern that the packages are "broken" and that we should be doing better, I'd say that the current nvidia packages in Debian are doing the utmost possible to make installing of the proprietary nvidia drivers as painless as possible (much of it thanks to Andreas, of course). Let me explain what we already have: ... I really see this and your work is great! But i only report here what i experience in the reality with my PC's. I don't think that this is an extraordinary hardware. One additional example from today: On a PC the NVidia VGA card died and i have to replace it. It is older hardware and i have a replacement that i simply installed. Now i installed the packages nvidia-detect and nvidia-xconfig. # nvidia-detect Detected NVIDIA GPUs: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) Your card is only supported up to the 173.14 legacy drivers series. It is recommended to install the nvidia-glx-legacy-173xx package. So i installed # aptitude install nvidia-glx-legacy-173xx nvidia-kernel-dkms After renaming the xorg.conf and reboot i land on the console! The error is "no screens found". I started nvidia-xconfig and a new xorg.conf has been generated. It shows: Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection Reboot - but nothing - the error "no screens found" still remains! So again i don't know what to do? What i am doing - it does not work! Given the constraints (i.e. the fact that the proprietary nvidia drivers are non-free, can't be installed by default, and how X is configured), I honestly don't know how/where you expect Debian to do better. For a usable system with X there should be always a running fallback like in windows. It should be nouveau for NVidia. I don't know exactly what Knoppix is doing, but here you get a running X in nearly all cases!? Why this is not possible in Debian? The packages work (at least, for me, and likely for many other users, given the high popcon count and relatively low number of bugs), and we (as in the pkg-nvidia team...well, mostly Andreas) have done our best to make the entire process as painless as possible. I mean, sure, there could be a bug somewhere that's caused by the packages, but I'm not seeing it. I believe this, but for me i always live in pain to get a running X. This i experienced on many different systems in many years. I am feeling it is running more and more worse than better. (Maybe because there is more and more different hardware out there.) But the future cannot be to boot Debian and have just a console with "have a lot of fun" like in the beginning of Linux. Then you must invest days to get a running X ... Best regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749264: No nvidia-driver working
Hello Adrian, Am 08.08.2014 12:58, schrieb John Paul Adrian Glaubitz: On 08/08/2014 12:43 PM, Karsten Malcher wrote: Fact is that it is impossible to simply upgrade an system without thrown back into an text shell! Well, blame nVidia for their shitty driver, but please don't blame us Debian people. The proprietary driver is really difficult to handle owed to the fact that most parts are closed source and only a small fraction of it, the kernel module glue or shim code, is open source. I don't want to blame you or other Debian people! It only think it would be very helpful when a package will cause a running X after installation when it exists. This is one of the (only) things that is working better in the installation of Kubuntu. Really good was and is the detection in Knoppix - why this is not possible in Debian? We can't really fix things which are binary-only. The proprietary driver is really a bitch to maintain and you should be aware that for most Debian Developers, the maintainer job is something they do in their free time and they're not getting paid for it. I know - and the time for testing and reporting bugs is not payed either. But we do it because we believe it is senseful (or at least i do it). As for that matter, I am using the free nouveau driver and I never run into any upgrade issues. So, you can either use the free driver or don't use an nVidia card on Linux at all. As I said, you are barking up the wrong tree. Really? It's nearly impossible to buy graphic cards with no 3D functionality now. So it is a great pity only to use it as tea warmer. For me it is really amazing and useful to use some of the opengl effects that are possible. And there are more and more game developer, who are going to use free 3D engines to make it possible to avoid Windows (see http://de.wikipedia.org/wiki/Liste_von_Spiel-Engines). (And often you loose the ability for sound and other multimedia too). How is that related to the nVidia driver? Why i set it in brackets? :-) This can happen also after an simple upgrade in the same distribution version. I have installed Linux (Kubuntu and Debian) on the PC's of two normal users. First they where very happy to get rid of the world of windows terror. But now both where back to windows because it is unacceptable to get an unusable PC after an simple upgrade! Well, my mom has been rocking Ubuntu on her Asus eeePC for quite a while now and she never complained. Yes - it's the same with a friend of mine. But he also does not really use Multimedia features. In jessie im am feeling the same way, because nothing seems to work. No X, chaotic kernel versions and everything seems to loose in chaos. Well, Jessie is a *testing* distribution and therefore unreleased. You shouldn't actually be using it unless you know what you are doing. If you want something *stable*, you should actually use Debian stable and not testing. I use stable and i am happy! But you are correct - maybe i expect to much here. In the history it was no problem to wait about half of a year after one Debian was stable and then move to Testing again. This time it seems to need much more time to get in Beta state ... I mean, you are not using beta versions of MacOS X or Windows either, are you? I always use what is running stable or nearly stable. But after a time i am curious for the testing version or need newer versions of some applications. At least this is testing on another partition and helping to find bugs. Maybe wheezy is the last usable Debian version you can really work with. That's probably related to the fact that Debian Wheezy *is* actually a current stable release. Yes - i will not complain about bugs in testing any more. :-) I hope you will understand what i want to say? Well, you are complaining about beta software breaking your system if I am getting this right. No - i am complaining that it is still a pain to get a running X-system after so much years of Linux. Before wheezy i never could get X running without installation of the original NVidia drivers. Now it seems to be impossible to get it running - what a progress? In the history i always was damned too from Debian people to use the NVidia driver instead of the packages. But what shall i do? But i am talking about the reasons why Linux have no chance to get an accepted OS to work with. Look, I don't actually care what people consider an accepted OS. Where I work, we deploy Debian Wheezy on over 150 desktops and since we are running a stable version, we are hardly having any issues. In fact, we usually have less issues than with the Windows 7 machines that we deploy as well. That's really interesting and a good reference to use Linux as desktop system. But you or a service team look for the problems and not the user itself - correct? It would be wonderful if there could be always a running fallback for X
Bug#749264: No nvidia-driver working
Hello Adrian, Am 01.08.2014 18:19, schrieb John Paul Adrian Glaubitz: I don't know how to create an xorg.conf? You maybe should have read the Debian Wiki before complaining and filing invalid bug reports. It's all there, please have a look at [1]. I understand this - but it is only one point of view. Fact is that it is impossible to simply upgrade an system without thrown back into an text shell! (And often you loose the ability for sound and other multimedia too). This can happen also after an simple upgrade in the same distribution version. I have installed Linux (Kubuntu and Debian) on the PC's of two normal users. First they where very happy to get rid of the world of windows terror. But now both where back to windows because it is unacceptable to get an unusable PC after an simple upgrade! In jessie im am feeling the same way, because nothing seems to work. No X, chaotic kernel versions and everything seems to loose in chaos. Maybe wheezy is the last usable Debian version you can really work with. After that i am feeling back to the time of "Have a lot of fun" on a text shell. I hope you will understand what i want to say? I don't want to criticize your engagement - i want to thank you for your support! But i am talking about the reasons why Linux have no chance to get an accepted OS to work with. Is it only intended for server use? There where so many changes in the X system an the drivers and as i know it normally runs without any xorg.conf now. Yes, and the automatic detection defaults to the open source nouveau drivers which are shipped with X.Org which fail to load because you also loaded the proprietary nvidia kernel module. You explitcitly have to tell X.Org to use the proprietary nvidia driver, that's all you need in /etc/X11/xorg.conf: Section "Device" Identifier "nVidia proprietary driver" Driver "nvidia" EndSection That's already enough to get X up and running with the proprietary drivers. The rest can be configured using xrandr. I tried it but it does not work. Please remember that i set up a new clean installation. When nouveau is really the intended standard, then we need no modern PC's with 3D graphic cards any more. In wheezy it is working with all graphic power! Can I assume the bug report to be invalid and close it? You can assume that this package is not usable - sorry. The only chance maybe is to use the original drivers from NVidia. But the really thing that is needed is that you install Debian and you can run X afterwards without problems. Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752901: Multiple sound cards in XFCE
Am 28.06.2014 11:01, schrieb Yves-Alexis Perez: On sam., 2014-06-28 at 10:51 +0200, Karsten Malcher wrote: Am 28.06.2014 10:31, schrieb Yves-Alexis Perez: On sam., 2014-06-28 at 10:17 +0200, Karsten Malcher wrote: The final question is how to handle multiple sound cards in Debian with XFCE? Well, for me “handle multiple sound cards” doesn't mean really anything. Xfce doesn't “handle” sound cards (the kernel does, somehow). Yes - of course - but you know what i mean. No, see above. Really - Debian seems to be a distribution that is intended for server use only. ;-) If you want to tune the volume, then xfce4-mixer can do that, and xfce4-volumed does it too. Controlling the volume of the different sources is really the minimum. But there are different reasons to select a sound device. 1. You use XFCE as desktop on a laptop and you want to switch to an external device e.g. HDMI There's no such thing as “switch”. Either the EC or kernel handle that by itself (for example when plugging a headphone), or you do that completely manually (you mute the volume on one output and unmute on the other). Yes - but this only works when it is the same output device. As said above there's no “handling” of sound card in Xfce, it doesn't try to be smart or anything. Maybe - but there could be an additional point of view: The use of the existant hardware has nothing to do with the smartness of the X-system. When the hardware can only be controlled direct in the underlaying Linux the use XFCE can be doubtful. 2. You use an additional sound card as simple DA-converter for different purposes. Definitely out of scope. Really? http://grade2linux.wordpress.com/2013/03/18/xfce-with-multiple-sound-cards/ In Debian I have only the attached volume control. It seems that the volume control in the article is the pavucontrol. So using Pulseaudio seems to be the only way to control different sound devices in XFCE. I will not test it in XFCE but i can say it works in KDE. Here is another helpful link: http://forum.xfce.org/viewtopic.php?id=7216 Please check the screenshot i posted first. The 'active-card' property is missing in the Debian configuration! How can i add it (correct) ? In xfce4-settings-editor, click “new”? O.K. i missed to enter a beginning "/" for the property. Thank you for your support! Karsten
Bug#752901: Multiple sound cards in XFCE
Am 28.06.2014 10:31, schrieb Yves-Alexis Perez: On sam., 2014-06-28 at 10:17 +0200, Karsten Malcher wrote: The final question is how to handle multiple sound cards in Debian with XFCE? Well, for me “handle multiple sound cards” doesn't mean really anything. Xfce doesn't “handle” sound cards (the kernel does, somehow). Yes - of course - but you know what i mean. If you want to tune the volume, then xfce4-mixer can do that, and xfce4-volumed does it too. Controlling the volume of the different sources is really the minimum. But there are different reasons to select a sound device. 1. You use XFCE as desktop on a laptop and you want to switch to an external device e.g. HDMI 2. You use an additional sound card as simple DA-converter for different purposes. xfce4-volumed is designed to be minimal, so it doesn't have any configuration interface, it just use the 'active-card' property of xfce4-mixer settings in xfconf. Please check the screenshot i posted first. The 'active-card' property is missing in the Debian configuration! How can i add it (correct) ? Regards Karsten Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752901: Multiple sound cards in XFCE
I will close the bug now - it seems to be more a (missing) feature than a bug. What i mean is the following: 1. When you search for the problem you will find this link: http://forum.xfce.org/viewtopic.php?id=7121 You will be directed to link i posted first. https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/885956/comments/9 But this is not helpfull, because the entries are missing in Debian? 2. You find alternative description like this: http://ubuntuforums.org/showthread.php?t=1941411 Here the solution is to use pavucontrol. But pavucontrol is to control the settings of Pulseaudio. I installed it but of course it does not help because Pulseaudio is not installed. There are enough problems with Pulseaudio itself, so it is a good idea to avoid the installation of it. The final question is how to handle multiple sound cards in Debian with XFCE? Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752901: Possible solution
I could solve the problem now in ALSA.
I generated a file /etc/asound.conf with this content:
pcm.!default {
type hw
card 1
}
ctl.!default {
type hw
card 1
}
Now the correct sound card is the standard device and the sound is working.
But why it is not possible to select the sound card in XFCE so that it is
working?
What you have to do to use multiple sound devices?
Cheers
Karsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752901: An additional test
It seems that nothing works: $ mpg123 test.mp3 | aplay ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave aplay: main:682: Fehler beim Öffnen des Gerätes: Datei oder Verzeichnis nicht gefunden Cannot connect to server socket err = No such file or directory Cannot connect to server request channel exec of JACK server (command = "/usr/bin/jackd") failed: No such file or directory Cannot connect to server socket err = No such file or directory Cannot connect to server request channel Cannot connect to server socket err = No such file or directory Cannot connect to server request channel Cannot connect to server socket err = No such file or directory Cannot connect to server request channel Cannot connect to server socket err = No such file or directory Cannot connect to server request channel Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [jack.c:252] error: Failed to open jack client: 0x11 [jack.c:58] warning: FIXME: One needs to wait or write some silence here to prevent the last bits of audio to vanish out of the ringbuffer. [module.c:142] error: Failed to open module portaudio: file not found [pulse.c:84] error: Failed to open pulse audio output: Connection refused [nas.c:220] error: could not open default NAS server $ cat /proc/asound/cards 0 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeb44000 irq 57 1 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xfeb4 irq 16 Sorry but i have not enough knowledge how sound works in XFCE. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752901: It is not possible to select the sound card
Package: xfce4-mixer Version: 4.8.0-3+b1 Severity: important After an system upgrade the sound does not work any more. It seems that the HDMI sound is standard and cannot be changed. # aplay -l Liste der Hardware-Geräte (PLAYBACK) Karte 0: HDMI [HDA ATI HDMI], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: HDMI [HDA ATI HDMI], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Generic [HD-Audio Generic], Gerät 0: ALC892 Analog [ALC892 Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Generic [HD-Audio Generic], Gerät 1: ALC892 Digital [ALC892 Digital] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Additional i found this link that is maybe helpful: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/885956/comments/9 An "active-card property" is missing (screenshot attached). The sound cards can't be seen. Regards Karsten -- System Information: Debian Release: 7.5 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-mixer depends on: ii gstreamer0.10-alsa [gstreamer0.10-audiosink] 0.10.36-1.1 ii gstreamer0.10-plugins-bad [gstreamer0.10-audiosink] 0.10.23-7.1+deb7u1 ii gstreamer0.10-plugins-base 0.10.36-1.1 ii gstreamer0.10-plugins-good [gstreamer0.10-audiosink 0.10.31-3+nmu1 ii libc62.13-38+deb7u1 ii libcairo21.12.2-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgstreamer-plugins-base0.10-0 0.10.36-1.1 ii libgstreamer0.10-0 0.10.36-1.2 ii libgtk2.0-0 2.24.10-2 ii libxfce4ui-1-0 4.8.1-1 ii libxfce4util44.8.2-1 ii libxfconf-0-24.8.1-1 ii xfce4-panel 4.8.6-4 xfce4-mixer recommends no packages. xfce4-mixer suggests no packages. -- no debconf information
Bug#737784: Wrong kernel installed after upgrade
Hello Guillem, i think it's better to close this bug. I will send the closing mail now. Fact is that there where several problems with an upgrade from wheezy to jessie. As there are much new packages now in jessie i can't say if this problem still exists. Thanks for your reply and investigation. Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749264: xorg.conf
After that i tried to copy the working xorg.conf from wheezy to jessie (attached). This seems not to fit for jessie as you can see. It's really hopeless ... Cheers Karsten # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 260.19.21 (buildmeister@builder101) Thu Nov 4 21:47:28 PDT 2010 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection [ 152.983] X.Org X Server 1.15.1 Release Date: 2014-04-13 [ 152.983] X Protocol Version 11, Revision 0 [ 152.983] Build Operating System: Linux 3.13-1-amd64 x86_64 Debian [ 152.983] Current Operating System: Linux PC10 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 [ 152.983] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64 root=/dev/sda3 [ 152.983] Build Date: 15 April 2014 06:58:36PM [ 152.984] xorg-server 2:1.15.1-1 (http://www.debian.org/support) [ 152.984] Current version of pixman: 0.32.4 [ 152.984] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 152.984] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 152.985] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 26 10:56:42 2014 [ 152.985] (==) Using config file: "/etc/X11/xorg.conf" [ 152.985] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 152.986] (==) ServerLayout "Layout0" [ 152.986] (**) |-->Screen "Screen0" (0) [ 152.986] (**) | |-->Monitor "Monitor0" [ 152.986] (**) | |-->Device "Device0" [ 152.986] (**) |-->Input Device "Keyboard0" [ 152.986] (**) |-->Input Device "Mouse0" [ 152.986] (==) Automatically adding devices [ 152.986] (==) Automatically enabling devices [ 152.986] (==) Automatically adding GPU devices [ 152.986] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 152.986] Entry deleted from font path. [ 152.986] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 152.986] (==) ModulePath set to "/usr/lib/xorg/modules" [ 152.986] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 152.986] (WW) Disabling Keyboard0 [ 152.986] (WW) Disabling Mouse0 [ 152.986] (II) Loader magic: 0x7f5abe804d40 [ 152.986] (II) Module ABI versions: [ 152.986] X.Org ANSI C Emulation: 0.4 [ 152.986] X.Org Video Driver: 15.0 [ 152.986] X.Org XInput driver : 20.0 [ 152.986] X.Org Server Extension : 8.0 [ 152.987] (--) PCI:*(0:2:0:0) 10de:0de1:: rev 161, Mem @ 0xfd00/16777216, 0xd800/134217728, 0xd600/33554432, I/O @ 0xc800/128, BIOS @ 0x/524288 [ 152.987] Initializing built-in extension Generic Event Extension [ 152.987] Initializing built-in extension SHAPE [ 152.987] Initializing built-in extension MIT-SHM [ 152.988] Initializing built-in extension XInputExtension [ 152.988] Initializing built-in extension XTEST [ 152.988] Initializing built-in extension BIG-REQUESTS [ 152.988] Initializing built-in extension SYNC [ 152.988] Initializing built-in extension XKEYBOARD [ 152.988] Initializing built-in extension XC-MISC [ 152.988] Initializing built-in extension SECURITY [ 152.988] Initializing built-in extension XINERAMA [ 152.988] Initializing built-in extension XFIXES [ 152.989] Initializing built-in extension RENDER [ 152.989] Initializing built-in extension RANDR [ 152.989] Initializing built-in extension COMPOSITE [ 152.989] Initializing built-in extension DAMAGE [ 152.989] Initializing built-in extension MIT-SCREEN-SAVER [ 152.989] Initializing built-in extension DOUBLE-BUFFE
Bug#749264: No nvidia-driver working
I tried to follow the Documentation now: https://wiki.debian.org/Xorg Why it is not possible to ask the user in the configuration script of the package if it should start "Xorg -configure" ? Nevertheless it does not work. The result is X.Org X Server 1.15.1 Release Date: 2014-04-13 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.13-1-amd64 x86_64 Debian Current Operating System: Linux PC10 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64 root=/dev/sda3 Build Date: 15 April 2014 06:58:36PM xorg-server 2:1.15.1-1 (http://www.debian.org/support) Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 26 10:39:28 2014 List of video drivers: r128 trident savage nouveau neomagic cirrus ati modesetting tdfx vmware radeon intel sisusb siliconmotion nvidia mga openchrome mach64 vesa fbdev (++) Using config file: "/root/xorg.conf.new" (==) Using system config directory "/usr/share/X11/xorg.conf.d" Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. There is only one screen connected over DVI ??? That makes no sense for me. Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749264: No nvidia-driver working
Am 25.05.2014 23:39, schrieb Andreas Beckmann: On 2014-05-25 19:55, Karsten Malcher wrote: Then i installed all the packages i have installed in my old wheezy installation, including KDE and nvidia-driver. I landed on the console after reboot! I don't see any traces that you created an xorg.conf to enable the proprietary driver, the xorg logs shows that it loaded nouveau ... Andreas I don't know how to create an xorg.conf? There where so many changes in the X system an the drivers and as i know it normally runs without any xorg.conf now. When an xorg.conf is needed, why it is not generated? Why there is no clear message what to do when it can't be done automatically? Please don't missunderstand me, but a running X after an installation is really basical. The X system is to complex to know what to do as "normal user". Landing on the console is a step backwards for 10 years or more. Maybe now you say "why you don't use the nouveau driver when it's working?" My answer is: "Why i have to go without 3D glx functions and the real potential of the graphics card?" Why there is no easy way to switch back to nouveau when the nvidia-driver does not work? Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737784: New email address
Control: submitter -1 ! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: New email address
Control: submitter -1 ! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749264: No nvidia-driver working
Am 25.05.2014 23:39, schrieb Andreas Beckmann: On 2014-05-25 19:55, Karsten Malcher wrote: Then i installed all the packages i have installed in my old wheezy installation, including KDE and nvidia-driver. I landed on the console after reboot! I don't see any traces that you created an xorg.conf to enable the proprietary driver, the xorg logs shows that it loaded nouveau ... Andreas I don't know how to create an xorg.conf? There where so many changes in the X system an the drivers and as i know it normally runs without any xorg.conf now. When an xorg.conf is needed, why it is not generated? Why there is no clear message what to do when it can't be done automatically? Please don't missunderstand me, but a running X after an installation is really basical. The X system is to complex to know what to do as "normal user". Landing on the console is a step backwards for 10 years or more. Maybe now you say "why you don't use the nouveau driver when it's working?" My answer is: "Why i have to go without 3D glx functions and the real potential of the graphics card?" Why there is no easy way to switch back to nouveau when the nvidia-driver does not work? Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: A new clean Installation of jessie is not working either
Hello, i tried a new run with a fresh clean installation of jessie: It does not work and there where many updates in the time between ... http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749264 Regarding this bug please always send a copy to my NEW email-address. The old domain does not exist any more. Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743706: Package broken due to initramfs-tools (< 0.110~) is 0.109.1
Package: linux-image-3.13-0.bpo.1-amd64 Version: 3.13.7-1~bpo70+1 Severity: important Hello, the package cannot be installed, because the dependency to initramfs-tools is incorrect. Regards Karsten -- System Information: Debian Release: 7.3 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver
Sorry for the delay! I didn't see to much sense in rolling back the original driver, so i made a new system upgrade. Booting another system i copied my actual system again to the partition. Then i boot it and made the system upgrade with interesting results: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737784 Of course X is not running again. I attached the test you requested. Cheers Karsten Paket build-essential: i A 11.6 testing 500 Paket dkms: i A 2.2.0.3-1.2 testing 500 Paket gcc: i A 4:4.8.2-2 testing 500 Paket gcc-4.3-base: id 4.3.5-4 100 Paket gcc-4.4: i A 4.4.7-7 testing 500 Paket gcc-4.4-base: i 4.4.7-7 testing 500 Paket gcc-4.6: i A 4.6.4-5 testing 500 Paket gcc-4.6-base: i A 4.6.4-5 testing 500 Paket gcc-4.7: i A 4.7.3-10 testing 500 Paket gcc-4.7-base: i A 4.7.3-10 testing 500 Paket gcc-4.7-base:i386: i A 4.7.3-10 testing 500 Paket gcc-4.8: i A 4.8.2-14 testing 500 Paket gcc-4.8-base: i A 4.8.2-14 testing 500 Paket gcc-4.8-base:i386: i A 4.8.2-14 testing 500 Paket gcc-avr: i 1:4.8-2 testing 500 Paket libgcc-4.7-dev: i A 4.7.3-10 testing 500 Paket libgcc-4.8-dev: i A 4.8.2-14 testing 500 Paket libgcc1: i 1:4.8.2-14testing 500 Paket libgcc1:i386: i A 1:4.8.2-14testing 500 Paket libreoffice-report-builder-bin: i A 1:4.1.4-2+b1 testing 500 Paket libresid-builder0c2a: i A 2.1.1-14 testing 500 Paket librpmbuild3: i A 4.11.1-3 testing 500 Paket linux-compiler-gcc-4.8-x86: i A 3.12.6-2 testing 500 Paket linux-headers-3.12-1-amd64: i A 3.12.6-2 testing 500 Paket linux-headers-3.12-1-common: i A 3.12.6-2 testing 500 Paket linux-headers-amd64: i A 3.12+55 testing 500 Paket linux-image-3.12.6: i 3.12.6 100 Paket linux-kbuild-2.6.32: id 2.6.32-1100 Paket linux-kbuild-3.12: i A 3.12.6-1 testing 500
Bug#737784: wrong kernel installed after upgrtade
Package: dpkg Version: 1.17.6 Severity: important Hello, i tried to upgrade from wheezy to jessie with the following steps: 1. I altered sources.list 2. apt-get update 3. apt-get dist-upgrade 4. apt-get remove linux-image-3.2.0-3-amd64 5. apt-get remove linux-headers-3.2.0-3-amd64 linux-headers-3.2.0-3-common 6. apt-get remove linux-headers-3.2.0-4-amd64 linux-headers-3.2.0-4-common As result i get a system booting a kernel 3.2.0-4 !? That's what i can see afterwards after a reboot: uname -a Linux PC10 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux dpkg -l rc linux-image-2.6.32-5-amd642.6.32-38 amd64 Linux 2.6.32 for 64-bit PCs rc linux-image-3.1.0-1-amd64 3.1.6-1amd64 Linux 3.1 for 64-bit PCs ii linux-image-3.12.63.12.6 amd64Linux kernel binary image for version 3.12.6 rc linux-image-3.2.0-3-amd64 3.2.23-1 amd64 Linux 3.2 for 64-bit PCs ii linux-headers-3.12-1-amd643.12.6-2 amd64 Header files for Linux 3.12-1-amd64 ii linux-headers-3.12-1-common 3.12.6-2 amd64 Common header files for Linux 3.12-1 ii linux-headers-amd64 3.12+55amd64Header files for Linux amd64 configuration (meta-package) ls -l /boot -rw-r--r-- 1 root root 127K Feb 2 02:16 config-3.2.0-4-amd64 drwxr-xr-x 3 root root 4,0K Feb 4 18:32 extlinux drwxr-xr-x 5 root root 12K Feb 4 18:32 grub -rw-r--r-- 1 root root 8,7M Dez 3 2010 initrd.img-2.6.32-5-amd64.org -rw-r--r-- 1 root root 11M Feb 2 19:03 initrd.img-3.2.0-4-amd64 -rw-r--r-- 1 root root 173K Nov 13 2011 memtest86+.bin -rw-r--r-- 1 root root 175K Nov 13 2011 memtest86+_multiboot.bin -rw-r--r-- 1 root root 2,1M Feb 2 02:16 System.map-3.2.0-4-amd64 -rw-r--r-- 1 root root 2,8M Feb 2 01:51 vmlinuz-3.2.0-4-amd64 How this is possible? Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver: New vesa test
Am 29.01.2014 12:52, schrieb Diederik de Haas: O.K. - but what is the difference? As "user" i expect to get the correct headers for the kernel linux-image-3.12-1-amd64 when i install 'linux-headers-3.12-1-amd64' That is correct. But you have the package 'linux-image-amd64' installed (and that's a good thing), so when a new kernel enters testing, it will be installed on your system and then you won't have the corresponding headers package on your system. No - i only installed the package linux-headers-3.12-1-amd64. The package linux-image-amd64 was installed automatically! First i have to install the original nvidia driver now. If you mean the 'nvidia-driver' package from Debian, then yes, do that. And report back with the requested information. Sorry - misstyping - i mean UNinstall the origianl nvidia driver. Do you think it is a good idea to start with a clean new copy of wheezy now and upgrade it to jessie? I think everything is really mixed up now. Not now. Let's try to find (and fix) your issue now, otherwise you may end up in the same situation again. Yes - i assume this will be the same. But there is an system upgrade and the installation of the original nvidia package between? What's about the backup of the system before the installation of the original nvidia driver? But it wouldn't hurt to start *preparing* for a complete new install and migrating your users files/settings/etc. Of course - but for 3 users this is really much trouble. And i must compare to have the same packages installed. I did this one time and it takes some days work. There should be a way to upgrade a system ... Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver: New vesa test
Hi Diederik, Am 29.01.2014 12:16, schrieb Diederik de Haas: Hi Karsten, On Wednesday 29 January 2014 11:29:51 Karsten Malcher wrote: ii linux-headers-3.12-1-amd64 3.12.6-2 amd64Header files for Linux 3.12-1-amd64 ii linux-headers-3.12-1-common 3.12.6-2 amd64Common header files for Linux 3.12-1 Reinstall the linux-headers-amd64 package. As i have written i purged all header packages and reinstalled this package. You've installed 'linux-headers-3.12-1-amd64' package, not 'linux-headers- amd64'. This won't solve your current issue, but it will make sure that when a new kernel lands in testing (which will happen), the appropriate linux-headers package will also be installed. O.K. - but what is the difference? As "user" i expect to get the correct headers for the kernel linux-image-3.12-1-amd64 when i install linux-headers-3.12-1-amd64 The package names seem to be chaotical now. Can you run the following command and attach the resulting file (bug735424-packages.txt) to your reply? I rebooted and you will find the file attached. I'm missing a whole bunch of nvidia packages ... Locating the problem becomes much harder if you keep using NVidia's .run file, so please stop doing that. Yes - i only tested the original nvidia installer as comparison to the environment with the self compiled kernel. Post the output of 'ls -l /usr/bin/gcc' And run the following command: 'aptitude install nvidia-driver' First i have to install the original nvidia driver now. Do you think it is a good idea to start with a clean new copy of wheezy now and upgrade it to jessie? I think everything is really mixed up now. When that has finished, attach the file '/var/lib/dkms/nvidia- current/319.76/3.12-1-amd64/x86_64/log/make.log' to your reply. Is there no precompiled nvidia driver included in the debian packages? Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver: New vesa test
O.K. Thank you for the advice. 1. I will deinstall all unneeded header packages 2. I will install the correct one and check it with dbsums 3. I will try to install the original nvidia driver and prove if it will work 4. When there is no hope to find the problem up to this point i will make a new installation of testing on the partition. Am 27.01.2014 20:28, schrieb Andreas Beckmann: Is the linux-headers-3.12-1-common package correctly installed? (check with debsums) Before reinstalling, delete the manually created link. Not used up to now - but i will find out. I tried to correct this by a symbolic link: linux-headers-3.12-1-common -> linux-headers-3.12-1-common-rt the NVIDIA driver does not work under RT kernels, so get rid of the linux-headers-3.12-1-rt-amd64 linux-headers-3.12-1-common-rt packages i can't remember to have this packages installed. They are not installed under wheezy! Then i rerun the installer and get make2.log I have no idea what's going wrong this time? Nothings works. :-( you probably don't need the uvm module ... ??? But this is not going to fix your problem. There is something X-related broken as you could see in the failing vesa test. Maybe some outdated library, forgotten file or symlink somewhere or a non-default configuration setting somewhere. Yes - but how to find out? I thought it would be easier to get a running NVida-driver first. Changing the tires does not get your car going if the battery is dead. Correct. I just wanted to see if this works. But i only found much problems with headers ... You should really try to do a clean minimal jessie install on a separate disk, ensure X is working properly, install the same package set as you have on the "grown" system, ensure X is still working, and compare the two installations. Hmmm - yes - but that will take really much time. I will try to do this, it will take time to find a day with some hours ... Unfortunately I don't see another way to find the tiny difference that breaks your system. You have convinced me. BTW, in your wheezy installation, which driver and kernel version were you using? Did you test with the nvidia driver from wheezy-backports? I posted somewhere at the beginning of the bug. It is 304.88-1+deb7u1 You mean i should install the backport driver on wheezy first? I can try whatever can be done that don't need a half of a day. 319.82 backport was uploaded a few hours ago. See the backports page for instructions how to use backports. This should be rather quick and is just to verify that there isn't something broken w.r.t 319.82 on your card. But then i must reinstall a copy of my running system first. I don't want to break my working system. I think it is more sensefull to try a clean installation of testing? Andreas Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736145: nvidia-detect gives no senseful output
Am 27.01.2014 20:00, schrieb Andreas Beckmann: On 2014-01-27 17:23, Karsten Malcher wrote: Am 25.01.2014 16:57, schrieb Andreas Beckmann: On 2014-01-20 10:30, Karsten Malcher wrote: When i run nvidia-detect i get this output: Detected NVIDIA GPUs: 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) Your card is supported by the default drivers and version 304. It is recommended to install the nvidia-driver package. That's wrong! Correct should be 319.76 and this is installed: Why do you think this is wrong? What would you expect instead? Andreas Please read exact - current driver is 319.76 or not? The purpose of nvidia-detect is not to tell you something about upstream version numbers, ... O.K. It's not a bug - it's a feature. nvidia-detect cries for 304. So how to install something that does not exist? ;-) ... but about Debian package names. And 'nvidia-driver' does exist. That's what 'default drivers' is about. The description says: "The 'nvidia-detect' script in this package checks for an NVIDIA GPU in the system and recommends one of the non-free accelerated driver meta-packages" When the main function is "only" to recommend something, everything is perfect. :-) But you are right, we could mark the '304' more prominently as 'legacy'. Fine. :-) Close the bug. Andreas PS: Note to self: check that nvidia-detect in wheezy-backports outputs something sane Then i should update the wiki that this package exists. It's really not clear how get NVidia running in Debian ... Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736145: nvidia-detect gives no senseful output
Am 25.01.2014 16:57, schrieb Andreas Beckmann: On 2014-01-20 10:30, Karsten Malcher wrote: When i run nvidia-detect i get this output: Detected NVIDIA GPUs: 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) Your card is supported by the default drivers and version 304. It is recommended to install the nvidia-driver package. That's wrong! Correct should be 319.76 and this is installed: Why do you think this is wrong? What would you expect instead? Andreas Please read exact - current driver is 319.76 or not? nvidia-detect cries for 304. So how to install something that does not exist? ;-) Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver: New vesa test
Hello,
Am 23.01.2014 13:14, schrieb Diederik de Haas:
On Thursday 23 January 2014 12:37:29 Karsten Malcher wrote:
2. Boot jessie, deinstall all Debian NVidia packages
Instead of just deinstalling, I'd suggest purging the package(s), which also
removes configuration files.
Optionally you can also do the following to make sure all config files are
indeed removed:
- check /etc/X11/xorg.conf.d/ to see if there are any config files there (which
could interfere)
- run 'updatedb.mlocate' (as root)
- run 'find -name *nvidia* -type f' (as root) to see whether there are still
nvidia files on your system you'd like to get rid of
Then reboot and install the nvidia driver
HTH,
Diederik
I have purged all the packages.
But installation of the NVidia driver fails, because compilation does not work.
I atteched the logs.
The directory /usr/src/linux-headers-3.12-1-amd64 exists!
But only with 1,9 MB content?
I already run an package update.
I think there are some things really misconfigured and bad in jessie.
Cheers
Karsten
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Thu Jan 23 13:50:56 2014
installer version: 331.38
PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
nvidia-installer command line:
./nvidia-installer
Using: nvidia-installer ncurses user interface
-> License accepted.
-> Installing NVIDIA driver version 331.38.
-> There appears to already be a driver installed on your system (version: 331.38). As part of installing this driver (version: 331.38), the existing driver will be uninstalled. Are you sure you want to continue? ('no' will abort installation) (Answer: Yes)
-> Would you like to register the kernel module sources with DKMS? This will allow DKMS to automatically build a new module, if you install a different kernel later. (Answer: Yes)
-> Installing both new and classic TLS OpenGL libraries.
-> Installing both new and classic TLS 32bit OpenGL libraries.
-> Install NVIDIA's 32-bit compatibility libraries? (Answer: Yes)
-> Parsing log file:
-> done.
-> Validating previous installation:
-> done.
-> Uninstalling NVIDIA Accelerated Graphics Driver for Linux-x86_64 (1.0-33138 (331.38)):
-> DKMS module detected; removing...
-> Unable to delete directories created by previous installation.
-> done.
-> Uninstallation of existing driver: NVIDIA Accelerated Graphics Driver for Linux-x86_64 (331.38) is complete.
-> Skipping installation of the libvdpau wrapper library.
-> Searching for conflicting X files:
-> done.
-> Searching for conflicting OpenGL files:
-> done.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' (331.38):
executing: '/sbin/ldconfig'...
executing: '/sbin/depmod -aq'...
-> done.
-> Driver file installation is complete.
-> Installing DKMS kernel module:
ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 331.38 -k 3.12-1-amd64`:
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area
make KERNELRELEASE=3.12-1-amd64 module KERNEL_UNAME=3.12-1-amd64; make -C uvm module KERNEL_UNAME=3.12-1-amd64 KBUILD_EXTMOD=/var/lib/dkms/nvidia/331.38/build/uvm(bad exit status: 2)
Error! Bad return status for module build on kernel: 3.12-1-amd64 (x86_64)
Consult /var/lib/dkms/nvidia/331.38/build/make.log for more information.
-> error.
ERROR: Failed to install the kernel module through DKMS. No kernel module was installed; please try installing again without DKMS, or check the DKMS logs for more information.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
DKMS make.log for nvidia-331.38 for kernel 3.12-1-amd64 (x86_64)
Do 23. Jan 13:51:09 CET 2014
NVIDIA: calling KBUILD...
make[1]: Entering directory `/usr/src/linux-headers-3.12-1-amd64'
make: Entering an unknown directory
make: *** /usr/src/linux-headers-3.12-1-common: Datei oder Verzeichnis nicht gefunden. Schluss.
make: Leaving an unknown directory
make[1]: *** [all] Fehler 2
make[1]: Leaving directory `/usr/src/linux-headers-3.12-1-amd64'
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make: *** [nvidia.ko] Fehler 1
make: Entering directory `/var/lib/dkms/nvidia/331.38/build/uvm'
cd /var/lib/dkms/nvidia/331.38/build; make module SYSSRC=/lib/modules/3.12-1-amd64/build SYSOUT=/lib/modules/3.12-1-amd64/build KBUILD_EXTMOD=/var/lib/dkms/nvidia/331.38/build
make[1]: Entering directory `/var/lib/dkms/nvidia/331.38/build'
NVIDIA: calling KBUILD...
make[2]: Entering directory `/usr/src/linux-headers-3.12-1-amd64'
make: Entering an unknown directory
make: *** /usr/src/linux-headers-3.12-1-common: Datei oder Verzeichnis nicht gefunden. Schluss.
ma
Bug#735424: nvidia-driver: New vesa test
Hello Andreas,
Am 22.01.2014 21:41, schrieb Andreas Beckmann:
[Please keep the Bug Cc:ed - therefore fullquote]
On 2014-01-22 10:47, Karsten Malcher wrote:
Hello Diederik,
that's really interesting.
So it must be a configuration problem of previous installations?
Do you have made a fresh installation or an upgrade?
I have made now an additional test:
On a third partition i have a copy of my wheezy installation.
In this installation i have an self compiled kernel V 3.12.6 for some
driver tests with a newer kernel.
Up to now i booted there using the neauveau driver with this configuration:
Section "Device"
Identifier "n"
Driver "nv"
EndSection
shouldn't that be Driver "nouveau" ? ("nv" is an even older driver last
seen in squeeze) but that wouldn't even need an xorg.conf
Yes - this was only a quick and dirty solution to get a running X with a new
kernel.
Now i deinstalled all Debian NVidia packages in this installation and
installed the actual NVIdia driver
NVIDIA-Linux-x86_64-331.38.run
I did have some problems with compilation of the driver, although i
installed the kernel with a debian building script.
ii linux-image-3.12.6 3.12.6 amd64
Linux kernel binary image for version 3.12.6
ii linux-image-3.2.0-3-amd64 3.2.23-1
amd64Linux 3.2 for 64-bit PCs
But the driver could be installed an is running fine!
So something with the configuration or the debian package of 319.82 is
not correct.
The newer driver 331.38 is running on the same installation as the
upgraded one in this bug.
This has only proved that 331.38 is running in a wheezy environment.
Yes and No - it has also proved that my configuration is able to run X with
kernel 3.12.6
Vesa should work there as well. As I understood your problem so far it
is "all xserver video drivers result in a black screen in jessie".
Yes - that's correct.
I will made the following test now:
1. Backup the current upgraded jessie partition (with the chance to recover).
2. Boot jessie, deinstall all Debian NVidia packages
3. Install NVidia driver 331.38
Then we will see if this will work.
Do you have a spare hard disk to make a minimal fresh jessie
installation (installing on a usb stick should work as well) and see if
you can get X running with vesa/nouveau (and nvidia afterwards)?
Thereafter compare /etc contents, maybe install the exactly same
packageset in the new install and look for differences.
I have no doubt that this will work.
The problem is a failing upgrade from wheezy to jessie.
Cheers
Karsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver: New vesa test
Am 22.01.2014 13:16, schrieb Andreas Beckmann: This time the log shows a clean vesa install. And if vesa is not working (even if it would be horribly slow), there seems to be something else going on. It's not the nvidia driver being faulty - the same happens there, but you don't see the flickering because its "too fast". I see the same in the Xorg.log from both drivers - X is started successfully. But right now I'm out of clues how to debug this further - the X maintainers might help here to get vesa running. And if that is working, switching back to nvidia should be no problem. Andreas Thank you for analyzing and trying to solve the problem! It seems to be a really sucking problem with the configuration of this installation. Is there a chance for a simply and clean reinstall of all the stuff around X and Nvida? Maybe this could save the personal settings and get the same situation as a new installation? Otherwise i think this will cost to much time for further analyzing of this problem. Then there only two options: 1. Wait and try another upgrade from wheezy to jessie in hope that it will work later. 2. Uninstall the nvidia debian packages and try to use the original NVidia installer. (I have no idea what the NVidia installer is making different that it works?) Best regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver: New vesa test
Hi Diederik, Am 22.01.2014 11:15, schrieb Diederik de Haas: Hi Karsten, On Wednesday 22 January 2014 10:47:48 Karsten Malcher wrote: Now i deinstalled all Debian NVidia packages in this installation and installed the actual NVIdia driver NVIDIA-Linux-x86_64-331.38.run I understand your eagerness to fix this asap, but I'm not going to interfere with Andreas bug-triage efforts. Of course i understand this. But from my point of view i never could made an upgrade in Debian without problems. I always where using Nvidia cards. Before wheezy i never got an running X without original NVidia drivers. In wheezy the first time the Nvidia Debian package was running for me. It seems it was the last time. :-( Any update of the kernel will cause the loose of X. But I can say this: - When trying to find a problem, only change 1 variable at a time, otherwise you don't know which change caused a change in behaviour. i only made an "simple" system upgrade from wheezy to jessie. - Don't use NVidia's .run file if you're reporting an issue on a Debian package, since they're not meant to be co-installed (and Debian's package cleans thing up from a possible previous .run installation). That's why i made this test in a different installation. It was a simple test if kernel 3.12.6 and the NVidia driver will work together. - Use the same system/installation on all bug-triage efforts, otherwise you're comparing completely different systems (btw 3.12 kernel on wheezy and not from backports?) Somehow it must be possible to have a working PC. ;-) In this case i hold back the upgraded installation for this bug. There is no additional mix up. I've been running Debian's NVidia packages for years, without any issue, including on my freshly installed system I'm running now. That's the main problem. On a fresh installation you don't have this problems. In most of the cases this will work. But what's about of the hundreds of personal configurations for mail, programming, viewing and working? You will loose them with a new installation and need to much time to get them back. In my case i have a "master installation" with the individual settings for 3 users! This installation will be cloned to all working PC's. When i want to upgrade to a newer distribution it must be an upgrade or it will kill me. I think this problems are not my personal problems and touch many users. So upgrade problems should also be in a distribution focus. Cheers Karsten HTH, Diederik Original-Nachricht Betreff: Re: Bug#735424: nvidia-driver: New vesa test Datum: Wed, 22 Jan 2014 10:47:48 +0100 Von:Karsten Malcher Antwort an: deb...@dct.mine.nu An: Diederik de Haas Kopie (CC): pkg-nvidia-de...@lists.alioth.debian.org Hello Diederik, that's really interesting. So it must be a configuration problem of previous installations? Do you have made a fresh installation or an upgrade? I have made now an additional test: On a third partition i have a copy of my wheezy installation. In this installation i have an self compiled kernel V 3.12.6 for some driver tests with a newer kernel. Up to now i booted there using the neauveau driver with this configuration: Section "Device" Identifier "n" Driver "nv" EndSection Now i deinstalled all Debian NVidia packages in this installation and installed the actual NVIdia driver NVIDIA-Linux-x86_64-331.38.run I did have some problems with compilation of the driver, although i installed the kernel with a debian building script. ii linux-image-3.12.6 3.12.6 amd64Linux kernel binary image for version 3.12.6 ii linux-image-3.2.0-3-amd64 3.2.23-1 amd64 Linux 3.2 for 64-bit PCs But the driver could be installed an is running fine! So something with the configuration or the debian package of 319.82 is not correct. The newer driver 331.38 is running on the same installation as the upgraded one in this bug. Cheers Karsten Andreas, I have the same graphics card (GT 430), the same driver version and (almost) the same kernel (Linux bagend 3.12-1-amd64 #1 SMP Debian 3.12.8-1 (2014-01-19) x86_64 GNU/Linux) and everything is running fine here. So if you want me to check/test things so 'notes' can be compared, just let me know (I'm subsribed to the pkg-nvidia-devel ML). Cheers, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: nvidia-driver: Test of unstable driver
Hello, i am sorry, at least nothing has worked. With the driver from unstable i get no running X. All the configurations of xorg.conf i testes result in "no screens found". I attach the last configuration. The first one was the minimal configuration.file:///sda/etc/X11/xorg.conf What is to do now? Regards Karsten # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 319.72 (pbuilder@cake) Sat Nov 9 14:15:48 UTC 2013 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection
Bug#735424: nvidia-driver: needed option x for additional information
Am 19.01.2014 19:00, schrieb Andreas Beckmann: On 2014-01-15 17:54, Karsten wrote: Here are the automatic collected informations. So far I don't see any errors ... X starts ... and after 30 seconds cleanly shuts down. Please check the logfile of login manager (gdm3, kdm, xdm or whatever) That's what i can't understand too. After boot X does not start and i land on the basic text shell. So i can log in as user and startx. Without xorg.conf i only get the error "no screens found". With an xorg.conf i only get an blank black screen. It seems that the graphic card is not initialized correctly or something else. Shutdown is with CTRL-C by the user. Please try the new driver releases 319.82 in unstable and 331.38 in experimental. How can i install this driver in jessie? And try a minimal config file as decribed in /usr/share/doc/nvidia-driver/README.Debian.gz I tried to use nvidia-xconfig with the same result of this black blank screen. The xorg.conf is attached. Karsten # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 319.72 (pbuilder@cake) Sat Nov 9 14:15:48 UTC 2013 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection
Bug#736145: nvidia-detect gives no senseful output
Package: nvidia-detect Version: 319.76-1 Severity: important Hello, the upgrade from wheezy to jessie failed. Please refer to bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735424 When i run nvidia-detect i get this output: Detected NVIDIA GPUs: 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) Your card is supported by the default drivers and version 304. It is recommended to install the nvidia-driver package. That's wrong! Correct should be 319.76 and this is installed: ii glx-alternative-nvidia0.4.1 amd64allows the selection of NVIDIA as GLX provider rc libgl1-nvidia-alternatives-ia32 304.88-1+deb7u1amd64simplifies replacing MESA libGL with GPU vendor libraries (32-bit) ii libgl1-nvidia-glx:amd64 319.76-1 amd64 NVIDIA binary OpenGL libraries ii libgl1-nvidia-glx:i386319.76-1 i386 NVIDIA binary OpenGL libraries ii libgl1-nvidia-glx-i386319.76-1 i386 NVIDIA binary OpenGL 32-bit libraries ii libnvidia-compiler:amd64 319.76-1 amd64 NVIDIA runtime compiler library ii libnvidia-ml1:amd64 319.76-1 amd64NVIDIA Management Library (NVML) runtime library rc libxvmcnvidia1:amd64 304.88-1+deb7u1amd64 NVIDIA binary XvMC library ii nvidia-alternative319.76-1 amd64allows the selection of NVIDIA as GLX provider ii nvidia-detect 319.76-1 amd64 NVIDIA GPU detection utility ii nvidia-driver 319.76-1 amd64 NVIDIA metapackage ii nvidia-glx319.76-1 amd64 transition to nvidia-driver ii nvidia-installer-cleanup 20131102+1 amd64cleanup after driver installation with the nvidia-installer ii nvidia-kernel-common 20131102+1 amd64NVIDIA binary kernel module support files ii nvidia-kernel-dkms319.76-1 amd64NVIDIA binary kernel module DKMS source ii nvidia-opencl-common 319.76-1 amd64 NVIDIA OpenCL driver ii nvidia-opencl-icd:amd64 319.76-1 amd64 NVIDIA OpenCL ICD ii nvidia-settings 319.72-1 amd64tool for configuring the NVIDIA graphics driver ii nvidia-support20131102+1 amd64NVIDIA binary graphics driver support files ii nvidia-vdpau-driver:amd64 319.76-1 amd64 NVIDIA vdpau driver ii nvidia-xconfig319.72-1 amd64X configuration tool for non-free NVIDIA drivers ii xserver-xorg-video-nvidia 319.76-1 amd64 NVIDIA binary Xorg driver Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: Only blank screen after system-upgrade from wheezy to jessie
Hello Andreas, Am 15.01.2014 12:27, schrieb Andreas Beckmann: On 2014-01-15 11:01, Karsten Malcher wrote: Package: nvidia-driver Version: 319.76-1 Severity: important Hello, again i tried to upgrade from a perfect running installation of Debian wheezy to jessie. That should be supported :-) That was my hope also - but i was really disappointed to land on the shell. This installation has been upgraded more than one time and in the history there might be the usage of original nvidia packages. I have put a lot of effort into cleaning up the mess created by having used the nvidia *.run installer in the past, but I may have missed some corner cases. I believe that and thank you for your work! There are really to many types of NVidia-cards out there. Is there a way to easy find out which package must be installed for an NVidia card? Here i can't find my card: http://packages.debian.org/jessie/nvidia-legacy-173xx-driver Here i can't find any hint what to do on jessie: https://wiki.debian.org/NvidiaGraphicsDrivers I would update this Wiki-page with the correct informations. Right now I don't see an obvious problem. Please run reportbug -N 735424 I will do this. But after this i would try to install the correct NVida-package for a GT 400 if possible. Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686754: Is there any hope that this bug will be fixed?
Am 15.01.2014 11:48, schrieb Lukas Schwaighofer: Hi Karsten, To my knowledge linux-boot-prober does the following: * Mount the given partition read-only to a temporary directory * Read the /etc/fstab of this partition to check if /boot is on a separate partition. If so, it is also mounted. * Read and parse the boot loader configuration from the temporary directory. For grub2 that is boot/grub/grub.cfg. The parameters to the linux kernel (the root=… directive that was wrong in your case) should be directly taken from this file. * Unmount everything again So your report from your message #15 makes sense, if the /boot/grub/grub.cfg file on sda3 (I'm assuming you do not have a separate boot partition) previously contained the "wrong" parameters for the Linux kernel (root=UUID=5c902625-e63e-446f-a5c5-c24a1176dec7 ro single). Regards Lukas Hi Lukas, then we have found the explanation for this problem - thank you! The grub.cfg on the copy of the installation will be correct only after boot and update of this installation. And i must run update-grub first on the standard installation to get the partition with the copy booted. It's impossible to avoid this error under this circumstances! So this bug can be closed. Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: Different drivers for different graphic cards?
When i search for my graphic card GT 430 at Nvidia, this driver is suggested for download: Version: 331.38 Date:2014.1.13 Again this is a different version! In Debian there is only one driver package. How it is able to suffer all the different graphic cards? This driver is for many different graphic cards, including my card: *GeForce 700 Series:* GeForce GTX TITAN, GeForce GTX 780, GeForce GTX 770, GeForce GTX 760, GeForce GTX 760 Ti (OEM) *GeForce 700M Series (Notebooks):* GeForce GTX 780M, GeForce GTX 770M, GeForce GTX 765M, GeForce GTX 760M, GeForce GT 755M, GeForce GT 750M, GeForce GT 745M, GeForce GT 740M, GeForce GT 735M, GeForce GT 730M, GeForce GT 720M, GeForce 710M *GeForce 600 Series:* GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GT 645, GeForce GT 640, GeForce GT 630, GeForce GT 620, GeForce GT 610, GeForce 605 *GeForce 600M Series (Notebooks):* GeForce GTX 680MX, GeForce GTX 680M, GeForce GTX 675MX, GeForce GTX 675M, GeForce GTX 670MX, GeForce GTX 670M, GeForce GTX 660M, GeForce GT 650M, GeForce GT 645M, GeForce GT 640M, GeForce GT 640M LE, GeForce GT 635M, GeForce GT 630M, GeForce GT 625M, GeForce GT 620M, GeForce 610M *GeForce 500 Series:* GeForce GTX 590, GeForce GTX 580, GeForce GTX 570, GeForce GTX 560 Ti, GeForce GTX 560 SE, GeForce GTX 560, GeForce GTX 555, GeForce GTX 550 Ti, GeForce GT 545, GeForce GT 530, GeForce GT 520, GeForce 510 *GeForce 500M Series (Notebooks):* GeForce GTX 580M, GeForce GTX 570M, GeForce GTX 560M, GeForce GT 555M, GeForce GT 550M, GeForce GT 540M, GeForce GT 525M, GeForce GT 520M, GeForce GT 520MX *GeForce 400 Series:* GeForce GTX 480, GeForce GTX 470, GeForce GTX 465, GeForce GTX 460 SE v2, GeForce GTX 460 SE, GeForce GTX 460, GeForce GTS 450, GeForce GT 440, GeForce GT 430, GeForce GT 420 *GeForce 400M Series (Notebooks):* GeForce GTX 485M, GeForce GTX 480M, GeForce GTX 470M, GeForce GTX 460M, GeForce GT 445M *GeForce 300 Series:* GeForce GT 340, GeForce GT 330, GeForce GT 320, GeForce 315, GeForce 310 *GeForce 300M Series (Notebooks):* GeForce GTS 360M, GeForce GTS 350M, GeForce GT 335M, GeForce GT 330M, GeForce GT 325M, GeForce GT 320M, GeForce 320M, GeForce 315M, GeForce 310M, GeForce 305M *GeForce 200 Series:* GeForce GTX 295, GeForce GTX 285, GeForce GTX 280, GeForce GTX 275, GeForce GTX 260, GeForce GTS 250, GeForce GTS 240, GeForce GT 230, GeForce GT 240 *GeForce 200M Series (Notebooks):* GeForce GTX 285M, GeForce GTX 280M, GeForce GTX 260M, GeForce GTS 260M *GeForce 100 Series:* GeForce GT 140, GeForce GT 130, GeForce GT 120, GeForce G100 *GeForce 100M Series (Notebooks):* GeForce GTS 160M, GeForce GT 130M, GeForce GT 120M, GeForce G 110M, GeForce G 105M, GeForce G 103M, GeForce G 102M *GeForce 9 Series:* GeForce 9800 GX2, GeForce 9800 GTX/GTX+, GeForce 9800 GT, GeForce 9600 GT, GeForce 9600 GSO, GeForce 9600 GSO 512, GeForce 9600 GS, GeForce 9500 GT, GeForce 9500 GS, GeForce 9400 GT, GeForce 9400, GeForce 9300 GS, GeForce 9300 GE, GeForce 9300 SE, GeForce 9300, GeForce 9200, GeForce 9100 *GeForce 9M Series (Notebooks):* GeForce 9800M GTX, GeForce 9800M GTS, GeForce 9800M GT, GeForce 9800M GS, GeForce 9700M GTS, GeForce 9700M GT, GeForce 9650M GT, GeForce 9650M GS, GeForce 9600M GT, GeForce 9600M GS, GeForce 9500M GS, GeForce 9500M G, GeForce 9400M G, GeForce 9400M, GeForce 9300M GS, GeForce 9300M G, GeForce 9200M GS, GeForce 9100M G *GeForce 8 Series:* GeForce 8800 Ultra, GeForce 8800 GTX, GeForce 8800 GTS, GeForce 8800 GT, GeForce 8800 GS, GeForce 8600 GTS, GeForce 8600 GT, GeForce 8600 GS, GeForce 8500 GT, GeForce 8400 GS *GeForce 8M Series (Notebooks):* GeForce 8800M GTX, GeForce 8800M GTS, GeForce 8700M GT, GeForce 8600M GT, GeForce 8600M GS, GeForce 8400M GT, GeForce 8400M GS, GeForce 8400M G, GeForce 8200M G, GeForce 8200M *Quadro Series:* Quadro K6000, Quadro K5000, Quadro K4000, Quadro K2000, Quadro K2000D, Quadro K600, Quadro 6000, Quadro 5000, Quadro 4000, Quadro 2000, Quadro 2000D, Quadro 600, Quadro 410, Quadro 400 *Quadro Series (Notebooks):* Quadro K5000M, Quadro K4000M, Quadro K3000M, Quadro K2000M, Quadro K1000M, Quadro K500M, Quadro 5010M, Quadro 5000M, Quadro 4000M, Quadro 3000M, Quadro 2000M, Quadro 1000M *Quadro FX Series:* Quadro FX 3400/4400, Quadro FX 3500, Quadro FX 3700, Quadro FX 3800, Quadro FX 4000, Quadro FX 4500, Quadro FX 4500 X2, Quadro FX 4600, Quadro FX 4700 X2, Quadro FX 4800, Quadro FX 5500, Quadro FX 5600, Quadro FX 5800 *Quadro FX Series (Notebooks):* Quadro FX 3800M, Quadro FX 3700M, Quadro FX 3600M, Quadro FX 2800M, Quadro FX 2700M, Quadro FX 1800M, Quadro FX 1700M, Quadro FX 1600M, Quadro FX 880M, Quadro FX 770M, Quadro FX 570M, Quadro FX 380M, Quadro FX 370M, Quadro FX 360M *Quadro Blade/Embedded Series :* Quadro FX 560M, Quadro FX 770M, Quadro FX 880M, Quadro FX 1600M, Quadro FX 2800M, Quadro FX 3600M *
Bug#686754: Is there any hope that this bug will be fixed?
Am 14.01.2014 19:00, schrieb Colin Watson:
GRUB doesn't generate those kernel parameters itself; it relies on os-prober to fetch them from the boot loader
configuration files on those other systems. It's quite possible that the problem is simply that the boot loader
configuration inside the filesystem on /dev/sda3 (or its associated /boot filesystem) is wrong. Could you find the
relevant configuration file and attach it?
Hello Colin,
now i understand more.
I found this description of os-prober here:
http://joeyh.name/code/os-prober/
Calling os-prober only give this information:
# os-prober
/dev/sda2:Debian GNU/Linux (7.2):Debian:linux
/dev/sda3:Debian GNU/Linux (jessie/sid):Debian1:linux
It seems not to merge the information with the UUID of the partitions.
I found an other interesting effect, which explains that this bug has not been
found.
Now an grub-update produces the correct grub.cfg.
menuentry "Debian GNU/Linux, mit Linux 3.12-1-amd64 (on /dev/sda3)" --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos3)'
search --no-floppy --fs-uuid --set=root
6bfc15a0-2e9d-4020-9346-9fd52d2696f5
linux /boot/vmlinuz-3.12-1-amd64
root=UUID=6bfc15a0-2e9d-4020-9346-9fd52d2696f5 ro quiet
initrd /boot/initrd.img-3.12-1-amd64
}
menuentry "Debian GNU/Linux, mit Linux 3.12-1-amd64 (Wiederherstellungsmodus) (on /dev/sda3)" --class gnu-linux --class
gnu --class os {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos3)'
search --no-floppy --fs-uuid --set=root
6bfc15a0-2e9d-4020-9346-9fd52d2696f5
linux /boot/vmlinuz-3.12-1-amd64
root=UUID=6bfc15a0-2e9d-4020-9346-9fd52d2696f5 ro single
initrd /boot/initrd.img-3.12-1-amd64
}
What i did in the history:
1. I unpacked an backup of /dev/sdb1 (Grub partition with Debian wheezy) to
/dev/sda3
2. I altered the fstab of the copy and run update-grub (After this i got this
wrong grub.cfg)
3. I boot from /dev/sda3 and made an system-upgrade from wheezy to jessie
4. After the upgrade i run update-grub again from /dev/sdb1 to actualize the new kernel on /dev/sda3 (Now grub.cfg is
correct)
Is it possible that the (wrong) information is extraced from initrd.img ?
Cheers
Karsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686754: Is there any hope that this bug will be fixed?
Again and again i have to correct the grub.cfg manually.
And you can see this bug in all depending distributions of Debian.
Example today:
# blkid
/dev/sda1: LABEL="P1EXT4-8G" UUID="c4aa8129-f5a0-4599-b487-3f63ff736c1b"
TYPE="ext4"
/dev/sda2: UUID="5166cbb1-8234-4127-bb0b-bbfda1658b68" TYPE="ext4"
LABEL="P2EXT4-30G"
/dev/sda5: UUID="448a6eb5-2173-43e3-b35a-62e9e81a2316" TYPE="swap"
/dev/sda6: LABEL="P3EXT20G" UUID="d37744be-c228-4add-9cf3-ce42aff94a7f" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sda7: LABEL="P7-EXT4-900G" UUID="f4d36b10-bae9-4b22-a19b-0f34916337b3"
TYPE="ext4"
/dev/sda3: LABEL="P3EXT4-30G" UUID="6bfc15a0-2e9d-4020-9346-9fd52d2696f5"
TYPE="ext4"
/dev/sdb1: LABEL="SSD" UUID="5c902625-e63e-446f-a5c5-c24a1176dec7" TYPE="ext4"
grub.cfg
menuentry "Debian GNU/Linux, mit Linux 3.2.0-3-amd64 (on /dev/sda3)" --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos3)'
search --no-floppy --fs-uuid --set=root 6bfc15a0-2e9d-4020-9346-9fd52d2696f5
linux /boot/vmlinuz-3.2.0-3-amd64
root=UUID=5c902625-e63e-446f-a5c5-c24a1176dec7 ro quiet
initrd /boot/initrd.img-3.2.0-3-amd64
}
menuentry "Debian GNU/Linux, mit Linux 3.2.0-3-amd64 (Wiederherstellungsmodus) (on /dev/sda3)" --class gnu-linux --class
gnu --class os {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos3)'
search --no-floppy --fs-uuid --set=root 6bfc15a0-2e9d-4020-9346-9fd52d2696f5
linux /boot/vmlinuz-3.2.0-3-amd64
root=UUID=5c902625-e63e-446f-a5c5-c24a1176dec7 ro single
initrd /boot/initrd.img-3.2.0-3-amd64
But the first 2 partitions are right now. ;-)
It would be fine if i can boot from all partitions ...
Cheers
Karsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704242: Driver for PL-2303 HX not working
Hello together, i will close this bug at Debian now. After the last update this error seems to disappear in Debian stable. http://ftp.debian.org/debian/dists/wheezy/ChangeLog USB: pl2303: fix device initialisation at open The source for this patch can be found here: http://www.spinics.net/lists/stable/msg30311.html It's possible that this will not fix the bug under all circumstances depending on the application. Summary: == I did need some time to realize that this bug will occur only with PL2303HX chips that are China clones. In fact this type of chips run out of production at Profilic. http://www.prolific.com.tw/US/ShowProduct.aspx?pcid=41&showlevel=0017-0037-0041 Only the PL2303HXD can be buyed as original, so any new PL2303HX is a China clone. I have been contacted by Frank Schäfer and so we tested some of his driver improvements in combination with newer kernels. Up to now this could not be backported to kernel 3.2.x, but i could test a kernel 3.12.6 on Debian wheezy and the PL2303HX is running fine. There are really much products with this clone chips out there, so some further improvements of the driver would be really helpful. I will make further tests together with Frank and hope that this improvements will find a place into the next kernel versions starting with Debian jessie and 3.12.6 Best regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704242: Driver for PL-2303 HX not working
Am 15.12.2013 18:05, schrieb Greg KH: Have you tried a newer kernel in a while? A number of things have been hopefully fixed since June when you last looked. greg k-h no at this time i have not tested it - sorry. Although i am fascinated from your work i personally prefer to use stable releases for my daily work. This bug here shows that several functionalites in detail can be lost with an update. Then it takes much time to find workarounds - specially when hardware is not running any more. When i look in the Debian repositories i only see kernel 3.11.10 for testing and unstable. The latest one is 3.12.3 in experimental. I will see to upgrade one copy of my installation to testing on another partition with 3.11.10. Do you mean that will hopefully show a resolution for this problem? I do not know, 3.11 is pretty old, sorry. My distribution update fails into a system without X. So no new tests with Kernel 3.11 so far. I looked for a CD booting system with a newer kernel, but there seems to be no one? * Knoppix Kernel 3.9.6 * Kubuntu Kernel 3.11 maybe a choice As you can see - you can only dream of a 3.12.5 stable kernel. ;-) But when Debian Testing will run i make a retest of the PL-2303 HX. Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704242: Driver for PL-2303 HX not working
Hello Greg, Am 14.12.2013 18:08, schrieb Greg KH: On Fri, Dec 13, 2013 at 04:06:35PM +0100, Karsten Malcher wrote: Hello together, is there anything new for the PL-2303 HX? It would be fine if it could work like in the past. Have you tried a newer kernel in a while? A number of things have been hopefully fixed since June when you last looked. greg k-h no at this time i have not tested it - sorry. Although i am fascinated from your work i personally prefer to use stable releases for my daily work. This bug here shows that several functionalites in detail can be lost with an update. Then it takes much time to find workarounds - specially when hardware is not running any more. When i look in the Debian repositories i only see kernel 3.11.10 for testing and unstable. The latest one is 3.12.3 in experimental. I will see to upgrade one copy of my installation to testing on another partition with 3.11.10. Do you mean that will hopefully show a resolution for this problem? Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704242: Driver for PL-2303 HX not working
Hello together, is there anything new for the PL-2303 HX? It would be fine if it could work like in the past. Of course for Linux there are good alternatives. Here is a new one with the CP2102 suffering easy supply voltage: http://www.ebay.de/itm/110954294607 Best regards Karsten Am 24.06.2013 21:00, schrieb Greg KH: On Mon, Jun 24, 2013 at 12:38:17PM -0400, Aric Fedida wrote: I will gladly ship you one. Give me address details, and I'll go to the post office to send it. I'll send it off-list, thanks. Personally, I have resolved to abandon the PL2303 chip, and move to FTDI instead. But for the sake of other Linux users who might buy that adapter by mistake, I am willing to donate the hardware to an able kernel hacker :-) Yes, I recommend the ftdi devices as well, the specs are availble, and the driver seems to work better because of it. thanks, greg k-h -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721595: KDE network manager does not work
Hi, Am 02.09.2013 17:10, schrieb Michael Biebl: Do you have a complete, default KDE desktop installation? What's complete? Default is very complicate with an upgraded system. So i would say - No. What's the output of 'ck-list-sessions' and 'pkaction'? karsten@pc:~$ ck-list-sessions Session1: unix-user = '1000' realname = 'Karsten' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2013-09-02T15:54:11.303898Z' login-session-id = '4294967295' karsten@pc:~$ pkaction Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success Do you have polkit-kde-1 installed? Yes ii polkit-kde-1 0.99.0-3 amd64KDE dialogs for PolicyKit Thanks for your help so far. Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721595: KDE network manager does not work
Hi Michael, the first thing is that wicd doesn't work also. :-) So i reinstalled the network-manager-kde. Am 02.09.2013 14:10, schrieb Michael Biebl: You've configured your network interface device(s) in /etc/network/interface, that means they are managed by ifupdown. It makes no difference if i have only the lines for "iface lo" in the interfaces file or if the file doesn't exist. Network is not coming up and the manager is not scanning for WLAN. The same message with insufficient privileges appers by manual entry and save. There must be more wrong. If you want to manage your interface with network-manager/plasma-widget-networkmanagement, you should remove those interfaces from /etc/network/interfaces. See also /usr/share/doc/network-manager/README.Debian Hmm - this dependencies are not not clear for me and for other users. It would be fine if the right dependencies would be checked when the package is installed. It seems to be always a struggle to get WLAN running. I will not think about bluetooth .. Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721595: package not working
Here is a forum thread with someone where it is not working also. http://debianforum.de/forum/viewtopic.php?f=30&t=138291 The solution was to deinstall the kde networkmanager and to install wicd. root@weide:/home/hugo# apt-get purge network-manager root@weide:/home/hugo# rm -r /etc/NetworkManager/ root@weide:/home/hugo# apt-get install wicd wicd-gtk wicd-curses I think i will test it now. Is this really the only solution? Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721595: KDE network manager does not work
Package: plasma-widget-networkmanagement Version: 0.9.0.3-1 Severity: important Hello, i am trying desperated to get WLAN working without problems on wheezy. One time i get a connection, then never again. I installed the network manager to have a comfortable configuration, but it seems not to have the correct rights to work. The scanning for hotspots does not work and when i manually create a WLAN connection and try to save it, it fails with insufficient privileges (see screenshot). As you can see here i have access to WLAN functionality on the shell: root@pc# iwlist wlan2 scan wlan2 Scan completed : Cell 01 - Address: 00:1E:58:BB:80:CD Channel:1 Frequency:2.412 GHz (Channel 1) Quality=68/70 Signal level=-42 dBm Encryption key:on ESSID:"dd-wrt" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf= Extra: Last beacon: 32ms ago IE: Unknown: 000664642D777274 IE: Unknown: 010882848B960C121824 IE: Unknown: 030101 IE: Unknown: 05040001 IE: Unknown: 2A0104 IE: Unknown: 32043048606C IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: Unknown: DD0900037F01010020FF7F But automatically it is not configured correct with the WPA key: root@pc# iwconfig wlan2 IEEE 802.11abg ESSID:"dd-wrt" Mode:Managed Frequency:2.412 GHz Access Point: 00:1E:58:BB:80:CD Tx-Power=200 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off This is my current network configuration file: root@pc:/etc/network# cat interfaces ... allow-hotplug eth6 iface eth6 inet static ... auto wlan2 iface wlan2 inet dhcp wpa-ssid "dd-wrt" wpa-psk "mysecretpassword" Why the network manager has not enough privileges? Any other idea to solve the problem? Best regards Karsten -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widget-networkmanagement depends on: ii kde-runtime 4:4.8.4-2 ii libc6 2.13-38 ii libgcc1 1:4.7.2-5 ii libkcmutils44:4.8.4-4 ii libkdecore5 4:4.8.4-4 ii libkdeui5 4:4.8.4-4 ii libkio5 4:4.8.4-4 ii libknotifyconfig4 4:4.8.4-4 ii libplasma3 4:4.8.4-4 ii libqt4-dbus 4:4.8.2+dfsg-11 ii libqt4-network 4:4.8.2+dfsg-11 ii libqt4-svg 4:4.8.2+dfsg-11 ii libqt4-xml 4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libsolid4 4:4.8.4-4 ii libsolidcontrol4abi24:4.8.4-6 ii libstdc++6 4.7.2-5 ii mobile-broadband-provider-info 20120708-1 ii network-manager 0.9.4.0-10 Versions of packages plasma-widget-networkmanagement recommends: ii kwalletmanager 4:4.8.4-3 ii network-manager-openvpn 0.9.4.0-1 ii network-manager-pptp 0.9.4.0-2 ii network-manager-vpnc 0.9.4.0-1 Versions of packages plasma-widget-networkmanagement suggests: pn kdebase-workspace-bin -- no debconf information <>
Bug#720859: kwalletmanager does not start
Package: kwalletmanager Version: 4:4.8.4-3 Severity: important Hello, today i want to delete two stored passwords from kwallet. But when i try to open the kwalletmanager nothing happens. When i try to open it from the shell i get: karsten@PC:~$ kwalletmanager QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Any ideas to solve the problem? Best regards Karsten -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kwalletmanager depends on: ii kde-runtime 4:4.8.4-2 ii libc62.13-38 ii libkdecore5 4:4.8.4-4 ii libkdeui54:4.8.4-4 ii libkio5 4:4.8.4-4 ii libqt4-dbus 4:4.8.2+dfsg-11 ii libqt4-xml 4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui44:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 kwalletmanager recommends no packages. kwalletmanager suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705919: Info received (Bug#705919: icedove does not play sounds (notifications when new messages arrive))
Today after the next reboot it works! My last actions where to install this two packages: pulseaudio-esound-compat alsaplayer-esd I think this seems to fix the problem. This bug can be closed. Cheers Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705919: icedove does not play sounds (notifications when new messages arrive)
One new idea basing on this Link: http://forums.bodhilinux.com/index.php?/topic/5060-solved-thunderbird-stopped-playing-sound-when-new-messages-arrive/ The libs libesd0 libcanberra0 libstdc are installed. Esound is installed, but the pulseaudio layer was missed first. # dpkg -l | grep esound ii esound-common 0.2.41-10 all Enlightened Sound Daemon - Common files ii pulseaudio-esound-compat 2.0-6.1amd64PulseAudio ESD compatibility layer Sound is still not playing. I found out that the esound daemon is not runnning. But when i manually start esd this does not matter. # esd -v pulseaudio esd wrapper 2.0 I am not shure if this mus really run, because it is also a wrapper? Regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705919: icedove does not play sounds (notifications when new messages arrive)
Hello Carsten, i tested now with the "original" Thunderbird and there is no sound notification also. So this should be a general problem or a sound misconfiguration. I attached a screenshot for the sound configuration of the Thunderbird. But how can i find the problem? All other sound is working! The file is playing perfect with any other soundplayer including "aplay siehabenpost.wav". Best regards Karsten <>
Bug#705919: icedove does not play sounds (notifications when new messages arrive)
Hi,
Am 21.07.2013 14:20, schrieb Carsten Schoenert:
Hello Karsten,
Where i can see this?
There is no line with something like sound.
You found the related lines as you wrote in the other mail.
No - i opened prefs.js directly with an editor.
Found this two lines in prefs.js now:
user_pref("mail.biff.play_sound.type", 1);
user_pref("mail.biff.play_sound.url", "file:///path/mysound.wav");
This means the file would be found in '/path/mysound.wav' ? Is that
true? And if so what about the access right of that file? Icedove is
able access that file (in context of your user permissions)?
A file location like this is very unconventional. Better select a file
inside your home directory.
Of course not - the file name was manually edited for the email from me.
If this want work your sound system is configured wrong.
My soundsystem is working perfect in all other cases.
I have renamed my prefs.js and started Icedove again.
Now i simply added the soundfile as shown in the screenshot.
This does not work!
The only thing i can do now is to try the "original" Thunderbird.
Cheers
Karsten
<>
Bug#705919: icedove does not play sounds (notifications when new messages arrive)
Found this two lines in prefs.js now:
user_pref("mail.biff.play_sound.type", 1);
user_pref("mail.biff.play_sound.url", "file:///path/mysound.wav");
Cheers
Karsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
