Re: Question about what package to report bug

[Erwan David]

Le 06/03/2024 à 18:19, ke6jti a écrit :

Hi,

I have a possible kernel regression for a usb-dvb tuner card.  I know 
the error in dmesg points to kernel : au0828 but I am not sure what 
package this belongs to.  I think it belongs to v4l(video for linux) 
but I am still not sure what specific v4l package.



Thanks for you help.


apt-file shows au0828.ko comes in the linux-image-* packages. So report 
the bug for the one you use.

Question about what package to report bug

[ke6jti]

Hi,

I have a possible kernel regression for a usb-dvb tuner card.  I know 
the error in dmesg points to kernel : au0828 but I am not sure what 
package this belongs to.  I think it belongs to v4l(video for linux) but 
I am still not sure what specific v4l package.



Thanks for you help.

Re: Report Bug

[Marco M.]

Am 26.10.2023 um 19:29:13 Uhr schrieb Kevin Freeman:

> I have a bug here that needs to be reported.

Please use the "reportbug" software for that, so it is in the bug
tracker and maintainers can find it.

> It has been present in multiple versions and still exists in Debian
> 12. The issue is related to the desktop version's Wi-Fi icon and
> driver. While I can use Wi-Fi to connect to the internet, I would
> like to have a more intuitive icon and a toggle button, similar to
> what Ubuntu offers. I hope the community experts can provide support
> or a viable solution as soon as possible.

Do you use the NetworkManager?

Report Bug

[Kevin Freeman]

Dear friend,

Hello, I have a bug here that needs to be reported. It has been present in
multiple versions and still exists in Debian 12. The issue is related to
the desktop version's Wi-Fi icon and driver. While I can use Wi-Fi to
connect to the internet, I would like to have a more intuitive icon and a
toggle button, similar to what Ubuntu offers. I hope the community experts
can provide support or a viable solution as soon as possible.

Wishing you a wonderful day.

Kevin

Bookworm lockup: Report bug?

[Christian Gelinek]

Dear group,

This morning I encountered my PC being frozen. Here are the last 
journalctl messages, just before I forced it to power down and reboot:


Apr 10 07:31:07 gar systemd[1]: Started anacron.service - Run anacron jobs.
Apr 10 07:31:07 gar anacron[4875]: Anacron 2.3 started on 2023-04-10
Apr 10 07:31:07 gar anacron[4875]: Will run job `cron.daily' in 5 min.
Apr 10 07:31:07 gar anacron[4875]: Jobs will be executed sequentially
Apr 10 07:36:07 gar anacron[4875]: Job `cron.daily' started
Apr 10 07:36:07 gar anacron[4882]: Updated timestamp for job 
`cron.daily' to 2023-04-10

Apr 10 07:36:07 gar anacron[4875]: Job `cron.daily' terminated
Apr 10 07:36:07 gar anacron[4875]: Normal exit (1 job run)
Apr 10 07:36:07 gar systemd[1]: anacron.service: Deactivated successfully.
Apr 10 07:50:01 gar kernel: snd_hda_intel :04:00.0: Unable to change 
power state from D3hot to D0, device inaccessible
Apr 10 07:50:03 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
Apr 10 07:50:03 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
Apr 10 07:50:07 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
Apr 10 07:50:07 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
Apr 10 07:50:11 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
Apr 10 07:50:11 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
Apr 10 07:50:15 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* gt: timed out waiting for forcewake ack to clear.
Apr 10 07:50:15 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
Apr 10 07:50:16 gar kernel: i915 :03:00.0: [drm] *ERROR* CT: 
Corrupted descriptor head=4294967295 tail=4294967295 status=0x
Apr 10 07:50:28 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
Apr 10 07:50:28 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
Apr 10 07:50:28 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* gt: timed out waiting for forcewake ack to clear.
Apr 10 07:50:28 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
Apr 10 07:50:28 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* vdbox0: timed out waiting for forcewake ack to clear.
Apr 10 07:50:28 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
Apr 10 07:50:28 gar kernel: watchdog: BUG: soft lockup - CPU#15 stuck 
for 26s! [kworker/15:2:1033]
Apr 10 07:50:28 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer 
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 
dns_resolver nfs lockd grace fscache netfs rfkill qrtr sunrpc 
binfmt_misc nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi snd_s>
Apr 10 07:50:28 gar kernel:  intel_uncore ee1004 pcspkr snd watchdog 
soundcore intel_vsec serial_multi_instantiate intel_pmc_core acpi_pad 
acpi_tad mei_me mei sg evdev parport_pc ppdev lp parport fuse loop 
efi_pstore configfs efivarfs ip_tables x_tables autofs4 ext4 crc1>
Apr 10 07:50:28 gar kernel: CPU: 15 PID: 1033 Comm: kworker/15:2 
Tainted: G U  W  6.1.0-7-amd64 #1  Debian 6.1.20-1
Apr 10 07:50:28 gar kernel: Hardware name: Micro-Star International Co., 
Ltd. MS-7E02/PRO B760M-P DDR4 (MS-7E02), BIOS 1.00 10/21/2022

Apr 10 07:50:28 gar kernel: Workqueue: pm pm_runtime_work
Apr 10 07:50:28 gar kernel: RIP: 0010:pci_mmcfg_read+0xb0/0xe0
Apr 10 07:50:28 gar kernel: Code: 5d 41 5e 41 5f c3 cc cc cc cc 4c 01 e0 
66 8b 00 0f b7 c0 89 45 00 eb dc 4c 01 e0 8a 00 0f b6 c0 89 45 00 eb cf 
4c 01 e0 8b 00 <89> 45 00 eb c5 e8 b6 ae 78 ff c7 45 00 ff ff ff ff b8 
ea ff ff ff

Apr 10 07:50:28 gar kernel: RSP: :b859c1963cc0 EFLAGS: 0286
Apr 10 07:50:28 gar kernel: RAX:  RBX: 0040 
RCX: 0ffc
Apr 10 07:50:28 gar kernel: RDX: 00ff RSI: 0004 
RDI: 
Apr 10 07:50:28 gar kernel: RBP: b859c1963cfc R08: 0004 
R09: b859c1963cfc
Apr 10 07:50:28 gar kernel: R10: 0004 R11: b6ba5d50 
R12: 0ffc
Apr 10 07:50:28 gar kernel: R13:  R14: 0004 
R15: 
Apr 10 07:50:28 gar kernel: FS:  () 
GS:8a3d1fbc() knlGS:
Apr 10 07:50:28 gar kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Apr 10 07:50:28 ga

Re: Package name to report bug with KDE file open dialog

[Patrick Dunford]

Ok

I will take this matter up with the application developers

thanks for your assistance to date.


On 29/01/22 06:10, Bijan Soleymani wrote:

On 2022-01-28 11:36, Patrick Dunford wrote:
It is not relevant whether the issue occurs in other applications 
because they all use the file open dialogs in ways that are specific 
to their application which the end user has no control over and 
therefore it cannot be tested for


If it doesn't occur in other applications we don't know if it is an 
app issue or a file chooser issue.


The application has been tested on various operating systems and this 
problem only occurs on the version of kde which is installed by the 
debian bookworm package manager.


Still could be an app issue.

Therefore just give me the name of the specific kde package that 
relates to that dialog, as I previously requested.


I believe a KDE app would use dolphin or possibly qt file chooser.

Bijan

Re: Package name to report bug with KDE file open dialog

[Bijan Soleymani]

On 2022-01-28 11:36, Patrick Dunford wrote:
It is not relevant whether the issue occurs in other applications 
because they all use the file open dialogs in ways that are specific to 
their application which the end user has no control over and therefore 
it cannot be tested for


If it doesn't occur in other applications we don't know if it is an app 
issue or a file chooser issue.


The application has been tested on various operating systems and this 
problem only occurs on the version of kde which is installed by the 
debian bookworm package manager.


Still could be an app issue.

Therefore just give me the name of the specific kde package that relates 
to that dialog, as I previously requested.


I believe a KDE app would use dolphin or possibly qt file chooser.

Bijan

Re: Package name to report bug with KDE file open dialog

[David Wright]

On Sat 29 Jan 2022 at 05:36:25 (+1300), Patrick Dunford wrote:
> On 29/01/22 05:16, Bijan Soleymani wrote:
> > On 2022-01-28 11:10, Patrick Dunford wrote:
> > > Which is the name of the package relating to the file open
> > > dialog to use in a bug report?
> > 
> > I think it depends on the application :)
> > 
> > Do you see it in other applications?
> > 
> > If so, you can figure out what GUI toolkit/environment it is gtk,
> > qt, gnome, kde.
> > 
> > Otherwise probably file a bug on the app.
> 
> It is not relevant whether the issue occurs in other applications
> because they all use the file open dialogs in ways that are specific
> to their application which the end user has no control over and
> therefore it cannot be tested for
> 
> The application has been tested on various operating systems and this
> problem only occurs on the version of kde which is installed by the
> debian bookworm package manager.
> 
> Therefore just give me the name of the specific kde package that
> relates to that dialog, as I previously requested.

Steady on — people here will answer the question in any way they feel
fit. Demanding an answer like that is just rude.

I think the idea of filing a bug on the app is that the maintainer
will have a pretty good idea of where the problem is likely to lie,
and will reassign the bug.

Cheers,
David.

Re: Package name to report bug with KDE file open dialog

[Patrick Dunford]

Hi

It is not relevant whether the issue occurs in other applications 
because they all use the file open dialogs in ways that are specific to 
their application which the end user has no control over and therefore 
it cannot be tested for


The application has been tested on various operating systems and this 
problem only occurs on the version of kde which is installed by the 
debian bookworm package manager.


Therefore just give me the name of the specific kde package that relates 
to that dialog, as I previously requested.


On 29/01/22 05:16, Bijan Soleymani wrote:

On 2022-01-28 11:10, Patrick Dunford wrote:
Which is the name of the package relating to the file open dialog to 
use in a bug report?


I think it depends on the application :)

Do you see it in other applications?

If so, you can figure out what GUI toolkit/environment it is gtk, qt, 
gnome, kde.


Otherwise probably file a bug on the app.

Bijan

Re: Package name to report bug with KDE file open dialog

[Bijan Soleymani]

On 2022-01-28 11:10, Patrick Dunford wrote:
Which is the name of the package relating to the file open dialog to use 
in a bug report?


I think it depends on the application :)

Do you see it in other applications?

If so, you can figure out what GUI toolkit/environment it is gtk, qt, 
gnome, kde.


Otherwise probably file a bug on the app.

Bijan

Package name to report bug with KDE file open dialog

[Patrick Dunford]

Hello

I am using debian bookworm with kde and have noticed a bug in an 
application which is using a file open dialog. The problem only occurs 
in bookworm and is not present when using the same combination of kde 
and software on a system running bullseye.


Which is the name of the package relating to the file open dialog to use 
in a bug report?

Re: Unable to which package to report bug against

[Andrei POPESCU]

On Du, 08 nov 20, 07:46:37, Branislav Makúch wrote:
> Hello fellow Debianites,
> 
> When I tried to install virtualbox and virtualbox-dkms; the 
> virtualbox-dkms package failed to build, because I miss the 
> linux-headers package, which I cannot find at the package 
> repositories. Is the problem in virtualbox package, or in kernel 
> headers, or is it between the keyboard and chair (ie: me)?

[...]

> Building for 5.7.0-2-amd64

This kernel is currently not available in any release, and neither are 
the corresponding headers.

You can either downgrade to the kernel in stable (safe), upgrade to the 
kernel in unstable (less safe) or alternatively enable backports and use 
the kernel from there (reasonably safe).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Unable to which package to report bug against

[Branislav Makúch]

Hello fellow Debianites,

When I tried to install virtualbox and virtualbox-dkms; the virtualbox-dkms 
package failed to build, because I miss the linux-headers package, which I 
cannot find at the package repositories. Is the problem in virtualbox package, 
or in kernel headers, or is it between the keyboard and chair (ie: me)?
Thanks for your help,
Branislav

1.) FINDING THE VIRTUALBOX

I am using Debian Bullseye, the virtualbox package is only in Sid. 
I have added Sid to sources.list and pinned it to 600

/etc/apt/preferences
--
Package: *
Pin: release a=bullseye
Pin-Priority: 900

Package: *
Pin: release a=sid
Pin-Priority: 600

2.) INSTALLING THE VIRTUALBOX
===
Loading new virtualbox-6.1.16 DKMS files...
Building for 5.7.0-2-amd64
Module build for kernel 5.7.0-2-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.
Nastavuje se balík virtualbox (6.1.16-dfsg-3) …
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb.service 
 → 
/lib/systemd/system/vboxweb.service.
Job for vboxweb.service failed because the service did not take the steps 
required by its unit configuration.
See "systemctl status vboxweb.service" and "journalctl -xe" for details.
Job for virtualbox.service failed because the control process exited with error 
code.
See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
 Loaded: loaded (/etc/init.d/virtualbox; generated)
 Active: failed (Result: exit-code) since Sun 2020-11-08 07:20:06 CET; 42ms 
ago
   Docs: man:systemd-sysv-generator(8)
    Process: 7307 ExecStart=/etc/init.d/virtualbox start (code=exited, 
status=1/FAILURE)

lis 08 07:20:05  systemd[1]: Starting LSB: VirtualBox Linux kernel 
module...
lis 08 07:20:06  virtualbox[7307]: Loading VirtualBox kernel 
modules...No suitable module for running kernel found ...lis 08 07:20:06 
 virtualbox[7317]:  failed!lis 08 07:20:06  virtualbox[7318]:  
failed!lis 08 07:20:06  systemd[1]: virtualbox.service: Control process 
exited, code=exited, status=1/FAILURElis 08 07:20:06  systemd[1]: 
virtualbox.service: Failed with result 'exit-code'.lis 08 07:20:06  
systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.

3.)My system
==
uname -a
-
Linux  5.7.0-2-amd64 #1 SMP Debian 5.7.10-1 (2020-07-26) x86_64 
GNU/Linux

apt show libc6 | grep ^Version

Version: 2.31-4

4.)The bug report
=
I have found a bug report, but I'm not sure if it the same problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968660
-- 
Skutečně si potřebujete tento email ponechat v Doručené poště? Šetřete životní 
prostředí a mažte si emaily, ať nezabírají místo v cloudových úložištích.

Re: Re: How do I report bug on Old machine via this New Laptop?

[PaulG]

Thanks Greg,

I will report it on Kali (not Debian).

Re: How do I report bug on Old machine via this New Laptop?

[Greg Wooledge]

On Mon, Jul 13, 2020 at 02:16:03PM -0700, Paul Gerken wrote:
> Fri 7/10  installed Kali linux from USB, burned from
> kali-linux-2020.2-installer-amd64  download of 7/7.

> Installed as Kali on different AMD Athalon 64x2 tower machine which has no
> email on it.

> Distro is  5.7.0-kali1-amd64 #1 SMP Debian 5.7.6-1kali2 (2020-07-01) x86_64
> GNU /Linux

> How do I go about reporting this problem? w/o email on target Kali linux
> machine?

You type "kali bug report" into Google, and then you follow whatever
the instructions are for reporting a bug to your operating system
vendor (Kali).

This is not a Debian system, so I don't know why you think Debian users
are going to be able to help you.

Re: How do I report bug on Old machine via this New Laptop?

[Andrei POPESCU]

On Lu, 13 iul 20, 19:27:22, The Wanderer wrote:
> 
> The short answer is that when you cancel an otherwise-complete bug
> report from the 'reportbug' program, it saves the result into a file,
> and you can take that file to another machine and (with a little work)
> turn it into an E-mail that can be sent from there.
> 
> I use a similar method on my own computer, since although I do have the
> ability to send E-mail from here, I can't do it from the command line or
> via reportbug. I suspect I don't have a working SMTP configuration
> defined anywhere those mail systems know how to access.

Run 'reportbug --configure' and choose reportbug.debian.org as 
smarthost.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: How do I report bug on Old machine via this New Laptop?

[The Wanderer]

On 2020-07-13 at 17:16, Paul Gerken wrote:

> Hi User,
> 
>apt-get install cups cups-client "foomatic-db*"  
> 
> fails with  foomatic-db-compressed-ppds  : Conflicts:   foomatic-db  Breaks:
> foomatic-db  
> 
>   Unable to correct problems, you have held broken packages.

That appears to be because it's not supposed to be possible to install
both of these two packages side-by-side.

They apparently both provide files that satisfy the same requirement,
such that having both of them present on the same running system
wouldn't make sense.

You'll need to narrow down your list of packages to be installed, by not
using the wildcard.

The list of package which that wildcard pattern would match can be
identified in a number of ways, but I just did it by the following:

$ apt-cache search foomatic | grep ^foomatic

(I'd expect 'apt-cache search ^foomatic' to do it, but apparently that
also matches the cups-filters package. I don't care enough to
investigate why at the moment.)

> How do I go about reporting this problem? w/o email on target Kali
> linux machine?

I did write out a fairly lengthy, step-by-step answer to this, but I
think the answer had started to become condescending and generally
unproductive, so I'm not going to include it here.

The short answer is that when you cancel an otherwise-complete bug
report from the 'reportbug' program, it saves the result into a file,
and you can take that file to another machine and (with a little work)
turn it into an E-mail that can be sent from there.

I use a similar method on my own computer, since although I do have the
ability to send E-mail from here, I can't do it from the command line or
via reportbug. I suspect I don't have a working SMTP configuration
defined anywhere those mail systems know how to access.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

How do I report bug on Old machine via this New Laptop?

[Paul Gerken]

Hi User,

   apt-get install cups cups-client "foomatic-db*"  

fails with  foomatic-db-compressed-ppds  : Conflicts:   foomatic-db  Breaks:
foomatic-db  

  Unable to correct problems, you have held broken packages.

  unmet dependencies

 

Fri 7/10  installed Kali linux from USB, burned from
kali-linux-2020.2-installer-amd64  download of 7/7.

D/L on this laptop Intel i7  WIN7 machine that has email.  

Installed as Kali on different AMD Athalon 64x2 tower machine which has no
email on it.

 

Distro is  5.7.0-kali1-amd64 #1 SMP Debian 5.7.6-1kali2 (2020-07-01) x86_64
GNU /Linux

 

How do I go about reporting this problem? w/o email on target Kali linux
machine?

Which package is it against?  foomatic-db-compressed-ppds   OR   foomatic-db
??

New-ish to Linux, fast learning, have programmed in different O/S-s back to
1961.

 

More importantly, how do I go about fixing it? 

Or does someone else need to change the source and re-gen?

 

Tkx, Paul Gerken

 

 

Re: How to report bug / enhancement request for official debian docker image

[tomas]

On Mon, Mar 02, 2020 at 01:14:59PM +1030, heman wrote:
> hi Tomas, thanks for the response, pretty sure the docker image was the 
> official debian:buster from dockerhub. I'll double check.
> 
> I hadn't thought of looking for an issue reporting link on dockerhub, as I 
> figured it would be part of the main Debian product, however indeed the page 
> for the Debian image has provided me a link to the git repo for reporting 
> issues, which seems to be:
>  https://github.com/debuerreotype/docker-debian-artifacts/issues
> 
> thanks again, I'll file an enhancement request there

Glad I could be of help -- and thanks for reporting the
issue :-)

Cheers
-- t


signature.asc
Description: Digital signature

Re: How to report bug / enhancement request for official debian docker image

[Jonathan Dowland]

On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:

I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from multiple packages.


If you mean this one 
(i.e. what docker gives you if you do "docker pull debian…")

Then the correct place to file issues is


The maintainer is aware the package is missing; c.f.

and

although reading those I don't think they've clearly ruled out including
it. You could file a new issue or pull request to add it.

And it seems netbase is indeed not present in any of the Debian images,
going by the metadata in


--
👱🏻  Jonathan Dowland
🔗   https://jmtd.net

Re: How to report bug / enhancement request for official debian docker image

[tomas]

On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:
> Hi,
> 
> I've read https://www.debian.org/Bugs/Reporting
> but it is still completely unclear to me how I can report what I
> consider to be a bug or flaw with the debian docker image [...]

That depends on where you got this Debian docker image from. I think
the relevant address for those bug reports is more that way?

Cheers
-- t


signature.asc
Description: Digital signature

How to report bug / enhancement request for official debian docker image

[heman]

Hi,

I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from multiple packages.
(from reading the page at the above URL it would seem you don't have
anything like bugzilla and I need to use the reportbug tool and file
a bug against a specific package).

The root of the problem that I'm trying to report is that the debian
docker image (for buster) seems to be missing the 'netbase' package,
which is almost a critical package, as it provides /etc/services and
/etc/protocols (and nothing else). This package is tiny and is essential
for system routines such as 'getprotobyname' to function.

For example, the tiger vncserver package uses getprotobyname and fails
to open a listening tcp socket if the netbase package is not installed.
I could file a bug against the tiger vncserver standalone package,
however in my opinion this missing dependency has highlighted a bigger
problem with the debian docker image, as /etc/services and
/etc/protocols should be included by any base image!

The cost of adding this package to the base image is extremely minimal,
as it basically provides 3 tiny system files,
/etc/protocols, /etc/services, and /etc/rpc (plus a changelog, copyright
file and so on)

Please advise on where/how I can submit a bug report / feature request
for getting the 'netbase' package included in the official debian docker
image.

cheers

Re: How to report bug

[Hans]

Am Montag, 25. November 2019, 20:07:56 CET schrieb Goran Delcev:
Hi Goran,

this bug is known since almost 2 years. I reported it in the list, sent a 
bugreport tzo 
powerdevil (and askeds the list, which package might be responsible for it), 
but got 
no solution. People told me, the kernel itself is the one, that controls all 
hibernation 
things. However, afaik there are other tools responsible, too (like 
laptop-mode, 
uswsuspm, tuxonice and others).
Hope, someone might helpö you.

Good luck and all the best

Hans
I have a bug to report. I have used reportbug tool, and the tool suggested to 
use 
this mailing list.
The bug is in that system is not waking up from "suspend to RAM". I get black 
screen and I have to do hardware reset. In log files there is nothing that 
could 
suggest what is wrong. Because I don't know in which package the bug is 
occurring 
I am writing to this list.
Thanks.
Goran Delcev






signature.asc
Description: This is a digitally signed message part.

Re: report bug

[Celejar]

On Fri, 25 Jan 2019 12:59:16 +
Paul Sutton  wrote:

> Hi
> 
> I have set up report-bug however upon running I am informs me that 
> gir1.2-vte-2.91
>  is missing, this is required to run the program with the GUI. 
> 
> I have no problem installing this (and have done) but just thought I
> would mention it.

This is explained in reportbug's "README.Users" file:

> If you tried to set the new GTK+ UI (named in reportbug as gtk2 ui)
> and it fails to start (falling back to text mode, hopefully), chances
> are that you are missing some of the packages listed as Suggests, in
> particular:
> 
>  - python3-gi
>  - python3-gi-cairo
>  - gir1.2-gtk-3.0
>  - gir1.2-vte-2.91
>  - python3-gtkspellcheck
> 
> or, install the reportbug-gtk package to get the needed dependencies.
> 
> If after installing both of them still GTK+ UI doesn't show up, please
> file a report (in text ui :) ).

>  report bug defaults to the CLI version anyway.

Celejar

report bug

[Paul Sutton]

Hi

I have set up report-bug however upon running I am informs me that 
gir1.2-vte-2.91
 is missing, this is required to run the program with the GUI. 

I have no problem installing this (and have done) but just thought I
would mention it.

 report bug defaults to the CLI version anyway.

Paul


-- 

Paul Sutton
http://www.zleap.net
https://www.linkedin.com/in/zleap/




signature.asc
Description: OpenPGP digital signature

Re: Report bug.

[Dejan Jocic]

On 22-05-17, G wrote:
> well my touchpad works when i start my laptop. Sometimes after a while
> it stop working. Touchpad works again after i reboot my laptop. I dont
> see how that is a hardware problem.
> I got more than two packages that match with the installed
> xserver-xorg-input-libinput - X.Org X server -- libinput input driver
> xserver-xorg-input-synaptics - Synaptics TouchPad driver for X.Org server
> 
> 
> On 05/22/2017 04:44 PM, Dejan Jocic wrote:
> > On 22-05-17, G wrote:
> >> Hello.
> >> After a while touchpad stop working. Im trying to report that bug but i
> >> dont know which package to report.
> >> Thanks
> >>
> > 
> > 
> > 1. For start, are you sure that it is system fault, not hardware fault?
> > If you have another system installed in dual boot, or live dvd/cd/usb,
> > did you check with it if touchpad works?
> > 
> > 2. Are you sure that you did not turn off touchpad? 
> > 
> > 3. If you are sure that it is system fault, do apt-cache search
> > touchpad. After that, compare those packages with packages you have
> > installed. Was there upgrade of some of those packages recently? Did
> > your touchpad stopped working after some of those upgrades?
> > 
> > 
> > 
> 

In my case, I've had xserver-xorg-input-synaptics removed, because it
was messing something in Gnome, like touchpad settings not showing up in
system settings. While you could/should report bug about some package,
you can also try uninstalling it too, perhaps it will solve your
problem. If not, you can reinstall it. As for questions 1 and 2, it is
logical course of actions and you did not provide much things to start
with, but I do apologise if it sounded condescending to you, or
something like that.

where to report a bug for touchpad issues (was Re: Report bug.)

[Jonathan Dowland]

On Mon, May 22, 2017 at 05:09:40PM +0300, G wrote:
> well my touchpad works when i start my laptop. Sometimes after a while
> it stop working. Touchpad works again after i reboot my laptop. I dont
> see how that is a hardware problem.
> I got more than two packages that match with the installed
> xserver-xorg-input-libinput - X.Org X server -- libinput input driver
> xserver-xorg-input-synaptics - Synaptics TouchPad driver for X.Org server

Are you using X? (If you are using a graphical environment, the answer is
almost certainly yes)

You will be using just one of those two drivers I think. You can determine
which by reading /var/log/Xorg.0.log. That should indicate which of the two
packages to report a bug against. (But first please check the existing bug
reports to make sure it is not already reported)

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: Report bug.

[G]

well my touchpad works when i start my laptop. Sometimes after a while
it stop working. Touchpad works again after i reboot my laptop. I dont
see how that is a hardware problem.
I got more than two packages that match with the installed
xserver-xorg-input-libinput - X.Org X server -- libinput input driver
xserver-xorg-input-synaptics - Synaptics TouchPad driver for X.Org server


On 05/22/2017 04:44 PM, Dejan Jocic wrote:
> On 22-05-17, G wrote:
>> Hello.
>> After a while touchpad stop working. Im trying to report that bug but i
>> dont know which package to report.
>> Thanks
>>
> 
> 
> 1. For start, are you sure that it is system fault, not hardware fault?
> If you have another system installed in dual boot, or live dvd/cd/usb,
> did you check with it if touchpad works?
> 
> 2. Are you sure that you did not turn off touchpad? 
> 
> 3. If you are sure that it is system fault, do apt-cache search
> touchpad. After that, compare those packages with packages you have
> installed. Was there upgrade of some of those packages recently? Did
> your touchpad stopped working after some of those upgrades?
> 
> 
> 

Re: Report bug.

[Dejan Jocic]

On 22-05-17, G wrote:
> Hello.
> After a while touchpad stop working. Im trying to report that bug but i
> dont know which package to report.
> Thanks
> 


1. For start, are you sure that it is system fault, not hardware fault?
If you have another system installed in dual boot, or live dvd/cd/usb,
did you check with it if touchpad works?

2. Are you sure that you did not turn off touchpad? 

3. If you are sure that it is system fault, do apt-cache search
touchpad. After that, compare those packages with packages you have
installed. Was there upgrade of some of those packages recently? Did
your touchpad stopped working after some of those upgrades?

Report bug.

[G]

Hello.
After a while touchpad stop working. Im trying to report that bug but i
dont know which package to report.
Thanks

Re: Where to report bug? Headphones must be plugged in then out after boots for built-in speakers to have sound.

[Brian]

On Sat 21 Feb 2015 at 21:46:58 -0500, Bryan Ritter wrote:

> debian-user@lists.debian.org,
> 
> I tried report-bug, but it said if I don't know the name of the package to 
> email
> this email address for assistance, if I don't know the name of package with 
> this bug

Just for your information - the Bug Tracking System is not for seeking
assistance with problems. The place to do that is the place you are at
now,


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/22022015191857.5e2c419b7...@desktop.copernicus.demon.co.uk

Re: Where to report bug? Headphones must be plugged in then out after boots for built-in speakers to have sound.

[Chris Bannister]

On Sun, Feb 22, 2015 at 11:52:38AM +, Lisi Reisz wrote:
> On Sunday 22 February 2015 02:46:58 Bryan Ritter wrote:
> > debian-user@lists.debian.org,
> >
> > I tried report-bug, but it said if I don't know the name of the package to
> > email this email address for assistance, if I don't know the name of
> > package with this bug
> >
> >
> > Headphones* must be plugged in after boot-up before any sound is produced
> > from built-in speakers on notebook.
> >
> > I have a Dell Latitude D830 notebook, using Debian 8, and KDE for desktop
> > environment.
> > When I boot up I don't get any sound from the laptops speakers until I plug
> > in and out my headphones.
> > I've tried playing with the volume/mute settings before the plugging in of
> > headphone, but changing the volume, mute/unmute doesn't have any effects
> > until the headphones get plugged in. Then it works normally.
> >
> > If it boots up without any headphones* plugged in sound should play from
> > the laptop's built in speakers unless headphones are plugged in.
> >
> > Thanks in advance for any assistance in reporting this bug,
> 
> There's a good chance that it is not a bug, so doesn't need reporting.  It 
> sounds much more like a fault in the device (device requiring 
> amplification/not requiring amplification) recognition of the socket on the 
> laptop.  Until proved otherwise, I'd assume hardware in this case, rather 
> than software.
> 
> I see that Ric thinks the same thing.

And me, that's why I suggested trying with a Knoppix CD first.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150222180317.GA16766@tal

Re: Where to report bug? Headphones must be plugged in then out after boots for built-in speakers to have sound.

[Lisi Reisz]

On Sunday 22 February 2015 02:46:58 Bryan Ritter wrote:
> debian-user@lists.debian.org,
>
> I tried report-bug, but it said if I don't know the name of the package to
> email this email address for assistance, if I don't know the name of
> package with this bug
>
>
> Headphones* must be plugged in after boot-up before any sound is produced
> from built-in speakers on notebook.
>
> I have a Dell Latitude D830 notebook, using Debian 8, and KDE for desktop
> environment.
> When I boot up I don't get any sound from the laptops speakers until I plug
> in and out my headphones.
> I've tried playing with the volume/mute settings before the plugging in of
> headphone, but changing the volume, mute/unmute doesn't have any effects
> until the headphones get plugged in. Then it works normally.
>
> If it boots up without any headphones* plugged in sound should play from
> the laptop's built in speakers unless headphones are plugged in.
>
> Thanks in advance for any assistance in reporting this bug,

There's a good chance that it is not a bug, so doesn't need reporting.  It 
sounds much more like a fault in the device (device requiring 
amplification/not requiring amplification) recognition of the socket on the 
laptop.  Until proved otherwise, I'd assume hardware in this case, rather 
than software.

I see that Ric thinks the same thing.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201502221152.38837.lisi.re...@gmail.com

Re: Where to report bug? Headphones must be plugged in then out after boots for built-in speakers to have sound.

[Ric Moore]

On 02/21/2015 09:46 PM, Bryan Ritter wrote:

debian-user@lists.debian.org,

I tried report-bug, but it said if I don't know the name of the package to email
this email address for assistance, if I don't know the name of package with 
this bug


Headphones* must be plugged in after boot-up before any sound is produced from
built-in speakers on notebook.

I have a Dell Latitude D830 notebook, using Debian 8, and KDE for desktop
environment.
When I boot up I don't get any sound from the laptops speakers until I plug in
and out my headphones.
I've tried playing with the volume/mute settings before the plugging in of
headphone, but changing the volume, mute/unmute doesn't have any effects until
the headphones get plugged in. Then it works normally.

If it boots up without any headphones* plugged in sound should play from the
laptop's built in speakers unless headphones are plugged in.

Thanks in advance for any assistance in reporting this bug,


I ~think~ it might be related to the autoswitching/sensing feature of 
the jack when it tries mightily to determine if you have an amplified 
device or non-amplified one. I'd have to unplug and plug in my amplified 
sound speakers for it to set itself. It used to be that you would have 
two jacks, one for a cheap speaker with just a wire with a plug, that 
would use the amplifier of the sound card. Then one for amplified 
speakers (line-out) for a base signal to be sent to the amplifier of a 
set of speakers where the amp built in. I know, it's dodgy at best when 
one jack is made to suit both cases. Mine seems to have settled down and 
it works all the time. But, I have a desktop where I use the same setup 
all the time.



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54e97a37.3080...@gmail.com

Re: Where to report bug? Headphones must be plugged in then out after boots for built-in speakers to have sound.

[Chris Bannister]

On Sat, Feb 21, 2015 at 09:46:58PM -0500, Bryan Ritter wrote:
> debian-user@lists.debian.org,
> 
> I tried report-bug, but it said if I don't know the name of the package to 
> email
> this email address for assistance, if I don't know the name of package with 
> this bug

Does it still happen if you boot with a live CD, e.g. Knoppix?


-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150222060321.GA9312@tal

Re: Where to report bug? Headphones must be plugged in then out after boots for built-in speakers to have sound.

[briand]

On Sat, 21 Feb 2015 21:46:58 -0500
Bryan Ritter  wrote:

> debian-user@lists.debian.org,
> 
> I tried report-bug, but it said if I don't know the name of the package to 
> email
> this email address for assistance, if I don't know the name of package with 
> this bug
> 
> 
> Headphones* must be plugged in after boot-up before any sound is produced from
> built-in speakers on notebook.
> 

do this :

aplay -l 
pacmd list-sinks

BEFORE you plug in headphones

then the same commands afterwards.

i'm suspecting that the wrong audio device is being enabled, although it's 
certainly not obvious why the speakers would work when you plugged in the 
headphones.

the other possibility is that plugging in the headphones is simply changing the 
volume setting or unmuting audio on the built-in speakers.



Brian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150221220153.124e1...@cedar.deldotd.com

Where to report bug? Headphones must be plugged in then out after boots for built-in speakers to have sound.

[Bryan Ritter]

debian-user@lists.debian.org,

I tried report-bug, but it said if I don't know the name of the package to email
this email address for assistance, if I don't know the name of package with 
this bug


Headphones* must be plugged in after boot-up before any sound is produced from
built-in speakers on notebook.

I have a Dell Latitude D830 notebook, using Debian 8, and KDE for desktop
environment.
When I boot up I don't get any sound from the laptops speakers until I plug in
and out my headphones.
I've tried playing with the volume/mute settings before the plugging in of
headphone, but changing the volume, mute/unmute doesn't have any effects until
the headphones get plugged in. Then it works normally.

If it boots up without any headphones* plugged in sound should play from the
laptop's built in speakers unless headphones are plugged in.

Thanks in advance for any assistance in reporting this bug,

bryanfr...@hotmail.com


*I suppose technically it could be anything plugged into that jack, just calling
it headphones here


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/blu436-smtp24316137cc4f0360de8d479d4...@phx.gbl

Re: inquire report bug

[Darac Marjal]

On Mon, Mar 04, 2013 at 09:04:50PM -0800, sting wing wrote:
>at this address: [1]http://www.debian.org/Bugs/Reporting
>there is this line: If you are unable to determine which package your bug
>report should be filed against, please send e-mail to the [2]Debian user
>mailing list asking for advice.
>The following is found in top panel menu Applications/Log File Viewer/
>messages.
>same data as found in kern log.
>i was told in lap top mail list i should consider it for a bug report, yet
>i know not.
>Installed in: HP Pavilion G4, Intel Pentium B960 @ 2.20 GHz. 
>thank you.

OK. You've done the right thing, we can help you move on from here.

First of all, is this a bug? That is, does you system behave badly
because of these errors? I see it's an ACPI error, so do the fan(s) run
at a decent speed, can you press the power button to invoke a graceful
shutdown etc etc?

If the computer acts normally, then these "errors" may not actually be a
problem. It could just be the kernel saying "I tried this, but it didn't
work. You didn't actually need it though"

If, however, there is an issue, do you have the latest BIOS firmware for
your machine?

If you have the latest firmware, there there are two more things you can
try, but require a bit more work. One is to compile and run the latest
vanilla kernel (that is, from kernel.org); that may include a
workaround. Two is to compile your own ACPI DSDT and fix the errors.
There are plenty of HOWTOs on the internet for achieving both of these.



signature.asc
Description: Digital signature

inquire report bug

[sting wing]

at this address: http://www.debian.org/Bugs/Reporting
there is this line: If you are unable to determine which package your bug 
report should be filed against, please send e-mail to the Debian user mailing 
list asking for advice.

The following is found in top panel menu Applications/Log File Viewer/ messages.
same data as found in kern log.

i was told in lap top mail list i should consider it for a bug report, yet i 
know not.

Installed in: HP Pavilion G4, Intel Pentium B960 @ 2.20 GHz. 

thank you.

Feb 28 07:21:08 Dhost kernel: [21652.104842] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 07:21:08 Dhost kernel: [21652.104850] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 07:21:08 Dhost kernel: [21652.104856] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 08:21:20 Dhost kernel: [25260.614673] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 08:21:20 Dhost kernel: [25260.614692] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 08:21:20 Dhost kernel: [25260.614707] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 09:21:33 Dhost kernel: [28869.505006] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 09:21:33 Dhost kernel: [28869.505025] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 09:21:33 Dhost kernel: [28869.505041] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 10:21:46 Dhost kernel: [32478.516818] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 10:21:46 Dhost kernel: [32478.516835] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 10:21:46 Dhost kernel: [32478.516851] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 11:21:59 Dhost kernel: [36087.481847] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 11:21:59 Dhost kernel: [36087.481865] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 11:21:59 Dhost kernel: [36087.481881] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 12:22:11 Dhost kernel: [39696.438934] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 12:22:11 Dhost kernel: [39696.438953] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 12:22:11 Dhost kernel: [39696.438969] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 13:22:22 Dhost kernel: [43303.467606] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 13:22:22 Dhost kernel: [43303.467624] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 13:22:22 Dhost kernel: [43303.467641] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 14:22:33 Dhost kernel: [46910.724382] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 14:22:33 Dhost kernel: [46910.724400] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 14:22:33 Dhost kernel: [46910.724417] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 15:22:47 Dhost kernel: [50519.890825] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 15:22:47 Dhost kernel: [50519.890844] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 15:22:47 Dhost kernel: [50519.890860] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 16:22:59 Dhost kernel: [54128.728143] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 16:22:59 Dhost kernel: [54128.728161] ACPI Error: Region
SystemCMOS(5) has no handler (20090903/exfldio-295)
Feb 28 16:22:59 Dhost kernel: [54128.728178] ACPI Error
(psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_._Q33] (Node 88014f643ac0), AE_NOT_EXIST
Feb 28 17:23:12 Dhost kernel: [57737.526968] ACPI Error: No handler
for Region [CMS0] (88014f642a20) [SystemCMOS]
(20090903/evregion-319)
Feb 28 17:23:12 Dhost kernel: [57737.526985] ACPI Error: Region
SystemCMOS(5) has no h

Re: where to report bug: Wheezy installer failed on a RTL8169 network card

[Martin Steigerwald]

Am Mittwoch, 29. August 2012 schrieb Yuwen Dai:
> Dear all,
> 
> I downloaded the latest Wheezy AMD64 version DVD iso image, trying to
> install it on a HP notebook with a RTL8169 NIC.  When the installer
> detects network, it hangs.  I could switch to other ttys and open a
> busybox  shell, but it's useless, the installation could not resume
> any more.  I tried a Squeeze  DVD on the same notebook,  the DHCP
> process appeared some difficult, I tried several times,  but at last,
> it got IP address.  Where can I report this bug?

One thing that you may try unless the bug report mentioned by you does not 
yet have this information:

Go to tty4 (Alt-F4) and look for suspicious log messages. You can add to 
the bug report by sending an mail to bu...@bugs.debian.org

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


-- 
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/201208291911.54549.mar...@lichtvoll.de

Re: where to report bug: Wheezy installer failed on a RTL8169 network card

[Yuwen Dai]

>
> Thank you for testing the early installer and then reporting problems
> with it.  The place to report those bugs is the "installation-reports"
> package.
>
>   
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=installation-reports
>
> You would want to look over the bugs already filed there to see if one
> matches.  In particular there is a now known kernel bug which caused
> hangs at boot that was just this week closed.  If not then file your
> details there.
>
> I recommend that you try one of the very new daily built netinst
> images from http://cdimage.debian.org/cdimage/weekly-builds/ to see if
> the latest is still a problem.
>
> Bob

Hi Bob,

Thank you for the links.  It appears that this is  a known bug:


#679795
Installation freezes when detecting network card Ralink corp. RT5390
Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E

Best regards,
Yuwen


-- 
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/candez-yew+euhfiom6vb34vezfugx77dwfuushpeybjeydp...@mail.gmail.com

Re: where to report bug: Wheezy installer failed on a RTL8169 network card

[Bob Proulx]

Yuwen Dai wrote:
> I downloaded the latest Wheezy AMD64 version DVD iso image, trying to
> install it on a HP notebook with a RTL8169 NIC.  When the installer
> detects network, it hangs.  I could switch to other ttys and open a
> busybox  shell, but it's useless, the installation could not resume
> any more.  I tried a Squeeze  DVD on the same notebook,  the DHCP
> process appeared some difficult, I tried several times,  but at last,
> it got IP address.  Where can I report this bug?

Thank you for testing the early installer and then reporting problems
with it.  The place to report those bugs is the "installation-reports"
package.

  
http://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=installation-reports

You would want to look over the bugs already filed there to see if one
matches.  In particular there is a now known kernel bug which caused
hangs at boot that was just this week closed.  If not then file your
details there.

I recommend that you try one of the very new daily built netinst
images from http://cdimage.debian.org/cdimage/weekly-builds/ to see if
the latest is still a problem.

Bob





signature.asc
Description: Digital signature

where to report bug: Wheezy installer failed on a RTL8169 network card

[Yuwen Dai]

Dear all,

I downloaded the latest Wheezy AMD64 version DVD iso image, trying to
install it on a HP notebook with a RTL8169 NIC.  When the installer
detects network, it hangs.  I could switch to other ttys and open a
busybox  shell, but it's useless, the installation could not resume
any more.  I tried a Squeeze  DVD on the same notebook,  the DHCP
process appeared some difficult, I tried several times,  but at last,
it got IP address.  Where can I report this bug?

Best regards,
Yuwen


-- 
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/CANdEz-Y02n62qLiZyH-UMKjvt5ZH3yMhdc+j=+we3jr5rac...@mail.gmail.com

Re: How to report bug in installation of squeeze

[Camaleón]

On Wed, 16 Feb 2011 09:32:56 +0100, Per Edlund wrote:

> I need help on how to report a bug in the installer.

http://wiki.debian.org/DebianInstaller/Bugs
http://www.debian.org/Bugs/Reporting.en.html

> I've tried to install Debian Squeeze (6.0) on a Dell PowerEdge 1750 for
> a day and it failes with Kernel Panic when detecting the network.

Add the error you get in your bug report. If you can't catch the log a 
snapshot (aka: photo) will also be useful.

> First I tried to upgrade Lenny to Squeeze, that failed (could make it
> work by using the old kernel though, by linking the old vmlinuz), then I
> tried to install it from scratch with no luck.

What ISO image did you download? CD, DVD, netiso...?
 
> I've tried both the unsupported version with non-free firmware included
> and also tried installing by adding it via usb but it failes all the
> time.

Lack of firmware should not prevent the installation, at least if you 
performed a local install using a CD/DVD as source. In such case, the 
installer should go on with no network adapter detected :-?

> I have never reported any bugs before, so I'm not sure which package to
> report this on and what to include. The info below is handwritten, since
> I have no way of getting the logs from the machine, but I thought it
> might be usefull ( and I tried using that with the HW compatible
> checks).

(...)

You can also include the above information in your report.

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.2011.02.16.15.36...@gmail.com

How to report bug in installation of squeeze

[Per Edlund]

Hi!

I need help on how to report a bug in the installer.

I've tried to install Debian Squeeze (6.0) on a Dell PowerEdge 1750 for a
day and it failes with Kernel Panic when detecting the network.

First I tried to upgrade Lenny to Squeeze, that failed (could make it work
by using the old kernel though, by linking the old vmlinuz), then I tried to
install it from scratch with no luck.

I've tried both the unsupported version with non-free firmware included and
also tried installing by adding it via usb but it failes all the time.

I have never reported any bugs before, so I'm not sure which package to
report this on and what to include. The info below is handwritten, since I
have no way of getting the logs from the machine, but I thought it might be
usefull ( and I tried using that with the HW compatible checks).


00:00.0 Host bridge: Broadcom CMIC-LE Host Bridge (GC-LE chipset) (rev 33)
00:00.1 Host bridge: Broadcom CMIC-LE Host Bridge (GC-LE chipset)
00:00.2 Host bridge: Broadcom CMIC-LE Host Bridge (GC-LE chipset)
00:0e:0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 Host bridge: Broadcom CSB5 South Bridge (rev 93)
00:0f.1 IDE interface: Broadcom CSB5 IDE Controller (rev 93)
00:0f.2 USB interface: Broadcom OSB4/CSB5 OHC1 USB Controller (rev 05)
00:0f.3 ISA bridge: Broadcom CSB5 LPC bridge
00:10.0 Host bridge: Broadcom CIOB-E I/O Bridge with Gigabit Ethernet (rev
12)
00:10.2 Host bridge: Broadcom CIOB-E I/O Bridge with Gigabit Ethernet (rev
12)
00:11.0 Host bridge: Broadcom CIOB-X2 PCI-X I/O Bridge (rev 05)
00:11.2 Host bridge: Broadcom CIOB-X2 PCI-X I/O Bridge (rev 05)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit
Ethernet (rev 02)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit
Ethernet (rev 02)
04:05.0 SCSI storage controller : LSI Logic / Symbios Logic 53c1030 PCI-X
Fusion-MPT Dual Ultra 320 SCSI (rev 07)
04:05.1 SCSI storage controller : LSI Logic / Symbios Logic 53c1030 PCI-X
Fusion-MPT Dual Ultra 320 SCSI (rev 07)

/P

Re: Squeeze X broken on Inspiron 8500--how to report bug

[Sven Joachim]

On 2010-10-26 05:05 +0200, Brian Sammon wrote:

>> As I explained in that bug report, it's an incompatibility between the
>> Squeeze kernel and Lenny userland.  Unfortunately, there is no way to
>> express this in package conflicts to ensure that it does not occur on
>> partial upgrades.
>
> Okay, so I'm clear:
> You're saying the Lenny xserver-xorg-video-nv is incompatible with the 
> squeeze 
> kernel?

With the nouveau.ko module, yes.  You have to prevent that module from
being loaded, or use nouveau.modeset=0 to disable kernel mode setting.

> The thing that threw me off is that this incompatibility only manifests 
> itself 
> if the squeeze udev is installed.  It doesn't occur with lenny udev.

Yes, but this means that Squeeze's udev works as designed and Lenny's
does not, because it actually *should* load nouveau.ko if you have an
NVidia card.

> Also... the Lenny xserver-xorg-video-nv is similarly incompatible with the 
> lenny-backports kernel, but that's a tangent.

Well, the lenny-backports kernel had better stop shipping the nouveau
module, since it does not do any good without a suitable X driver.

> Also... if I upgrade xserver-xorg-video-nv to squeeze, then my situation 
> improves to "X refuses to run", and I have to reboot to fix it.

The nv driver does not work correctly with kernel mode setting, that's
why the Squeeze version of nv refuses to load.  The Lenny version of nv
does not, messing things up as you had noticed.

> I don't think I have a custom kernel/udev/boot configuration.  Is this 
> problem 
> going to happen to everyone who tries to run squeeze on an Inspiron 8500?
> Everyone who tries to run squeeze on a nvidia system?

Not for people who have xserver-xorg-video-all installed and do not
specify a driver in xorg.conf.  That's the default actually.

> Right now this looks like a "Squeeze doesn't really support the Inspiron 
> 8500" 
> problem.  Is the Inspiron 8500 the type of machine that debian would like to 
> support?  Granted, it is pretty old.
>
> I wouldn't disagree at all with lowering this bug report to "feature request" 
> or reassigning it to a different package, but it seems like the current 
> situation for the Inspiron 8500 (and other nvidia systems?) is sub-optimal, 
> and sub-optimal, to me, means "bug report".
>
> PS... I don't have xserver-xorg-video-all or xserver-xorg-video-nouveau 
> installed on the machine.  Is that a factor?  Am I using the wrong X video 
> driver?

Yes, you have to use xserver-xorg-video-nouveau (or -fbdev, that's the
only other option) if nouveau.ko is loaded and kernel mode setting is
enabled.

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/87ocahv1so@turtle.gmx.de

Re: Squeeze X broken on Inspiron 8500--how to report bug

[Andrei Popescu]

On Lu, 25 oct 10, 23:05:56, Brian Sammon wrote:
 
> I don't think I have a custom kernel/udev/boot configuration.  Is this 
> problem 
> going to happen to everyone who tries to run squeeze on an Inspiron 8500?
> Everyone who tries to run squeeze on a nvidia system?

But you are not running squeeze, you have a mixed system. Can you 
reproduce this problem with *pure* squeeze? I maintain several machines 
running squeeze with nvidia cards and I have no problem.

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: Squeeze X broken on Inspiron 8500--how to report bug

[Brian Sammon]

> As I explained in that bug report, it's an incompatibility between the
> Squeeze kernel and Lenny userland.  Unfortunately, there is no way to
> express this in package conflicts to ensure that it does not occur on
> partial upgrades.

Okay, so I'm clear:
You're saying the Lenny xserver-xorg-video-nv is incompatible with the squeeze 
kernel?
The thing that threw me off is that this incompatibility only manifests itself 
if the squeeze udev is installed.  It doesn't occur with lenny udev.
Also... the Lenny xserver-xorg-video-nv is similarly incompatible with the 
lenny-backports kernel, but that's a tangent.

Also... if I upgrade xserver-xorg-video-nv to squeeze, then my situation 
improves to "X refuses to run", and I have to reboot to fix it.

I don't think I have a custom kernel/udev/boot configuration.  Is this problem 
going to happen to everyone who tries to run squeeze on an Inspiron 8500?
Everyone who tries to run squeeze on a nvidia system?

Right now this looks like a "Squeeze doesn't really support the Inspiron 8500" 
problem.  Is the Inspiron 8500 the type of machine that debian would like to 
support?  Granted, it is pretty old.

I wouldn't disagree at all with lowering this bug report to "feature request" 
or reassigning it to a different package, but it seems like the current 
situation for the Inspiron 8500 (and other nvidia systems?) is sub-optimal, 
and sub-optimal, to me, means "bug report".

PS... I don't have xserver-xorg-video-all or xserver-xorg-video-nouveau 
installed on the machine.  Is that a factor?  Am I using the wrong X video 
driver?



-- 
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/e1pazri-000113...@thinkpad

Re: Squeeze X broken on Inspiron 8500--how to report bug

[Sven Joachim]

On 2010-10-24 21:17 +0200, Brian Sammon wrote:

> I entered a bug that upgrading udev from lenny to unstable breaks X.  (It 
> also 
> breaks with the squeeze version of udev )
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
>
> The bug was closed without any changes to the package, or any other package.

As I explained in that bug report, it's an incompatibility between the
Squeeze kernel and Lenny userland.  Unfortunately, there is no way to
express this in package conflicts to ensure that it does not occur on
partial upgrades.

> While I've found a workaround, I'm concerned that this problem means that 
> Squeeze and X will not work out of the box for other people using an Inspiron 
> 8500.
>
> What do I do now?

Upgrade your *xorg-* packages, including xserver-xorg-video-all, to the
Squeeze version and move /etc/X11/xorg.conf out of the way.  Ensure that
the 2.6.32-5 kernel is booted *without* the "nomodeset" and
"nouveau.modeset=0" parameters.  If X still does not work correctly
after that, file a bug report against the xserver-xorg-video-nouveau
package.

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/87mxq2rc59@turtle.gmx.de

Re: Squeeze X broken on Inspiron 8500--how to report bug

[Andrei Popescu]

On Du, 24 oct 10, 15:17:50, Brian Sammon wrote:
> I entered a bug that upgrading udev from lenny to unstable breaks X.  (It 
> also 
> breaks with the squeeze version of udev )
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
> 
> The bug was closed without any changes to the package, or any other package.
> 
> While I've found a workaround, I'm concerned that this problem means that 
> Squeeze and X will not work out of the box for other people using an Inspiron 
> 8500.
> 
> What do I do now?
> 
> Create another bug?
> Re-open the bug?  Is reopening a bug only supposed to be done by 
> debian-developers?
> Do I appeal to a higher authority within Debian?
> Am I wrong in thinking that this concern merits a bug report?
> 
> Also, what package should the bug (new or reopened) be assigned to?  I chose 
> udev because it was the udev upgrade that triggered the problem, but maybe 
> udev isn't the best choice.

As far as I can tell from a quick read of the bug log, you are 
experiencing an incompatibility between the kernel and userspace, things 
that can happen when you run a mixed system.

Unless you can reproduce the problem with a pure squeeze or pure 
unstable system I'd say you'll have to work around it.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Squeeze X broken on Inspiron 8500--how to report bug

[Brian Sammon]

I entered a bug that upgrading udev from lenny to unstable breaks X.  (It also 
breaks with the squeeze version of udev )
( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )

The bug was closed without any changes to the package, or any other package.

While I've found a workaround, I'm concerned that this problem means that 
Squeeze and X will not work out of the box for other people using an Inspiron 
8500.

What do I do now?

Create another bug?
Re-open the bug?  Is reopening a bug only supposed to be done by 
debian-developers?
Do I appeal to a higher authority within Debian?
Am I wrong in thinking that this concern merits a bug report?

Also, what package should the bug (new or reopened) be assigned to?  I chose 
udev because it was the udev upgrade that triggered the problem, but maybe 
udev isn't the best choice.



-- 
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/e1pa64l-0008tz...@thinkpad

Re: report bug

[Boyd Stephen Smith Jr.]

This is not a bug report mailing list.  You bug reports should be filed using 
the directions http://www.debian.org/Bugs/Reporting and updated following the 
information http://www.debian.org/Bugs/server-control and 
http://www.debian.org/Bugs/Developer.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

report bug

[igorka santo]

BitTorrent T-0.3.18 (BitTornado)
OS: linux2
Python version: 2.6.4 (r264:75706, Dec  7 2009, 18:45:15) 
[GCC 4.4.1]
wx.Windows version: 2.6.3.2

Traceback (most recent call last):
  File "/usr/bin/btdownloadgui.bittornado", line 2312, in _next
savedas = dow.saveAs(choosefile, d.newpath)
  File "/usr/lib/pymodules/python2.6/BitTornado/download_bt1.py", line
414, in saveAs
if path.exists(path.join(file, x['path'][0])):
  File "/usr/lib/python2.6/posixpath.py", line 70, in join
path += '/' + b
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 14:
ordinal not in range(128)



-- 
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/1272386173.2354.0.ca...@igor-laptop

Re: Report bug in migration-assistant

[Wayne]

Krasimir Chonov wrote:

Hello. I found a bug in migration-assistant. The bug is in Ubuntu, but
to report bug about this package I was redirected to Debian. So the bug
is the fowolling:



Do you mean the module-assistant package?

Debian does not have a migration-assistant package AFAIK.


When installing Ubuntu and selected to migrate documents and setting
from previous version of Ubuntu, the settings and bookmarks wasn`t
migrated. The version of Firefox from which I want to migrate the
setting and bookmarks is 3.5.8 and the version to which they should go
is Firefox 3.6. The old version of Ubuntu is 9.10 and the new one is
Ubuntu 10.04 Beta 1. They both are i386.


Wayne


--
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/4ba26661.6000...@gmail.com

Re: Report bug in migration-assistant

[Sven Joachim]

On 2010-03-18 10:56 +0100, Krasimir Chonov wrote:

> Hello. I found a bug in migration-assistant. The bug is in Ubuntu, but
> to report bug about this package I was redirected to Debian.

Whoever told you that what wrong.  This package does not even exist in
Debian.

> So the bug is the fowolling:
>
> When installing Ubuntu and selected to migrate documents and setting
> from previous version of Ubuntu, the settings and bookmarks wasn`t
> migrated. The version of Firefox from which I want to migrate the
> setting and bookmarks is 3.5.8 and the version to which they should go
> is Firefox 3.6. The old version of Ubuntu is 9.10 and the new one is
> Ubuntu 10.04 Beta 1. They both are i386.

You had better ask on the ubuntu-user mailing list or on an Ubuntu
forum.  This is OT here.

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/87fx3xu9oe@turtle.gmx.de

Report bug in migration-assistant

[Krasimir Chonov]

Hello. I found a bug in migration-assistant. The bug is in Ubuntu, but
to report bug about this package I was redirected to Debian. So the bug
is the fowolling:

When installing Ubuntu and selected to migrate documents and setting
from previous version of Ubuntu, the settings and bookmarks wasn`t
migrated. The version of Firefox from which I want to migrate the
setting and bookmarks is 3.5.8 and the version to which they should go
is Firefox 3.6. The old version of Ubuntu is 9.10 and the new one is
Ubuntu 10.04 Beta 1. They both are i386.



Best regards
Krasimir Chonov


-- 
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/1268906187.2708.8.ca...@bfaf-desktop

Re: Where to report bug? sparc64 crashes probably from mysqld

[Cassiano Bertol Leal]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Michael Shuler wrote:
> On 12/10/2007 11:04 AM, Cassiano Bertol Leal wrote:
>> Dominik Reusser wrote:
>> [...]
>>> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->context = 
>>> 099b
>>> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->pgd = f80016884000
>>> Dec 10 10:11:45 libdb kernel:   \|/  \|/
>>> Dec 10 10:11:45 libdb kernel:   "@'/ .. \`@"
>>> Dec 10 10:11:45 libdb kernel:   /_| \__/ |_\
>>> Dec 10 10:11:45 libdb kernel:  \__U_/
>> [...]
>>
>> Is this for real???
> 
> Yes.  This is still in the 2.6.23.9 sparc and sparc64 arch
> kernel/traps.c source.
> 
> /* Amuse the user. */
> printk(
> "  \\|/  \\|/\n"
> "  \"@'/ .. [EMAIL PROTECTED]"\n"
> "  /_| \\__/ |_\\\n"
> " \\__U_/\n");
> 

LOL... That's why I love free software! Heh!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHXYISq4Bz51JiUuERAnGgAJ9H52oiVsv0Q32dwFWUJnFrP0hN1wCg3668
0qAGb4QyvaPg27/RruJpqxc=
=Lhxu
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where to report bug? sparc64 crashes probably from mysqld

[Michael Shuler]

On 12/10/2007 11:04 AM, Cassiano Bertol Leal wrote:
> Dominik Reusser wrote:
> [...]
>> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->context = 
>> 099b
>> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->pgd = f80016884000
>> Dec 10 10:11:45 libdb kernel:   \|/  \|/
>> Dec 10 10:11:45 libdb kernel:   "@'/ .. \`@"
>> Dec 10 10:11:45 libdb kernel:   /_| \__/ |_\
>> Dec 10 10:11:45 libdb kernel:  \__U_/
> [...]
> 
> Is this for real???

Yes.  This is still in the 2.6.23.9 sparc and sparc64 arch
kernel/traps.c source.

/* Amuse the user. */
printk(
"  \\|/  \\|/\n"
"  \"@'/ .. [EMAIL PROTECTED]"\n"
"  /_| \\__/ |_\\\n"
" \\__U_/\n");

-- 
Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where to report bug? sparc64 crashes probably from mysqld

[Cassiano Bertol Leal]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dominik Reusser wrote:
[...]
> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->context = 
> 099b
> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->pgd = f80016884000
> Dec 10 10:11:45 libdb kernel:   \|/  \|/
> Dec 10 10:11:45 libdb kernel:   "@'/ .. \`@"
> Dec 10 10:11:45 libdb kernel:   /_| \__/ |_\
> Dec 10 10:11:45 libdb kernel:  \__U_/
[...]

Is this for real???
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHXXGmq4Bz51JiUuERAkHuAJ9UbTY7CHV3M2VnzuKMoEGTRpmYsACghC0H
ccii/O6PaFZFNidZqf1tcTU=
=N34N
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Where to report bug? sparc64 crashes probably from mysqld

[Dominik Reusser]

Hi, 
I get unaligned access errors and I suspect mysqld to cause these,  as it 
reports page corruption just before. How would I find out whether this is 
true?
is mysql-server-5.0 the  package to file a bug report for the problem. What 
else to include in the report? 


mysql-Version: 5.0.32-7etch1

Description of what is happening:
mysqld finds a page corruption in a InnoDB database.
The kernel then reports an unaligned access.
mysqld restarts and performs the crash recovery. 
unaligned access occurs again and ssh, ping, apache, mysql do not respond 
anymore starting from this point.

Based on /var/log/syslog (see attachment) I suspect mysqld causes these 
problems.

Any help would be appreciated


-- 
Dominik Reusser
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Database page corruption on disk or 
a failed
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: file read of page 1672847.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: You may have to recover from a 
backup.
Dec 10 10:11:44 libdb mysqld[3524]: 071210 10:11:43  InnoDB: Page dump in ascii 
and hex (16384 bytes):
Dec 10 10:11:44 libdb mysqld[3524]:  len 16384; hex c4deb3030  
--snip--  ;InnoDB: End of page dump
Dec 10 10:11:44 libdb mysqld[3524]: 071210 10:11:44  InnoDB: Page checksum 
2910718267, prior-to-4.0.14-form checksum 3244052608
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: stored checksum 3302929155, 
prior-to-4.0.14-form stored checksum 126
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page lsn 49 3962043205, low 4 bytes 
of lsn at page end 4096
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page number (if stored to page 
already) 1672847,
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: space id (if created with >= 
MySQL-4.1.1 and stored already) 0
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page may be an index page where 
index id is 0 523
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: (index LocatID_2 of table 
iller/TBL_Sample)
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Database page corruption on disk or 
a failed
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: file read of page 1672847.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: You may have to recover from a 
backup.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: It is also possible that your 
operating
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: system has corrupted its own file 
cache
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: and rebooting your computer removes 
the
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: error.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: If the corrupt page is an index page
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: you can also try to fix the 
corruption
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: by dumping, dropping, and 
reimporting
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: the corrupt table. You can use CHECK
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: TABLE to scan your table for 
corruption.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: See also InnoDB: 
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: about forcing recovery.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Ending processing because of a 
corrupt database page.
Dec 10 10:11:45 libdb kernel: Kernel unaligned access at TPC[4c6af0] 
do_task_stat+0x188/0x588
Dec 10 10:11:45 libdb kernel: Unable to handle kernel paging request in mna 
handler<1> at virtual address 80a65493
Dec 10 10:11:45 libdb kernel: current->{active_,}mm->context = 099b
Dec 10 10:11:45 libdb kernel: current->{active_,}mm->pgd = f80016884000
Dec 10 10:11:45 libdb kernel:   \|/  \|/
Dec 10 10:11:45 libdb kernel:   "@'/ .. \`@"
Dec 10 10:11:45 libdb kernel:   /_| \__/ |_\
Dec 10 10:11:45 libdb kernel:  \__U_/
Dec 10 10:11:45 libdb kernel: ps(6642): Oops [#1]
Dec 10 10:11:45 libdb kernel: TSTATE: 004411009603 TPC: 004c6af0 
TNPC: 004c6af4 Y: Not tainted
Dec 10 10:11:45 libdb kernel: TPC: 
Dec 10 10:11:45 libdb kernel: g0: f800110dd000 g1: 0013 g2: 
80a653e7 g3: 170008a0
Dec 10 10:11:45 libdb kernel: g4: f80011062980 g5: 73746174 g6: 
f8001c66 g7: f8001fb41c60
Dec 10 10:11:45 libdb kernel: o0: f8001fc82500 o1: f8001c663c38 o2: 
f8001c663c30 o3: f8001c663d48
Dec 10 10:11:45 libdb kernel: o4: 0252 o5: f80010d18800 sp: 
f8001c6631c1 ret_pc: 004c6a3c
Dec 10 10:11:45 libdb kernel: RPC: 
Dec 10 10:11:45 libdb kernel: l0: 0007 l1: f8001c663d48 l2: 
f8001fb86e40 l3: 0013
Dec 10 10:11:45 libdb kernel: l4: 0011 l5: 0001 l6: 
00030400 l7: 0053
Dec 10 10:11:45 libdb kernel: i0: f8001fc82500 i1: f800148ea000 i2: 
0001 i3: 
Dec 10 10:11:45 libdb kernel: i4: 0001 i5:  i6: 
f8001c663451 i7: 004c4aa0
Dec 10 10:11:45 libdb kernel

Re: Unsure where to report bug

[Andrew Sackville-West]

On Mon, Feb 26, 2007 at 08:25:50PM -0500, Roberto C. Sanchez wrote:
> On Mon, Feb 26, 2007 at 08:04:52PM -0500, dominijannir wrote:
> > 
> > 
> > Hi,
> > 
> > I'm running Gnome on Etch (AMD64) and, after today's batch
> > of updates, started having the following problem:
> > 
> > Unless the Configuration Editor has been used to set the
> > screensaver to a blank page, opening
> > Desktop->Preferences->screensaver (either Gnome's or
> > xscreensaver) immediately logs me out and puts me at the gdm
> > login screen.
> > 
> > Where should I report this bug and what information should I
> > provide?  (As you can tell, I'm new at this.)
> > 
> This is as good a place as any to start.  What does the gdm log and the
> X.org log file say when this happens?  They are both located in
> /var/log.
> 

you might also switch over to VT1 -<1> as xscreensaver puts
out lots of output to the console when its having trouble. might be
something of interest there.

A


signature.asc
Description: Digital signature

Re: Unsure where to report bug

[Roberto C. Sanchez]

On Mon, Feb 26, 2007 at 08:04:52PM -0500, dominijannir wrote:
> 
> 
> Hi,
> 
> I'm running Gnome on Etch (AMD64) and, after today's batch
> of updates, started having the following problem:
> 
> Unless the Configuration Editor has been used to set the
> screensaver to a blank page, opening
> Desktop->Preferences->screensaver (either Gnome's or
> xscreensaver) immediately logs me out and puts me at the gdm
> login screen.
> 
> Where should I report this bug and what information should I
> provide?  (As you can tell, I'm new at this.)
> 
This is as good a place as any to start.  What does the gdm log and the
X.org log file say when this happens?  They are both located in
/var/log.

Regards,

-Roberto

-- 
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Unsure where to report bug

[dominijannir]

Hi,

I'm running Gnome on Etch (AMD64) and, after today's batch
of updates, started having the following problem:

Unless the Configuration Editor has been used to set the
screensaver to a blank page, opening
Desktop->Preferences->screensaver (either Gnome's or
xscreensaver) immediately logs me out and puts me at the gdm
login screen.

Where should I report this bug and what information should I
provide?  (As you can tell, I'm new at this.)

Thank you,
Roberto Dominijanni


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

report bug about kde-devel

[Andrea D'Amico]

Hi. I am an italian debian user,and I find a stranger bug

when i do (like as testing or as unstable) ,after "apt-get update",
"apt-get install kde-devel"
receive this announce

some packages can't be installed(etc etc etc)
this packages have dependences not satisfied
kde-devel: Depend :kdesdk but not be install
  Depend: libarts1-dev but not be install
  Depend: kdelibs4-dev but not be install
  Depend: kdebase-dev but not be install
  Depend: libkonq4-dev but not be install
Is: package not complete

what can I do? i want use KDevelop but can compile my programs for
there packages lossed because when i execute configure file receive
message that the KDE headers are not installed

HELP meplease