Bug#961014: ifcplusplus: locale issue preventing to load any ifc file
Package: ifcplusplus Version: 0~git20190402.13744d5+dfsg-2 Severity: important Dear Maintainer, I tried to load several .ifc files (created from FreeCAD and ArchiCAD) in SimpleViewerExample. All files fail to load and each time I get this message: Error: loadModelFromFile, setlocale failed Warning: getLengthInMeterFactor, No length unit definition found in model I believe, if ifcplusplus requires a specific locale to be available on the system, then the package should make sure that this locale is available. Thanks for the work you put into BIM on debian! Harald -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ifcplusplus depends on: ii libc6 2.30-8 ii libgcc-s1 [libgcc1] 10.1.0-1 ii libgcc1 1:10.1.0-1 ii libifcplusplus0~git20190402.13744d5+dfsg-2 ii libopenscenegraph160 3.6.4+dfsg1-3+b11 ii libopenthreads21 3.6.4+dfsg1-3+b11 ii libqt5core5a 5.12.5+dfsg-10 ii libqt5gui55.12.5+dfsg-10 ii libqt5widgets55.12.5+dfsg-10 ii libstdc++610.1.0-1 ifcplusplus recommends no packages. ifcplusplus suggests no packages. -- no debconf information
Bug#959906: linux-image-5.6.0-1-arm64: Please enable CONFIG_DRM_ANALOGIX_ANX6345 on arm64
Package: src:linux Version: 5.6.7-1 Severity: wishlist Dear maintainer, the analogix ANX6345 RGB-to-eDP video bridge is used at least in pinebook and Teres-I OSHW Laptop. Including the driver in debian kernel packages would allow using the proper display enginge instead of the simple-framebuffer setup by u-boot. Enabling CONFIG_DRM_ANALOGIX_ANX6345 should do the tick. TIA, Harald -- Package-specific info: ** Version: Linux version 5.6.0-1-arm64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-11)) #1 SMP Debian 5.6.7-1 (2020-04-29) ** Command line: rootwait root=UUID=2f4b7ce4-b9c5-4544-a938-9f189be41719 debug=on console=tty0 console=ttyS0,115200n8 no_console_suspend ** Tainted: WC (1536) * kernel issued warning * staging driver was loaded ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Device Tree model: Olimex A64 Teres-I ** Loaded modules: psnap llc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common hid_generic videodev usbhid mc hid evdev r8723bs(C) ghash_ce axp20x_battery des_generic lima libdes axp20x_ac_power axp20x_adc gf128mul sha2_ce cfg80211 industrialio sha256_arm64 gpu_sched axp20x_pek aes_ce_blk sun50i_codec_analog sha1_ce crypto_simd sun8i_adda_pr_regmap snd_soc_simple_card sun8i_thermal sun8i_codec sun4i_i2s rfkill cryptd snd_soc_simple_amplifier snd_soc_simple_card_utils sunxi_wdt watchdog sun4i_drm snd_soc_core pwm_sun4i sun4i_frontend aes_ce_cipher sun4i_tcon snd_pcm_dmaengine sun8i_mixer snd_pcm sun8i_tcon_top drm_kms_helper snd_timer sun8i_ce nvmem_sunxi_sid sun6i_dma snd drm gpio_keys soundcore pwm_bl cpufreq_dt leds_gpio asix usbnet mii libphy ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic axp20x_regulator pinctrl_axp209 ohci_platform ohci_hcd ehci_platform axp20x_rsb axp20x ehci_hcd fixed usbcore i2c_mv64xxx phy_sun4i_usb usb_common sunxi_mmc ** PCI devices: ** USB devices: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 007: ID 15ba:003c Olimex Ltd. Bus 001 Device 005: ID 1908:2311 GEMBIRD Bus 001 Device 009: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.6.0-1-arm64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-5.6.0-1-arm64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.132 ii kmod27-2 ii linux-base 4.5 Versions of packages linux-image-5.6.0-1-arm64 recommends: pn apparmor ii firmware-linux-free 3.4 Versions of packages linux-image-5.6.0-1-arm64 suggests: pn debian-kernel-handbook pn linux-doc-5.6 Versions of packages linux-image-5.6.0-1-arm64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic ii firmware-realtek 20180825+dfsg-1 pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#828190: this bug (pulseaudio) actually breaks unrelated software
Hi, I have been wrong in at least one part of my previous update to this bug. Even if I stop all threads in the sound application (in my case baresip) in the debugger, pulseaudio still run's at 100% CPU spamming syslog. Only killing baresip (probably the closing of file descriptors) makes pulseaudio recover. I got confused, because somehow this situation causes an other thread of baresip consume lot's of CPU, which made me believe that there is a rather tight loop between baresip and pulseaudio. Actually the calls to the sound API never return while pulseaudio is busy, thus the application never get's an error and can't actually close its ALSA handles. So at this point I'm convinced the entire problem is within pulseaudio. Since baresip is not a pulseaudio but an ALSA application, works fine without pulseaudio installed and only uses pulseaudio because pulseaudio makes itself the default ALSA device on installation, I think it is fair to say that pulseaudio is breaking unrelated software here. I'm tempted to raise the severity of this bug to release critical, but I guess this should be at the discretion of the maintainers. This is clearly a (probably rather old) upstream bug. It seems to mostly manifest itself with SoC devices, which might explain why it is more often seen recently and with debian: Debian arm ports are quite popular with users of SoC based laptops. >From the debian packaging PoV I can see two possible workarounds: * Disable sample rate switching by setting defaut-sample-rate and alternate-sample-rate to the same value by default for the ARM based ports and prominently document the problem for everybody else. * Don't enable pulseaudio at all on ARM based ports without some kind of manual intervention by the local admin. HTH, Harald -- Es gibt viele Maßnahmen gegen die Klimakrise, die leicht und ohne Verlierer umsetzbar sind. Das Problem ist immer noch das Desinteresse der etablierten Parteien. https://haraldgeyer.at/Klimaschutz.html
Bug#828190: pulseaudio fails to interact with alsa, hangs and spams syslog
retitle 828190 [pulseaudio] sometimes locks up
tag 828190 - moreinfo
stop
Dear Maintainer,
this report is tagged "moreinfo", but I don't see which info is
missing. AFAICS the original submitter provided everything he was
asked. Please add the tag again and clarify, if indeed some information
is missing.
Also I want to refute the theory, that this problem is mostly a bug
in the kernel driver: Everything works for me, if I use ALSA directly
instead of via pulseaudio and duckduckgo finds variants of this problem
reported on the internet related to many different drivers.
Here are my observations:
On my system audio mostly works fine for trivial things like beeps
or playing .wav files. However advanced uses (mostly VoIP software
like empathy, pidgin and baresip) cause pulseaudio to run at
100% CPU (one thread) and spam syslog with this message
Mar 31 00:19:02 teres pulseaudio[9099]: W: [alsa-source-1c22c00.dai-sun8i
sun8i-0] alsa-source.c: Resume failed, couldn't restore original sample
settings.
about 315 times per second.
The really fun part: After executing
pulseaudio -k; pulseaudio --log-level=4 --log-target=stderr
I can't reproduce the issue. Must be some race involved somewhere.
The system is set up with pulse as the default ALSA device. Interaction
with pulseaudio typically happens via the ALSA API.
From the difficulty in reproducing the behaviour and the content of the
message I gather, that the trigger depends on the state of the
audio HW/alsa and the properties of the audio data to be played.
Eg. Simply playing an audio file from baresip usually works fine from
a pristine state, but might fail if earlier activity caused the messages
to appear. Using "aplay" to play a .wav file might restore a working
state.
From reading [1] and [2] I understand, that mismatched sample rates
might cause such a problem. But pulseaudio should resample as needed
to avoid this. Upstream bug [3] might be related somewhat.
I focused my efforts for analyzing this problem with baresip, because it
has the most straight forward and easy to understand code. I can reproduce
this without any other audio applications running, so it really seems like
pulseaudio is stepping on its own toes. The versions in unstable and
experimental are both affected.
The code in baresip, responsible for handling audio is at:
https://github.com/alfredh/baresip/blob/be4448a54117cfd2cda69d4fc88e1c2802e8a5b6/modules/alsa/alsa_play.c#L53
If the ALSA API immediatly returns an error without blocking at all, this
code turns into a tight loop. Neatly explaining why the system hangs with
100% CPU.
I guess this code should be smarter about handling errors. OTOH I don't
see anything illegal happening there and pulseaudio should resample instead
of throwing errors, so the main problem must be with pulseaudio.
--- begin ---
static void *write_thread(void *arg)
{
struct auplay_st *st = arg;
int n;
int num_frames;
num_frames = st->prm.srate * st->prm.ptime / 1000;
while (st->run) {
const int samples = num_frames;
void *sampv;
st->wh(st->sampv, st->sampc, st->arg);
sampv = st->sampv;
n = snd_pcm_writei(st->write, sampv, samples);
if (-EPIPE == n) {
snd_pcm_prepare(st->write);
n = snd_pcm_writei(st->write, sampv, samples);
if (n != samples) {
warning("alsa: write error: %s\n",
snd_strerror(n));
}
}
else if (n < 0) {
warning("alsa: write error: %s\n", snd_strerror(n));
}
else if (n != samples) {
warning("alsa: write: wrote %d of %d samples\n",
n, samples);
}
}
snd_pcm_drain(st->write);
return NULL;
}
--- end ---
I might dig into this further in the coming days, but since I'm very much
not familiar with ALSA, pulseaudio and debugging threaded applications,
some help would be much appreciated.
I'm mostly writing this to tell you, that I can reproduce this issue at
will (mostly, considering I couln't get debug level logs) and can run
any tests you might need. But figuring out how to make pulseaudio
smarter about switching sample rates or how to make the debian package
detect, that alternate sample rates might not be a good idea on any given
system, is probably above my paygrade.
[1]
https://pulseaudio-discuss.freedesktop.narkive.com/KCt6OOkP/testing-echo-cancellation-on-an-armhf-omap-phone
[2] https://arunraghavan.net/2011/10/alternate-sample-rates/
[3] https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/374
--
Es gibt viele Maßnahmen gegen die Klimakrise, die leicht und ohne Verlierer
umsetzbar sind. Das Problem ist immer noch das Desinteresse
Bug#954771: already fixed upstream: empathy-accounts fails to create any account
reassign 954771 telepathy-mission-control-5 forwarded 954771 https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues/84 tag 954771 + fixed-upstream retitle 954771 telepathy-mission-control-5 broken by strict checks in recent glib stop Dear Maintainers, turns out the bug has already been reported upstream some time ago. Actually upstream git contains a trival fix (not tested by me): https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/-/commit/d8dab08fe8db137c6bbd8bbdc3d9b01d98c48910 HTH, Harald -- Es gibt viele Maßnahmen gegen die Klimakrise, die leicht und ohne Verlierer umsetzbar sind. Das Problem ist immer noch das Desinteresse der etablierten Parteien. https://haraldgeyer.at/Klimaschutz.html
Bug#954771: empathy-accounts fails to create any account
Package: empathy Version: 3.25.90+really3.12.14-2 Severity: important Dear Maintainers, when I start empathy, if first asks me to import my accounts from pidgin. However this doesn't work at all, but nevermind. The real issue: When I try to manually add any account for any protocoll (tried Jabber and SIP) clicking on the "Add" button just shows no visible response at all. Since I can't add any accounts, this renders the package unusable for me. A web search turns up some sporadic forum posts discussion this issue over the past decade. Most of them end in "Oh, no [eg after rebooting] it suddenly works." Well, rebooting didn't solve the problem for me. Since I'm not running a full gnome desktop, my first guess was, that some vital dependency might be missing, which actual gnome users never notice. But after installing all gnome components, that might be remotely related to storing account data, up to gnome-control-center, the issue still persists. I got the following debug output during the critical action of clicking the "Add" button: EMPATHY_DEBUG=all G_MESSAGES_DEBUG=all empathy (empathy:3596): tp-glib/accounts-DEBUG: 23:48:09.567: tp_account_request_create_account_cb: failed to create account: (empathy:3596): tp-account-widgets-DEBUG: 23:48:09.568: account_widget_applied_cb: Could not apply changes to account: (empathy:3596): tp-glib/proxy-DEBUG: 23:48:09.568: tp_proxy_pending_call_lost_weak_ref: 0xda9eab00 lost weak ref to 0xda52e6e0 (empathy:3596): tp-glib/proxy-DEBUG: 23:48:09.568: tp_proxy_pending_call_cancel: 0xda9eab00 Please note, that telepathy unhelpfully provides empty error messages for the problem. During the same operation this is the debug output from mission-control: G_MESSAGES_DEBUG=all MC_DEBUG=all /usr/lib/telepathy/mission-control-5 (process:3557): mcd-DEBUG: 23:48:09.562: _mcd_account_manager_create_account: called (process:3557): mc-plugins-DEBUG: 23:48:09.563: mcp_account_storage_set_attribute: accounts-sso: (process:3557): mc-plugins-DEBUG: 23:48:09.563: mcp_account_storage_set: accounts-sso: (process:3557): mcd-DEBUG: 23:48:09.563: update_storage: MCP:accounts-sso -> ignore gabble/jabber/foo_40jabber_2ede1.manager (process:3557): mc-plugins-DEBUG: 23:48:09.563: mcp_account_storage_set_attribute: goa: (process:3557): mc-plugins-DEBUG: 23:48:09.563: mcp_account_storage_set: goa: (process:3557): mcd-DEBUG: 23:48:09.563: update_storage: MCP:goa -> ignore gabble/jabber/foo_40jabber_2ede1.manager (process:3557): mc-plugins-DEBUG: 23:48:09.563: mcp_account_storage_set_attribute: default-gkeyfile: (process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set: default-gkeyfile: (process:3557): mcd-DEBUG: 23:48:09.564: update_storage: MCP:default-gkeyfile -> store gabble/jabber/foo_40jabber_2ede1.manager (process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set_attribute: accounts-sso: (process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set: accounts-sso: (process:3557): mcd-DEBUG: 23:48:09.564: update_storage: MCP:accounts-sso -> ignore gabble/jabber/foo_40jabber_2ede1.protocol (process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set_attribute: goa: (process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set: goa: (process:3557): mcd-DEBUG: 23:48:09.564: update_storage: MCP:goa -> ignore gabble/jabber/foo_40jabber_2ede1.protocol (process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set_attribute: default-gkeyfile: (process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set: default-gkeyfile: (process:3557): mcd-DEBUG: 23:48:09.565: update_storage: MCP:default-gkeyfile -> store gabble/jabber/foo_40jabber_2ede1.protocol (process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set_attribute: accounts-sso: (process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set: accounts-sso: (process:3557): mcd-DEBUG: 23:48:09.565: update_storage: MCP:accounts-sso -> ignore gabble/jabber/foo_40jabber_2ede1.DisplayName (process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set_attribute: goa: (process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set: goa: (process:3557): mcd-DEBUG: 23:48:09.565: update_storage: MCP:goa -> ignore gabble/jabber/foo_40jabber_2ede1.DisplayName (process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set_attribute: default-gkeyfile: (process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set: default-gkeyfile: (process:3557): mcd-DEBUG: 23:48:09.566: update_storage: MCP:default-gkeyfile -> store gabble/jabber/foo_40jabber_2ede1.DisplayName (process:3557): GLib-GObject-CRITICAL **: 23:48:09.566: g_object_new_is_valid_property: object class 'McdAccount' has no property named 'connectivity-monitor' (process:3557): mcd-DEBUG: 23:48:09.566: _mcd_account_dispose: 0xfa63f490 ((null)) (process:3557): mcd-DEBUG: 23:48:09.566:
Bug#946260: Please enable SPDIF support for Allwinner based systems
On 06.12.2019 11:55, andreimpope...@gmail.com wrote: > Would this enable also the S/PDIF or is something else needed > (CONFIG_SND_SUN4I_SPDIF maybe?)? Indeed, for S/PDIF on A64 CONFIG_SND_SUN4I_SPDIF is needed. Based on the name I'm guessing this is not A64 specific, so retitling the bug accordingly. However AFAICS debian ships no sun50i-a64 devicetrees where S/PDIF is enabled. You would need a custom DT or an overlay, to make the debian kernel actually load the module. Is this still needed or do recent kernels have this already enabled? AFAICS no a64 based systems yet, but other arm64 allwinner systems. For example: sun50i-h6-beelink-gs1.dts HTH, Harald -- https://haraldgeyer.at
Bug#921019: arm64: Please provide sound modules for Allwinner A64 based systems
Andrei POPESCU writes: > On Jo, 31 ian 19, 17:21:54, Harald Geyer wrote: > > > Please enable the following Kconfig symbols as modules: > > > > CONFIG_SND_SUN50I_CODEC_ANALOG > > CONFIG_SND_SUN8I_CODEC > > CONFIG_SND_SUN4I_I2S > > CONFIG_SND_SOC_SIMPLE_AMPLIFIER > > CONFIG_SND_SIMPLE_CARD > > > > These are necessary for sound support on pinebook, Olimex TERES-I, etc. > > The drivers are available upstream since 4.20. > > Pinebook has sound enabled in devicetree starting with 5.0 > > Would this enable also the S/PDIF or is something else needed > (CONFIG_SND_SUN4I_SPDIF maybe?)? Indeed, for S/PDIF on A64 CONFIG_SND_SUN4I_SPDIF is needed. However AFAICS debian ships no sun50i-a64 devicetrees where S/PDIF is enabled. You would need a custom DT or an overlay, to make the debian kernel actually load the module. BTW there have been two uploads of linux 5.0 to experimental since this bug was opened. Would be nice if somebody could address this for the next upload. Harald
Bug#921244: comp/send: strange error and undocumented behaviour when using Bcc-header
Alexander Zangerl writes: > On Sun, 03 Feb 2019 14:13:24 +0000, Harald Geyer writes: > >I get the following error: > >| What now? send > >| sendmail: No recipients specified although -t option used > >| exit 1 > > could you please provide (possibly sanitised) copies > of your ~/.mh_profile and /etc/nmh/mts.conf? I actually installed nmh from scratch to reproduce the bug before writing up the report, so there shouldn't be anything special in there, but sure: lambda@hdev:~$ cat .mh_profile MH-Profile-Version: 1.0 Path: Mail lambda@hdev:~$ cat .mh_profile MH-Profile-Version: 1.0 Path: Mail lambda@hdev:~$ cat /etc/nmh/mts.conf # nmh mail transport interface customization file. # # Check the mh-tailor(5) man page for descriptions of available options. # # The delivery method to use, which must be one of the following: # smtp: nmh opens a socket connection to the appropriate port #on the servers listed below and speaks SMTP to the #first one that responds. This is the default. # sendmail/smtp: nmh pipes messages directly to the sendmail program, #speaking SMTP. Can be abbreviated to "sendmail". # sendmail/pipe: nmh pipes messages directly to the sendmail program, #using the -t option so that addresses are retrieved #from the message. mts: sendmail/pipe # Name that nmh considers `local'. If not set, nmh will # query the system for this value (gethostname, etc...). #localname: foo.bar.com # Default location of mail drops. If this option is # set, but empty, the user's home directory is used. mmdfldir: /var/mail # The name of the maildrop file in the directory where maildrops # are kept. If this is empty, the user's login name is used. mmdflfil: # # The locking algorithm to use on the spool file. Valid settings are: # # fcntl Locking using the fcntl() function # dot "Dot" locking using an external lock file # flock Locking using the flock() function (if supported by OS) # lockf Locking using the lockf() function (if supported by OS) # # Locking algorithms supported on this installation are: # # fcntl dot flock lockf # # The default spool locking configured on this system is fcntl; # change the line below to get a different value #spoollocking: fcntl # Hardcoded POP server name (prevents inc'ing from local mail spool). #pophost: localhost # A SINGLE SMTP server to use when using SMTP support servers: localhost > >Both recipients get messages with different Message-Ids, but the > >content seems to be exactly the same. > ... > >I believe this is in conflict > >with the man page of send(1), which states that Bcc-recipients will > >receive a message with a clear indication in the body, warning them > >not to disclose their status as recipients by replying. > > i don't see any indication in the send manpage that supports your reasoning. It is implied in the description of the dcc header. > but looking closely at the FAQ, the post manpage and the actual > code i do see that nmh tries to reformat bcc's under some/many/most > circumstances (and offers a weird nonstandard dcc header to create the > 'normal'/classic behaviour of identical copies). > > i can confirm that nmh 1.7 has buggy bcc handling, at least > when sendmail/pipe is used as transport: > using a shim program instead of actual sendmail/postfix/whatever i could see > that the sequence of comp-whatnow-post creates TWO messages to transmit, > > * one that contains the original body, complete with to: and bcc:, > ie. leaving sendmail/postfix/whatever to handle that bcc:, > which causes normal mail transfer agents to produce the > 'normal'/classic bcc: behaviour, > * and one that has the warning-encrusted body but no to: at all and only a > blank > bcc: header. that one is clearly untransmittable, which is what causes > the error message you saw. > > i'll get in touch with upstream and have a deeper look at the problem myself > as well. > > you might try switching to 'smtp' or 'sendmail/smtp' in /etc/nmh/mts.conf > as a potential workaround until that bug is sorted; Thanks for the info. I guess this explains why I vaguely remember bcc working in the past. > note that > according to the mts.conf manpage dcc: is NOT supported if 'sendmail/pipe' > is the transport. Thanks again, I'd have totally missed that. Sometimes it is hard to know which man pages to read ... :) Thanks for your help, Harald
Bug#921244: comp/send: strange error and undocumented behaviour when using Bcc-header
Package: nmh Version: 1.7.1-3 Severity: normal Hi, when drafting a message with comp(1) and including something like the following in the headers: | To: f...@example.com | Bcc: b...@example.com I get the following error: | What now? send | sendmail: No recipients specified although -t option used | exit 1 Both recipients get messages with different Message-Ids, but the content seems to be exactly the same. I believe this is in conflict with the man page of send(1), which states that Bcc-recipients will receive a message with a clear indication in the body, warning them not to disclose their status as recipients by replying. See the discussion von Bcc: vs. Dcc: fields in the man page of send(1) for details. I believe the body of bcc messages used to start with: | --- Blind-Carbon-Copy | | From: har...@ccbib.org | To: f...@example.com | Bcc: b...@example.com | Subject: ... | [more headers] | | [original body] Best regards and thanks for maintaining nmh. Harald -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-7-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nmh depends on: ii libc6 2.28-5 ii libcurl47.63.0-1 ii libdb5.35.3.28+dfsg1-0.2 ii liblockfile11.14-1.1 ii libsasl2-2 2.1.27+dfsg-1 ii libssl1.1 1.1.1a-1 ii libtinfo6 6.1+20181013-1 ii mime-support3.61 ii netbase 5.5 ii sensible-utils 0.0.12 Versions of packages nmh recommends: ii ssmtp [mail-transport-agent] 2.64-8+b2 Versions of packages nmh suggests: pn exmh ii libmailtools-perl 2.18-1 ii libmime-tools-perl 5.509-1 pn mh-book pn mh-e pn par -- no debconf information
Bug#921019: arm64: Please provide sound modules for Allwinner A64 based systems
Package: linux-image-arm64 Version: 4.18+100 Severity: wishlist Hi! Please enable the following Kconfig symbols as modules: CONFIG_SND_SUN50I_CODEC_ANALOG CONFIG_SND_SUN8I_CODEC CONFIG_SND_SUN4I_I2S CONFIG_SND_SOC_SIMPLE_AMPLIFIER CONFIG_SND_SIMPLE_CARD These are necessary for sound support on pinebook, Olimex TERES-I, etc. The drivers are available upstream since 4.20. Pinebook has sound enabled in devicetree starting with 5.0 I'm currently working on enabling sound for TERES-I ... Also while looking into this I noticed the following quite general drivers, that might be reasonable to enable too: CONFIG_SND_SIMPLE_SCU_CARD CONFIG_SND_AUDIO_GRAPH_CARD CONFIG_SND_AUDIO_GRAPH_SCU_CARD CONFIG_SND_XEN_FRONTEND However I'm not aware of anybody using them on arm64, so enabling them is strictly optional. TIA, Harald -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.0.0-rc4+ (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-arm64 depends on: ii linux-image-4.18.0-3-arm64 4.18.20-2 linux-image-arm64 recommends no packages. linux-image-arm64 suggests no packages. -- no debconf information
Bug#909142: wicd-curses: Right-arrow on first wlan errors wicd-curses.py
Package: wicd-curses
Version: 1.7.4+tb2-6
Followup-For: Bug #909142
Dear Maintainer,
I ran into this issue too. (The same backtrace)
I'm not sure at which exact step caused the problem, but what I did
was:
1) Try to connect to an encrypted (WPA2) network - the only network
listed, ie the first one
2) Notice that wicd doesn't prompt me for the passphrase.
3) Entering the config screen with right arrow and setting the
passphrase
4) Trying to connect again
5) Turning the maschine off (got distracted)
6) Realize that I actually used the wrong passphrase
7) Turning the maschine on again
8) start wicd-curses
9) Trying to enter the setting screen again -> crash
In this state the crash was reproducible across reboots whenever I
tried
to enter the setting screen.
To fix this issue (for now) I did:
sudo service wicd stop
sudo rm /etc/wicd/wireless-settings.conf
sudo rm /var/lib/wicd/configurations/${offending network}
sudo service wicd start
It now works for me. Since the configuration files belong to the daemon
rather then the UI my best guess is that misconfiguration of encrypted
networks puts the daemon into some odd state where it sends garbage to
the UI, which the UI can't handle.
HTH,
Harald
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 4.18.0-3-arm64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wicd-curses depends on:
ii python2.7.15-3
ii python-urwid 2.0.1-2+b1
ii wicd-daemon 1.7.4+tb2-6
Versions of packages wicd-curses recommends:
ii sudo 1.8.26-2
wicd-curses suggests no packages.
Versions of packages wicd-daemon depends on:
ii adduser 3.118
ii dbus 1.12.10-1
ii debconf 1.5.69
ii iputils-ping 3:20180629-2
ii isc-dhcp-client 4.3.5-4+b1
ii lsb-base 10.2018112800
ii psmisc23.2-1
ii python2.7.15-3
ii python-dbus 1.2.8-2+b1
ii python-gobject-2 2.28.6-13+b1
ii python-wicd 1.7.4+tb2-6
ii udhcpc1:1.27.2-3
ii wireless-tools30~pre9-13
ii wpasupplicant 2:2.6-18
Versions of packages wicd-daemon recommends:
ii rfkill 2.32.1-0.1
Versions of packages wicd-daemon suggests:
pn pm-utils
Versions of packages python-wicd depends on:
ii net-tools 1.60+git20180626.aebd88e-1
ii python 2.7.15-3
Versions of packages python-wicd suggests:
pn ethtool
ii iproute2 4.18.0-2
-- debconf information:
* wicd/users: harald, olimex
--
If you want to support my work:
see http://friends.ccbib.org/harald/supporting/
or donate via peercoin to P98LRdhit3gZbHDBe7ta5jtXrMJUms4p7w
or CLAM xASPBtezLNqj4cUe8MT5nZjthRSEjrRQXN
Bug#881564: Olimex Teres-I support
Hi, looks like this bug is the inofficial "let's get debian working on Teres-I" thread. So let me point here to https://wiki.debian.org/InstallingDebianOn/Olimex/Teres-I and invite you to contribute to that page if you have additional experiences. I think at this time we have everything necessary in debian except for some u-boot patches to get simplefb up. TIA, Harald
Bug#892786: linux,arm64: please enable modules needed for teres-i OSHW laptop
Source: linux Version: 4.15.4-1 Severity: wishlist Hi, I have the TERES I open hardware laptop from olimex https://www.olimex.com/Products/DIY-Laptop/ running with buster, but I had to recompile the kernel to get all the modules necessary to have a useable system. Mainlineing the devicetree file for the teres is work in progress, (see: https://lkml.org/lkml/2018/3/12/653 ) but most of the missing bit's in the kernel config are needed for all Allwinner A64 based boards anyway - many of which already have upstream support. Please enable the following configuration symbols for arm64 builds: 1) Relevant to all A64 based systems and other SoCs using the AXP803 PMIC: at least: CONFIG_MFD_AXP20X=y CONFIG_MFD_AXP20X_RSB=y CONFIG_REGULATOR_AXP20X=m CONFIG_INPUT_AXP20X_PEK=m (note about builtin vs. module: This is the combination I tested. It should be possible to have everything as modules so long as mkinitramfs puts them into the initrd. In theory we also need the regulator module in the initrd to power up the supply chain of the MMC hosts. In practice MMCs are already powered up by the boot loader, but we need at least the mfd part of the pmic driver, to get the kernel probing the devices. You might want to draw the line between builtin and module drivers in a saner way. I can test your configuration, once you have made up your mind.) probably also (untested yet, but will be demanded in the future obviously): CONFIG_PINCTRL_AXP209=m CONFIG_CHARGER_AXP20X=m CONFIG_BATTERY_AXP20X=m CONFIG_AXP20X_POWER=m CONFIG_AXP288_FUEL_GAUGE=m CONFIG_AXP20X_ADC=m CONFIG_AXP288_ADC=m 2) Relevant to A64 based systems, driver available since long and likely going to be enabled by default in upstream devicetrees starting with 4.17: CONFIG_SUNXI_WATCHDOG=m 3) Relevant at least to A64 based systems with backlight. Probably at the moment only the teres-i laptop: CONFIG_PWM_SUN4I=m CONFIG_BACKLIGHT_PWM=m 4) Maybe not relevant at the moment, but might be a sane default to include anyway: CONFIG_LEDS_PWM=m BTW, as you might have inferred from my message, I'm a bit unsure how you decide which drivers to enable. Do you have a script, that scan's the device trees for required drivers (if so it clearly failed to find the drivers listed in (1)), or do you rely solely on users speaking up when something is missing? Any hints on how to efficiently report missing drivers or upcoming upstream changes would be appreciated. Thanks for your consideration, Harald
Bug#494372: Need more information about potential tc-prio(8) bug
Hi Andreas Henriksson! Appologies for never following up on this bug. I solved my problem back then the trial-and-error way and never had to use tc again, so never invested time into this. However reading the man page again, it actually makes sense now. What cleared thing up for me was the following sentence: "The priomap also allows you to list higher priorities (> 7) which do not correspond to TOS mappings, but which are set by other means." Now I see: The priomap maps from "Linux Priority" to Band not from TOS Bits. I guess what confused me was that the priomap has 16 entries which also is the number of possible TOS values. So actually there is no bug in the man page. Since we both had a hard time understanding it, maybe it should be improved. Or maybe is has already been improved over the past 10 years - after all it looks sufficiently clear to me now. I think, unless you have an idea how to explain things more naturally or unambiguous, this report can be closed. Thanks, Harald -- If you want to support my work: see http://friends.ccbib.org/harald/supporting/
Bug#873176: linux-image-armmp-lpae: Please add module for DHT11/DHT22 sensors
Ben Hutchings writes: > Control: reassign -1 src:linux tag -1 moreinfo > This driver appears to depend on Device Tree properties, but none of the > DTBs we build set those properties. It's not clear to me how it would be > usable. That's a fair point. The user will need to either add a node to the DTB on his system or have the bootloader apply a device tree fragment on top of the DTB installed by debian, which would work well with automatic updates of the kernel. (Or load a device tree fragment from userspace once debian supports dynamic DT.) Since updating the DTB is a lot easier then compiling the module for every update of the debian linux package (and security updates usually don't change the DTB anyway), I still feel providing the module would be useful. Thanks for considering my report, Harald
Bug#873176: linux-image-armmp-lpae: Please add module for DHT11/DHT22 sensors
Package: linux-image-armmp-lpae Version: 4.12+84 Severity: wishlist Dear Maintainer, the DHT22 sensors are quite popular temperature and humidity sensors. I'm the upstream driver author so I am biased but from my experience with bug reports many users seem to run custom compiled (and mostly outdated) kernels only because debian doesn't ship the kernel module for this sensor. Also I'm switching my systems using these sensors from OpenWRT to debian ATM so I'm directly affeced by this as well. Adding CONFIG_DHT11=m will be enough, however I'm less sure about the architectures to enable this: It will be mostly used on all variants of ARM but the driver works on any platform with native (ie fast enough for bit banging) GPIOs. Thanks for your consideration, Harald -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.12.0-1-armmp-lpae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-armmp-lpae depends on: ii linux-image-4.12.0-1-armmp-lpae 4.12.6-1 linux-image-armmp-lpae recommends no packages. linux-image-armmp-lpae suggests no packages. -- no debconf information
Bug#873038: linux-image-armmp-lpae: Please enable support for X-Powers AXP20X PMICs
Package: linux-image-armmp-lpae Version: 4.12+84 Severity: wishlist Dear Maintainer, please enable support for the PMICs from X-Powers. The drivers were added upstream in 4.12 and bring features like battery management to many allwinner bases systems. I think the following additions are necessary: CONFIG_AXP20X_ADC=m CONFIG_CHARGER_AXP20X=m CONFIG_BATTERY_AXP20X=m Also maybe CONFIG_GPIO_AXP209=m to support the GPIOs on the PMIC and CONFIG_AXP288_CHARGER=m CONFIG_AXP288_FUEL_GAUGE=m CONFIG_EXTCON_AXP288=m CONFIG_AXP288_ADC=m to bring power management to a different set of devices might be good ideas, but I have no hardware to test these so I don't dare to recommend it. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.12.0-1-armmp-lpae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-armmp-lpae depends on: ii linux-image-4.12.0-1-armmp-lpae 4.12.6-1 linux-image-armmp-lpae recommends no packages. linux-image-armmp-lpae suggests no packages. -- no debconf information
Bug#856388: xserver-xorg-video-vesa: screen is black though xserver itself works
Package: xserver-xorg-video-vesa Version: 1:2.3.4-1+b2 Severity: important Hi, I started X via startx and it decided to use the vesa driver - probably for the first time on this maschine. (See: Bug#855070) The X server itself works, ie. I can launch applications using key binding, but the screen remains entirely black. The backlight is on and the monitor reports 640x480 75Hz via its builtin menu. I don't see anything wrong in the log file other then that I'd hope to get a higher screen resolution. Please tell me if there is anything I can do to help debugging this. TIA, Harald -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Mar 25 2011 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Jan 20 00:22 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 04) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 4.9.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28) Xorg X server log files on system: -- -rw-r--r-- 1 root root 21485 Feb 15 00:59 /var/log/Xorg.1.log -rw-r--r-- 1 lambda lambda 7579 Feb 15 22:23 /home/lambda/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 49643 Feb 28 14:40 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 2262.890] X.Org X Server 1.19.1 Release Date: 2017-01-11 [ 2262.891] X Protocol Version 11, Revision 0 [ 2262.891] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 2262.891] Current Operating System: Linux stardust 4.9.0-1-686-pae #1 SMP Debian 4.9.6-3 (2017-01-28) i686 [ 2262.891] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-686-pae root=UUID=e3efea47-7349-4d1b-8346-751bbde3e43f ro quiet [ 2262.891] Build Date: 20 January 2017 02:28:45AM [ 2262.891] xorg-server 2:1.19.1-4 (https://www.debian.org/support) [ 2262.892] Current version of pixman: 0.34.0 [ 2262.892]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2262.892] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2262.893] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 28 14:40:20 2017 [ 2262.894] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 2262.894] (==) No Layout section. Using the first Screen section. [ 2262.894] (==) No screen section available. Using defaults. [ 2262.894] (**) |-->Screen "Default Screen Section" (0) [ 2262.894] (**) | |-->Monitor "" [ 2262.895] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 2262.895] (==) Automatically adding devices [ 2262.895] (==) Automatically enabling devices [ 2262.895] (==) Automatically adding GPU devices [ 2262.895] (==) Max clients allowed: 256, resource mask: 0x1f [ 2262.895] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 2262.895]Entry deleted from font path. [ 2262.895] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 2262.895]Entry deleted from font path. [ 2262.895] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 2262.895]Entry deleted from font path. [ 2262.895] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 2262.895]Entry deleted from font path. [ 2262.895] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 2262.895]Entry deleted from font path. [ 2262.896] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [ 2262.896] (==) ModulePath set to "/usr/lib/xorg/modules" [ 2262.896] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 2262.896] (II) Loader magic: 0x8032c720 [ 2262.896] (II) Module ABI versions: [ 2262.896]X.Org ANSI C Emulation: 0.4 [ 2262.896]X.Org Video Driver: 23.0 [ 2262.896]X.Org XInput driver : 24.1 [ 2262.896]X.Org Server Extension : 10.0 [ 2262.901] (++) using VT number 3 [ 2262.913] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_38 [ 2262.915] (--) PCI:*(0:0:2:0) 8086:1132:0e11:001a rev 4, Mem @ 0x4400/67108864, 0x4030/524288, BIOS @
Bug#855070: xserver-xorg-video-intel: fails to start after upgrade to stretch
Hi, I found out that if I 'modprobe i810' before executing 'startx', then the xserver actually starts normally. (I guess in (2) of my bug report, I didn't choose the right set of modules.) However all the issues mentioned in this report still stand. In particular the xserver shouldn't crash that badly because of a missing kernel module. I'm not sure which package's fault this is, though. HTH, Harald -- If you want to support my work: see http://friends.ccbib.org/harald/supporting/
Bug#855070: xserver-xorg-video-intel: fails to start after upgrade to stretch
Package: xserver-xorg-video-intel Version: 2:2.99.917+git20161206-1 Severity: important Hi, I have been using the xserver-xorg-video-intel driver on this machine for many years and across serveral debian releases withouth problems. After upgrading the machine from stable to stretch, X stopped working. There are a number of problems involved, please clone this bug report as you see fit. What happened in detail: 1) after the upgrade the intel driver isn't probed anymore: This machine was running without xorg.conf for a long time, but after the upgrade, it wouldn't even try to use the intel driver. (Falling back to vesa, which isn't working either, but that's a different issue.) No idea, why that is the case, but copying the example xorg.conf from /usr/share/doc/xserver-xorg-video-intel/xorg.conf solved this problem. But ... 2) I'm usually starting X as user with startx, but now this aborts with a number of error messages: It can't load the drm kernel modules -> fixed by manual modprobe and can't access /dev/agpgart -> solved by installing xserver-xorg-legacy The last lines of the log without the -legacy package are [ 2026.930] (II) Loading sub module "int10" [ 2026.930] (II) LoadModule: "int10" [ 2026.930] (II) Loading /usr/lib/xorg/modules/libint10.so [ 2026.930] (II) Module int10: vendor="X.Org Foundation" [ 2026.930]compiled for 1.19.1, module version = 1.0.0 [ 2026.930]ABI class: X.Org Video Driver, version 23.0 [ 2026.931] (II) intel(0): initializing int10 [ 2026.931] (EE) intel(0): Cannot read int vect [ 2026.931] (II) intel(0): this driver cannot do DDC without VBE [ 2026.931] (--) intel(0): Integrated Graphics Chipset: Intel(R) i815 [ 2026.931] (--) intel(0): Linear framebuffer at 0x4400 [ 2026.931] (--) intel(0): IO registers at addr 0x4030 [ 2026.931] (EE) GARTInit: Unable to open /dev/agpgart (Permission denied) [ 2026.931] (EE) intel(0): AGP GART support is not available. Make sure your kernel has agpgart support or that the agpgart kernel module is loaded. [ 2026.932] (II) UnloadModule: "intel" [ 2026.932] (II) UnloadSubModule: "int10" [ 2026.932] (II) Unloading int10 [ 2026.932] (II) UnloadSubModule: "vbe" [ 2026.932] (II) Unloading vbe [ 2026.932] (II) UnloadSubModule: "vgahw" [ 2026.932] (II) Unloading vgahw [ 2026.932] (EE) Screen(s) found, but none have a usable configuration. [ 2026.932] (EE) Fatal server error: [ 2026.932] (EE) no screens found(EE) [ 2026.932] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 2026.933] (EE) Please also check the log file at "/home/lambda/.local/share/xorg/Xorg.0.log" for additional information. [ 2026.933] (EE) [ 2026.939] (EE) Server terminated with error (1). Closing log file. This package should probably depend on or at least recommend xserver-xorg-legacy. 3) However with xserver-xorg-legacy installed the real trouble started. The xserver seems to start but immediatly crashes and even fails to print a proper backtrace (see the included log). The screen is gone (ie. can't be switched back to text mode by any means I know) but the keyboard works ok. I don't even know where to start debugging this. However all the issues described can be reproduced reliably. Any help appreciated. TIA, Harald -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Mar 25 2011 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Jan 20 00:22 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 04) Xorg X server configuration file status: -rw-r--r-- 1 root root 93 Feb 13 17:10 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "Device" Identifier "Intel" Driver "intel" # Option "AccelMethod" "uxa" EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 4.9.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28) Xorg X server log files on system: -- -rw-r--r-- 1 root root 47889 Jan 23 2015 /var/log/Xorg.1.log -rw-r--r-- 1 lambda lambda 7602 Feb 13 18:00 /home/lambda/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 41763 Feb 13 18:05 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 2370.667] X.Org X Server 1.19.1 Release Date: 2017-01-11 [ 2370.667] X Protocol Version 11, Revision 0 [
Bug#806800: [lcdproc/lcdproc] LCDd floods syslog with critical messages (#45)
On 14.01.2017 11:49, Dominique Dumont wrote: Do you know why anarcat got logs at "critical" level ? (which is indeed a bit overboard) Too me his problems look like corruption of some data structures or the stack or whatever. This could be caused by a buffer overflow somewhere or tempering with the binary or a number of other things. I don't think there is any way to narrow this down other then running LCDd inside a debugger... HTH, Harald -- If you want to support my work: see http://friends.ccbib.org/harald/supporting/ or donate via peercoin to P98LRdhit3gZbHDBe7ta5jtXrMJUms4p7w or CLAM xASPBtezLNqj4cUe8MT5nZjthRSEjrRQXN
Bug#806800: [lcdproc/lcdproc] LCDd floods syslog with critical messages (#45)
On 08.01.2017 15:53, Dominique Dumont wrote:
In [bug
806800](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806800), a
Debian user reports:
Looking at the bug report, it seems that LCDd logs to syslog because
it was started with `-s 1`
```
LCDd seems to send critical syslog messages on some weird
situations. I don't know why. Here's an example of a tail on a
logfile:
Message from syslogd@marcos at Dec 1 10:16:06 ...
sten L
Message from syslogd@marcos at Dec 1 10:16:06 ...
nore L
déc 01 10:16:05 marcos LCDd[11778]: ignore I
déc 01 10:16:05 marcos LCDd[11778]: listen NT
déc 01 10:16:05 marcos LCDd[11778]: ignore NT
déc 01 10:16:05 marcos LCDd[11778]: listen M
déc 01 10:16:05 marcos LCDd[11778]: ignore M
déc 01 10:16:05 marcos LCDd[11778]: listen L
déc 01 10:16:05 marcos LCDd[11778]: ignore L
Notice how you got `Message` lines above? Those flood *all* terminals
I am connected to - not just the one where i was tailing the
logfile. oddly enough, part of that message is stripped as well
("listen" becomes "sten" and "ignore" becomes "nore", not sure why).
```
Here I don't fully understand what he says: He is getting a number of
valid listen/ignore messages to syslog with the proper level, but
occasionally there are critical messages, that are mangled?
In this case there seems to be some serious corruption of data
structures, i.e. something not obvious from reading the source code.
I think the only way forward is to run LCDd from within a debugger.
```
I wonder if this isn't connected to the vsyslog call:
vsyslog(LOG_USER | (level + 2), format, ap);
This seems to bump up the level, which could distort the levels...
```
While the code is clearly fishy (non-portable) it is actually correct
at least on debian systems.
HTH,
Harald
--
If you want to support my work:
see http://friends.ccbib.org/harald/supporting/
or donate via peercoin to P98LRdhit3gZbHDBe7ta5jtXrMJUms4p7w
or CLAM xASPBtezLNqj4cUe8MT5nZjthRSEjrRQXN
Bug#803402: nmh: bad interaction with mime-support
Alexander Zangerl writes: > On Sun, 08 Nov 2015 15:18:22 +0100, Harald Geyer writes: > >"run-mailcap --action=view" is meant to start a pager, which is not > >what mhshow wants to do. > > why not? where does it say that? I don't know if this is written down anywhere, but it can be infered from the fact that mhshow does start a pager of its own. > view is meant to do whatever is necessary to present the material to > the user. Agreed. > >mhshow wants formatted output that can be > >passed on to it's own pager (moreproc). > > not necessarily; look at the examples in man mhshow for, say, audio > or image/*: > > mhshow-show-audio/basic: raw2audio 2>/dev/null | play > mhshow-show-image: xv %f > mhshow-show-application/PostScript: lpr -Pps Well, these of course can not be displayed in a pager in the first place ... > there is no paging by nmh involved in any of these. there is nothing > in the mhshow docs that indicates that a pager supplied by mhshow must > be used. I haven't read the source of mhshow, but from what I have seen with strace (yes, actually needed strace to figure out what's wrong) it looks to me like mhshow always fires up moreproc to display the headers *and* any text/* parts after they have been filtered by the respective command from mhn.defaults - I think this implies that mhshow expects the entries in mhn.defaults to behave as filters - at least if X is not available. > >x/console/whatever use, but nmh (and sensible-tools) are messing > >things up, because they try to do part of the job themselfs. I think > >the easy way to fix this is to dump run-mailcap down so it doesn't > >interfere with what nmh is doing. > > to be honest i have not yet seen any of the interference problems > you're having. with the default mhn.defaults, no special .mh_profile entries > whatsoever, and a pure html email (yuck), for me mhshow > > a) fires up my real browser if i have a $DISPLAY, Yes. > b) falls back to showing me the transmogrified text (via w3m) > and paged by less if there is no $DISPLAY. Looks like w3m is smarter than links2 and doing the right thing when stdout is not a terminal. > if i switch the mhn.defaults to --action=cat, then case a) never > happens anymore, because action cat ignores all mailcap entries but the > ones with 'copiousoutput' and not many have that set, Yes, but I have proposed a solution to that in my original message, in case you acutally think this is desired. > and in the remaining case b) no paging whatsoever is performed. This is not true. The paging is done by moreproc (less on my system). If this is not the case on your system, then I see where your opposition is coming from. However I belive something else must be broken in that case. > i find this latter setup highly undesirable. > > >I think your explanation in the News.Debian is a good one. > > ok, then i'll expand that in the next upload to mention that people > should also consider run-mailcap --action=cat as alternative to > the defaults... > > >configuration probably works on many sytems - but only by chance, not > >by being right. > > ...because i disagree with your opinion that there is > anything wrong with delegating show actions to run-mailcap --action=view. I think we are not yet disagreeing about opinion, we are still disagreeing about facts (ie when is moreproc fired up). Let's first sort out the facts, then move on to opinions. > so, shall we agree to disagree? i just don't think there's a single > setup that'll match everybody's preferences. I believe this is not about my preferences (that's what config files are for) but about software compatibility. And software compatibility is a matter of debian packaging. Obviously I had a bad start at explaining what the issue is - it's your decision if the issue is worth fixing (ie tag the bug report wontfix), but I want you to actually see the issue first. (Once we are there, maybe you can tell me how I could have presented the issue better.) HTE, Harald
Bug#803402: nmh: bad interaction with mime-support
Alexander Zangerl writes: > On Thu, 29 Oct 2015 17:34:43 +0100, Harald Geyer writes: > >The actual problem: > >When I mhshow a message with a text/html part on the linux virtual > >terminal, the current mhn.defaults invokes "run-mailcap --action=view", > >which in turn invokes sensible-browser, which on my system happens to > >produce output not suitable for display in a pager - ie lots of > >escape sequences. > > the fact that run-mailcap may or may not produce ideal output for terminal > or paged use isn't nmh's problem. I think correctly using run-mailcap semantics is nmh's problem: "run-mailcap --action=view" is meant to start a pager, which is not what mhshow wants to do. mhshow wants formatted output that can be passed on to it's own pager (moreproc). There is a way to get the output expected by mhshow: run-mailcap --action=cat > i most definitely don't want nmh to depend on particular browsers > or blob viewers, so i set the default mhn.defaults to the really > low common denominator of run-mailcap. Agreed. > as this is just the default mhn config, nothing keeps people from > overriding this with their personal variations that are finetuned for > x/console/whatever use. Actually run-mailcap is an effort to seamlessly support x/console/whatever use, but nmh (and sensible-tools) are messing things up, because they try to do part of the job themselfs. I think the easy way to fix this is to dump run-mailcap down so it doesn't interfere with what nmh is doing. > personally i think the NEWS.Debian that i added to 1.6-6 does spell out > the options sufficiently well, but i'm certainly open to suggestions > to make this more obvious. I think your explanation in the News.Debian is a good one. However since the differene between "run-mailcap --action=view" and "run-mailcap --action=cat" is somewhat subtle it took me a while to figure out, what's actually wrong. And I think the current default configuration probably works on many sytems - but only by chance, not by being right. If you think that this problem should be fixed in the mime-support or sensible-tools packages, then please reassign the bug there instead of closing it. HTE, Harald
Bug#803402: nmh: bad interaction with mime-support
Package: nmh
Version: 1.6-2
Severity: normal
Hi,
first of all I think nmh should depend on mime-support, as it is using
run-mailcap in mhn.defaults. Yes I could file an extra bug for that, but
I know Alexander will pick this up here as well.
The actual problem:
When I mhshow a message with a text/html part on the linux virtual
terminal, the current mhn.defaults invokes "run-mailcap --action=view",
which in turn invokes sensible-browser, which on my system happens to
produce output not suitable for display in a pager - ie lots of
escape sequences.
There are a number of things going wrong in this szenario, and I'm
not sure which ones should be reported as bugs:
Involved browser shouldn't output escape sequences if not attached
to a terminal and I guess it is particularly hard to write a correct
mailcap entry for sensible-browser as it can start an application either
in X or in a terminal.
On the nmh side, mhshow probably shouldn't use --action=view if the output
is acutally displayed in a pager. I changed this to --action=cat and
got the correct behavior. However this has a side effect: Under X the
message is still shown in a pager and not in a browser window. I like the
side effect, but if this is not desired then maybe something like
--action=$(if test $DISPLAY; then echo view; else echo cat; fi) or
a wrapper is necessary.
HTH,
Harald
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nmh depends on:
ii libc6 2.19-18+deb8u1
ii libdb5.3 5.3.28-9
ii liblockfile1 1.09-6
ii libsasl2-22.1.26.dfsg1-13+deb8u1
ii libssl1.0.0 1.0.1k-3+deb8u1
ii libtinfo5 5.9+20140913-1+b1
ii netbase 5.3
Versions of packages nmh recommends:
ii exim4-daemon-light [mail-transport-agent] 4.84-8
Versions of packages nmh suggests:
pn exmh
ii libmailtools-perl 2.13-1
ii libmime-tools-perl 5.505-1
pn mh-book
pn mh-e
ii par 1.52-3
-- Configuration Files:
/etc/nmh/mhl.headers changed:
; mhl.headers
;
; Default format file for displaying headers in
; MIME messages. mhn calls the mhlproc with this
; filter to display message header.
;
overflowtext="***",overflowoffset=5
leftadjust,compwidth=9
ignores=msgid,message-id,received,content-type,content-transfer-encoding,content-id,x-ui-filterresults,dkim-signature,x-spam-report
Date:formatfield="%<(nodate{text})%{text}%|%(pretty{text})%>"
To:
cc:
From:decode
Subject:decode
:
extras:nocomponent
:
/etc/nmh/mhl.reply changed:
; mhl.reply
;
; default message filter for `repl' (repl -format)
;
;from:nocomponent,formatfield="%(decode(friendly{text})) writes:"
body:nocomponent,format,nowrap,formatarg="%(trim{content-type})%(putstr)",formatarg="%(trim{content-transfer-encoding})%(putstr)",formatarg=">
"
/etc/nmh/mhn.defaults changed:
mhshow-show-application: run-mailcap --action=view 'application/%s:%F'
mhshow-show-text: run-mailcap --action=cat 'text/%s:%F'
mhshow-show-text/plain: %lsensible-pager %F
mhshow-show-audio: run-mailcap --action=view 'audio/%s:%F'
mhshow-show-image: run-mailcap --action=view 'image/%s:%F'
mhshow-show-message: run-mailcap --action=view 'message/%s:%F'
mhshow-show-message/rfc822: %lshow -file %F
mhshow-show-video: run-mailcap --action=view 'video/%s:%F'
mhshow-suffix-application/msword: .doc
mhshow-suffix-application/ogg: .ogg
mhshow-suffix-application/onenote: .onepkg
mhshow-suffix-application/onenote: .onetmp
mhshow-suffix-application/onenote: .onetoc
mhshow-suffix-application/onenote: .onetoc2
mhshow-suffix-application/pdf: .pdf
mhshow-suffix-application/postscript: .ps
mhshow-suffix-application/rtf: .rtf
mhshow-suffix-application/vnd.ms-excel.addin.macroEnabled.12: .xlam
mhshow-suffix-application/vnd.ms-excel.sheet.binary.macroEnabled.12: .xlsb
mhshow-suffix-application/vnd.ms-excel.sheet.macroEnabled.12: .xlsm
mhshow-suffix-application/vnd.ms-excel.template.macroEnabled.12: .xltm
mhshow-suffix-application/vnd.ms-excel: .xla
mhshow-suffix-application/vnd.ms-excel: .xlc
mhshow-suffix-application/vnd.ms-excel: .xld
mhshow-suffix-application/vnd.ms-excel: .xll
mhshow-suffix-application/vnd.ms-excel: .xlm
mhshow-suffix-application/vnd.ms-excel: .xls
mhshow-suffix-application/vnd.ms-excel: .xlt
mhshow-suffix-application/vnd.ms-excel: .xlw
mhshow-suffix-application/vnd.ms-powerpoint.addin.macroEnabled.12: .ppam
mhshow-suffix-application/vnd.ms-powerpoint.presentation.macroEnabled.12: .pptm
mhshow-suffix-application/vnd.ms-powerpoint.slide.macroEnabled.12: .sldm
mhshow-suffix-application/vnd.ms-powerpoint.slideshow.macroEnabled.12: .ppsm
mhshow-suffix-application/vnd.ms-powerpoint.template.macroEnabled.12: .potm
Bug#779040: fake-hwclock: does not run at shutdown
Alexandre Detiste writes: [...] here is an exercpt from the last version of this service file I found in /etc; the only things I tweaked further are the Before=systemd-journald.service because I didn't liked seeing 1970-01-01 in the journal and Conflicts=shutdown.target, this line may actually helps you solve your problem. /lib/systemd/system/systemd-timesyncd.service also includes the same Conflicts=. --- [Unit] Description=Restore / save the current clock Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=systemd-journald.service Conflicts=shutdown.target Indeed, the following patch fixes the issue I have reported for me: --- fake-hwclock.service.orig 2015-03-03 12:49:11.32451 +0100 +++ fake-hwclock.service2015-03-03 12:45:30.54823 +0100 @@ -3,6 +3,7 @@ Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=sysinit.target +Conflicts=shutdown.target [Service] EnvironmentFile=-/etc/default/fake-hwclock Your other suggestion might be useful too. Thanks to both of you for your help. Harald
Bug#779040: fake-hwclock: does not run at shutdown
Package: fake-hwclock Version: 0.8 Severity: important Dear Maintainer, I'm using fake-hwclock on a cubieboard to keep my time monotonic. The following things work: Restoring the saved time at boot. Saving the system time once per hour. The following doesn't work: Saving the system time at shutdown or reboot. This leads to fsck running everytime the system starts, because time is not monotonic. I tried to look into this a bit but alas I'm not yet familiar enough with systemd to see what is going wrong. (And I won't have a serial console available in the next days.) So if you need more information to make sense of this, you will need to tell me how to aquire it. TIA, Harald -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.16.0-4-armmp (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fake-hwclock depends on: ii init-system-helpers 1.22 fake-hwclock recommends no packages. Versions of packages fake-hwclock suggests: ii cron [cron-daemon] 3.0pl1-127 pn ntp none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775748: installation-report: alternative installation method on cubieboard
Package: installation-reports
Version: 2.57
Severity: normal
Dear Maintainer,
I see that there is already an installation report for cubieboard,
but as I tried a different approach for booting the installer than
recommended on https://wiki.debian.org/InstallingDebianOn/Allwinner
is think it might be useful to document it here.
The basic idea is to have uboot laod the kernel and initrd of the installer
from it's own boot partition instead of the network. Using preseeding
to get the network up, it is possible to install debian without
having a serial console around.
See below for details and config snippets.
-- Package-specific info:
Boot method: mmc
Image version: http://d-i.debian.org/daily-images/armhf/daily/netboot
Date: 20150119
Machine: cubieboard1
Partitions:
Disk /dev/mmcblk0: 7,4 GiB, 7969177600 bytes, 15564800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8d80bbc6
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 499711 497664 243M 83 Linux
/dev/mmcblk0p2 499712 14798847 14299136 6,8G 83 Linux
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card:[ ]
Configure network: [ ]
Detect CD: [ ]
Load installer modules: [O]
Clock/timezone setup: [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system:[O]
Install tasks: [O]
Install boot loader:[O]
Overall install:[O]
Comments/Problems:
Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.
On sunxi we have to prepare an SD card with uboot ourselves (no ready
image available), so I used the instructions and files from openwrt,
but modified the uEnv.txt like this to load the installer:
fdt_addr=0x4300
loaddtb=fatload mmc 0 ${fdt_addr} dtb
ramdisk_addr_r=0x4800
loadramdisk=fatload mmc 0 ${ramdisk_addr_r} initrd.gz
kernel_addr_r=0x4700
loadkernel=fatload mmc 0 ${kernel_addr_r} vmlinuz
bootargs=console=ttyS0,115200 --- DEBIAN_FRONTEND=text
uenvcmd=run loadkernel run loaddtb run loadramdisk fdt addr
${fdt_addr} 0x4 bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize}
${fdt_addr}
I copied vmlinuz and a modified initrd.gz from d-i/netboot to the
boot partition. The initrd.gz was modified to include a preseed.cfg
to load network-console, because I wouldn't have a serial cable available
at installation time.
However from the preseed templates available online I had a hard time
figuring out a working configuration. This is what finally worked for
me. Maybe a few lines are unnecessary:
d-i auto-install/enable boolean true
d-i netcfg/use_autoconfig boolean false
d-i netcfg/disable_autoconfig boolean true
d-i netcfg/link_wait_timeout string 60
d-i netcfg/choose_interface select eth0
d-i netcfg/get_ipaddress string 192.168.11.54
d-i netcfg/get_netmask string 255.255.255.0
d-i netcfg/get_gateway string 192.168.11.52
d-i netcfg/get_nameservers string 8.8.8.8
d-i netcfg/confirm_static boolean true
d-i netcfg/get_hostname string debian
d-i netcfg/get_domain string unassigned-domain
d-i netcfg/hostname string debian
d-i mirror/protocol string http
d-i mirror/country string manual
d-i mirror/http/countries string manual
d-i mirror/http/hostname string 192.168.11.52:
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string
d-i anna/choose_modules string network-console
d-i network-console/authorized_keys_url string http://192.168.11.52/openssh-key
d-i network-console/password password r00tme
d-i network-console/password-again password r00tme
Especially the following lines were not obviously necessary when reading
the templates:
d-i netcfg/use_autoconfig boolean false
d-i netcfg/disable_autoconfig boolean true
d-i netcfg/link_wait_timeout string 60
d-i mirror/country string manual
The rest of the installation was quite normal:
I removed the swap partition suggested by guided partitioning because
I don't want to wear out the SD card.
Before booting into the new system I copied the ssh-key used for
network-console to my users .ssh/authorized_keys - that could have
been offered by the installer.
When booting into the newly installed system I installed the package
fake-hwclock because cubieboard has no backup battery for the rtc.
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to sub...@bugs.debian.org.
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
Bug#739597: docx2txt: missing dependency on unzip
Package: docx2txt Version: 1.2-1 Severity: serious Justification: Policy 3.5 After trying to view a docx file I got the following error message: Failed to locate unzip command '/usr/bin/unzip'! -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728741: nmh: please suggest packages necessary for replyfilter
Package: nmh Version: 1.5-release-0.2 Severity: wishlist The subject line pretty much says it all: There is the replyfilter script provided in doc/contrib, which needs the package 'par' and a number of perl libraries installed to work. However it wasn't that easy for me to figure out which libraries exactly are necessary. Having these packages suggested (or even recommended) via dependencies, would have helped me a lot. Thanks, Harald -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nmh depends on: ii libc6 2.13-38 ii libdb5.1 5.1.29-5 ii liblockfile1 1.09-5 ii libsasl2-22.1.25.dfsg1-6+deb7u1 ii libssl1.0.0 1.0.1e-2 ii libtinfo5 5.9-10 ii netbase 5.0 Versions of packages nmh recommends: ii exim4-daemon-light [mail-transport-agent] 4.80-7 Versions of packages nmh suggests: pn exmh none pn mh-book none pn mh-e none -- Configuration Files: /etc/nmh/mhl.headers changed [not included] /etc/nmh/mhl.reply changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680486: installation-reports: fails to install via approx mirror
Package: installation-reports Severity: important Dear Maintainer, I tried to install kfreebsd-i386, which was largely successful with two glitches: 1) I selected german keyboard layout, which was completly ignored. I see this has already been reported in other reports, so I'll focus on the other issue. 2) Since mz internet connection is somewhat flaky I usuallz install via a local approx mirror. This never caused anz problems so far (on i386, powerpc) but as this is my first installation of wheeyz I can't tell for sure if the following is related to kfreebsd or is a new bug affecting all archs... The installer correctlz downloaded it's additional components via approx. Also installation of the base szstem was without problems, but late in the installation procedure, when trying to install more software (most notably grub without which the installation won't complete) the installer failed to retrieve the package list of the full kfreebsd-i386 archive. As a workaround I chrooted into /target and installed grub-pc via aptitude. As aptitude worked fine (using the same mirror) I'm prettz confindent, that the mirror setup is ok, but the problem is some incompatibilitz between approx and the wheezy installer. Actuallz I didn't trz installing without approx so I can't know for sure if the issue is reallz related to approx, but I can't think of anzthing else special about mz setup. So unless the installer is broken for everybody, it likely is approx. -- Package-specific info: Boot method: network Image version: Installer build: 20120508 Date: 20120705 Machine: Acer TravelMate 529ATX Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [E] Install boot loader:[E] Overall install:[O] Comments/Problems: Comments are alreadz at the beginning of this report. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/kFreeBSD installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20120508 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: GNU/kFreeBSD rosetta 8.3-1-486 #0 Tue Apr 10 20:24:01 UTC 2012 i386 GNU/Linux lspci -nn: 00:00.0 Host bridge [0600]: ALi Corporation M1621 [10b9:1621] (rev 05) lspci -nn: 00:01.0 PCI bridge [0604]: ALi Corporation PCI to AGP Controller [10b9:5247] (rev 01) lspci -nn: 00:06.0 Multimedia audio controller [0401]: ALi Corporation M5451 PCI AC-Link Controller Audio Device [10b9:5451] (rev 01) lspci -nn: 00:07.0 ISA bridge [0601]: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] [10b9:1533] lspci -nn: 00:0a.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 08) lspci -nn: 00:10.0 IDE interface [0101]: ALi Corporation M5229 IDE [10b9:5229] (rev c3) lspci -nn: 00:11.0 Bridge [0680]: ALi Corporation M7101 Power Management Controller [PMU] [10b9:7101] lspci -nn: 00:13.0 CardBus bridge [0607]: O2 Micro, Inc. OZ6933/711E1 CardBus/SmartCardBus Controller [1217:6933] (rev 01) lspci -nn: 00:13.1 CardBus bridge [0607]: O2 Micro, Inc. OZ6933/711E1 CardBus/SmartCardBus Controller [1217:6933] (rev 01) lspci -nn: 00:14.0 USB controller [0c03]: ALi Corporation USB 1.1 Controller [10b9:5237] (rev 03) lspci -nn: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Rage Mobility P/M AGP 2x [1002:4c4d] (rev 64) lspci -nn: 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) usb-list: Error: directory /sys/bus does not exist; is sysfs mounted? kldstat: Id Refs AddressSize Name kldstat: 1 11 0xc040 a3a000 kfreebsd.gz kldstat: 21 0xc4c51000 1ext2fs.ko kldstat: 31 0xc4c64000 181000 zfs.ko kldstat: 41 0xc4de5000 3000 opensolaris.ko df: Filesystem 1K-blocks Used Available Use% Mounted on df: /dev/md0 42527 29147 13380 69% / df: devfs1 1 0 100% /dev df: devfs1 1 0 100% /dev df: fdescfs 1 1 0 100% /dev/fd df: linprocfs4
Bug#680491: xserver-xorg: segfaults at startup
Package: xserver-xorg Version: 1:7.7+1 Severity: important Dear Maintainer, this is the first time I install Debian on this machine, so I don't know if older versions would have worked nor do I know if this is specific to kfreebsd: I tried starting X via startx and got a segfault as can be seen in the log below. Also note the DRM related error message... If I find the time, I'll try to install again with linux kernel and followup on this. (Should there be anything more productive I could do on this, then I'm in for it of course.) BTW: I read in some other report, that a user had similar problems that went away when running as root. So I tried running as root, but still got the segfault it this case. -- Package-specific info: X server symlink status: lrwxr-xr-x 1 root root 13 Jul 5 21:53 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1991060 May 20 13:23 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 2.6.16 (d...@freebsd.org) (gcc version 4.6.3) #4 Sun Dec 18 04:30:00 CET 1977 Xorg X server log files on system: -- -rw-r--r-- 1 root root 35715 Jul 5 22:40 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 3920.977] X.Org X Server 1.12.1.902 (1.12.2 RC 2) Release Date: 2012-05-19 [ 3920.978] X Protocol Version 11, Revision 0 [ 3920.978] Build Operating System: GNU/kFreeBSD 8.1-1-686 i686 Debian [ 3920.978] Current Operating System: GNU/kFreeBSD rosetta 9.0-1-686 #0 Fri Jun 15 17:33:32 UTC 2012 i386 [ 3920.978] Build Date: 20 May 2012 10:36:25AM [ 3920.978] xorg-server 2:1.12.1.902-1 (Cyril Brulebois k...@debian.org) [ 3920.978] Current version of pixman: 0.24.4 [ 3920.978]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 3920.978] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 3921.005] (==) Log file: /var/log/Xorg.0.log, Time: Thu Jul 5 22:40:40 2012 [ 3921.121] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 3921.130] (==) No Layout section. Using the first Screen section. [ 3921.130] (==) No screen section available. Using defaults. [ 3921.130] (**) |--Screen Default Screen Section (0) [ 3921.130] (**) | |--Monitor default monitor [ 3921.153] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 3921.153] (==) Automatically adding devices [ 3921.153] (==) Automatically enabling devices [ 3921.179] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 3921.179]Entry deleted from font path. [ 3921.179] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [ 3921.179]Entry deleted from font path. [ 3921.179] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [ 3921.179]Entry deleted from font path. [ 3921.180] (WW) The directory /usr/share/fonts/X11/Type1 does not exist. [ 3921.180]Entry deleted from font path. [ 3921.180] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [ 3921.180]Entry deleted from font path. [ 3921.180] (WW) The directory /usr/share/fonts/X11/75dpi does not exist. [ 3921.180]Entry deleted from font path. [ 3921.180] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [ 3921.180]Entry deleted from font path. [ 3921.180] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 3921.180] (==) ModulePath set to /usr/lib/xorg/modules [ 3921.180] (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. [ 3921.180] (II) Loader magic: 0x8229580 [ 3921.180] (II) Module ABI versions: [ 3921.180]X.Org ANSI C Emulation: 0.4 [ 3921.180]X.Org Video Driver: 12.0 [ 3921.180]X.Org XInput driver : 16.0 [ 3921.180]X.Org Server Extension : 6.0 [ 3921.201] (--) PCI:*(0:1:0:0) 1002:4c4d:1025:1010 rev 100, Mem @ 0x8100/16777216, 0x8060/4096, I/O @ 0x8000/256, BIOS @ 0x/65536 [ 3921.202] (II) LoadModule: extmod [ 3921.237] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [ 3921.275] (II) Module extmod: vendor=X.Org Foundation [ 3921.275]compiled for 1.12.1.902, module version = 1.0.0 [ 3921.276]Module class: X.Org Server Extension [ 3921.276]ABI class: X.Org Server Extension, version 6.0 [ 3921.276] (II) Loading extension MIT-SCREEN-SAVER [ 3921.276] (II) Loading
Bug#680486: installation-reports: fails to install via approx mirror
Followup to my own bug report: I just installed linux-i386 on the same machine using the same mirror setup and the installer with the same build date. Everything went well this time, so the issue seems kfreebsd related. HTH, Harald -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630425: python2.6-minimal: textwrap - breaks lines at non-breakable unicode spaces
Package: python2.6-minimal
Version: 2.6.6-8+b1
Severity: normal
Tags: upstream
The problem lies in the following definitions in textwrap.py:
wordsep_simple_re = re.compile(r'(\s+)')
wordsep_re = re.compile(
r'(\s+|' # any whitespace
r'[^\s\w]*\w+[^0-9\W]-(?=\w+[^0-9\W])|' # hyphenated words
r'(?=[\w\!\\'\\.\,\?])-{2,}(?=\w))') # em-dash
self.wordsep_re_uni = re.compile(self.wordsep_re.pattern, re.U)
self.wordsep_simple_re_uni = re.compile(
self.wordsep_simple_re.pattern, re.U)
Since in unicode mode \s matches any whitespace - even non-breakable
one - the regexp generates false positives.
As a workaround I have replaced \s by normal space, but of course this
breaks textwrap if the replace_whitespace option is set to false...
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python2.6-minimal depends on:
ii libc6 2.11.2-10Embedded GNU C Library: Shared lib
ii libssl0.9.8 0.9.8o-4squeeze1 SSL shared libraries
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages python2.6-minimal recommends:
ii python2.6 2.6.6-8+b1 An interactive high-level object-o
Versions of packages python2.6-minimal suggests:
pn binfmt-supportnone (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622902: sisu: Unclear how to get latex output
Package: sisu Version: 2.7.9-1 Severity: normal The package description and the man page both claim that sisu can produce latex code. But from the documentation I don't see how to call sisu to actually get there. If I try to generate PDF output then latex code probably gets generated in some temporary file, but gets deleted afterwards. Sorry if I'm missing something obvious. -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: powerpc (ppc) Kernel: Linux 2.6.32-5-powerpc Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sisu depends on: ii libruby [libwebrick-ruby] 4.5Libraries necessary to run Ruby 1. ii rsync 3.0.7-2fast remote file copy program (lik ii ruby 4.5An interpreter of object-oriented ii unzip 6.0-4 De-archiver for .zip files ii zip 3.0-3 Archiver for .zip files Versions of packages sisu recommends: ii imagemagick 8:6.6.0.4-3 image manipulation programs ii keychain2.6.8-2 key manager for OpenSSH ii librmagick-ruby 2.13.1-2 ImageMagick API for Ruby ii libruby [librexml-ruby] 4.5 Libraries necessary to run Ruby 1. ii openssh-client 1:5.5p1-6secure shell (SSH) client, for sec ii openssl 0.9.8o-4squeeze1 Secure Socket Layer (SSL) binary a pn sisu-pdfnone (no description available) pn sisu-postgresql none (no description available) pn sisu-sqlite none (no description available) ii tidy20091223cvs-1HTML syntax checker and reformatte pn vim-addon-manager none (no description available) Versions of packages sisu suggests: pn calibre none (no description available) pn lvnone (no description available) pn pinfo none (no description available) ii texinfo 4.13a.dfsg.1-6 Documentation system for on-line i pn trang none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614419: installation-reports: kfreebsd-i386 netboot installer doesn't detect ethernet device
Hi! Thanks for your fast response. You can find info on what happens in the installation on console 4 and you have the install log /var/log/installer/syslog) Can you send the install log (gzipped) ? I found some logs in /var/log/syslog and it's just a few kB, so sending it inline: Feb 25 22:37:48 syslogd started: BusyBox v1.17.1 Feb 25 22:37:48 kernel: /proc/sys/kernel/printk: No such file or directory Feb 25 22:37:48 kernel: klogd started: BusyBox v1.17.1 (Debian 1:1.17.1-8) Feb 25 22:37:48 kernel: Copyright (c) 1992-2010 The FreeBSD Project. Feb 25 22:37:48 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Feb 25 22:37:48 kernel: The Regents of the University of California. All rights reserved. Feb 25 22:37:48 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Feb 25 22:37:48 kernel: #0 Tue Jan 4 16:41:50 UTC 2011 i386 Feb 25 22:37:48 kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Feb 25 22:37:48 kernel: CPU: Intel Pentium III (996.77-MHz 686-class CPU) Feb 25 22:37:48 kernel: Origin = GenuineIntel Id = 0x68a Family = 6 Model = 8 Stepping = 10 Feb 25 22:37:48 kernel: Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE Feb 25 22:37:48 kernel: real memory = 267190272 (254 MB) Feb 25 22:37:48 kernel: avail memory = 205832192 (196 MB) Feb 25 22:37:48 kernel: ACPI APIC Table: COMPAQ SOLANO Feb 25 22:37:48 kernel: ioapic0: Changing APIC ID to 8 Feb 25 22:37:48 kernel: ioapic0 Version 2.0 irqs 0-23 on motherboard Feb 25 22:37:48 kernel: kbd1 at kbdmux0 Feb 25 22:37:48 kernel: acpi0: COMPAQ CPQ0004 on motherboard Feb 25 22:37:48 kernel: acpi0: [ITHREAD] Feb 25 22:37:48 kernel: acpi0: Power Button (fixed) Feb 25 22:37:48 kernel: acpi0: reservation of 0, a (3) failed Feb 25 22:37:48 kernel: acpi0: reservation of 10, fe0 (3) failed Feb 25 22:37:48 kernel: Timecounter ACPI-fast frequency 3579545 Hz quality 1000 Feb 25 22:37:48 kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 Feb 25 22:37:48 kernel: cpu0: ACPI CPU on acpi0 Feb 25 22:37:48 kernel: pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 Feb 25 22:37:48 kernel: pci0: ACPI PCI bus on pcib0 Feb 25 22:37:48 kernel: vgapci0: VGA-compatible display mem 0x4400-0x47ff,0x4030-0x4037 irq 16 at device 2.0 on pci0 Feb 25 22:37:49 kernel: agp0: Intel 82815 (i815 GMCH) SVGA controller on vgapci0 Feb 25 22:37:49 kernel: pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 Feb 25 22:37:49 kernel: pci2: ACPI PCI bus on pcib1 Feb 25 22:37:49 kernel: pci2: network, ethernet at device 8.0 (no driver attached) Feb 25 22:37:49 kernel: isab0: PCI-ISA bridge at device 31.0 on pci0 Feb 25 22:37:49 kernel: isa0: ISA bus on isab0 Feb 25 22:37:49 kernel: atapci0: Intel ICH2 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2460-0x246f at device 31.1 on pci0 Feb 25 22:37:49 kernel: ata0: ATA channel 0 on atapci0 Feb 25 22:37:49 kernel: ata0: [ITHREAD] Feb 25 22:37:49 kernel: ata1: ATA channel 1 on atapci0 Feb 25 22:37:49 kernel: ata1: [ITHREAD] Feb 25 22:37:49 kernel: uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0x2440-0x245f irq 23 at device 31.4 on pci0 Feb 25 22:37:49 kernel: uhci0: [ITHREAD] Feb 25 22:37:49 kernel: usbus0: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci0 Feb 25 22:37:49 kernel: pci0: multimedia, audio at device 31.5 (no driver attached) Feb 25 22:37:49 kernel: acpi_button0: Power Button on acpi0 Feb 25 22:37:49 kernel: atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Feb 25 22:37:49 kernel: atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 Feb 25 22:37:49 kernel: atkbd0: AT Keyboard irq 1 on atkbdc0 Feb 25 22:37:49 kernel: kbd0 at atkbd0 Feb 25 22:37:49 kernel: atkbd0: [GIANT-LOCKED] Feb 25 22:37:49 kernel: atkbd0: [ITHREAD] Feb 25 22:37:49 kernel: ppc0: Parallel port port 0x378-0x37f,0x778-0x77d irq 7 drq 3 on acpi0 Feb 25 22:37:49 kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Feb 25 22:37:49 kernel: ppc0: FIFO with 16/16/13 bytes threshold Feb 25 22:37:49 kernel: ppc0: [ITHREAD] Feb 25 22:37:49 kernel: ppbus0: Parallel port bus on ppc0 Feb 25 22:37:49 kernel: uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Feb 25 22:37:49 kernel: uart0: [FILTER] Feb 25 22:37:49 kernel: uart1: 16550 or compatible port 0x2f8-0x2ff irq 3 on acpi0 Feb 25 22:37:49 kernel: uart1: [FILTER] Feb 25 22:37:49 kernel: pmtimer0 on isa0 Feb 25 22:37:49 kernel: orm0: ISA Option ROMs at iomem 0xc-0xc9fff,0xca000-0xcb7ff,0xe-0xe pnpid ORM on isa0 Feb 25 22:37:49 kernel: sc0: System console at flags 0x100 on isa0 Feb 25 22:37:49 kernel: sc0: VGA 16 virtual consoles, flags=0x300 Feb 25 22:37:49 kernel: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Feb 25 22:37:49 kernel: acpi_throttle0: ACPI CPU Throttling on cpu0 Feb 25 22:37:49 kernel:
Bug#614419: installation-reports: kfreebsd-i386 netboot installer doesn't detect ethernet device
Package: installation-reports Severity: important Tags: d-i -- Package-specific info: Boot method: network Image version: official squeeze netboot.tar.gz Date: Mon Feb 21 20:47:22 CET 2011 Machine: Compaq Deskpro EN Partitions: df -Tl will do; the raw partition table is preferred FilesystemType 1K-blocks Used Available Use% Mounted on /dev/sda1 ext318754428941896 16859856 6% / tmpfstmpfs 126852 0126852 0% /lib/init/rw udev tmpfs 122500 124122376 1% /dev tmpfstmpfs 126852 0126852 0% /dev/shm Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Booting the kfreebsd-i386 installer via DHCP went fine. However then the installer reported that it didn't find any network interface. At first I thought this was some firmware issue (on linux the interfaces uses the e100 driver) but then I tried the i386 netboot installer and this time (with linux) the installation went ok without any manual actions related to firmware. So obviously firmware is no excuse for kfreebsd not detecting the interface. When looking around in the shell of the (kfreebsd) installer, I also noticed that there seemed no USB support at all, that is no way to mount usb storage or activate usb wifi. - But I don't have much experience with *BSD at all, so maybe I just didn't do the right thing... I'm now writing this installation report from this very machine, but with linux installed not kfreebsd. So the information below is linux output despite the report primarly concerning kfreebsd. If there is anything I can do to help you debug/fix this: Please let me know. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20110106+b1 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux stardust 2.6.32-5-486 #1 Fri Dec 10 15:32:53 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 04) lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 04) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:001a] lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 02) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801BA ISA Bridge (LPC) [8086:2440] (rev 02) lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801BA IDE U100 Controller [8086:244b] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:2411] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 82801BA/BAM SMBus Controller [8086:2443] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:2411] lspci -knn: 00:1f.4 USB Controller [0c03]: Intel Corporation 82801BA/BAM USB Controller #1 [8086:2444] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:2411] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801BA/BAM AC'97 Audio Controller [8086:2445] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:000f] lspci -knn: 02:08.0 Ethernet controller [0200]: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller [8086:2449] (rev 01) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:0012] lspci -knn: Kernel driver in use: e100 usb-list: usb-list: Bus 01 Device 01: UHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 2.6.32-5-486 uhci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub lsmod: Module Size Used by lsmod: ufs55534 0 lsmod: qnx45078 0 lsmod: ntfs 162591 0 lsmod: reiserfs 173392 0
Bug#494372: iproute: Description in tc-prio(8) is inconsistent or unclear
Package: iproute Version: 20061002-3 Severity: normal In the man page tc-prio(8) there is the following table: TOS Bits MeansLinux PriorityBand 0x0 0 Normal Service 0 Best Effort 1 0x2 1 Minimize Monetary Cost 1 Filler 2 0x4 2 Maximize Reliability 0 Best Effort 1 0x6 3 mmc+mr 0 Best Effort 1 0x8 4 Maximize Throughput 2 Bulk2 0xa 5 mmc+mt 2 Bulk2 0xc 6 mr+mt2 Bulk2 0xe 7 mmc+mr+mt2 Bulk2 0x108 Minimize Delay 6 Interactive 0 0x129 mmc+md 6 Interactive 0 0x1410mr+md6 Interactive 0 0x1611mmc+mr+md6 Interactive 0 0x1812mt+md4 Int. Bulk 1 0x1a13mmc+mt+md4 Int. Bulk 1 0x1c14mr+mt+md 4 Int. Bulk 1 0x1e15mmc+mr+mt+md 4 Int. Bulk 1 The description says: The last column shows the result of the default priomap. On the command line, the default priomap looks like this: 1, 2, 2, 2, 1, 2, 0, 0 , 1, 1, 1, 1, 1, 1, 1, 1 To me it is not obvious how this maps together. Actually I suspect that the table is buggy, because for example band 0 is mentioned four times in the table but twice in the command line version ... Do I miss something? Kind regards, Harald -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-6-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages iproute depends on: ii libatm12.4.1-17 shared library for ATM (Asynchrono ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries ii libdb4.3 4.3.29-8 Berkeley v4.3 Database Libraries [ Versions of packages iproute recommends: ii iproute-doc 20061002-3 Professional tools to control the -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#151292: route: MSS bug still present
Package: net-tools Version: 1.60-17 Followup-For: Bug #151292 Hi! I can still reproduce the problem, that route MSS M doesn't set the default MSS value to M but to M-(header size). I think either the behavior of route should be changed or the man page for route should be updated to reflect this ... HTH, Harald -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-4-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages net-tools depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries net-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308631: fbpanel: breaks mouse after launching two apps and switching to Konsole
What about this bug, was it fixed in fbpanel 4.9-1? I just tried and i can't reproduce it anymore. Also i downgraded to fbpanel 4.1-2 and i can't reproduce it there either. So it seems the problem was not in fbpanel itself or i'm to dumb to follow the instructions in my own bug report ... I guess you can close this report. I won't be able to give futher input. The original hardware is now broken and i won't install sarge on a new system to investigate this further. Cheers, Harald -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295042: /usr/X11R6/bin/XFree86: cannot use keyboard in gdm or kdm after fresh install of sarge
Hi Brice, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding unusable keyboard in gdm or kdm after sarge install, possibly related to the mouse configuration. Well, the issue I had, was not related to gdm oder kdm or any display manager but direcly to the X Server. Actually it's a hardware bug with the PS/2 controller of some mainboards, I think I refered to a gpm bug log, where the issue is discussed in length, in this bug's log somewhere. In essence the hardware bug was triggered by the X default configuration of two years ago. Did any of you guys reproduce this problem recently? If not, I will close this bug in the next weeks. I don't have access to the specific hardware, which showed the problem, anymore. I don't know how widespread this buggy mainboards was/is. Regards, Harald -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405155: abiword-gnome: crashes on spell checking
Package: abiword-gnome Version: 2.4.6-1 Severity: important Whenever abiword tries to check a word (i.e. I select spell checking from the menu or I have auto spell checking enabled an type a word of at least two characters) it crashes with the following message: abiword: common/convert.cpp:391: acommon::PosibErracommon::NormTableT* acommon::create_norm_table(acommon::IStream, acommon::String) [with T = acommon::ToUniNormEntry]: Zusicherung »cur - d == size« nicht erfüllt. This happens with a newly created account. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.8-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages abiword-gnome depends on: ii abiword-common2.4.6-1WYSIWYG word processor based on GT ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.12.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.14.0-3 Bonobo CORBA interfaces library ii libbonoboui2-02.8.1-2The Bonobo UI library ii libc6 2.3.6.ds1-8GNU C Library: Shared libraries ii libcairo2 1.2.4-4The Cairo 2D vector graphics libra ii libenchant1c2a1.3.0-2a wrapper library for various spel ii libfontconfig12.4.1-2generic font configuration library ii libfreetype6 2.2.1-5FreeType 2 font engine, shared lib ii libfribidi0 0.10.7-4 Free Implementation of the Unicode ii libgcc1 1:4.1.1-19 GCC support library ii libgconf2-4 2.16.0-3 GNOME configuration database syste ii libglade2-0 1:2.6.0-3 library to load .glade files at ru ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libgnome-keyring0 0.6.0-3GNOME keyring services library ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.14.0-2 A powerful object-oriented display ii libgnomeprint2.2-02.12.1-6 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-4 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-02.14.2-4 GNOME virtual file-system (runtime ii libgtk2.0-0 2.8.20-3 The GTK+ graphical user interface ii libgucharmap4 1:1.6.0-1 Unicode browser widget library (sh ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii liborbit2 1:2.14.3-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.14.8-3 Layout and rendering of internatio ii libperl5.85.8.8-7Shared Perl library ii libpng12-01.2.15~beta5-1 PNG library - runtime ii libpopt0 1.10-3 lib for parsing cmdline parameters ii libsm61:1.0.1-3 X11 Session Management library ii libstdc++64.1.1-19 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor1 1.1.3-1X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes31:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxft2 2.1.7-1FreeType-based font drawing librar ii libxi61:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1X11 Xinerama extension library ii libxml2 2.6.27.dfsg-1 GNOME XML library ii libxrandr22:1.1.0.2-5X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii zlib1g1:1.2.3-13 compression library - runtime Versions of packages abiword-gnome recommends: pn abiword-plugins-gnome none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404113: linphone-nox: linphonec segfaults without framebuffer
Package: linphone-nox Version: 1.5.1-1 Severity: important Hi, I just installed linphone-nox on an etch system and got the following error message: -- DirectFB v0.9.25 - (c) 2000-2002 convergence integrated media GmbH (c) 2002-2004 convergence GmbH --- (*) DirectFB/Core: Single Application Core. (2006-10-17 10:09) (*) Direct/Memcpy: Using linux kernel memcpy() (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed -- No such file or directory (!) DirectFB/FBDev: Error opening framebuffer device! (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable. (!) DirectFB/Core: Could not initialize 'system' core! -- Initialization error! ortp-error-Couldn't initialize SDL: DirectFBCreate: Initialization error! ortp-error-MSV4l: cannot open video device (/dev/video0): No such file or directory. Speicherzugriffsfehler The last line is the german term for segementation fault. On the same system the x-version seems to work fine. After doing modprobe vga16fb linphonec works fine also. I'm somewhat surprised to see a package with uitoolkit::ncurses depend on libsdl1.2debian and thus libdirectfb. If it was only to make the linker happy, so be it (though I'd still consider this unnecessary bloat), but permanently activating framebuffer is not an option, because it's way slower. Regards, Harald -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-3-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linphone-nox depends on: ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii liblinphone1 1.5.1-1 linphone web phone's library (supp ii libmediastreamer01.5.1-1 linphone web phone's media library ii libncurses5 5.5-5 Shared libraries for terminal hand ii libortp5 1.5.1-1 Real-time Transport Protocol stack ii libosip2-3 2.2.2-3.1 Session Initiation Protocol (SIP) ii libreadline5 5.2-1 GNU readline and history libraries ii linphone-common 1.5.1-1 web phone linphone-nox recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390709: nmh post tries to execve no instead of sendmail on amd64 system
I found this bug because I couldn't send outgoing mail using MH and eventually strace'd post to find that it was calling execve on no with other arguments appearing to be sendmail arguments. Interesting. I had heard inklings of this bug, I wonder if its a build problem though. Could you rebuild nmh on your system (with postfix installed) and see if it fixes the problem for you? This is a bug in the configure script. It has already been fixed upstream. For an explanation see the thread starting at http://lists.gnu.org/archive/html/nmh-workers/2006-04/msg00010.html especially: http://lists.gnu.org/archive/html/nmh-workers/2006-04/msg00013.html http://lists.gnu.org/archive/html/nmh-workers/2006-04/msg00015.html Dunno why this only seems to hit amd64. Regards, Harald -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386453: translate: doesn't encode private entries in UTF-8
Package: translate Version: 0.6-9 Severity: normal Hi! When I teach translate a new word, it add's a line to ~/.translate/xx-yy However this line is encoded in latin-9 (my system default), but on reading translate expects UTF-8 and thus either doesn't find entries with non-Ascii characters or crashes on displaying them. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages translate depends on: ii trans-de-en 1.4-4 A German-English translation dicti translate recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384366: x11-common: /usr/bin/X is not stripped
Package: x11-common Version: 1:7.0.22 Severity: minor On my system file /usr/bin/X reports: /usr/bin/X: setuid setgid ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.1, dynamically linked (uses shared libs), for GNU/Linux 2.4.1, not stripped Applying strip reduces the size of the file to about the half. In case this is intended for some reason, it is not documented in /usr/share/doc/x11-common/* Also note, that Policy 10.1 says, that ... by default all installed binaries should be stripped ... Kind regards, Harald -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy ii debianutils 2.17 Miscellaneous utilities specific t ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: * x11-common/xwrapper/nice_value: 0 * x11-common/xwrapper/allowed_users: Console Users Only x11-common/experimental_packages: x11-common/xwrapper/actual_allowed_users: console x11-common/xwrapper/nice_value/error: x11-common/x11r6_bin_not_empty: * x11-common/upgrade_issues: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363909: gcl: version in etch breaks maxima 5.9.3
Package: gcl Version: 2.6.7-14 Severity: normal Hi! I compiled the original maxima 5.9.3 sources, which worked fine. However with the newly compiled maxima binary I get the following session: (%i1) bug_report(); The Maxima bug database is available at http://sourceforge.net/tracker/?atid=104933group_id=4933func=browse Submit bug reports by following the 'Submit New' link on that page. Please include the following build information with your bug report: - Maxima version: 5.9.3 Maxima build date: 13:0 3/31/2006 host type: i686-pc-linux-gnu lisp-implementation-type: GNU Common Lisp (GCL) lisp-implementation-version: GCL 2.6.7 - The above information is also available from the Maxima function build_info(). (%o1) (%i2) integrate(1/(a*x^2+b), x); Is a b positive or negative? Is a b positive or negative? Is a b positive or negative? Is a b positive or negative? Is a b positive or negative? Is a b positive or negative? Is a b positive or negative? Is a b positive or negative? Is a b positive or negative? Maxima encountered a Lisp error: Console interrupt. Automatically continuing. To reenable the Lisp debugger set *debugger-hook* to nil. (%i3) That is: Maxima asks the same question over and over again, without giving me a chance to enter anything. The same maxima sources work under sarge without any problems. So I guess, it must be gcl's fault. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.4.27-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages gcl depends on: ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii gcc 4:4.0.2-2 The GNU C compiler ii libc6 2.3.6-7GNU C Library: Shared libraries ii libgmp3c2 4.1.4-10 Multiprecision arithmetic library ii libncurses5 5.5-1.1Shared libraries for terminal hand ii libreadline5 5.1-7 GNU readline and history libraries ii libx11-6 6.9.0.dfsg.1-6 X Window System protocol client li ii tcl8.48.4.12-1 Tcl (the Tool Command Language) v8 ii tk8.4 8.4.12-1 Tk toolkit for Tcl and X11, v8.4 - gcl recommends no packages. -- debconf information: * gcl/default_gcl_prof: false * gcl/default_gcl_ansi: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344367: nmh: Better wait for nmh 1.2.1
Hi! It seems that nmh 1.2 is again a broken release (at least on *BSD). Since Debian also has a BSD port, I suggest waiting for 1.2.1 or whatever it will be called. Regards, Harald -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#146449: [Nmh-workers] things still to fix for this release?
[CCing the Debian BTS] You didn't include it in your list, but we perhaps ought to consider bug 9228: https://savannah.nongnu.org/bugs/index.php?func=detailitemitem_id=9228 Anyone know the history of $mheditor? Can we just remove the reference in the man page? i only checked 1.1, but mheditor sure looks like it's honored to me. i think the bug report is bogus. I once forwarded this bug from the Debian BTS. I believe I did some tests then and came to the same conclusion as the original submitter. However I agree, that I can't reproduce this anymore. It seems to work as expected in the CVS version and the Debian version. Therefore I'll close both bug reports. Regards, Harald -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332696: gnumeric-plugins-extra: python unuseable under german locale
Package: gnumeric-plugins-extra Version: 1.5.90-1 Severity: normal Hi, Start gnumeric with a german locale ([EMAIL PROTECTED] in my case) and the following session from the python console shows the problem: print 1.2 1.0 print 1.2+1.3 2.0 print 1,2 1 2 print 1,2+1,3 1 3 3 print 7.2/2 3,5 Obviously the decimal point isn't interpreted correctly. I don't understand the above behavior, but if I start gnumeric under LANG=C everything works as expected. Also note that this is not a problem with python itself: The standalone python interpreter works ok under any locale I tried. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.4.27-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages gnumeric-plugins-extra depends on: ii gnumeric 1.5.90-1 GNOME spreadsheet application ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libperl5.85.8.7-3Shared Perl library ii pxlib10.5.1-1library to read/write Paradox data ii python2.3 2.3.5-6An interactive high-level object-o gnumeric-plugins-extra recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332509: gnumeric-plugins-extra: missing dependency on python-gtk2
Package: gnumeric-plugins-extra Version: 1.5.90-1 Severity: serious Justification: Policy 3.5 gnumeric-plugins-extra doesn't depend on phython-gtk2, but if I want to start the python console and this package is not installed, then gnumeric crashes. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.4.27-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages gnumeric-plugins-extra depends on: ii gnumeric 1.5.90-1 GNOME spreadsheet application ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libperl5.85.8.7-3Shared Perl library ii pxlib10.5.1-1library to read/write Paradox data ii python2.3 2.3.5-6An interactive high-level object-o gnumeric-plugins-extra recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329908: dpkg: german man page of update-alternatives has no umlauts
Package: dpkg Version: 1.13.11 Severity: minor To reproduce this bug just set a german locale and view the man page of update-alternatives. You get a nice german text but all umlauts are stripped off. Indeed they are not even present in /usr/share/man/de/man8/update-alternatives.8.gz Harald -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.4.27-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages dpkg depends on: ii coreutils [textutils] 5.2.1-2.1 The GNU core utilities ii libc6 2.3.5-6GNU C Library: Shared libraries an dpkg recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308631: fbpanel: breaks mouse after launching two apps and switching to Konsole
Package: fbpanel
Version: 4.1-2
Severity: normal
Hi!
The following problem is a bit strange and exotic, feel free lower the
severity or tag it unreproducible if it seems appropriate. It took me
quite some time to reproduce it reliably an MY computer:
I start X using startx and the following /etc/X11/xinit/xinitrc:
-- start -
#!/bin/sh
# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit (startx)
# invoke global X session script
#. /etc/X11/Xsession
metacity --sm-disable
fbpanel
- end -
The configuration of fbpanel ist included below.
When fbpanel is up, I launch a xterm and immediately (i.e. before the
xterm shows up) I launch the browser (Mozilla) too. Next I switch to
the Konsole via Ctrl-Alt-F1. This also needs to happen, before the
xterm appears on the screen.
'ps -A' gives the following Output:
2956 tty3 00:00:00 startx
2967 tty3 00:00:00 xinit
2968 ?00:00:01 XFree86
2973 tty3 00:00:00 sh
2974 tty3 00:00:05 metacity
2975 tty3 00:00:04 fbpanel
2977 tty3 00:00:00 x-terminal-emul
2978 pts/000:00:00 bash
Obviously fbpanel didn't start the browser.
If I go back to X, I see that the browser icon is still pressed (even if
I move the mouse away), I can move the mouse and type into the xterm (it has
the focus), but I neither clicking nor moving the mouse has any effect.
(i. e. The cursor doesn't change if I move it over the border of the
window and i can't move or resize it)
It seems that both, fbpanel and metacity stay alive: 'top' doesn't show
any anomalies and if I start 'xmessage Test' from the xterm I get
a message window, which is correctly decorated, shows up in the
panel and has the focus.
Thus it seems the only thing, that doesn't work is processing the
mouse events. Sorry, I haven't been able to produce any useful debugging
information yet.
Please note, that I need this very sequence to reproduce the problem.
If I launch the browser prior to the xterm or change anything else, it
works fine. Also you need to be very fast, because you need to do
everyting before the xterm appears on the screen.
This is my fbpanel configuration:
- begin -
## fbpanel configuration file ##
# DESCRIPTION
# Configuration file consists of mandatory 'Global' block that MUST come first,
# and optionally one or more 'Plugin' block.
# Lines having '#' as first non-blank char or blank lines are ignored
# Value of variable is a text from first non-blank char after '='
# till the last non-blank char. '#' is NOT treated as coment in this context
# 'Global' block describes gloabal parameters like position, size and
# some NETWM settings
# GLobal {
# # screen edge
# # legal values are: left, right, top, bottom
# edge = bottom
# # allignment of a panel
# # legal values are: left, right, center
# allign = left
# # length of margin (in pixels)
# # legal values are numbers
# margin = 0
# # widthtype specifies how panel width is calculated
# # legal values are: request, pixel, percent
# # request - follow widgets' size requests. can shrink or grow
dynamically
# # pixel - ocupy fixed number of pixels, then 'width' variable holds a
number
# # percent - be 'width' precent of an edge.
# widthtype = percent
# # numerical value of width (not applicable for 'request' widthtype)
# # legal values are numbers
# width = 80
# # heighttype specifies how panel height is calculated
# # legal values are: pixel
# # pixel - ocupy fixed number of pixels, then 'height' variable holds
a number
# heighttype = pixel
# # numerical value of height (if applicable)
# # legal values are numbers
# height = 28
# # Identify panel window type as dock
# # legal values are boolean
# SetDockTpe = true
# # Reserve panel's space so that it will not be covered by maximazied
windows
# # legal values are boolean
# # SetPartialStrut = true
# # Transparency stuff:
# # TintColor is a color to composite on root background
# # Alpha is transparency of the tint color.
# # Transparent = true
# # TintColor = 0x
# # Alpha = 127
# }
# 'Plugin' block specifies a plugin to load. It has same syntax for both
# builtin and external plugins.
# First parameter is 'type'. It's mandatory and must come first
# Legal values are plugin names. Names of builtin plugins are:
# separator - visual separator
# wincmd - 'show desktop' button
# taskbar - lists all opened windows (tasks)
# launchbar - bar with launch button
# image - just shows an image
# dclock - digital clock
# space - just seize space
# pager - thumbnailed view of the desktop
# tray- tray for XEMBED icons (aka docklets)
# expand - specifies if plugin can accomodate extra space or not
Bug#295042: Keyboard problem resolved
Hi Braden and all! I can now confirm that indeed a bad mouse setup is causing all that keyboard trouble: After adding a CorePointer Option to the Section about the USB-mouse and commenting out the PS2-mouse from the ServerLayout Section, the keyboard is working now. If you want the technical details, then please read #169427. Harald -- http://www.unet.univie.ac.at/~a0300802/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295042: Keyboard problems
Hi Braden! You have sent your message to the wrong Bug# too. Thus fullquoteing it here: Wow, I wish I could help you, but I haven't solved my own problem yet. If I do find out what it is I will let you know ASAP, but it doesn't look like the solution will be in my grasp soon. I've talked to several people about the keyboard setup, and they all say that my settings are correct, so I am going to assume that yours is as well. The only way I have been able to work around the problem is to connect remotely via XDMCP. Its not the best solution (or a good solution), but it has given me X access to the box. Probably I haven't made my point clear enough by referring to bug #169427: I believe the cause is not keyboard setup but the mouse setup. Hopefully I can confirm that tomorrow when I have access to the affected PC again ... Harald -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION Kein Einrichtungspreis nutzen: http://www.gmx.net/de/go/dsl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295242:
Hi! I ran into this while setting up a friends machine. Unfortunately there is no internet there, so I couldn't look into the BTS there and now I don't have the PC available. Sorry for the incomplete information! Ad Braden: Can you confirm, whether the same problem shows up when starting X with startx? I believe that this bug is an instance of the problems described in #169427, but here are the details: I set up the machine with sarge-installer RC2, Kernel 2.4 The keyboard is ordinary pc105 on a PS2-Port. The mouse is on USB. After a few tries we got gpm running. (Sorry don't remember the details, didn't expect any real trouble then.) Issuing xstart as an ordinary user brougth up X without trouble. I don't know, whether the keyboard worked at that time. My friend pressed some key-combinations he doesn't remember. (They had some effect at least.) At some point the keyboard went away. Neither of Ctrl-Alt-Fn nor anything else showed any effect. After terminating the running Gnome-Session using the mouse, we got the ttys back, but the keyboard was in trouble there too: To me it seems like the Ctrl-key was pressed the whole time (d leading to eof (logout), s leading to Scroll_Lock - I don't know a possibility to recover from that, ans Scroll_Lock itself leading to Show_State) As we believed the keyboard configuration to be wrong, we tried a lot of different things. But all in subsequent tries the keyboard was broken under X from the very beginning (even after cold booting). In some cases ttys worked well after the x server had terminated and sometimes the above Ctrl-key problem showed up again. We can't reproduce this reliably yet. After reading #169427 I believe that the mouse setting is causing that and IIRC we had the very same setting of Configured Mouse and Generic Mouse as Braden has. I don't have access to the PC ATM, so I can't investigate this further. Hopefully this is helpful to somebody. I'll send a follow up as soon as I have access to the affected computer again. Harald -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION Kein Einrichtungspreis nutzen: http://www.gmx.net/de/go/dsl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295042: Keyboard problems under X
The following mail was sent to the wrong bug in error. Hope I get it right this time ... --- Weitergeleitete Nachricht / Forwarded Message --- Date: Wed, 23 Feb 2005 19:32:04 +0100 (MET) From: Harald Geyer [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Hi! I ran into this while setting up a friends machine. Unfortunately there is no internet there, so I couldn't look into the BTS there and now I don't have the PC available. Sorry for the incomplete information! Ad Braden: Can you confirm, whether the same problem shows up when starting X with startx? I believe that this bug is an instance of the problems described in #169427, but here are the details: I set up the machine with sarge-installer RC2, Kernel 2.4 The keyboard is ordinary pc105 on a PS2-Port. The mouse is on USB. After a few tries we got gpm running. (Sorry don't remember the details, didn't expect any real trouble then.) Issuing xstart as an ordinary user brougth up X without trouble. I don't know, whether the keyboard worked at that time. My friend pressed some key-combinations he doesn't remember. (They had some effect at least.) At some point the keyboard went away. Neither of Ctrl-Alt-Fn nor anything else showed any effect. After terminating the running Gnome-Session using the mouse, we got the ttys back, but the keyboard was in trouble there too: To me it seems like the Ctrl-key was pressed the whole time (d leading to eof (logout), s leading to Scroll_Lock - I don't know a possibility to recover from that, ans Scroll_Lock itself leading to Show_State) As we believed the keyboard configuration to be wrong, we tried a lot of different things. But in all subsequent tries the keyboard was broken under X from the very beginning (even after cold booting). In some cases ttys worked well after the x server had terminated and sometimes the above Ctrl-key problem showed up again. We can't reproduce this reliably yet. After reading #169427 I believe that the mouse setting is causing that and IIRC we had the very same setting of Configured Mouse and Generic Mouse as Braden has. I don't have access to the PC ATM, so I can't investigate this further. Hopefully this is useful to somebody. I'll send a follow up as soon as I have access to the affected computer again. Harald -- Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295242: Wrong bug number
I think you mistyped your bug number, look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295242, it's a but related to update-alternatives for java, while you seem to be talking about a xfree problem. Yes, you are totally right. It should be #295042 Sorry, for the inconvenience. Harald -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION Kein Einrichtungspreis nutzen: http://www.gmx.net/de/go/dsl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
