Bug#928764: alsa-utils does not store or restore configuration
Le samedi 11 mai 2019, 17:27:55 CEST Elimar Riesebieter a écrit : > Control: tags -1 unreproducible > Control: severity -1 normal > > * MERLIN Philippe [2019-05-11 16:59 +0200]: > > [...] > > > Yes , i have removed pulseaudio, i don't like it, i have had too many > > problems with pulseaudio. > > For the plugin libasound2-plugins it's important ? > > Not that much. It depends on your soundcard > > Well I can't reproduce your behaviour. I have a machine running only > libasound2, libasund2-data and alsa-utils. The sound card settings > are restored by the systemd services. And I have a clean environment > with no .asoundrc or /etc/alsa settings. > > You can check your installation with: > > $ dpkg -l | egrep '(alsa|libasound|pulsea)' > > Hmm > Elimar dpkg -l | egrep '(alsa|libasound|pulsea Copy paste must introduce parasitic characters that prevent sending full message dpkg -l | egrep '(alsa|libasound|pulsea)' ii alsa-base 1.0.27+1 ii alsa-firmware-loaders 1.1.7-1 amd64 Amd64 ii alsa-oss 1.1.8-1 amd64 ii alsa-utils 1.1.8-2 amd64 ii gstreamer0.10-alsa:amd640.10.36-2 amd64 ii gstreamer1.0-pulseaudio:amd64 1.14.4-dmo2 amd64 ii libasound2:amd641.1.8-1 amd64 ii libasound2:i386 1.1.8-1 i386 ii libasound2-data1.1.8-1 all ii libasound2-dev:amd641.1.8-1 amd64 ii libasound2-plugins:amd64 1:1.1.8-dmo1 amd64 ii libasound2-plugins:i386 1:1.1.8-dmo1 i386 rc libsdl1.2debian-alsa 1.2.14-6.2 amd64 ii libsnack2-alsa2.2.10-dfsg1-12.1 amd64 ii libsox-fmt-alsa:amd64 14.4.2+git20190427-1 amd64 rc pulseaudio 11.1-2 amd64 Thanks. Philippe Merlin
Bug#928764: alsa-utils does not store or restore configuration
Le samedi 11 mai 2019, 17:27:55 CEST Elimar Riesebieter a écrit : > Control: tags -1 unreproducible > Control: severity -1 normal > > * MERLIN Philippe [2019-05-11 16:59 +0200]: > > [...] > > > Yes , i have removed pulseaudio, i don't like it, i have had too many > > problems with pulseaudio. > > For the plugin libasound2-plugins it's important ? > > Not that much. It depends on your soundcard > > Well I can't reproduce your behaviour. I have a machine running only > libasound2, libasund2-data and alsa-utils. The sound card settings > are restored by the systemd services. And I have a clean environment > with no .asoundrc or /etc/alsa settings. > > You can check your installation with: > > $ dpkg -l | egrep '(alsa|libasound|pulsea)' > > Hmm > Elimar it seems tht i have libasound2-plugins installed. dpkg -l | egrep '(alsa|libasound|pulsea)'
Bug#928764: alsa-utils does not store or restore configuration
Le samedi 11 mai 2019, 16:32:13 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe [2019-05-11 16:19 +0200]:
>
> [...]
>
> > > > > > The result:
> > > > > > systemctl -t service | grep alsa | awk '{print $1}' | xargs
> > > > > > systemctl
> > > > > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > > > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > > > *●* alsa-state.service - Manage Sound Card State (restore and
> > > > > > store)
> > > > > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > >
> > > > > Please post the output of:
> > > > >
> > > > > $ ls -al /etc/alsa
> > > > > $ ls -al /etc/alsa/conf.d
> > > > > $ ls -al /var/lib/alsa
> > > > > $ ls -al ~/.asoundrc
> > > > >
> > > > > Elimar
> > > >
> > > > s -al /etc/alsa
> > > > export LANG=C| ls -al ~/.asoundrc
> > >
> > > ?
> > >
> > > Elimar
> >
> > Sorry:
> >
> > export LANG=C| ls -al ~/.asoundrc
>
> Try as follows ;-)
>
> $ LC_ALL=C ls -al ~/.asoundrc
> ls: cannot access '/home/users/riesebie/.asoundrc': No such file or
> directory
>
> Well, it seems that you don't have pulseaudio nor libasound2-plugins
> installed. Otherwise you should have an output of:
>
> $ ls -al /etc/alsa/conf.d
> drwxr-xr-x 2 root root 335 Feb 16 08:16 ./
> drwxr-xr-x 3 root root 20 Apr 10 14:17 ../
> lrwxrwxrwx 1 root root 44 Jan 26 16:17 10-rate-lav.conf ->
> /usr/share/alsa/alsa.conf.d/10-rate-lav.conf lrwxrwxrwx 1 root root 46 Jan
> 26 16:17 10-samplerate.conf ->
> /usr/share/alsa/alsa.conf.d/10-samplerate.conf lrwxrwxrwx 1 root root 45
> Jan 26 16:17 10-speexrate.conf ->
> /usr/share/alsa/alsa.conf.d/10-speexrate.conf lrwxrwxrwx 1 root root 48
> Jan 26 16:17 50-arcam-av-ctl.conf ->
> /usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf lrwxrwxrwx 1 root root 40
> Jan 26 16:17 50-jack.conf -> /usr/share/alsa/alsa.conf.d/50-jack.conf
> lrwxrwxrwx 1 root root 39 Jan 26 16:17 50-oss.conf ->
> /usr/share/alsa/alsa.conf.d/50-oss.conf lrwxrwxrwx 1 root root 46 Jan 26
> 16:17 50-pulseaudio.conf -> /usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
> lrwxrwxrwx 1 root root 47 Jan 26 16:17 60-a52-encoder.conf ->
> /usr/share/alsa/alsa.conf.d/60-a52-encoder.conf lrwxrwxrwx 1 root root 41
> Jan 26 16:17 60-upmix.conf -> /usr/share/alsa/alsa.conf.d/60-upmix.conf
> lrwxrwxrwx 1 root root 44 Jan 26 16:17 60-vdownmix.conf ->
> /usr/share/alsa/alsa.conf.d/60-vdownmix.conf lrwxrwxrwx 1 root root 46 Jan
> 26 16:17 98-usb-stream.conf ->
> /usr/share/alsa/alsa.conf.d/98-usb-stream.conf lrwxrwxrwx 1 root root 38
> Feb 15 00:05 99-pulse.conf -> /usr/share/alsa/alsa.conf.d/pulse.conf
> -rw-r--r-- 1 root root 201 Nov 10 16:29 99-pulseaudio-default.conf.example
>
> Elimar
Yes , i have removed pulseaudio, i don't like it, i have had too many problems
with pulseaudio.
For the plugin libasound2-plugins it's important ?
Philippe Merlin
Bug#928764: alsa-utils does not store or restore configuration
Le samedi 11 mai 2019, 16:12:38 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe [2019-05-11 16:06 +0200]:
> > Le samedi 11 mai 2019, 15:33:23 CEST Elimar Riesebieter a écrit :
> > > * MERLIN Philippe [2019-05-11 14:38
+0200]:
> > > > Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > > > > Hi merlin,
> > > > >
> > > > > * merlin [2019-05-10 17:59 +0200]:
> > > > > > Package: alsa-utils
> > > > > > Version: 1.1.8-2
> > > > > > Severity: important
> > > > > >
> > > > > > Dear Maintainer,
> > > > > >
> > > > > > At each start of the computer the sound function is absent so that
> > > > > > it
> > > > > > works the only method that I found is to launch in a window the
> > > > > > alsamixer
> > > > > > program and to modify a parameter and the sound is restored,the
> > > > > > most
> > > > > > surprising is that the parameters previously saved by alsamixer
> > > > > > are
> > > > > > present.
> > > > >
> > > > > could you please check the status of alsa's systdemd services?
> > > > >
> > > > > # systemctl -t service | grep alsa | awk '{print $1}' | xargs
> > > > > systemctl
> > > > > status
> > > > >
> > > > >
> > > > > Elimar
> > > >
> > > > The result:
> > > > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > >
> > > Please post the output of:
> > >
> > > $ ls -al /etc/alsa
> > > $ ls -al /etc/alsa/conf.d
> > > $ ls -al /var/lib/alsa
> > > $ ls -al ~/.asoundrc
> > >
> > > Elimar
> >
> > s -al /etc/alsa
> > export LANG=C| ls -al ~/.asoundrc
>
> ?
>
> Elimar
Sorry it seems that a character cut the message :
export Lang=C| ls -al ~/.asoundrc
ls : cannot access /home/philippe/.asoundrc : No such file or directory
Philippe Merlin
Bug#928764: alsa-utils does not store or restore configuration
Le samedi 11 mai 2019, 16:12:38 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe [2019-05-11 16:06 +0200]:
> > Le samedi 11 mai 2019, 15:33:23 CEST Elimar Riesebieter a écrit :
> > > * MERLIN Philippe [2019-05-11 14:38 +0200]:
> > > > Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > > > > Hi merlin,
> > > > >
> > > > > * merlin [2019-05-10 17:59 +0200]:
> > > > > > Package: alsa-utils
> > > > > > Version: 1.1.8-2
> > > > > > Severity: important
> > > > > >
> > > > > > Dear Maintainer,
> > > > > >
> > > > > > At each start of the computer the sound function is absent so that
> > > > > > it
> > > > > > works the only method that I found is to launch in a window the
> > > > > > alsamixer
> > > > > > program and to modify a parameter and the sound is restored,the
> > > > > > most
> > > > > > surprising is that the parameters previously saved by alsamixer
> > > > > > are
> > > > > > present.
> > > > >
> > > > > could you please check the status of alsa's systdemd services?
> > > > >
> > > > > # systemctl -t service | grep alsa | awk '{print $1}' | xargs
> > > > > systemctl
> > > > > status
> > > > >
> > > > >
> > > > > Elimar
> > > >
> > > > The result:
> > > > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > >
> > > Please post the output of:
> > >
> > > $ ls -al /etc/alsa
> > > $ ls -al /etc/alsa/conf.d
> > > $ ls -al /var/lib/alsa
> > > $ ls -al ~/.asoundrc
> > >
> > > Elimar
> >
> > s -al /etc/alsa
> > export LANG=C| ls -al ~/.asoundrc
>
> ?
>
> Elimar
Sorry:
export LANG=C| ls -al ~/.asoundrc
Bug#928764: alsa-utils does not store or restore configuration
Le samedi 11 mai 2019, 15:33:23 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe [2019-05-11 14:38 +0200]:
> > Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > > Hi merlin,
> > >
> > > * merlin [2019-05-10 17:59 +0200]:
> > > > Package: alsa-utils
> > > > Version: 1.1.8-2
> > > > Severity: important
> > > >
> > > > Dear Maintainer,
> > > >
> > > > At each start of the computer the sound function is absent so that it
> > > > works the only method that I found is to launch in a window the
> > > > alsamixer
> > > > program and to modify a parameter and the sound is restored,the most
> > > > surprising is that the parameters previously saved by alsamixer are
> > > > present.
> > >
> > > could you please check the status of alsa's systdemd services?
> > >
> > > # systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > status
> > >
> > >
> > > Elimar
> >
> > The result:
> > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > status *●* alsa-restore.service - Save/Restore Sound Card State
> > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
>
> Please post the output of:
>
> $ ls -al /etc/alsa
> $ ls -al /etc/alsa/conf.d
> $ ls -al /var/lib/alsa
> $ ls -al ~/.asoundrc
>
> Elimar
s -al /etc/alsa
export LANG=C| ls -al ~/.asoundrc
thanks.
Philippe Merlin
Bug#928764: alsa-utils does not store or restore configuration
Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> Hi merlin,
>
> * merlin [2019-05-10 17:59 +0200]:
> > Package: alsa-utils
> > Version: 1.1.8-2
> > Severity: important
> >
> > Dear Maintainer,
> >
> > At each start of the computer the sound function is absent so that it
> > works the only method that I found is to launch in a window the alsamixer
> > program and to modify a parameter and the sound is restored,the most
> > surprising is that the parameters previously saved by alsamixer are
> > present.
>
> could you please check the status of alsa's systdemd services?
>
> # systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> status
>
>
> Elimar
The result:
systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl status
*●* alsa-restore.service - Save/Restore Sound Card State
*active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
*●* alsa-state.service - Manage Sound Card State (restore and store)
*active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
Another information is a rather new phenomenon,
the alsactl store command does not solve the problem
Philippe Merlin
Bug#900145: plasmashell freezes with xserver 1.20
It seems that the freeze is due to xserver-xorg 1.20. Yes Maybe, but this problem is not new for me its appears not so frequently that now, but sometimes when i reached Firefox by mans of the taskbar and they are many firefox windows plasmashell freeze often.
Bug#900145: plasmashell freezes every few times it appears
I have the same problem, since last update i must kill plasmashell and restart it. This restarting i have to make it at every starting up of session kde. Today i have to make it second time, by looking at tracks on console it looks like a loss of the message return of the applet just started.
Bug#861977: python3-pil:i386 can't be remove
Package: python3
Version: 3.5.3-1
Severity: important
Dear Maintainer,
On a migration of Debian testing i386 to amd64 an :
apt-get install -f is stopped when he tries to remove package python3-pil:i386
the python3-pil:amd64 is present:
The result of an dpkg -l :
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
/| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-/
installé/W=attend-traitement-déclenchements
/|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)/
/||/ Nom Version Architecture Description/
+++-=---
=
iU python3-pil:amd64 4.0.0-4 amd64Python Imaging Library
(Python3)
rF python3-pil:i386 4.0.0-4 i386 Python Imaging Library
(Python3)
This a part of the result of :
apt-get install -f
.
Suppression de python3-pil:i386 (4.0.0-4) ...
dpkg-query: erreur: --listfiles requiert un nom de paquet légal.
« python3-pil » ne l'est pas ; nom de paquet « python3-pil » ambigu avec plus
d'une instance installée
Utiliser --help pour de l'aide sur la recherche de paquets.
Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in
main()
File "/usr/bin/py3clean", line 196, in main
pfiles = set(dpf.from_package(options.package))
File "/usr/share/python3/debpython/files.py", line 53, in from_package
raise Exception("cannot get content of %s" % package_name)
Exception: cannot get content of python3-pil
dpkg: erreur de traitement du paquet python3-pil:i386 (--remove) :
le sous-processus script pre-removal installé a retourné une erreur de sortie
d'état 1
dpkg-query: erreur: --listfiles requiert un nom de paquet légal.
« python3-pil » ne l'est pas ; nom de paquet « python3-pil » ambigu avec plus
d'une instance installée
Utiliser --help pour de l'aide sur la recherche de paquets.
Traceback (most recent call last):
File "/usr/bin/py3compile", line 290, in
main()
File "/usr/bin/py3compile", line 270, in main
options.force, options.optimize, e_patterns)
File "/usr/bin/py3compile", line 154, in compile
for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 106, in filter_files
for fn in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
for fn in files:
File "/usr/share/python3/debpython/files.py", line 53, in from_package
raise Exception("cannot get content of %s" % package_name)
Exception: cannot get content of python3-pil
dpkg: error while cleaning up:
le sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
Des erreurs ont été rencontrées pendant l'exécution :
python3-pil:i386
Please can you correct this problem or give me a way to pass, i am stopped by
this.
The report of the bug was writed on another computer
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages python3 depends on:
ii dh-python 2.20170125
ii libpython3-stdlib 3.5.3-1
ii python3-minimal3.5.3-1
ii python3.5 3.5.3-1
python3 recommends no packages.
Versions of packages python3 suggests:
pn python3-doc
pn python3-tk
pn python3-venv
Bug#860885: systemd fails to mount five of six system files indicated in /etc/fstab
Le vendredi 21 avril 2017, 21:18:07 CEST Michael Biebl a écrit : > Control: tags -1 + moreinfo > > Am 21.04.2017 um 15:04 schrieb phil-deb1.merlin: > > Package: systemd > > Version: 232-22 > > Severity: important > > Can you share more details, like: > Is this problem reproducible on every boot? > Does it only happen for certain file systems/drives, i.e. are only file > systems affected which are *not* on /dev/sda? > > How are your drives connected? Thank you for looking into my problem so quickly 1)Yes Its reproducible on every boot 2)Not the Swap is /dev/sda1 and its fail to mount 3) Two Disks IDE , One Disk Sata (Sda)
Bug#844707: plasma-workspace: plasmadesktop - excessive cpu usage, slow desktop operation
I am sure that the problem is not solved. My version of plama-workspace is : dpkg -l|grep plasma-workspace The problem CPU >100% appears often when i open and click to the icon Firefox on the taskbarRecently I have started plamashell in Konsole and i received plenty error messages when CPU grows more 100% the last error message received is : *QXcbConnection: XCB error: 2 (BadValue), sequence: 36336, resource id: 71303772, major code: 142 (Unknown), minor code: 3* no more messages and top give CPU > 100% When the problem arrived i kill the process plasmashell and i restart plasmashell. I don't know if this error message can help you to solve thr problem
Bug#811452: phpmyadmin: Missing Depends on dbconfig-mysql packages
With the new version of phpmyadmin 4:4.5.4.1-2 for me its works fine. Thank you. Philippe Merlin
Bug#811452: phpmyadmin: Missing Depends on dbconfig-mysql packages
Le samedi 30 janvier 2016, 15:03:43 Michal Čihař a écrit : > Hi > > Dne 29.1.2016 v 11:54 MERLIN Philippe napsal(a): > > Hello, > > > > I don't think so for me its not closed. > > > > My version of debian is SID AMD64 and with the last update of phpmyadmin > > the 4:4.5.4-1 I have this message: > > "MySQL database support detected, apparently missing Depends on > > dbconfig-mysql package. Please report this issue to the package > > maintainer " no additional error in the installation, > > Not sure how it came to this, but the dependency on dbconfig-mysql is > there, see https://packages.debian.org/sid/phpmyadmin I don't understand what you mean, but i have this message and my mysql server works fine. With webmin i can access at the phpmyadmin db. an dpkg -l|grep dbconfig best regards. Philippe Merlin
Bug#811452: phpmyadmin: Missing Depends on dbconfig-mysql packages
Hello, I don't think so for me its not closed. My version of debian is SID AMD64 and with the last update of phpmyadmin the 4:4.5.4-1 I have this message: " MySQL database support detected, apparently missing Depends on dbconfig- mysql package. Please report this issue to the package maintainer " no additional error in the installation, Paramétrage de phpmyadmin (4:4.5.4-1) ... on the other hand white screen during the access at phpmyadmin. an dpkg -l|grep phpmyadmin Philippe Merlin
Bug#794768: kde-window-manager: the scren freeze after a while and everything freeze
The problem always exists, these last two days I had had no blocking, previously I had to reboot the system one twice a day what is not very pleasant, today I was still a victim of this blocking. The blocking does not still show itself in the same way, the common point is however the impossibility to launch a program since the bar of command. Certain times it is possible to exploit the open windows and even to launch the yakuake konsoles, of other time we can make nothing except open a new session by Ctl+Alt+F2. On a Yakuake console qdbus org.kde.plasmashell show that it does not work, on the screen sometimes its seems that an little white window is open, one time an little window name plasma is open and blocked. The blocking can arrive the session being opened and without activity. The only method to reboot the computer is to launch a poweroff yakuake is in a new session or in a console. Today after a poweroff I had this message: policykit daemon disconnected from the bus. we are no longer a registered authentication agent Sometimes when all is blocked after an poweroff the system never stop, the only method is to stop the computer electrically. Philippe Merlin
Bug#794768: kde-window-manager: the scren freeze after a while and everything freeze
once again the bottom bar of screen indicating the launched programs does notanswer, i succeed on a konsole : portable:~# qdbus org.kde.plasmashell Error: org.freedesktop.DBus.Error.NoReply Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. portable:~# qdbus org.kde.plasmashell Error: org.freedesktop.DBus.Error.NoReply Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. portable:~# qdbus :1.10 org.kde.kglobalaccel :1.104 org.freedesktop.Akonadi.Agent.akonadi_kcal_resource_1 org.freedesktop.Akonadi.Resource.akonadi_kcal_resource_1 org.kde.akonadi_kcal_resource_1-2751 :1.105 org.freedesktop.Akonadi.Agent.akonadi_kcal_resource_0 org.freedesktop.Akonadi.Resource.akonadi_kcal_resource_0 org.kde.akonadi_kcal_resource_0-2723 :1.106 org.freedesktop.Akonadi.Agent.akonadi_mixedmaildir_resource_0 org.freedesktop.Akonadi.Resource.akonadi_mixedmaildir_resource_0 org.kde.akonadi_mixedmaildir_resource_0-2773 :1.107 org.freedesktop.Akonadi.Agent.akonadi_newmailnotifier_agent org.freedesktop.Akonadi.NewMailNotifierAgent org.kde.akonadi_newmailnotifier_agent-2783 :1.108 org.freedesktop.Akonadi.Agent.akonadi_pop3_resource_1 org.freedesktop.Akonadi.Resource.akonadi_pop3_resource_1 org.kde.akonadi_pop3_resource_1-2821 :1.109 org.freedesktop.Akonadi.Agent.akonadi_notes_agent org.freedesktop.Akonadi.NotesAgent org.kde.akonadi_notes_agent-2802 :1.11 org.kde.KScreen.Backend.XRandR :1.110 org.freedesktop.Akonadi.Agent.akonadi_pop3_resource_0 org.freedesktop.Akonadi.Resource.akonadi_pop3_resource_0 org.kde.akonadi_pop3_resource_0-2820 :1.111 org.kde.kio_http_cache_cleaner :1.113 org.freedesktop.Akonadi.Agent.akonadi_vcard_resource_2 org.freedesktop.Akonadi.Resource.akonadi_vcard_resource_2 :1.114 org.freedesktop.Akonadi.Agent.akonadi_vcard_resource_3 org.freedesktop.Akonadi.Resource.akonadi_vcard_resource_3 :1.115 org.freedesktop.Akonadi.Agent.akonadi_sendlater_agent org.freedesktop.Akonadi.SendLaterAgent org.kde.akonadi_sendlater_agent-2822 :1.118 :1.120 :1.124 org.kde.konsole :1.13 org.bluez.obex :1.14 org.kde.kaccess :1.17 ca.desrt.dconf :1.18 org.freedesktop.ScreenSaver org.kde.ksmserver org.kde.screensaver :1.19 org.kde.krunner :1.20 org.kde.KWin org.kde.kwin.Screenshot :1.21 org.kde.baloo :1.22 org.freedesktop.Notifications org.kde.StatusNotifierHost-2380 org.kde.plasmashell :1.23 org.kde.polkit-kde-authentication-agent-1 :1.25 org.kde.kmix :1.27 org.kde.akregator org.kde.kaddressbook org.kde.kjots org.kde.kmail org.kde.kmail2 org.kde.knotes org.kde.kontact org.kde.korganizer org.kde.pim.TransportManager :1.276 net.sourceforge.ksudoku-20721 :1.29 org.kde.dolphin-2391 :1.3 org.kde.klauncher5 :1.356 :1.45 :1.46 org.gnome.GConf :1.47 :1.48 org.kde.klauncher :1.49 org.kde.kded :1.5 org.freedesktop.PowerManagement org.freedesktop.PowerManagement.Inhibit org.kde.Solid.PowerManagement org.kde.Solid.PowerManagement.PolicyAgent org.kde.StatusNotifierWatcher org.kde.kded5 org.kde.keyboard :1.51 org.a11y.Bus :1.52 org.kde.StatusNotifierItem-2408-1 :1.53 :1.54 :1.55 :1.57 org.gtk.vfs.Daemon :1.58 org.blueman.Applet :1.59 :1.60 org.kde.JobViewServer org.kde.kuiserver :1.62 org.freedesktop.Akonadi.Control org.freedesktop.Akonadi.Control.lock :1.63 org.freedesktop.Akonadi :1.64 org.kde.kwalletd :1.66 org.kde.knotify :1.68 org.kde.StatusNotifierItem-2409-1 :1.69 :1.70 org.freedesktop.Akonadi.Janitor :1.71 org.freedesktop.Akonadi.Agent.akonadi_akonotes_resource_0 org.freedesktop.Akonadi.Resource.akonadi_akonotes_resource_0 :1.72 org.freedesktop.Akonadi.Agent.akonadi_akonotes_resource_1 org.freedesktop.Akonadi.Resource.akonadi_akonotes_resource_1 :1.73 org.freedesktop.Akonadi.Agent.akonadi_akonotes_resource_2 org.freedesktop.Akonadi.Resource.akonadi_akonotes_resource_2 :1.74 org.kde.korgac :1.76 org.freedesktop.Akonadi.Agent.akonadi_archivemail_agent org.freedesktop.Akonadi.ArchiveMailAgent org.kde.akonadi_archivemail_agent-2692 :1.77 org.freedesktop.Akonadi.Agent.akonadi_contacts_resource_2 org.freedesktop.Akonadi.Resource.akonadi_contacts_resource_2 :1.78 org.freedesktop.Akonadi.Agent.akonadi_contacts_resource_0 org.freedesktop.Akonadi.Resource.akonadi_contacts_resource_0 :1.79 org.freedesktop.Akonadi.Agent.akonadi_contacts_resource_3 org.freedesktop.Akonadi.Resource.akonadi_contacts_resource_3 :1.80 org.kde.StatusNotifierItem-2699-1 :1.81 org.freedesktop.Akonadi.Agent.akonadi_contacts_resource_4 org.freedesktop.Akonadi.Resource.akonadi_contacts_resource_4 :1.82 org.freedesktop.Akonadi.Agent.akonadi_ical_resource_0 org.freedesktop.Akonadi.Resource.akonadi_ical_resource_0 :1.83
Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates
Le dimanche 26 juillet 2015, 23:03:21 Lisandro Damián Nicanor Pérez Meyer a écrit : On Sunday 26 July 2015 18:32:47 MERLIN Philippe wrote: [snip] Les paquets suivants contiennent des dépendances non satisfaites : kde-full : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé kde-standard : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé Recommande: plasma-widget-networkmanagement mais il n'est pas installable E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ». Yes, as Jeremey said, that was a bug already solved. Can you try again? I'm wanting to see if it's due to a missing dependency or not. I succeed to install kde-full and at restart all works fine no problem . Whatever the appearance of windows changed well, I think that with a minimum of effort I shall manage to configure them as he pleases me. Thank you for your precious help. For I consider the bug as closed Philippe Merlin
Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates
Le samedi 25 juillet 2015, 11:06:29 Lisandro Damián Nicanor Pérez Meyer a écrit : On Saturday 25 July 2015 10:36:01 MERLIN Philippe wrote: The problem for me is on a Debian Sid AMD64 where kwin-x11 4:5.3.2-2 was installed with kde-window-manager 4:5.3.2-2 at the same time. All windows are generate without the top left button - # x and can't be selected with the cursor, some windows open on the full screen and hide all. Sounds like if only kwin_wayland is installed, which is just strange. I got the same result when I missed kwin_x11, but once I installed it and reopened the X session everything went just OK. Can you try removing kwin_wayland and only keeping kwin_x11? i test removing kwin_wayland with no success, all the windows generate are not selectable and they have not on top left the three buttons - # x for reduct, or change size of the window or close the window for sample the windows of kwallet open at the start of kontact it's impossible to write into. If that doesn't works, can you try installing (or updating) kde-full? Yes, that will install the whole stack, but I want to know if it's a dependency problem or not. actually it's impossible to install kde-full apt-get -s install kde-full kde-standard Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Certains paquets ne peuvent être installés. Ceci peut signifier que vous avez demandé l'impossible, ou bien, si vous utilisez la distribution unstable, que certains paquets n'ont pas encore été créés ou ne sont pas sortis d'Incoming. L'information suivante devrait vous aider à résoudre la situation : Les paquets suivants contiennent des dépendances non satisfaites : kde-full : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé kde-standard : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé Recommande: plasma-widget-networkmanagement mais il n'est pas installable E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».apt-get -s install kde-full kde-standard Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Certains paquets ne peuvent être installés. Ceci peut signifier que vous avez demandé l'impossible, ou bien, si vous utilisez la distribution unstable, que certains paquets n'ont pas encore été créés ou ne sont pas sortis d'Incoming. L'information suivante devrait vous aider à résoudre la situation : Les paquets suivants contiennent des dépendances non satisfaites : kde-full : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé kde-standard : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé Recommande: plasma-widget-networkmanagement mais il n'est pas installable E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ». Also, which video card do you have? Running with which drivers? Old ATI radeon driver radeon of Xorg Feel free to reply with any question that might arise in the process, I would be happy to try to help! thanks for help -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates
The problem for me is on a Debian Sid AMD64 where kwin-x11 4:5.3.2-2 was installed with kde-window-manager 4:5.3.2-2 at the same time. All windows are generate without the top left button - # x and can't be selected with the cursor, some windows open on the full screen and hide all. thanks Le samedi 25 juillet 2015, 01:01:10 Lisandro Damián Nicanor Pérez Meyer a écrit : tag 793026 moreinfo thanks Hi everyone! Please check if you have kwin-x11 installed. There was a missing dependency somewhere and some packages should have migrated to testing without them. Feel free to get the package from unstable and test if you can reproduce this. Thanks, and my most sincere apologies for the inconvenience. Lisandro. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates a disfonctionnement of any window kde
I was unable to generate this bug with kde-window-manager 4:5.3.2-2 Because of this dysfunction -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783787: ImportError: No module named '_sysconfigdata_m'
Same problem with python2.7-minimal and libpython2.7-minimal 2.7.9-3 amd64 the error is different : ImportError: No module named _sysconfigdata_nd Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776979: kmail: First Filter of the list disappeared at each launch of Kontact
Now the filters works Fine. I think you can close the Bug. I don't know why they now work, but they work.!!! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761647: kde-full: an poweroff never succeed with kde
You can close the Bug. M Sandro Knau give me the solution modify the file /etc/kde4/kdm/kdmrc with the right command. Philippe Merlin
Bug#747637: akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too
Le mercredi 26 novembre 2014, 11:40:48 Raphael Hertzog a écrit : Control: tag -1 + moreinfo Hello Markus Merlin, you reported that you were affected by Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747637 Maximiliano believes that the latest update 1.13.0-1 should fix the db upgrade problems (see below). Can you confirm this so that we can close this bug ? On Tue, 19 Aug 2014, Maximiliano Curia wrote: I think the new uploaded akonadi version (1.13.0-1) fixes more db upgrade cases, but I haven't had any issues with the previous upgrades so it's hard for me to be sure. Could you please confirm if it fixes the issues you had with the 1.12.1 version? Yes you can close. With the new version there is no problem. Sorry I forget to say this. Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761647: kde-full: an poweroff never succeed with kde
Hello, I had no answer to my last observations concerning the procedure of stop of the computer by Kde. Kde seems to make a Halt instead of a Poweroff , to be sure there I have throw in a console the command systemctl halt the tracks which I make at the level of systemd confirm this hypothesis they ended exactly same by reboot system halted and the computer is not electrically stopped. Please could cure this established fact because it is very annoying, in advance thank you, except for this small problem, I find that the last versions of Kde are really excellent. Best regards. Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761647: kde-full: an poweroff never succeed with kde
Le dimanche 21 septembre 2014, 11:28:11 Maximiliano Curia a écrit : ¡Hola MERLIN! El 2014-09-21 a las 10:31 +0200, MERLIN Philippe escribió: My Sid system is up to date and the problem is on the agenda unfortunately always. With a novelty, further to the last update of Systemd I am blocked(surrounded) during 5 minutes with a message concerning the stop(ruling) of Samba I created Bug*762087 concerning this problem. 5 minutes is the normal tcp timeout, so it sounds like a network issue, some service might be getting stoped after the network went down and then it fails to communicate with the server. This might be caused by your network connection being configured in your user session through your network manager widget. So when the session ends, the network connection is closed. Another service that might be affected by this is a network file system. If you have some system dependency on having your network connection available, make sure that the network connection is applied system wide and not only during your session. I think that the problem which arrived with Systemd is caused by a mismanagement of Kde and Systemd. Sorry, I can't reproduce the issue, and I don't see a KDE mismanagement, if you want us to act on this bug we need a way to reproduce it. Hello, Thank you very much, for the hypotheses which you formulate to try to explain the problem. I drew the calls made by Systemd at the time of the demand of stop of the computer. I also drew a demand of stop in a Konsole by means of the command systemctl poweroff which it stops(arrests) effectively the computer. By studying and by comparing these tracks I noticed that in the case of a demand of stop(ruling) by Kde we see clearly a starting Halt and in the other case a Starting Poweroff , now I read that in the system only Debian Sid Poweroff stops machines Halt does not make it any more, I think but i am not sure that it is an error of Kde. Best regards Philippe Merlin Happy hacking, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761311: systemd: Sometimes at Boot systemd can't start some services (avahi, bluetooth)
Hello, I confirm the new version of systemd corrected for me the problem, I think that we can close this Bug. Best Regards. Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761311: systemd: Sometimes at Boot systemd can't start some services (avahi, bluetooth)
Le samedi 27 septembre 2014, 18:31:51 Michael Biebl a écrit : Thanks for reporting back. Am 27.09.2014 um 18:05 schrieb MERLIN Philippe: Hello, I confirm the new version of systemd corrected for me the problem, I think that we can close this Bug. With new version you mean 215-4? Yes, systemd 215-4, However with this version of systemd, i have a new problem,I am going to create a Bug concerning the stop of Samba by systemctl. Best Regards. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740942: [samba] /etc/init.d/samba forbit systemd shutdown system
I have the same problem in the stop of the computer, infringe 5 minutes. For the record, Systemd launches to the starting up of Samba 4 services(departments): samba, samba-ad-dc, nmbd, smbd. In the stop(ruling) it should stop all these services, if we look at the script of /etc/init.d/samba its stop samba-ad-ac, smbd, nmbd. In a Konsole i do an : portable:/usr/share/man# time systemctl stop samba real5m0.350s user0m0.000s sys 0m0.000s As time show : 5 minutes wait portable:/usr/share/man# systemctl status samba ● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd) Loaded: loaded (/etc/init.d/samba) Active: failed (Result: timeout) since sam. 2014-09-27 18:26:04 CEST; 46s ago Process: 31126 ExecStop=/etc/init.d/samba stop (code=killed, signal=TERM) sept. 27 18:26:04 portable samba[31126]: Stopping samba-ad-dc (via systemctl): samba-ad-dc.service portable:/usr/share/man# systemctl status samba-ad-dc ● samba-ad-dc.service - LSB: start Samba daemons for the AD DC Loaded: loaded (/etc/init.d/samba-ad-dc) Active: inactive (dead) since sam. 2014-09-27 18:26:05 CEST; 1min 55s ago Process: 31764 ExecStop=/etc/init.d/samba-ad-dc stop (code=exited, status=0/SUCCESS) It shows that : samba and samba-ad-dc are stopped But portable:/usr/share/man# systemctl status smbd ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded (/etc/init.d/smbd) Active: active (running) since sam. 2014-09-27 11:50:21 CEST; 6h ago CGroup: /system.slice/smbd.service ├─1732 /usr/sbin/smbd -D └─1746 /usr/sbin/smbd -D sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.658274, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter password level sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.658774, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter share modes sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.658899, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter share modes sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.659245, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter share modes sept. 27 11:50:21 portable smbd[1694]: Starting SMB/CIFS daemon: smbd. sept. 27 11:50:24 portable smbd[1732]: [2014/09/27 11:50:24.239602, 0] ../lib/util/become_daemon.c:136(daemon_ready) portable:/usr/share/man# systemctl status nmbd ● nmbd.service - LSB: start Samba NetBIOS nameserver (nmbd) Loaded: loaded (/etc/init.d/nmbd) Active: active (running) since sam. 2014-09-27 11:49:56 CEST; 6h ago CGroup: /system.slice/nmbd.service └─1034 /usr/sbin/nmbd -D sept. 27 11:49:56 portable nmbd[1033]: [2014/09/27 11:49:56.510769, 0] ../source3/param/loadparm.c:3067(lp_set_enum_parm) sept. 27 11:49:56 portable nmbd[1033]: WARNING: Ignoring invalid value 'share' for parameter 'security' sept. 27 11:49:56 portable nmbd[1033]: [2014/09/27 11:49:56.579792, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:49:56 portable nmbd[1033]: Ignoring unknown parameter password level sept. 27 11:49:56 portable nmbd[1034]: [2014/09/27 11:49:56.581992, 0] ../source3/nmbd/nmbd_subnetdb.c:250(create_subnets) sept. 27 11:49:56 portable nmbd[920]: Starting NetBIOS name server: nmbd. sept. 27 11:49:56 portable nmbd[1034]: create_subnets: No local IPv4 non- loopback interfaces ! sept. 27 11:49:56 portable nmbd[1034]: [2014/09/27 11:49:56.582973, 0] ../source3/nmbd/nmbd_subnetdb.c:251(create_subnets) sept. 27 11:49:56 portable nmbd[1034]: create_subnets: Waiting for an interface to appear ... sept. 27 11:50:46 portable nmbd[1034]: [2014/09/27 11:50:46.586911, 0] ../lib/util/become_daemon.c:136(daemon_ready) portable:/usr/share/man# But smbd and nmbd services are still Active. If i do in a Konsole : systemctl stop smbd or nmbd its stop correctly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762087: samba: systemd and samba stop computer wait of 5 minute
Hello, I made additional tests to try to take forward the solution of the problem which is always on the agenda. I do an on a console: portable:/usr/share/man# systemctl stop samba After an long time an : -- portable:/usr/share/man# systemctl status samba ● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd) Loaded: loaded (/etc/init.d/samba) Active: failed (Result: timeout) since lun. 2014-09-22 15:16:08 CEST; 2min 35s ago Process: 9792 ExecStop=/etc/init.d/samba stop (code=killed, signal=TERM) Process: 9548 ExecStart=/etc/init.d/samba start (code=exited, status=0/SUCCESS) sept. 22 15:07:58 portable samba[9548]: Starting nmbd (via systemctl): nmbd.service. sept. 22 15:07:58 portable samba[9548]: Starting smbd (via systemctl): smbd.service. sept. 22 15:08:02 portable samba[9548]: Starting samba-ad-dc (via systemctl): samba-ad-dc.service. sept. 22 15:16:08 portable samba[9792]: Stopping samba-ad-dc (via systemctl): samba-ad-dc.service portable:/usr/share/man# systemctl status samba-ad-dc ● samba-ad-dc.service - LSB: start Samba daemons for the AD DC Loaded: loaded (/etc/init.d/samba-ad-dc) Active: inactive (dead) since lun. 2014-09-22 15:16:09 CEST; 4min 16s ago Process: 10428 ExecStop=/etc/init.d/samba-ad-dc stop (code=exited, status=0/SUCCESS) Process: 9579 ExecStart=/etc/init.d/samba-ad-dc start (code=exited, status=0/SUCCESS) sept. 22 15:16:09 portable samba-ad-dc[10428]: Stopping Samba AD DC daemon: samba. an -- portable:/usr/share/man# systemctl status smbd ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded (/etc/init.d/smbd) Active: active (running) since lun. 2014-09-22 12:18:04 CEST; 3h 3min ago CGroup: /system.slice/smbd.service ├─1688 /usr/sbin/smbd -D └─1704 /usr/sbin/smbd -D sept. 22 10:29:55 portable smbd[1688]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNIN...urity' sept. 22 10:29:55 portable smbd[1688]: [2014/09/22 10:29:55.866847, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 22 10:29:55 portable smbd[1688]: Ignoring unknown parameter password level sept. 22 10:29:55 portable smbd[1688]: [2014/09/22 10:29:55.867306, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 22 10:29:55 portable smbd[1688]: Ignoring unknown parameter share modes sept. 22 10:29:55 portable smbd[1688]: [2014/09/22 10:29:55.867419, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 22 10:29:55 portable smbd[1688]: Ignoring unknown parameter share modes sept. 22 10:29:55 portable smbd[1688]: [2014/09/22 10:29:55.867631, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 22 10:29:55 portable smbd[1688]: Ignoring unknown parameter share modes sept. 22 10:29:55 portable smbd[5621]: Reloading /etc/samba/smb.conf: smbd. Hint: Some lines were ellipsized, use -l to show in full. portable:/usr/share/man# -- Same result for nmbd. This information shows that the stop of samba by systemd works badly, nor smbd or nmbd are stopped. It is can be the cause of the wait of 5 minutes in the stop of the computer. Best Regards. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761647: kde-full: an poweroff never succeed with kde
Le lundi 15 septembre 2014, 19:13:14 Maximiliano Curia a écrit : ¡Hola merlin! On Lu, 15 sep 14, 12:16:23, merlin wrote: When I click the window extinction in 30 seconds, the operation is very long more than 4 minutes and always ends by the reboot message [ 43302,405120 ]: system halted without the computer stops only average to cut electrically I test in a window Konsole : systemctl poweroff and all works fine the computer stop Ok, I have seen this behavior. Let me explain: Trying to shutdown the computer from the kde shutdown dialog doesn't work. It takes a while (longer than expected) to end the services and after halting it doesn't turn off. I've been able to reproduce the issue in my notebook until today. Today, after I upgraded everything to the current jessie versions, I re tested this bug and could still reproduce it, but after rebooting (i.e. restarting all the services) it started working correctly. I believe this is a bug creeping from udev/systemd/upower, that seems to be gone in the current versions. Merlin, could you please upgrade your system and confirm if after a reboot the issue is fixed for you? Happy hacking, My Sid system is up to date and the problem is on the agenda unfortunately always. With a novelty, further to the last update of Systemd I am blocked(surrounded) during 5 minutes with a message concerning the stop(ruling) of Samba I created Bug*762087 concerning this problem. I think that the problem which arrived with Systemd is caused by a mismanagement of Kde and Systemd. Best Regards Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761311: systemd: Sometimes at Boot systemd can't start some services (avahi, bluetooth)
Le mardi 16 septembre 2014, 21:36:32 Michael Biebl a écrit : Am 16.09.2014 um 10:58 schrieb MERLIN Philippe: Le vendredi 12 septembre 2014, 22:01:55 Michael Biebl a écrit : Am 12.09.2014 21:39, schrieb merlin: Sep 11 11:28:36 localhost kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-1-amd64 root=UUID=cfefa5bd-93c0-4451-818e-26207c170c14 ro clocksource=acpi_pm ipv6.disable=1 systemd.log_target=kmsg systemd.log_level=debug log_buf_len=1M enforcing=0 .. Sep 11 11:28:36 localhost kernel: [0.619303] IPv6: Loaded, but administratively disabled, reboot required to enable I wonder if this is the reason. Could you please enable ipv6 and test again. I test it and it works on two start of the system, the third start failed. I join at my message, syslog of the session, the result of the commands : systemctl status avahi-daemon.service --- avahi-status-16-09-2014.txt journalctl -xn avahi-journal-16-09-2014.txt Best Regard. Philippe Merlin I wonder, if this a hardware issue which causes dbus to timeout (iirc the default timeout for responses is 25 seconds). Is you hard drive / system slow? Thank you, Since the last update of systemd, the problem seems to have disappeared, if it confirms I think that we can close the Bug. Could you indicate to me if all the messages which appear on the console when we put at the level of grub systemd.log_target=kmsg systemd.log_level=debug log_buf_len=1M enforcing=0 are recorded in a file? If yes it would be useful for me to understand(include) the problems which I meet in the stop(ruling) of the computer. Kde and systemd, I never manage to stop(arrest) the computer besides that it lasts for a very long time Bug#761647: kde-full: an poweroff never succeed with kde and now with the new version of systemd another Bug#762087 samba: systemd and samba stop computer wait of 5 minutes. Best regards Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761647: kde-full: an poweroff never succeed with kde
Le lundi 15 septembre 2014, 10:27:32 Lisandro Damián Nicanor Pérez Meyer a écrit : On Monday 15 September 2014 15:29:43 Andrei POPESCU wrote: [snip] *** I do not know which is the package of Kde concerned by this problem that's why I send him(it) to kde-full house hoping that the persons in charge will redirect towards the concerned package. When I click the window extinction in 30 seconds, the operation is very long more than 4 minutes and always ends by the reboot message Do you have your loopback interface enabled and working? I do not understand!! What information do you want? Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742900: No mysqld.service File
Now, Systemd Is in service so much in the version Sid and testing, Debian has not the file mysqld.service so mysql can't start or stop with Systemd, It is really boring, could please repair you relatively quickly this problem, because it impacte many using applications mysql. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747637: akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too
Hello, Last days i was blocked by akonadi-12-1-1 and kmail out of service. I tried to modify the schematic layout of the base Akonadi Mysql to correct the error that akonadi-server meeting as indicates it the message of Markus Meier, not being a specialist Mysql, I looked on Google and found which to have FOREIGN KEY in Mysql it was necessary that the concerned table have an engine InnoDB, I converted a table Myisam in InnoDB, but the same error occurs farther on another table, then I converted all the tables Myisam in InnoDB, unfortunately an error occurs farther and i did not find solution.I then decided as advised me somebody to protect the base(basis) akonadi and to delete it, with the re-creation of the akonadi base I was able to found the use of Kmail. All the modifications introduced by akonadi-server 12-1-1 are optimizations at the level of the plan of the base(basis), I think that a specialist Mysql should deal with the modifications to be brought to allow a transition of 11- 12 which is made without error. Best Regards. Philippe Merlin
Bug#742512: linux: kernel 3.13 breaks fan cooling on HP 6830S laptop fine
Le dimanche 6 avril 2014, 19:33:48 Aurelien Jarno a écrit : reassign 742512 linux retitle 742512 linux: kernel 3.13 breaks fan cooling on HP 6830S laptop found 742512 linux/3.13.4-1 forwarded 742512 https://bugzilla.kernel.org/show_bug.cgi?id=717 thanks On Fri, Mar 28, 2014 at 04:21:15PM +0100, MERLIN Philippe wrote: Le mardi 25 mars 2014, 23:55:44 Aurelien Jarno a écrit : On Mon, Mar 24, 2014 at 05:30:56PM +0100, merlin wrote: Package: lm-sensors Version: 1:3.3.4-2 Severity: important Dear Maintainer, When i move to linux 3.13-1 i remark that the fan of my computer HP 6830S work by in blow and when i observe the temperature given by sensors the temperature are very high so it's must be critical for the computer. sensors : lm-sensors doesn't control the fan, it only display the temperatures returned by the sensors. Have you configured fancontrol to control the fan or did you leave the BIOS of you computer handling that (which is fine if it worked with 3.12)? Thanks for your answer. For the Bios i can't answer at your question, I do'nt see in the Bios HP anything about leaving kernel control the fan. fancontrol was never configured because pwmconfig does not work, so fancontrol is installed but not configured. At start there is a message saying that fancontrol is not started because not configured. I observe in 3.12 the fan works smoothly and in an continuous way, in 3.13 by in blow. in 3.12 the temp6 indicator given by sensors evolves during the session and the speed of the fan also. in 3.13 the temp6 indicator doe's not evolve during the session and kept the value of start low if the computer is cold and high if the computer is hot at start and then the fan works continuously. With these observation i think that the temp6 indicator is very important for the speed of the fan. Do you think i must remove fancontrol ? If you don't use fancontrol and that just switch from kernel 3.12 to 3.13 causes this issue, it is definitely a kernel issue. It is very likely to be the following upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=71711 I am therefore reassigning the bug to the linux package. Thanks. I think you are right. Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742512: lm-sensors and kernel linux 3.13-1 does not work fine
Le mardi 25 mars 2014, 23:55:44 Aurelien Jarno a écrit : On Mon, Mar 24, 2014 at 05:30:56PM +0100, merlin wrote: Package: lm-sensors Version: 1:3.3.4-2 Severity: important Dear Maintainer, When i move to linux 3.13-1 i remark that the fan of my computer HP 6830S work by in blow and when i observe the temperature given by sensors the temperature are very high so it's must be critical for the computer. sensors : lm-sensors doesn't control the fan, it only display the temperatures returned by the sensors. Have you configured fancontrol to control the fan or did you leave the BIOS of you computer handling that (which is fine if it worked with 3.12)? Thanks for your answer. For the Bios i can't answer at your question, I do'nt see in the Bios HP anything about leaving kernel control the fan. fancontrol was never configured because pwmconfig does not work, so fancontrol is installed but not configured. At start there is a message saying that fancontrol is not started because not configured. I observe in 3.12 the fan works smoothly and in an continuous way, in 3.13 by in blow. in 3.12 the temp6 indicator given by sensors evolves during the session and the speed of the fan also. in 3.13 the temp6 indicator doe's not evolve during the session and kept the value of start low if the computer is cold and high if the computer is hot at start and then the fan works continuously. With these observation i think that the temp6 indicator is very important for the speed of the fan. Do you think i must remove fancontrol ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724827: hp_wmi problem
Dear Maintener, After search with google, i found in bugzilla the exactly same description of the bug, but it seems that it's interest nobody within the kernel mainteners. Bug 60595 in bugzilla[1] Another Search i found in Archlinux Forum[2] Very interesting informations, it's describe the problem but also the last message give me an solution. *blacklisted* *hp_wmi *and all works fine. So now i think the module* hp_wmi* seems caused the problem. Another Search : Found another information with Google a bug of hp-wmi for an user in 3.9 and the patch to correct his problem. i think that may be the actually problem which cames with the 3.9+ kernel is caused by this patch patch hp-wmi[3] Best Regards. Philippe Merlin [1] https://bugzilla.kernel.org/show_bug.cgi?id=60595 [2] https://bbs.archlinux.org/viewtopic.php?pid=1322387 [3] http://www.spinics.net/lists/platform-driver-x86/msg04251.html
Bug#724827: bug 724827
Dear Maintainer, I test the last linux-image 3.11.5-1 i have a new message : TSC calibration failed no more pciehp errors Unfortunally the problem still remain, no WIFI at boot, the only way to obtain wifi is in a Konsole to put the command : rfkill unblock all and to open wicd to choose the good wifi net. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724827: (no subject)
I search with google on pciehp and pci_hp_register error and i find a method to avoid these messages https://bugzilla.redhat.com/show_bug.cgi?id=963991 is to put on a command line to Grub acpi=off. With this command line no errors and wifi is not desactivated at boot. But, but, at shutdown the computer does not stop i must push a button to stop it seems that many tools does not work. It seems, still with redhat that the last version of linux 3.12 correct this problem. Any hope to have a Debian linux-image-3-12 quickly ? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719278: Same Problem on my Debian Sid AMD64
Me too, On my Debian Sid AMD64 jitsi crashes when i goto the options video. Same message : warning: The VAD has been replaced by a hack pending a complete rewrite /usr/bin/java: symbol lookup error: /usr/lib/jni/libjnffmpeg.so: undefined symbol: ff_make_format_list. Cheers Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563263: [googleearth-package] Creates uninstallable packages (ia32-libs dependency)
Hello, I have tested the patch : make-googleearth-package and it works fine in multiarch configuration and correct the googleearth package build, the patch was created on 22 Mar 2013, Why in May 2013 the patch is not active ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634670: kde-full: Normal update of kde impossible by apt-get or aptitude
Le dimanche 21 octobre 2012 19:34:15, Adrien a écrit : tag 634670 moreinfo thanks Hi, As KDE 4.6 is not anymore available in Debian, does this bug is still relevant ? I think we can close it. Regards, Adrien yes !!! you can close. Regards Philippe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672472: linux-image-3.2.0-2-686-pae: Load of Linux 3.2-2 are very slow and brings plenty errors
Le mercredi 16 mai 2012 22:58:09, Roger Leigh a écrit : On Tue, May 15, 2012 at 11:19:29AM +0200, MERLIN Philippe wrote: I look at the date of the mountkernfs on the system on errors : 4 February 2009. I open a mountkernfs installed on a much recent system and i observe its were very differents. So i copy the much recent mountkernfs on this system and i reboot. Now there is no problem. So i can say it's Solved. But why the script in /etc/init.d/mountkernfs whas never upgraded from 2009 ? I think its a Bug . Well, it's a regular conffile. If you upgraded the package and this script wasn't upgraded, there must be a reason for that. Did you edit this file, and then tell dpkg not to upgrade it at the conffile prompt when it wanted to replace it with the new version? This has not been a problem for anyone else, and this /has/ been well tested by everyone else running testing and unstable systems, so I would look carefully at what you have done on this system to result in the conffile not being upgraded. Regards, Roger I am not sure, but i don't think i edit or modify this file, I am not so clever to do this, may be an old package do this. Yes certainly at the upgrade of initscripts they ask me, and generally i answer [N] ,i was not aware of the importance of this script and what he do, its was working so fine until 2.6.39 and 3.0 with errors. A suggestion, the maintener of the initscripts can he test the date of the scripts and suggest firmly to replace the script. 2009---2012, in 3 years linux 2.2 linux 3.3 they were plenty changes and the normal user don't know what and it's normal. Regards. Philippe MERLIN -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672472: linux-image-3.2.0-2-686-pae: Load of Linux 3.2-2 are very slow and brings plenty errors
Hello, I found a solution to this problem. Searching with google udev requires a mounted sysfs not started failed i found a paper saying to look at mountkernfs. I look at the date of the mountkernfs on the system on errors : 4 February 2009. I open a mountkernfs installed on a much recent system and i observe its were very differents. So i copy the much recent mountkernfs on this system and i reboot. Now there is no problem. So i can say it's Solved. But why the script in /etc/init.d/mountkernfs whas never upgraded from 2009 ? I think its a Bug . Thanks for your help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672472: linux-image-3.2.0-2-686-pae: Load of Linux 3.2-2 are very slow and brings plenty errors
Le samedi 12 mai 2012 23:36:49, Roger Leigh a écrit : On Sat, May 12, 2012 at 10:49:00PM +0200, MERLIN Philippe wrote: Le samedi 12 mai 2012 20:19:58, Roger Leigh a écrit : On Sat, May 12, 2012 at 07:51:55PM +0200, MERLIN Philippe wrote: Le samedi 12 mai 2012 18:52:59, Roger Leigh a écrit : On Fri, May 11, 2012 at 12:38:15PM +0200, phil-deb1.merlin wrote: This looks like it might be an issue with initscripts, but it's not clear what the cause is. Which version of Debian are using. Your report indicated testing, is this the case? Which version of initscripts are you using (dpkg -s initscripts)? Are you booting using a stock Debian kernel? Are you using an initramfs? Or do you boot directly from the root filesystem? Thanks, Roger Thanks for your answer. The version is testing. the result of dpkg -s initscripts Version: 2.88dsf-22.1 Its a Debian Kernel linux-image-3.2.0-2-686-pae 3.2.15-1 The start is given by GRUB2. Is grub using an initramfs/initrd? Also, what's the output of cat /proc/mounts after boot? So you are using a standard initramfs according to this info. The mounts look normal though. You've got all the standard filesystems mounted, plus your own. Have you ever edited the initscripts under /etc/init.d or the shell libraries under /lib/init? Can you try installing initscripts/sysv-rc/sysvinit/sysvinit-utils with 'dpkg --force-confnew -i' to make it update all of the scripts to their current versions? You'll need to download the testing versions if they aren't in /var/cache/apt/archives. Thanks, Roger I do :dpkg --force-confnew -i ini... After I have corrected many errors, I can migrate to the new boot system. Unfortunately there is no progress at Boot, the same error messages, except /dev/hda, /dev/hdb,/dev/hdc who disapeared they were started by a script hdparm.sh (which i suppress). Thanks. Philippe MERLIN -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672472: linux-image-3.2.0-2-686-pae: Load of Linux 3.2-2 are very slow and brings plenty errors
Le samedi 12 mai 2012 18:52:59, Roger Leigh a écrit : On Fri, May 11, 2012 at 12:38:15PM +0200, phil-deb1.merlin wrote: On a computer i386, i have installed linux-image-3.2-0-2 and its works bad. average time of load :ÃÂÃÂ 15 minutes no sound cards detected the mice ps/2 on aux is not activated. on load i have on the screen plenty messages which are nonsense for me and does not reflected the /etc/fstab of the computer, these error messages are not recorded in the log : dmesg, syslog, or messages. the error messages : Filesystem types and /lib/init/rw are not supported .Skipping mount touch :cannot touch '/lib/init/rw/.ramfs' Read only file system ... Filesystem types and /proc are not supported .Skipping mount Filesystem types and /sys are not supported .Skipping mount Filesystem types and /var/lock are not supported .Skipping mount Filesystem types usbdevfs and /proc/bus/usb are not supported .Skipping mount udev requires a monted sysfs not started failed! failed! This looks like it might be an issue with initscripts, but it's not clear what the cause is. Which version of Debian are using. Your report indicated testing, is this the case? Which version of initscripts are you using (dpkg -s initscripts)? Are you booting using a stock Debian kernel? Are you using an initramfs? Or do you boot directly from the root filesystem? Thanks, Roger Thanks for your answer. The version is testing. the result of dpkg -s initscripts Package: initscripts Status: install ok installed Priority: required Section: admin Installed-Size: 263 Maintainer: Debian sysvinit maintainers pkg-sysvinit- de...@lists.alioth.debian.org Architecture: i386 Source: sysvinit Version: 2.88dsf-22.1 Replaces: libc0.1, libc0.3, libc6, libc6.1 Depends: libc6 (= 2.4), ucf, mount (= 2.11x-1), debianutils (= 4), lsb-base (= 3.2-14), sysvinit-utils (= 2.86.ds1-64), sysv-rc | file-rc, coreutils (= 5.93) Recommends: psmisc, e2fsprogs Breaks: aide ( 0.15.1-5), atm-tools ( 1:2.5.1-1.3), autofs ( 5.0.0), console-common ( 0.7.86), console-setup ( 1.74), cruft ( 0.9.16), eepc- acpi-scripts ( 1.1.12), fcheck ( 2.7.59-16), hostapd ( 1:0.7.3-3), libpam-mount ( 2.13-1), live-build ( 3.0~a26-1), ltsp-client-core ( 5.2.16-1), mdadm ( 3.2.2-1), nbd-client ( 1:2.9.23-1), nfs-common ( 1:1.2.5-3), portmap ( 6.0.0-2), readahead-fedora ( 2:1.5.6-3), resolvconf ( 1.49), rpcbind ( 0.2.0-7), rsyslog ( 5.8.2-2), selinux-policy-default (= 2:0.2.20100524-9), splashy ( 0.3.13-5.1+b1), sysklogd ( 1.5-6.2), wpasupplicant ( 0.7.3-4), xymon ( 4.3.0~beta2.dfsg-9) Conflicts: libdevmapper1.02.1 ( 2:1.02.24-1) Conffiles: /etc/init.d/bootlogs db75db678fb0a8cce7138f5c18e44dd6 /etc/init.d/bootmisc.sh d8c6b3fb84741af57a74c3d32bc09dfb /etc/init.d/checkfs.sh 74457ecf8bd853fe1a2ba758053735dc /etc/init.d/checkroot.sh efc13158c7d643b5d4baaf68c984dcd1 /etc/init.d/halt 6ae1b3b1b8198567a5e32116077f12a2 /etc/init.d/hostname.sh 2180072dbb4e2f42f7ad4df4a2f9888d /etc/init.d/killprocs 5e404d35091fab6c4889302736ed4602 /etc/init.d/mountall.sh ba8a8bfee0a3457a055ed3a7236bf630 /etc/init.d/mountall-bootclean.sh d4994c72205f718f3b369d4dc69e0b0e /etc/init.d/mountnfs.sh 289709c3a76bfd9f59a0f071670f01a0 /etc/init.d/mountnfs-bootclean.sh 6df926cddd77372967e4a1f22c174b88 /etc/init.d/mountoverflowtmp 066812f55fd49c260af4efb3eed07b96 /etc/init.d/mountdevsubfs.sh 51801719b56a5acddfb1fdefdb3bfeb1 /etc/init.d/mountkernfs.sh 3b2d43b60bc5eac5a507530f3d86bfdc /etc/init.d/mtab.sh df8b4a53c9a18b748543891a2c792de7 /etc/init.d/rc.local 18cd07959adfa8411ca17fe7c2ec3d96 /etc/init.d/reboot 1b9db1ef7bfd79b128ef85d5065721a6 /etc/init.d/rmnologin 3e720aea2c7de0696879cce254b00d87 /etc/init.d/sendsigs 00ed9a4cdc73711fceef76ddef67dd12 /etc/init.d/single dc13cb373c5c098a8fb95424701373e3 /etc/init.d/umountfs 07e4c8c8d9136f36745feb4776edc6f4 /etc/init.d/umountnfs.sh be451dcc644058cd0e4448c8866e1e7b /etc/init.d/umountroot 3e6a08830565a2938fb009b63d8bd0b9 /etc/init.d/urandom 96d5bd37396a40ab5fe7071139f780fc /etc/default/devpts fc857c5ac5fb84d80720ed4d1c624f6e /etc/default/halt 18d9844cf8ca8608e2a559a4555e593a /etc/default/tmpfs 43c56edaa7b9a5f11017613656397493 /etc/network/if-up.d/mountnfs 5d79218a43b286c5a2fea1a77c7851e7 /etc/init.d/stop-bootlogd-single 648d8624e708151500c5e299a6005afe obsolete /etc/init.d/bootlogd 267ceea04f703171e6c62f506fda3305 obsolete /etc/init.d/stop-bootlogd 4544c7e1a2d0c713d29424d02faad237 obsolete Description: scripts for initializing and shutting down the system The scripts in this package initialize a standard Debian system at boot time and shut it down at halt or reboot time. Homepage: http://savannah.nongnu.org/projects/sysvinit Its a Debian Kernel linux-image-3.2.0-2-686-pae 3.2.15-1 The start is given by GRUB2. Thanks. Philippe MERLIN -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact
Bug#672472: linux-image-3.2.0-2-686-pae: Load of Linux 3.2-2 are very slow and brings plenty errors
Le samedi 12 mai 2012 20:19:58, Roger Leigh a écrit : On Sat, May 12, 2012 at 07:51:55PM +0200, MERLIN Philippe wrote: Le samedi 12 mai 2012 18:52:59, Roger Leigh a écrit : On Fri, May 11, 2012 at 12:38:15PM +0200, phil-deb1.merlin wrote: This looks like it might be an issue with initscripts, but it's not clear what the cause is. Which version of Debian are using. Your report indicated testing, is this the case? Which version of initscripts are you using (dpkg -s initscripts)? Are you booting using a stock Debian kernel? Are you using an initramfs? Or do you boot directly from the root filesystem? Thanks, Roger Thanks for your answer. The version is testing. the result of dpkg -s initscripts Version: 2.88dsf-22.1 Its a Debian Kernel linux-image-3.2.0-2-686-pae 3.2.15-1 The start is given by GRUB2. Is grub using an initramfs/initrd? You should have something like /boot/initrd.img-3.2.0-2-686-pae when you take a look (edit on the boot menu), or look in /boot/grub/grub.cfg. Also, what's the output of cat /proc/mounts after boot? Thanks, Roger grub.cfg : - insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos6)' search --no-floppy --fs-uuid --set=root cfefa5bd-93c0-4451-818e-26207c170c14 echo'Chargement de Linux 3.2.0-2-amd64 ...' linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=cfefa5bd-93c0-4451-818e-26207c170c14 ro single echo'Chargement du disque mémoire initial ...' initrd /boot/initrd.img-3.2.0-2-amd64 -- cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=1030508k,nr_inodes=219093,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=414676k,mode=755 0 0 /dev/disk/by-uuid/49214c0f-99a5-482e-aa81-4051a9f47737 / ext3 rw,relatime,errors=remount-ro,barrier=1,data=ordered 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /run/shm tmpfs rw,nosuid,nodev,relatime,size=414676k 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 /dev/sda1 /mnt/hda1 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0 /dev/sda5 /mnt/hda5 vfat rw,nosuid,nodev,relatime,fmask=,dmask=,allow_utime=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount- ro 0 0 /dev/sdb3 /mnt/hdb3 ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0 /dev/sda6 /home/pmn/chargement ext3 rw,relatime,errors=remount- ro,barrier=1,data=ordered 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 Thanks. Philippe Merlin } -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634821: libgcc1: filename change breaks old gcc
Hello, I am sorry , i think you must reopen the Bug , or give an solution , some debian packets by example like linux-headers-2.6.32-5-AMD64 want gcc-4.3 and so in SID the kernel linux 2.6.32-5 can't be used any time, when some driver or services must be updated and compiled whith dkms they can't. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630728: mesa-utils: glxgears and glxinfo does not work
As you ask me This is the Xorg.log [42.627] X.Org X Server 1.10.2 Release Date: 2011-05-28 [42.647] X Protocol Version 11, Revision 0 [42.647] Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian [42.647] Current Operating System: Linux portable 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 [42.647] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=cfefa5bd-93c0-4451-818e-26207c170c14 ro quiet [42.648] Build Date: 14 June 2011 12:32:34PM [42.648] xorg-server 2:1.10.2-1+b1 (amd64 Builddd Daemon (barber) buildd_amd64-bar...@buildd.debian.org) [42.648] Current version of pixman: 0.21.8 [42.648] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [42.648] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [42.648] (==) Log file: /var/log/Xorg.0.log, Time: Thu Jun 16 10:18:04 2011 [42.796] (==) Using config file: /etc/X11/xorg.conf [42.796] (==) Using system config directory /usr/share/X11/xorg.conf.d [43.004] (==) ServerLayout aticonfig Layout [43.004] (**) |--Screen aticonfig-Screen[0]-0 (0) [43.004] (**) | |--Monitor aticonfig-Monitor[0]-0 [43.004] (**) | |--Device aticonfig-Device[0]-0 [43.004] (**) Option Xinerama off [43.004] (==) Automatically adding devices [43.004] (==) Automatically enabling devices [43.125] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [43.125] Entry deleted from font path. [43.197] (==) 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 [43.197] (==) ModulePath set to /usr/lib/xorg/modules [43.197] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [43.197] (II) Loader magic: 0x7d7b20 [43.197] (II) Module ABI versions: [43.197] X.Org ANSI C Emulation: 0.4 [43.197] X.Org Video Driver: 10.0 [43.197] X.Org XInput driver : 12.2 [43.197] X.Org Server Extension : 5.0 [43.198] (--) PCI:*(0:1:0:0) 1002:95c2:103c:30e9 rev 0, Mem @ 0x8000/268435456, 0x9840/65536, I/O @ 0x7000/256, BIOS @ 0x/131072 [43.198] (II) Open ACPI successful (/var/run/acpid.socket) [43.198] (II) extmod will be loaded by default. [43.198] (II) dbe will be loaded by default. [43.198] (II) glx will be loaded by default. [43.198] (II) record will be loaded by default. [43.198] (II) dri will be loaded by default. [43.198] (II) dri2 will be loaded by default. [43.198] (II) LoadModule: extmod [43.424] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [43.441] (II) Module extmod: vendor=X.Org Foundation [43.441] compiled for 1.10.2, module version = 1.0.0 [43.441] Module class: X.Org Server Extension [43.441] ABI class: X.Org Server Extension, version 5.0 [43.441] (II) Loading extension SELinux [43.441] (II) Loading extension MIT-SCREEN-SAVER [43.441] (II) Loading extension XFree86-VidModeExtension [43.441] (II) Loading extension XFree86-DGA [43.441] (II) Loading extension DPMS [43.441] (II) Loading extension XVideo [43.441] (II) Loading extension XVideo-MotionCompensation [43.441] (II) Loading extension X-Resource [43.441] (II) LoadModule: dbe [43.442] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so [43.442] (II) Module dbe: vendor=X.Org Foundation [43.442] compiled for 1.10.2, module version = 1.0.0 [43.442] Module class: X.Org Server Extension [43.442] ABI class: X.Org Server Extension, version 5.0 [43.442] (II) Loading extension DOUBLE-BUFFER [43.442] (II) LoadModule: glx [43.443] (II) Loading /usr/lib/xorg/modules/extensions/fglrx/libglx.so [43.664] (II) Module glx: vendor=FireGL - ATI Technologies Inc. [43.674] compiled for 6.9.0, module version = 1.0.0 [43.674] (II) Loading extension GLX [43.674] (II) LoadModule: record [43.675] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so [43.699] (II) Module record: vendor=X.Org Foundation [43.699] compiled for 1.10.2, module version = 1.13.0 [43.699] Module class: X.Org Server Extension [43.699] ABI class: X.Org Server Extension, version 5.0 [43.699] (II) Loading extension RECORD [43.699] (II) LoadModule: dri [43.699] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so [43.720] (II) Module dri: vendor=X.Org Foundation [43.720] compiled for 1.10.2, module version = 1.0.0 [43.720] ABI class: X.Org Server Extension, version 5.0 [43.720] (II) Loading
