do not know how to report this bug
I recently made a 8.3 netinstall cd and went through the installation process (with encryption). After installation was done it rebooted and the password prompt came up. I tried entering my password several times, failing each time, even though I am sure I entered it correctly most of the time. I then re-inserted the 8.3 netinstall cd and using rescue mode, I was able to successfully enter the password and mount the drive in 'rescue mode'. I am new to Linux so i wasn't sure how to fix it from there. I then made a 7.9 netinstall cd and installed with encryption to test if my hardware was at fault. This time I was able to successfully enter my password and boot my encrypted OS. BTW my password consisted of upper case, lower case and numbers.
how to report a bug on reportbug
Dear everybody, I have some trouble reporting a bug on the current xserver in testing using reportbug or reportbug-ng, in fact because I encouter a problem with reportbug itself. Everything goes well until at the end reportbug wants to send an email somehow. Then I get Report will be sent to Debian Bug Tracking System sub...@bugs.debian.org Submit this report on xserver-xorg-video-nouveau (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? y Connecting to smtp via SMTP... SMTP send failure: [Errno -2] Name or service not known. Do you want to retry (or else save the report and exit)? [Y|n|q|?]? n My guess is that reportbug wants to contact a local sendmail or sendmail-replacement which I do not have installed. I have a direct connection to the internet, no firewall configured in my router, I can ping bugs.debian.org and connect to port 25 without problems using netcat or telnet. In an attempt to change the reportbug behavior, I have modified the configuration in /etc/reportbug # Use this to enable the internal MTA (bypassing /usr/sbin/sendmail) smtphost localhost # # You can also specify a port other than 25 # smtphost mail.example.com:2525 Just to be clear: I checked both with this line enabled and commented out, also the setting 'smtphost bugs.debian.org' will not work. 'reportbug' is the version that I get from the testing archive (6.4.3). Can anybody enlighten me? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ai1642fehn...@mid.individual.net
Re: how to report a bug on reportbug
On Du, 02 dec 12, 14:15:32, Stefan Schwarzer wrote: Just to be clear: I checked both with this line enabled and commented out, also the setting 'smtphost bugs.debian.org' will not work. 'reportbug' is the version that I get from the testing archive (6.4.3). It should be 'smtphost reportbug.debian.org'. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
On Mi, 07 mar 12, 13:30:12, Sylvain wrote: 2012/3/7 Camaleón noela...@gmail.com: Anyway, I would have expected some kind of warning at the logs coming from backuppc indicating a problem for accessing to the configured mount point which was not available at that time and thus failing. Me too, and I didn't understand why I wasn't getting anything in the logs until now: the default LogDir (/var/lib/backuppc/log/) is in a subdirectory of the TopDir (/var/lib/backuppc/), which means that if the TopDir doesn't exist, backuppc won't be able to log the error in LogDir. So in order to check the logs to find out what the problem is you first have to solve the problem. :-) [Note: I know nothing about backuppc] If having /var/lib/backuppc on media that may or may not be available during startup is common, then I guess this is a bug in backuppc (documentation, configuration, behaviour, etc.). On the other hand /var and subdirs are usually local[1], in which case you just shot yourself in the foot (which Linux and associated software traditionally does allow). [1] in this context I don't consider removable media that may or may not be connected to be local Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
On Wed, Mar 7, 2012 at 2:46 AM, Sylvain sylvainterside...@gmail.com wrote: 2012/3/6 Tom H tomh0...@gmail.com: AFAICT, a bug should be filed against backuppc to change its init script to have $remote_fs (or $all!) in Required-Start or autofs in Should-Start. autofs doesn't seem to be included in $remote_fs, and autofs doen't have anything to do with backuppc so I don't think it should be included in backuppc's init script. I'm surprised that autofs isn't in $remote_fs; maybe it's in $network but I have no idea how to check either and I'll take your word for it. You misunderstand the LSB headers and insserv. It doesn't matter whether aufofs and backuppc are related; insserv has to have whatever infomation's required to order the init scripts in rcX.d properly. For example, nfs-kernel-server has named or $named (I'm not sure) in Should-Start. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SyGMOs88u+Ci-aCXY1mRFPJA===pxhmh5ft3ybccmo...@mail.gmail.com
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
On Wed, 07 Mar 2012 08:46:23 +0100, Sylvain wrote: 2012/3/6 Camaleón noela...@gmail.com: Well, there are some packages that in addition to be installed have to be configured to be run on booting. I mean, the fact a service is not started by default cannot be considered a bug or error per se. Sure, but you usually have either configuration files to edit, or a note in the readme file stating that you'll need some additional steps to make the package work if you're using some special configuration. Yes, but this does not seem to be the case. What I wanted to note is that an installed package does not have to be enabled by default, it can need manual intervention. Also the resolution of the problem was not straightforward; in fact I was writing to the list to get a solution to my problem when the solution came to my mind. Problems and straightforward do not usually go in the same phrase, by their own nature :-) So backuppc daemon is starting but fails because it cannot access to the configured external USB hard disk? You can check the service status with service backuppc status. Yes, the /removable/sbackup/backuppc directory is empty since autofs has not started yet and thus has not created the directory yet. Okay, then the service is started but fails. Mmm, I would open a bug against the package it self (that is, backuppc) to get some feedback from the package maintainers about this situation. In principle (though I don't know BackupPC requirements in deep), it should not require autofs by default (nor smb, nfs...) because there can be people/installations not having that service even installed. Sure. Maybe the best solution is a note in the readme file for autofs users. I'll file a bugreport against backuppc. Sure, documenting that kind of things never hurts. Anyway, I would have expected some kind of warning at the logs coming from backuppc indicating a problem for accessing to the configured mount point which was not available at that time and thus failing. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jj7jul$ujn$5...@dough.gmane.org
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
2012/3/7 Camaleón noela...@gmail.com: Anyway, I would have expected some kind of warning at the logs coming from backuppc indicating a problem for accessing to the configured mount point which was not available at that time and thus failing. Me too, and I didn't understand why I wasn't getting anything in the logs until now: the default LogDir (/var/lib/backuppc/log/) is in a subdirectory of the TopDir (/var/lib/backuppc/), which means that if the TopDir doesn't exist, backuppc won't be able to log the error in LogDir. So in order to check the logs to find out what the problem is you first have to solve the problem. :-) Cheers, Sylvain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwBQFNYny=wdQUBKPCi_Mc4bN1-R=kkU_=T=oftvzlbdnv...@mail.gmail.com
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
On Wed, 07 Mar 2012 13:30:12 +0100, Sylvain wrote: 2012/3/7 Camaleón noela...@gmail.com: Anyway, I would have expected some kind of warning at the logs coming from backuppc indicating a problem for accessing to the configured mount point which was not available at that time and thus failing. Me too, and I didn't understand why I wasn't getting anything in the logs until now: the default LogDir (/var/lib/backuppc/log/) is in a subdirectory of the TopDir (/var/lib/backuppc/), which means that if the TopDir doesn't exist, backuppc won't be able to log the error in LogDir. So in order to check the logs to find out what the problem is you first have to solve the problem. :-) There is /var/log/syslog for that kind of purpose. Why is not used, I can't tell :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jj7kpu$ujn$7...@dough.gmane.org
How to report a bug related to multiple packages (insserv, autofs, backuppc)
Hey there, I installed backuppc the other day, configured it and it works fine except for one thing: it doesn't start at boot. I looked in the backuppc logs and in the syslog and saw nothing suspicious. If I start it manually with /etc/init.d/backuppc start, it works just fine. There are also startup scripts in /etc/rc*.d/. My backuppc version is 3.2.1-2 (I'm running a testing install). Note that my /var/lib/backuppc directory points to /removable/sbackup/backuppc which is my external USB HDD mounted by autofs, which is in /etc/rc*.d/S21autofs (backuppc is /etc/rc*.d/S21backuppc). After some investigation I found that adding autofs in the Required-Start section of the insserv overrides of the backuppc init script solved the problem. Now I'm not sure how to report the bug. Should I report it against autofs (so that autofs gets included into $local_fs or in the mountall.sh script but these scripts have nothing to do with autofs), or in insserv (again so that autofs gets included into $local_fs, but insserv doesn't have anything to do with autofs) or in backuppc so that the init script is modified (but again, backuppc has nothing to do with autofs)? Thanks for your advice, Sylvain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwBQFNR=CNtB43SE=-ggizrl8ehqeqgsfruawskjkqmjj8...@mail.gmail.com
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
On 06/03/12 11:35, Sylvain wrote: Hey there, I installed backuppc the other day, configured it and it works fine except for one thing: it doesn't start at boot. I looked in the backuppc logs and in the syslog and saw nothing suspicious. If I start it manually with /etc/init.d/backuppc start, it works just fine. There are also startup scripts in /etc/rc*.d/. My backuppc version is 3.2.1-2 (I'm running a testing install). Note that my /var/lib/backuppc directory points to /removable/sbackup/backuppc which is my external USB HDD mounted by autofs, which is in /etc/rc*.d/S21autofs (backuppc is /etc/rc*.d/S21backuppc). After some investigation I found that adding autofs in the Required-Start section of the insserv overrides of the backuppc init script solved the problem. Now I'm not sure how to report the bug. Should I report it against autofs (so that autofs gets included into $local_fs or in the mountall.sh script but these scripts have nothing to do with autofs), or in insserv (again so that autofs gets included into $local_fs, but insserv doesn't have anything to do with autofs) or in backuppc so that the init script is modified (but again, backuppc has nothing to do with autofs)? Thanks for your advice, Sylvain I think I would call that configuration, not a bug. How would backuppc know the drive is connected switched on, if you don't tell it. :) (Others may need it to run as a cron job; they may backup to tape, etc.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f55fe54.3010...@gmail.com
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
On Tue, Mar 6, 2012 at 6:35 AM, Sylvain sylvainterside...@gmail.com wrote: I installed backuppc the other day, configured it and it works fine except for one thing: it doesn't start at boot. I looked in the backuppc logs and in the syslog and saw nothing suspicious. If I start it manually with /etc/init.d/backuppc start, it works just fine. There are also startup scripts in /etc/rc*.d/. My backuppc version is 3.2.1-2 (I'm running a testing install). Note that my /var/lib/backuppc directory points to /removable/sbackup/backuppc which is my external USB HDD mounted by autofs, which is in /etc/rc*.d/S21autofs (backuppc is /etc/rc*.d/S21backuppc). After some investigation I found that adding autofs in the Required-Start section of the insserv overrides of the backuppc init script solved the problem. Now I'm not sure how to report the bug. Should I report it against autofs (so that autofs gets included into $local_fs or in the mountall.sh script but these scripts have nothing to do with autofs), or in insserv (again so that autofs gets included into $local_fs, but insserv doesn't have anything to do with autofs) or in backuppc so that the init script is modified (but again, backuppc has nothing to do with autofs)? autofs *usually* mounts remote filesystems so including it in $local_fs doesn't make sense. AFAICT, a bug should be filed against backuppc to change its init script to have $remote_fs (or $all!) in Required-Start or autofs in Should-Start. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=swmkbe6y38k3ceiofnxurtjehopkva03s7rd13mda7...@mail.gmail.com
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
On Tue, 06 Mar 2012 12:35:21 +0100, Sylvain wrote: I installed backuppc the other day, configured it and it works fine except for one thing: it doesn't start at boot. I looked in the backuppc logs and in the syslog and saw nothing suspicious. If I start it manually with /etc/init.d/backuppc start, it works just fine. There are also startup scripts in /etc/rc*.d/. My backuppc version is 3.2.1-2 (I'm running a testing install). Well, there are some packages that in addition to be installed have to be configured to be run on booting. I mean, the fact a service is not started by default cannot be considered a bug or error per se. Note that my /var/lib/backuppc directory points to /removable/sbackup/backuppc which is my external USB HDD mounted by autofs, which is in /etc/rc*.d/S21autofs (backuppc is /etc/rc*.d/S21backuppc). After some investigation I found that adding autofs in the Required-Start section of the insserv overrides of the backuppc init script solved the problem. So backuppc daemon is starting but fails because it cannot access to the configured external USB hard disk? You can check the service status with service backuppc status. Now I'm not sure how to report the bug. Should I report it against autofs (so that autofs gets included into $local_fs or in the mountall.sh script but these scripts have nothing to do with autofs), or in insserv (again so that autofs gets included into $local_fs, but insserv doesn't have anything to do with autofs) or in backuppc so that the init script is modified (but again, backuppc has nothing to do with autofs)? Mmm, I would open a bug against the package it self (that is, backuppc) to get some feedback from the package maintainers about this situation. In principle (though I don't know BackupPC requirements in deep), it should not require autofs by default (nor smb, nfs...) because there can be people/installations not having that service even installed. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jj5kvp$ds9$2...@dough.gmane.org
Re: How to report a bug related to multiple packages (insserv, autofs, backuppc)
2012/3/6 Tom H tomh0...@gmail.com: AFAICT, a bug should be filed against backuppc to change its init script to have $remote_fs (or $all!) in Required-Start or autofs in Should-Start. autofs doesn't seem to be included in $remote_fs, and autofs doen't have anything to do with backuppc so I don't think it should be included in backuppc's init script. 2012/3/6 Camaleón noela...@gmail.com: On Tue, 06 Mar 2012 12:35:21 +0100, Sylvain wrote: I installed backuppc the other day, configured it and it works fine except for one thing: it doesn't start at boot. I looked in the backuppc logs and in the syslog and saw nothing suspicious. If I start it manually with /etc/init.d/backuppc start, it works just fine. There are also startup scripts in /etc/rc*.d/. My backuppc version is 3.2.1-2 (I'm running a testing install). Well, there are some packages that in addition to be installed have to be configured to be run on booting. I mean, the fact a service is not started by default cannot be considered a bug or error per se. Sure, but you usually have either configuration files to edit, or a note in the readme file stating that you'll need some additional steps to make the package work if you're using some special configuration. Also the resolution of the problem was not straightforward; in fact I was writing to the list to get a solution to my problem when the solution came to my mind. Note that my /var/lib/backuppc directory points to /removable/sbackup/backuppc which is my external USB HDD mounted by autofs, which is in /etc/rc*.d/S21autofs (backuppc is /etc/rc*.d/S21backuppc). After some investigation I found that adding autofs in the Required-Start section of the insserv overrides of the backuppc init script solved the problem. So backuppc daemon is starting but fails because it cannot access to the configured external USB hard disk? You can check the service status with service backuppc status. Yes, the /removable/sbackup/backuppc directory is empty since autofs has not started yet and thus has not created the directory yet. Now I'm not sure how to report the bug. Should I report it against autofs (so that autofs gets included into $local_fs or in the mountall.sh script but these scripts have nothing to do with autofs), or in insserv (again so that autofs gets included into $local_fs, but insserv doesn't have anything to do with autofs) or in backuppc so that the init script is modified (but again, backuppc has nothing to do with autofs)? Mmm, I would open a bug against the package it self (that is, backuppc) to get some feedback from the package maintainers about this situation. In principle (though I don't know BackupPC requirements in deep), it should not require autofs by default (nor smb, nfs...) because there can be people/installations not having that service even installed. Sure. Maybe the best solution is a note in the readme file for autofs users. I'll file a bugreport against backuppc. Thanks for the hints, Sylvain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwBQFN6GNUmyPDE=mDrYpP4Sd0f3=z3ocm4lf6yqgpb00s...@mail.gmail.com
RE: How to report a bug in Debian using reportbug
If I'm not missing anything, the reportbug package doesn't seem to be found when you install the minimal system: root@debian:~# aptitude install reportbug No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. root@debian:~# uname -a Linux debian 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux root@debian:~# cat /etc/debian_version 6.0.1 root@debian:~# cat /etc/apt/sources.list # # deb cdrom:[Debian GNU/Linux 6.0.1a _Squeeze_ - Official i386 NETINST Binary-1 20110320-15:03]/ squeeze main #deb cdrom:[Debian GNU/Linux 6.0.1a _Squeeze_ - Official i386 NETINST Binary-1 20110320-15:03]/ squeeze main deb http://ftp.ro.debian.org/debian/ squeeze main deb-src http://ftp.ro.debian.org/debian/ squeeze main deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main # squeeze-updates, previously known as 'volatile' deb http://ftp.ro.debian.org/debian/ squeeze-updates main deb-src http://ftp.ro.debian.org/debian/ squeeze-updates main root@debian:~# -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktinfwapnzs3wgkt-kcbtt940_7e...@mail.gmail.com
Re: How to report a bug in Debian using reportbug
On 2011-05-28 15:06 +0200, Vlad GURDIGA wrote: If I'm not missing anything, the reportbug package doesn't seem to be found when you install the minimal system: Not in a minimal system, but in a standard system (the one you get when you don't select anything else during installation). root@debian:~# aptitude install reportbug No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. AFAICS this means that reportbug is already installed in the latest version, otherwise aptitude would install it (or tell you that it cannot be found). root@debian:~# cat /etc/apt/sources.list # # deb cdrom:[Debian GNU/Linux 6.0.1a _Squeeze_ - Official i386 NETINST Binary-1 20110320-15:03]/ squeeze main #deb cdrom:[Debian GNU/Linux 6.0.1a _Squeeze_ - Official i386 NETINST Binary-1 20110320-15:03]/ squeeze main deb http://ftp.ro.debian.org/debian/ squeeze main deb-src http://ftp.ro.debian.org/debian/ squeeze main deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main # squeeze-updates, previously known as 'volatile' deb http://ftp.ro.debian.org/debian/ squeeze-updates main deb-src http://ftp.ro.debian.org/debian/ squeeze-updates main Looks good. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874o4fj665@turtle.gmx.de
Re: How to report a bug in Debian using reportbug
On 05/28/11 at 04:06pm, Vlad GURDIGA wrote: If I'm not missing anything, the reportbug package doesn't seem to be found when you install the minimal system: root@debian:~# aptitude install reportbug No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. try dpkg -l reportbug, looks like it's already installed. -- Liam signature.asc Description: Digital signature
Re: How to report a bug in Debian using reportbug
On Sat, May 28, 2011 at 03:39:14PM +0200, Sven Joachim wrote: On 2011-05-28 15:06 +0200, Vlad GURDIGA wrote: If I'm not missing anything, the reportbug package doesn't seem to be found when you install the minimal system: Not in a minimal system, but in a standard system (the one you get when you don't select anything else during installation). root@debian:~# aptitude install reportbug No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. AFAICS this means that reportbug is already installed in the latest version, otherwise aptitude would install it (or tell you that it cannot be found). snip... Looks like he needs to run dpkg -l reportbug. -- Bob Holtzman Key ID: 8D549279 If you think you're getting free lunch, check the price of the beer signature.asc Description: Digital signature
How to report an bug in updating grub-pc to 1.98+20100804-10?
I ran update manager and it hanged on setting up grub-pc (1.98+20100804-10)
Relevant pstree output:
├─update-manager,25821 /usr/bin/update-manager
│ └─gksu,25825 -k -D /usr/share/applications/update-manager.desktop
--...
│ └─su,25830 root -p -c ...
│ └─gksu-run-helper,25839 /usr/bin/update-manager
│ └─sh,25843 -c /usr/bin/update-manager
│ └─update-manager,25844 /usr/bin/update-manager
│ ├─update-manager,25863 /usr/bin/update-manager
│ │ └─dpkg,26727 --status-fd 34 --configure ...
│ │ └─frontend,26773 -w ...
│ │ └─grub-pc.postins,26789 ...
│ │ └─grub-pc.postins,26865 ...
│ │ ├─grep,26867 -v ^(fd[0-9]\\+)
│ │ └─grub-mkdevicema,26866 -m -
│ ├─{update-manager},25860
│ └─{update-manager},25864
System: 64bit Debian testing, multiple kernels and windows 7 installed.
--
Life is too serious to be taken seriously
Elämä on liian vakavaa otettavaksi vakavasti
Re: How to report an bug in updating grub-pc to 1.98+20100804-10?
On Sun, 12 Dec 2010 11:36:09 +0200, Tuomo Kalliokoski wrote: I ran update manager and it hanged on setting up grub-pc (1.98+20100804-10) (...) You can review /var/log/apt/term.log or /var/log/dpkg.log to gather additional information. Does it happen when using apt-get update or aptitude? If the error is reproducible, you can fill a report for update-manager package. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.12.14.52...@gmail.com
Re: How to report an bug in updating grub-pc to 1.98+20100804-10?
On Sun, Dec 12, 2010 at 4:52 PM, Camaleón noela...@gmail.com wrote: On Sun, 12 Dec 2010 11:36:09 +0200, Tuomo Kalliokoski wrote: I ran update manager and it hanged on setting up grub-pc (1.98+20100804-10) (...) You can review /var/log/apt/term.log or /var/log/dpkg.log to gather additional information. Does it happen when using apt-get update or aptitude? If the error is reproducible, you can fill a report for update-manager package. Greetings, I would say that the bug is in grub-pc, not in update-manager nor in apt... I killed the processes started by the update-manager and here are relevant parts from the logs. term.log: Setting up grub-common (1.98+20100804-10) ... Setting up grub-pc (1.98+20100804-10) ... dpkg: error processing grub-pc (--configure): subprocess installed post-installation script killed by signal (Killed) Errors were encountered while processing: grub-pc Log ended: 2010-12-12 15:55:20 dpkg.log: 2010-12-12 10:35:31 status unpacked gir1.0-soup-2.4 0.6.5-7 2010-12-12 10:35:31 status half-configured gir1.0-soup-2.4 0.6.5-7 2010-12-12 10:35:31 status installed gir1.0-soup-2.4 0.6.5-7 2010-12-12 10:35:31 configure grub-common 1.98+20100804-10 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-common 1.98+20100804-10 2010-12-12 10:35:31 status half-configured grub-common 1.98+20100804-10 2010-12-12 10:35:31 status installed grub-common 1.98+20100804-10 2010-12-12 10:35:31 configure grub-pc 1.98+20100804-10 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-pc 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-pc 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-pc 1.98+20100804-10 2010-12-12 10:35:31 status unpacked grub-pc 1.98+20100804-10 2010-12-12 10:35:31 status half-configured grub-pc 1.98+20100804-10 Running apt-get upgrade it hangs just like update-manager /# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up grub-pc (1.98+20100804-10) ... And it hangs here, pstree output: │ │ │ └─bash,28261 │ │ │ └─apt-get,28773 upgrade │ │ │ └─dpkg,28777 --status-fd 18 --configure grub-pc │ │ │ └─frontend,28778 -w /usr/share/debconf/frontend /var/lib/dpkg/info/grub-pc.postinst configure ... │ │ │ └─grub-pc.postins,28790 /var/lib/dpkg/info/grub-pc.postinst configure 1.98+20100804-8 │ │ │ └─grub-pc.postins,28866 /var/lib/dpkg/info/grub-pc.postinst configure 1.98+20100804-8 │ │ │ ├─grep,28868 -v ^(fd[0-9]\\+) │ │ │ └─grub-mkdevicema,28867 -m - -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.12.14.52...@gmail.com -- Life is too serious to be taken seriously Elämä on liian vakavaa otettavaksi vakavasti
Re: How to report an bug in updating grub-pc to 1.98+20100804-10?
On Sun, 12 Dec 2010 17:04:04 +0200, Tuomo Kalliokoski wrote: On Sun, Dec 12, 2010 at 4:52 PM, Camaleón wrote: On Sun, 12 Dec 2010 11:36:09 +0200, Tuomo Kalliokoski wrote: I ran update manager and it hanged on setting up grub-pc (1.98+20100804-10) (...) You can review /var/log/apt/term.log or /var/log/dpkg.log to gather additional information. Does it happen when using apt-get update or aptitude? If the error is reproducible, you can fill a report for update-manager package. I would say that the bug is in grub-pc, not in update-manager nor in apt... I killed the processes started by the update-manager and here are relevant parts from the logs. term.log: Setting up grub-common (1.98+20100804-10) ... Setting up grub-pc (1.98+20100804-10) ... dpkg: error processing grub-pc (--configure): subprocess installed post-installation script killed by signal (Killed) Errors were encountered while processing: grub-pc Log ended: 2010-12-12 15:55:20 The origin of the failure is not very clear but there are some bug reports with similar a error: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584499 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558422 Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.12.15.49...@gmail.com
Re: How to report an bug in updating grub-pc to 1.98+20100804-10?
On Sun, 12 Dec 2010 17:04:04 +0200 Tuomo Kalliokoski tuok...@gmail.com wrote: Hello Tuomo, I would say that the bug is in grub-pc, not in update-manager nor in apt... FWIW, everything upgraded without issue on my AMD64 (Testing) box. -- Regards _ / ) The blindingly obvious is / _)radnever immediately apparent It's not your heart, it's your bank I want to break It's Yer Money - Wonder Stuff signature.asc Description: PGP signature
Re: How to report a Bug (Which Package?)
On Wed, 19 Jun 2002, Steve Juranich wrote: As suggested in http://www.debian.org/Bugs/Reporting ; I am sending this to debian-user. This is a good place to hang out for Debian users of all levels. I encourage you to stick around. Apology, that I do not subscribe debian-user. But, I do have web access to that list. My intention was to report a problem as suggested in http://www.debian.org/Bugs/Reporting and then I run tasksel. I selected X11; and then choose kdm out of xdm, gdm, and kdm. Apparently, it installs everything, unfortunately it does not like to install gdm (dpkg error code 1). Fortunetely, everything works fine after rerunning the installation process. As a matter of fact, this is the first time ever, I have managed automatically to install the X11 server (I used to configure it manually). Erm, do you mean 'kdm' in the second paragraph, otherwise I'm confused. No, I guess that the X Window System option in tasksel installs everything: xdm, gdm, kdm. But, apparently gdm does not like to be installed together with kdm? It happen more than once that the KDE installing process crashes (at another time and another system). Question: - whoose bug is that? - how to report it? After browsing the current bug list queue, I believe that not repporting this trivial bug is a better option. Thank you anyway. -- Abdul Latip -- Angkasa Internet Junior Staff -- ANGIN.com http://people.WebIndonesia.com/dullatip/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to report a Bug (Which Package?)
As suggested in http://www.debian.org/Bugs/Reporting ; I am sending this to debian-user. This is a good place to hang out for Debian users of all levels. I encourage you to stick around. I have just installed woody from scratch (due to trying ext3fs); and then I run tasksel. I selected X11; and then choose kdm out of xdm, gdm, and kdm. Apparently, it installs everything, unfortunately it does not like to install gdm (dpkg error code 1). Fortunetely, everything works fine after rerunning the installation process. As a matter of fact, this is the first time ever, I have managed automatically to install the X11 server (I used to configure it manually). Erm, do you mean 'kdm' in the second paragraph, otherwise I'm confused. Unfortunately, just getting the exit code is not really enough to diagnose the problem. Apt is normally pretty good about spitting out useful error messages when it dies. What error messages do you see? Question: - whoose bug is that? Well, again, without having more useful error messages, it's difficult to tell. Maybe you tried running apt-get as a normal user, maybe the package is broken, maybe there was just too much bad mojo in the room when you tried the install. - how to report it? The best way I've found to report bugs is to first of all do 'apt-get install reportbug'. Then when you think you've found a bug in (for instance) kdm, you would type 'reportbug kdm'. You'll want to read the man page for reportbug as there are a couple of environment variables you'll want to set. But it is a very nice way to file new bugs. HTH -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washingtonhttp://ssli.ee.washington.edu/ssli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to report a Bug (Which Package?)
Please be careful about your attribution lines. I did not write any of what you attributed to me. All of that was written by Abdul Latip [EMAIL PROTECTED]. Bob On Wednesday 19 June 2002 03:22, Bob Proulx wrote: I have just installed woody from scratch (due to trying ext3fs); and then I run tasksel. I selected X11; and then choose kdm out of xdm, gdm, and kdm. Apparently, it installs everything, unfortunately it does not pgpvKXa6YBwHz.pgp Description: PGP signature
How to report a Bug (Which Package?)
As suggested in http://www.debian.org/Bugs/Reporting ; I am sending this to debian-user. I have just installed woody from scratch (due to trying ext3fs); and then I run tasksel. I selected X11; and then choose kdm out of xdm, gdm, and kdm. Apparently, it installs everything, unfortunately it does not like to install gdm (dpkg error code 1). Fortunetely, everything works fine after rerunning the installation process. As a matter of fact, this is the first time ever, I have managed automatically to install the X11 server (I used to configure it manually). Question: - whoose bug is that? - how to report it? Thank you, -- Abdul Latip -- Junior Staff -- Angkasa Internet -- http://angin.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to report a Bug (Which Package?)
I have just installed woody from scratch (due to trying ext3fs); and then I run tasksel. I selected X11; and then choose kdm out of xdm, gdm, and kdm. Apparently, it installs everything, unfortunately it does not A suggestion. It is possible to run 'tasksel -t' and select what you want, then finish. The -t is test mode and won't actually run anything. But it will print the apt-get line that it would have installed without the -t option. I find that useful. Use that output as a starting point hint and run apt-get yourself manually. Avoid installing what you don't want. In this way I can install 'automake1.5' instead of the older 'automake' and so forth. For my own personal situation I plan to create my own metapackage that will pull these things in to make this simpler for me. Right now I just install a long list of 'good stuff'. But I am installing Debian almost regularly on different machines these days and a meta package customized for my installation so as to avoid tasksel would be useful. Sorry I can't help with the rest of your question. But hopefully this is useful by itself. Bob pgplWRjubSLgB.pgp Description: PGP signature
RE: How to report a Bug (Which Package?)
On 19-Jun-2002 Abdul Latip wrote: As suggested in http://www.debian.org/Bugs/Reporting ; I am sending this to debian-user. I have just installed woody from scratch (due to trying ext3fs); and then I run tasksel. I selected X11; and then choose kdm out of xdm, gdm, and kdm. Apparently, it installs everything, unfortunately it does not like to install gdm (dpkg error code 1). Fortunetely, everything works fine after rerunning the installation process. As a matter of fact, this is the first time ever, I have managed automatically to install the X11 server (I used to configure it manually). Question: - whoose bug is that? - how to report it? if you have your machine setup to send mail via the mailer daemon (exim by default) the handy package reportbug will help you. As to whose bug is it, that is harder to say based on your report. Try starting with gdm. Be sure to give as much of the error message and surrounding info as you can remember. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to report a Bug (Which Package?)
On Wednesday 19 June 2002 03:22, Bob Proulx wrote: I have just installed woody from scratch (due to trying ext3fs); and then I run tasksel. I selected X11; and then choose kdm out of xdm, gdm, and kdm. Apparently, it installs everything, unfortunately it does not My suggestion would be to install nothing with tasksel and dselect and then apt-get everything. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: HOW-TO report a bug?
zhaoway wrote: Hi, I cannot report a bug using neither reportbug nor bug. The problem is that even I have set the EMAIL environment or using the --email opt to set my from: line, the bug message sent were still using my local not-FQDN hostname hence got to be rejected by Debian's SMTP server. (only that reportbug sent a bcc: to the mail addr suggested in --email.) My message got rejected saying by Debian SMTP server that he cannot route to me after the MAIL FROM: [EMAIL PROTECTED] . Perhaps you can configure your MTA to rewrite the header so that the out-going From: [EMAIL PROTECTED] to From: [EMAIL PROTECTED] ? What MTA are you using? I've successfully done this kind of thing with exim. I took out the CC: to debian-simplified-chinese, since I thought this was off-topic for that forum. -- [EMAIL PROTECTED] 972-729-5387 [EMAIL PROTECTED] (home phone on request) http://www.koyote.com/users/bolan RE: xmailtool http://www.koyote.com/users/bolan/xmailtool/index.html I am the ILOVEGNU signature virus. Just copy me to your signature. This email was infected under the terms of the GNU General Public License.
HOW-TO report a bug?
Hi, I cannot report a bug using neither reportbug nor bug. The problem is that even I have set the EMAIL environment or using the --email opt to set my from: line, the bug message sent were still using my local not-FQDN hostname hence got to be rejected by Debian's SMTP server. (only that reportbug sent a bcc: to the mail addr suggested in --email.) My message got rejected saying by Debian SMTP server that he cannot route to me after the MAIL FROM: [EMAIL PROTECTED] . Please help! Thanks! Please Cc: me!
