Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

Hi there Note: A reply in bugs failed. On 09/09/18 10:08, Marco Lucidi wrote: > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault > wrote: > > Unfortunately AIUI upstream has stopped supporting ALSA, so we are stuck > > with pulseaudio for firefox. > > Is there any particular reason for

Bug#907640: compiz: Migrating to compiz-reloaded?

Package: compiz Severity: important Hello, The launchpad upstream for compiz has switched to light maintenance mode and will not make further development since Ubuntu has stopped using it. How do people feel about switching to compiz-reloaded? https://gitlab.com/compiz Basically they

Re: How to file bug for installation images that don't boot

Hi, Tabor Kelly > How do I report this bug? In general, do what https://www.debian.org/Bugs/Reporting prescribes. If you do not have a running system with program "reportbug", then scroll down to paragraph "Sending the bug report via e-mail". Main decision to take

Re: How to file bug for installation images that don't boot

gt; question is: How do I report this bug? Use plaintext e-mail as outlined by [1]. IMO bug should be filled against the "grub" or the "linux" depending on where boot process fails for you. Reco [1] https://www.debian.org/Bugs/Reporting

How to file bug for installation images that don't boot

I have an Intel NUC8i7HNK which does not boot Debian Stretch, testing alpha3, or the latest testing nightly. I have gathered some pertinent triage information which I won't bore everyone with here. My real question is: How do I report this bug? Thanks, Tabor Statement of Confidentiality

Bind bug

Hi there See; https://kb.isc.org/article/AA-01639/0 I don't think not using deny-answer-aliases is really an option. Regards, Rob

Re: Linux Cinamon bug avec les médias amovibles ..suite

- Mail original - > De: "Bernard Schoenacker" > À: cont...@billard-francois-marie.eu > Cc: "Liste Debian" > Envoyé: Mardi 31 Juillet 2018 14:21:11 > Objet: Re: Linux Cinamon bug avec les médias amovibles ..suite > > > > - Mail

Re: Linux Cinamon bug avec les médias amovibles ..suite

- Mail original - > De: "contact" > À: "Liste Debian" > Envoyé: Mardi 31 Juillet 2018 14:04:59 > Objet: Linux Cinamon bug avec les médias amovibles ..suite > > Bonjour > > j'utilise l’environnement Cinamon sous linux stretch sans problème

Linux Cinamon bug avec les médias amovibles ..suite

session tout est en ordre sans problèmes. Le bug n’apparaît qu'au montage du média amovible. Merci -- François-Marie BILLARD

Bug #862397 (thunar freezing) is closed, but I'm still hit. What to do?

HI all. I run a stretch (stable) xfce desktop, and I'm regularly hit by thunar (v1.6.11-1) freezing. I've found: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862397 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868704 but these have been closed since (apparently) the bug is fixed

Re: Bug#900533: The most annoying bug ever: https://bugs.debian.org/900533 , fix it!

On Sun, 22 Jul 2018 17:19:42 +0100, Phil Wyett wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >On Sun, 2018-07-22 at 18:55 +0300, Askar Safin wrote: - 8< - >> >> I am unable listen music using https://vk.com/audio anymore.

Re: Bug#900533: The most annoying bug ever: https://bugs.debian.org/900533 , fix it!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 2018-07-22 at 18:55 +0300, Askar Safin wrote: > Recently Debian Stretch introduced the most annoying bug ever: https://bugs.de > bian.org/900533 ("chromium 67.0.3396.62-1: youtube video, gif's, html5, and > movies no longer work

Re: Bug related to "USB"/unknown package

Hi Mike, Thank you a lot. Problem is solved. :-) Best greetings, thanks again Benjamin On 03/07/18 13:53, Michael Stone wrote: > On Tue, Jul 03, 2018 at 01:18:57PM +0200, Benjamin Herwig wrote: >> I encountered some strange USB behaviour (also others on the internet, >> for example >>

Re: Bug related to "USB"/unknown package

On Tue, Jul 03, 2018 at 01:18:57PM +0200, Benjamin Herwig wrote: I encountered some strange USB behaviour (also others on the internet, for example https://www.linuxquestions.org/questions/linux-hardware-18/what-does-cdc_acm-unknown-symbol-refcount_inc_not_zero-err-0-in-dmesg-mean-4175633136/)

Bug related to "USB"/unknown package

/) Attaching an Arduino to my computer gives an errormessage (cdc_acm: Unknown symbol refcount_inc_not_zero (err 0)) and no /dev/ttyACM* is bound. This is completely new and I dont know of any failure from my side. Could you please assist me on how to file that bug? Thank yu for all your efforts, best

Re: Nvidia 340 driver bug

Le 02/06/2018 à 17:17, dekkz...@gmail.com a écrit : > > > This is a bug in the nvidia driver module. There is not much you can do > until it is fixed upstream. > > https://devtalk.nvidia.com/default/topic/1031067/ > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8992

Re: How to diagnose and report a bug

On 16/06/18 01:30, Thomas Schmitt wrote: > Hi, > >> In pcmanfm's address bar, [...] >> [...] >> Any recomendations on how to diagnose and report this bug? > > Since there is a package with name "pcmanfm", there is also a tracker page > for it

Re: How to diagnose and report a bug

On 2018-06-15, Gene Heskett wrote: >> > >> > Obviously one test to attempt to corner the real culprit in this >> > affair would be to try another editor. How about gedit, for example? >> > Or have you done that already? > > Gedit can be dangerous to your mental health. At least recommend an >

Re: How to diagnose and report a bug

On Friday 15 June 2018 12:51:08 Curt wrote: > On 2018-06-15, Curt wrote: > > On 2018-06-15, rv riveravaldez wrote: > >> Hi, I've found this bug consistently on debian testing (updated): > >> > >> Steps to reproduce: > >> In pcmanfm's address bar,

Re: How to diagnose and report a bug

On 2018-06-15, Curt wrote: > On 2018-06-15, rv riveravaldez wrote: >> Hi, I've found this bug consistently on debian testing (updated): >> >> Steps to reproduce: >> In pcmanfm's address bar, type: >> ssh://user@ip >> Write password, Enter. >> Navigate

Re: How to diagnose and report a bug

On 2018-06-15, rv riveravaldez wrote: > Hi, I've found this bug consistently on debian testing (updated): > > Steps to reproduce: > In pcmanfm's address bar, type: > ssh://user@ip > Write password, Enter. > Navigate to the remote machine user's folder. > Open, edit an

Re: How to diagnose and report a bug

Hi, > In pcmanfm's address bar, [...] > [...] > Any recomendations on how to diagnose and report this bug? Since there is a package with name "pcmanfm", there is also a tracker page for it https://tracker.debian.org/pkg/pcmanfm Registered maintainer contact is the mail

How to diagnose and report a bug

Hi, I've found this bug consistently on debian testing (updated): Steps to reproduce: In pcmanfm's address bar, type: ssh://user@ip Write password, Enter. Navigate to the remote machine user's folder. Open, edit and save a plain text file with leafpad. Result: The file gets blanked (no content

Serious bug: pcmanfm-ssh-leafpad [howto diagnose]

Hi, I've found this bug consistently on debian testing (updated): Steps to reproduce: >From the address bar of pcmanfm, type: ssh://user@ip Write password, Enter. Navigate to the remote machine user folder. Open, edit and save a plain text file with leafpad. The file gets blanked (no cont

Nvidia 340 driver bug

Le 03/06/2018 à 20:47, floris a écrit : > Pétùr schreef op 2018-06-02 17:46: >>> This is a bug in the nvidia driver module. There is not much you can do >>> until it is fixed upstream. >> >> Thanks! >> >> I would like to use the nouveau driver waiting f

Re: Nvidia 340 driver bug

dekkz...@gmail.com schreef op 2018-06-02 17:17: On 06/01, floris wrote: Pétùr schreef op 2018-05-31 16:20: I have a recurrent bug with the nvidia 340 driver. Here is the trace. Any idea is welcomed. Pétùr [6.748358] [ cut here ] snip f3 eb [6.749313

Re: Nvidia 340 driver bug

Pétùr schreef op 2018-06-02 17:46: This is a bug in the nvidia driver module. There is not much you can do until it is fixed upstream. Thanks! I would like to use the nouveau driver waiting for the fix. However I an unable to boot X with the nouveau driver. I did: # apt-get purge nvidia

Re: Nvidia 340 driver bug

Le 02/06/2018 à 17:46, Pétùr a écrit : > >> This is a bug in the nvidia driver module. There is not much you can do >> until it is fixed upstream. > > Thanks! > > I would like to use the nouveau driver waiting for the fix. > > However I an unable to boot

Re: Nvidia 340 driver bug

> This is a bug in the nvidia driver module. There is not much you can do > until it is fixed upstream. Thanks! I would like to use the nouveau driver waiting for the fix. However I an unable to boot X with the nouveau driver. I did: # apt-get purge nvidia. # apt-get install --rei

Re: Re: Nvidia 340 driver bug

On 06/01, floris wrote: Pétùr schreef op 2018-05-31 16:20: I have a recurrent bug with the nvidia 340 driver. Here is the trace. Any idea is welcomed. Pétùr [6.748358] [ cut here ] snip f3 eb [6.749313] ---[ end trace dc2afdad83c552e7 ]--- This is a bug

Re: Nvidia 340 driver bug

Pétùr schreef op 2018-05-31 16:20: I have a recurrent bug with the nvidia 340 driver. Here is the trace. Any idea is welcomed. Pétùr [6.748358] [ cut here ] [6.748361] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object

Nvidia 340 driver bug

I have a recurrent bug with the nvidia 340 driver. Here is the trace. Any idea is welcomed. Pétùr [6.748358] [ cut here ] [6.748361] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size

Re: appropriate package for bug report about qualcomm atheros attansic l1

On Wed, 30 May 2018, Υπάτιος Μ. Μωυσιάδης wrote: > i want to send through email a bug report, for a bug that i think my pc has. > My problem/bug, is that i have a network card qualcomm atheros attansic l1 > gigabit ethernet (revb0) [1969:1048], that can't connect to the internet,

appropriate package for bug report about qualcomm atheros attansic l1

Hello, i want to send through email a bug report, for a bug that i think my pc has. My problem/bug, is that i have a network card qualcomm atheros attansic l1 gigabit ethernet (revb0) [1969:1048], that can't connect to the internet, through ethernet which is the only option. From some

Re: Usability BUG - Which package appropriate?

On 05/29/2018 05:03 AM, Richard Owlett wrote: >>> *HOWEVER!* >>> The first line stated "Emacs 26.1 is out, download it here!" >>> Bu [https://packages.debian.org/stretch/emacs] refers to >>> "Package: emacs (46.1)". >> >> And goes onto say that it's a metapackage that depends on emacs24; so,

Re: Usability BUG - Which package appropriate?

On Mon 28 May 2018 at 15:03:09 (-0500), Richard Owlett wrote: > On 05/28/2018 02:14 PM, Dan Purgert wrote: > >Richard Owlett wrote: > >>In another thread I asked for text editor recommendations to address a > >>Later someone else suggested emacs. > >>My mental image of "emacs" was of something for

Re: Usability BUG - Which package appropriate?

On 05/28/2018 02:14 PM, Dan Purgert wrote: Richard Owlett wrote: In another thread I asked for text editor recommendations to address a Later someone else suggested emacs. My mental image of "emacs" was of something for a 'dumb terminal'. I went to Synaptic searching for 'emacs'. Got a hit for

Re: Usability BUG - Which package appropriate?

Richard Owlett wrote: > In another thread I asked for text editor recommendations to address a > Later someone else suggested emacs. > My mental image of "emacs" was of something for a 'dumb terminal'. > I went to Synaptic searching for 'emacs'. > Got a hit for a metapaqckage - *NO* associated

Usability BUG - Which package appropriate?

In another thread I asked for text editor recommendations to address a narrowly focused problem - making non-printing (one respondent called them "ink-free) characters obvious. I had specified a GUI editor. One person suggested geany. I checked Synaptic and found it was already installed.

Re: Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug

Hi Henrique, Thanks very much for detailing the steps involved in getting this patch into a stable Debian 9 release. It looks like I have to do a bunch of testing before I file a bug to get this change into a stable Debian 9 release or even a backport. Regards, Dinesh On Sun, May 6, 2018 at 7

Re: Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug

On Sat, 05 May 2018, Liam O'Toole wrote: > On 2018-05-05, Henrique de Moraes Holschuh wrote: > > On Fri, 04 May 2018, Dinesh Iyer wrote: > >> "You'll have to talk to whoever is providing you your older version of > >> GStreamer. They will have to backport the fix to that old

Re: Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug

On 2018-05-05, Henrique de Moraes Holschuh wrote: > On Fri, 04 May 2018, Dinesh Iyer wrote: >> "You'll have to talk to whoever is providing you your older version of >> GStreamer. They will have to backport the fix to that old version, but it >> should just cleanly apply to the

Re: Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug

utly, as applied to the Debian stable codebase: you'd get the current source packages for gstreamer in Debian stable, apply the required patches, and do a lot of testing to ensure it caused no regressions _and_ fixed the issue properly. Then you file a bug, severity important or above, with a full desc

Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug

Hi team, I develop applications that does multimedia I/O on Linux. I have noticed stalls on Debian 9 due to a bug in Gstreamer 1.10. The Gstreamer developers have acknowledged this as a bug and have fixed this for the 1.14 line of Gstreamer. As I use the Gstreamer that comes by default

Re: webalizer bug in debian jessie

BASSAGET Cédric wrote: > Can not install 2.23.08-3 because it needs libpng16-16 This refers to Buster https://packages.debian.org/testing/web/webalizer either look for backport or recompile source on jessie

webalizer bug in debian jessie

Hello, Referring to : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858602 I'm looking for the 2.23.08-2 version of webalizer, which is referred in this bug. Can't find it... Can not install 2.23.08-3 because it needs libpng16-16 which is not available in debian jessie repositories. Can

Re: Bug#896806: systemd-resolved violates The Debian Free Software Guidelines

On Mon, 30 Apr 2018 10:09:44 -0400 Roberto C. Sánchez sent: > On Mon, Apr 30, 2018 at 04:18:01PM +0300, Abdullah Ramazanoglu wrote: > > > > AFAIK it is still there untouched in git sources, as originally > > mentioned in the bug report > > https://bugs.debian.org/cgi-b

Re: Bug#896806: systemd-resolved violates The Debian Free Software Guidelines

..@tuxteam.de said: > > > > [...] > > > > > > It seems this issue is fixed upstream. Would you like to check that? > > > > > > > > Tone down. Apply Hanlon's razor generously [...] > > > > > This is not about systemd or some bug or something. This is abou

Re: Bug#896806: systemd-resolved violates The Debian Free Software Guidelines

On Monday 30 April 2018 10:09:44 Roberto C. Sánchez wrote: > On Mon, Apr 30, 2018 at 04:18:01PM +0300, Abdullah Ramazanoglu wrote: > > AFAIK it is still there untouched in git sources, as originally > > mentioned in the bug report > > https://bugs.debian.org/cgi-bin/bug

Re: Bug#896806: systemd-resolved violates The Debian Free Software Guidelines

On Mon, Apr 30, 2018 at 04:18:01PM +0300, Abdullah Ramazanoglu wrote: > > AFAIK it is still there untouched in git sources, as originally mentioned in > the bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896806 > > That aside, the question of whether it will

Re: Bug#896806: systemd-resolved violates The Debian Free Software Guidelines

Apply Hanlon's razor generously [...] > This is not about systemd or some bug or something. This is about attitude. Exactly my point :-) On a more practical note: care to double-check whether the issue is actually fixed upstream? Cheers - -- t -BEGIN PGP SIGNATURE- Version:

Re: Bug#896806: systemd-resolved violates The Debian Free Software Guidelines

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Apr 29, 2018 at 11:20:00PM +0300, Abdullah Ramazanoglu wrote: > On Sun, 29 Apr 2018 12:52:54 -0700 Don Armstrong said: > > > If there is a concern here, it's a privacy concern. Google's public > > statements regarding maintaining privacy and

Re: BUG: soft lockup CPU stuck

do estos errores >> y no puedo dar cual es la causa! >> >> Podrian orientarme como para reportar el bug a Debian, jamas hice un >> reporte de bug, pero ya esto me esta volviendo loco! >> >> Les dejo el call trace entero: >> >> Apr 23 13:10:01 proxy ker

Re: BUG: soft lockup CPU stuck

ale otro Debian 9.4, el cual estoy utilizando como > servidor de Bastion (entre LAN y DMZ) que funciona con Shorewall > 5.0.15.6 y Proxy con Squid 3.5.23, pero me esta tirando estos errores > y no puedo dar cual es la causa! > > Podrian orientarme como para reportar el bug a Debian,

Re: BUG: soft lockup CPU stuck

stale otro Debian 9.4, el cual estoy utilizando como > servidor de Bastion (entre LAN y DMZ) que funciona con Shorewall > 5.0.15.6 y Proxy con Squid 3.5.23, pero me esta tirando estos errores > y no puedo dar cual es la causa! > > Podrian orientarme como para reportar el bug a De

BUG: soft lockup CPU stuck

y DMZ) que funciona con Shorewall 5.0.15.6 y Proxy con Squid 3.5.23, pero me esta tirando estos errores y no puedo dar cual es la causa! Podrian orientarme como para reportar el bug a Debian, jamas hice un reporte de bug, pero ya esto me esta volviendo loco! Les dejo el call trace entero: Apr 23

Bug in pdf display probably due to synctex update

uffers from the same bug? Any temporary solution before the fix? Cheers, Pétùr

Re: Update for i965-va-driver-shaders - Bug -

+0100 If that's the case then we have a bug. Package details state "depends on 1965-driver" and "enhances i965-driver" Cheers, -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263

nmtui bug

I'd normally use reportbug to report this except nmtui is preventing that from happening. The version in use is on debian-mac-9.4.0 disk and I used that version since the system is too old for efi or uefi. I was able to edit my wifi connection and save the connection with all fields filled in

Re: Bug melden vanaf ander systeem

Op 24-03-18 om 22:58 schreef Jan Claeys: > On Sat, 2018-03-24 at 11:50 +0100, Paul van der Vlis wrote: >> Op 24-03-18 om 04:48 schreef Diederik de Haas: >>> On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote: >>>> Mijn bug gaat er over, dat de Debian insta

Bug with hack in bsdgames-2.17-26build1 - SIGSEGV when type 'i' after restoring a saved game - WITH A FIX!

Program hack core dumps when you restore a saved game and then enter 'i' to see Inventory.  The following patch to hack.o_init.c fixes the problem.  (Sorry if cut and paste changed tabs to spaces...)  I am running Ubuntu 17.10, but don't think platform matters. *** hack.o_init.c.old   

Re: Bug melden vanaf ander systeem

On Sat, 2018-03-24 at 11:50 +0100, Paul van der Vlis wrote: > Op 24-03-18 om 04:48 schreef Diederik de Haas: > > On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote: > > > Mijn bug gaat er over, dat de Debian installer de firmware voor > > > een wifi-stick u

Re: Bug melden vanaf ander systeem

Op 24-03-18 om 04:48 schreef Diederik de Haas: > On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote: >> Mijn bug gaat er over, dat de Debian installer de firmware voor een >> wifi-stick uit firmware-linux-free niet laadt. > > $ reportbug installation-report --print

Re: Bug melden vanaf ander systeem

On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote: > Mijn bug gaat er over, dat de Debian installer de firmware voor een > wifi-stick uit firmware-linux-free niet laadt. $ reportbug installation-report --print

Re: Bug melden vanaf ander systeem

Op 23-03-18 om 02:00 schreef Jan Claeys: > On Thu, 2018-03-22 at 16:25 +0100, Paul van der Vlis wrote: >> Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de >> gegevens van mijn systeem erbij vermelden. Echter, ik meld een >> probleem over een heel ander s

Re: Bug melden vanaf ander systeem

On Thu, 2018-03-22 at 16:25 +0100, Paul van der Vlis wrote: > Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de > gegevens van mijn systeem erbij vermelden. Echter, ik meld een > probleem over een heel ander systeem, deze gegevens zijn dus > waardeloos en scheppe

Re: Bug melden vanaf ander systeem

Op 22-03-18 om 16:50 schreef Geert Stappers: > Wat ik de meeste tijd doe, is een email aan sub...@bugs.debian.org > schrijven en op de eerste twee regels > > Package: > Version: > > Dan verder als gewone email vertellen over de bug. > Let wel: plain text

Re: Bug melden vanaf ander systeem

Op 22-03-18 om 16:34 schreef floris: > Paul van der Vlis schreef op 2018-03-22 16:25: >> Hoi, >> >> Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de >> gegevens van mijn systeem erbij vermelden. Echter, ik meld een probleem >> over een heel

Re: Bug melden vanaf ander systeem

On Thu, Mar 22, 2018 at 04:34:33PM +0100, floris wrote: > Paul van der Vlis schreef op 2018-03-22 16:25: > >Hoi, > > > >Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de > >gegevens van mijn systeem erbij vermelden. Echter, ik meld een probleem >

Re: Bug melden vanaf ander systeem

Paul van der Vlis schreef op 2018-03-22 16:25: Hoi, Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de gegevens van mijn systeem erbij vermelden. Echter, ik meld een probleem over een heel ander systeem, deze gegevens zijn dus waardeloos en scheppen verwarring. Eerder kon ik

Bug melden vanaf ander systeem

Hoi, Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de gegevens van mijn systeem erbij vermelden. Echter, ik meld een probleem over een heel ander systeem, deze gegevens zijn dus waardeloos en scheppen verwarring. Eerder kon ik de gegevens van mijn systeem verwijderen door het

Re: bug remmina

- Mail original - > De: "hamster" <hams...@suna.fdn.fr> > À: debian-user-french@lists.debian.org > Envoyé: Lundi 12 Mars 2018 17:48:32 > Objet: Re: bug remmina > > Le 12/03/2018 à 15:40, Bernard Schoenacker a écrit : > > > > > >

Re: bug remmina

Le 12/03/2018 à 15:40, Bernard Schoenacker a écrit : - Mail original - De: "hamster" <hams...@suna.fdn.fr> À: debian-user-french@lists.debian.org Envoyé: Lundi 12 Mars 2018 13:01:26 Objet: bug remmina Hello J'arrive pas a faire marcher remmina. Je commence par mont

bug remmina

Hello J'arrive pas a faire marcher remmina. Je commence par monter un tunnel ssh, ensuite je me connecte a localhost (donc au tunnel) avec le protocole VNC. La fenetre qui devrait me montrer le bureau distant s'ouvre, et se referme aussitot. Je suis sur que le souci ne viens pas de l'ordi

Re: Bug when installing texlive in debian 9.3 stretch.

t; dpkg seems to fail configuring a bunch of packages that are tex related. > > I tried to fix with >     $ sudo apt --fix-broken install > > But I got a similar output, which is bellow: This looks like a variant of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832570 If I was

Bug when installing texlive in debian 9.3 stretch.

in /tmp/fmtutil.mCfb4czR Please include this file if you report a bug. dpkg: error processing package tex-common (--configure):  subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of texlive-pictures-doc:  texlive-pictures-doc

Re: bug filing question: Gnome session crashes on resume from suspend or hibernate; Nvidia driver suspected

I submitted this bug to the nvidia-driver package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891960

bug filing question: Gnome session crashes on resume from suspend or hibernate; Nvidia driver suspected

Hello, I am trying to determine which package to file this bug under. My login session is frequently lost when the computer resumes from suspension or hibernation.  The computer takes me to the Gnome login screen.  About one in two resumptions fail this way. Debian 9.3 kernel 4.15.0-1

info ou bug ? lvm2 echoue sans udev

Bonjour, Je viens d'avoir une erreur sur la création d'un volume logique sous Stretch. La création du PV et du VG se passe bien. Lors du lvcreate : root@soy-2bk:~# lvcreate -L70G -nlv_var debian /dev/debian/lv_var: not found: device not cleared Aborting. Failed to wipe start of new LV.

Re: is this a bug of startx?

On Sun, Feb 18, 2018 at 03:20:11AM +, Long Wind wrote: > maybe few users still use startx? Depends on where you draw your samples from. If you consider "all Debian users", then you are probably correct. The vast majority of users probably use one of the Display Managers. If you consider

Re: is this a bug of startx?

On Sun 18 Feb 2018 at 03:20:11 (+), Long Wind wrote: > maybe few users still use startx?at first i found some strange problems with > stretchand unable to run X > now i'm able to describe the problemafter i install twm , i can't run > startxthen i create .xinitrc: > xterm & > twm > and it

Re: libgparted bug.

On Monday 12 February 2018 17:29:58 David Wright wrote: > On Mon 12 Feb 2018 at 15:32:50 (-0500), Gene Heskett wrote: > > On Monday 12 February 2018 13:44:04 Brian wrote: > > > On Mon 12 Feb 2018 at 08:17:23 +0100, deloptes wrote: > > > > Gene Heskett wrote: > > > > >> TDE has support channels.

Re: libgparted bug.

On Mon 12 Feb 2018 at 15:32:50 (-0500), Gene Heskett wrote: > On Monday 12 February 2018 13:44:04 Brian wrote: > > > On Mon 12 Feb 2018 at 08:17:23 +0100, deloptes wrote: > > > Gene Heskett wrote: > > > >> TDE has support channels. People there are far more likely to be > > > >> familiar with

Re: libgparted bug.

On Monday 12 February 2018 16:29:43 deloptes wrote: > Gene Heskett wrote: > > usbmount has been disabled.  That would I think, have fixed the > > original problem that started all this hoohaw. > > > > My apologies to the list in that case. > > With full respect, Gene, we are glad it worked for

Re: libgparted bug.

Gene Heskett wrote: > I, based on the previous post, scanned thru the trinity control center, > and found the automount unchecked, but mount as user is checked. That > seems like its handy, so I left it checked. Yes, indeed, I found it too automount is unchecked mount as user is checked +

Re: libgparted bug.

Gene Heskett wrote: > usbmount has been disabled.  That would I think, have fixed the original > problem that started all this hoohaw. > > My apologies to the list in that case. With full respect, Gene, we are glad it worked for you once again! regards

Re: libgparted bug.

On Monday 12 February 2018 15:16:47 Brian wrote: > On Mon 12 Feb 2018 at 14:14:56 -0500, Gene Heskett wrote: > > I have restored everything that I played with in the udev dept. And > > re-enabled usbmount in its config, exactly as installed originally. > > Mmm. > > > I have unmounted both visible

Re: libgparted bug.

On Monday 12 February 2018 14:00:42 deloptes wrote: > Brian wrote: > >> I don't know what you mean, but I read and post to both lists > >> (user/devel) > > > > January was a busy time on the list. > > I didn't have that impression if you mean TDE. It is a small community > (at least the posting

Re: libgparted bug.

On Monday 12 February 2018 13:44:04 Brian wrote: > On Mon 12 Feb 2018 at 08:17:23 +0100, deloptes wrote: > > Gene Heskett wrote: > > >> TDE has support channels. People there are far more likely to be > > >> familiar with wheezy (unsupported on Debian) and their own > > >> packages (not in

Re: libgparted bug.

On Mon 12 Feb 2018 at 14:14:56 -0500, Gene Heskett wrote: > I have restored everything that I played with in the udev dept. And > re-enabled usbmount in its config, exactly as installed originally. Mmm. > > I have unmounted both visible partitions of this sd card, and they have > not

Re: libgparted bug.

On Monday 12 February 2018 13:36:43 deloptes wrote: > Curt wrote: > > On 2018-02-11, Gene Heskett wrote: > >> On Sunday 11 February 2018 18:19:00 Brian wrote: > >>> On Sun 11 Feb 2018 at 17:07:03 -0500, Gene Heskett wrote: > >>> > On Sunday 11 February 2018 15:31:13 Brian

Re: libgparted bug.

On Mon 12 Feb 2018 at 20:00:42 +0100, deloptes wrote: > Brian wrote: > > >> I don't know what you mean, but I read and post to both lists > >> (user/devel) > > > > January was a busy time on the list. > > > I didn't have that impression if you mean TDE. It is a small community (at > least the

Re: libgparted bug.

On Monday 12 February 2018 02:17:23 deloptes wrote: > Gene Heskett wrote: > >> TDE has support channels. People there are far more likely to be > >> familiar with wheezy (unsupported on Debian) and their own packages > >> (not in Debian) and any automounting issues. > > there is no automount -

Re: libgparted bug.

Brian wrote: >> I don't know what you mean, but I read and post to both lists >> (user/devel) > > January was a busy time on the list. > I didn't have that impression if you mean TDE. It is a small community (at least the posting part of it). >> Unfortunately I upgraded long time ago from

Re: libgparted bug.

On Mon 12 Feb 2018 at 08:17:23 +0100, deloptes wrote: > Gene Heskett wrote: > > >> TDE has support channels. People there are far more likely to be > >> familiar with wheezy (unsupported on Debian) and their own packages > >> (not in Debian) and any automounting issues. > > > > there is no

Re: libgparted bug.

Curt wrote: > On 2018-02-11, Gene Heskett wrote: >> On Sunday 11 February 2018 18:19:00 Brian wrote: >> >>> On Sun 11 Feb 2018 at 17:07:03 -0500, Gene Heskett wrote: >>> > On Sunday 11 February 2018 15:31:13 Brian wrote: >>> > > linuxcnc is an Xfce based system and that DE

Re: libgparted bug.

On Sun 11 Feb 2018 at 17:07:03 (-0500), Gene Heskett wrote: > On Sunday 11 February 2018 15:31:13 Brian wrote: > > On Sun 11 Feb 2018 at 11:08:23 -0500, Gene Heskett wrote: > > > On Sunday 11 February 2018 10:19:16 David Wright wrote: > > > > […] Otherwise, look to your DE configuration. […] > >

Re: libgparted bug.

On 2018-02-11, Gene Heskett wrote: > On Sunday 11 February 2018 18:19:00 Brian wrote: > >> On Sun 11 Feb 2018 at 17:07:03 -0500, Gene Heskett wrote: >> > On Sunday 11 February 2018 15:31:13 Brian wrote: >> > > linuxcnc is an Xfce based system and that DE does the >> > >

Re: libgparted bug.

Gene Heskett wrote: >> TDE has support channels. People there are far more likely to be >> familiar with wheezy (unsupported on Debian) and their own packages >> (not in Debian) and any automounting issues. > there is no automount - Gene might remove usbmount package and see if this helps. The

Re: libgparted bug.

On Sunday 11 February 2018 18:19:00 Brian wrote: > On Sun 11 Feb 2018 at 17:07:03 -0500, Gene Heskett wrote: > > On Sunday 11 February 2018 15:31:13 Brian wrote: > > > linuxcnc is an Xfce based system and that DE does the > > > automounting. It is not usbmount or 60-persistent-storage.rules. > >

<    7   8   9   10   11   12   13   14   15   16   >