[Bug 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
TLDR version, yes it's fixed! I guess there's only one way to find out! I've been running kisak PPA so was on 24.1.x on there, but I'm ppa-purge'ing is now to test. I no longer have that Sandy Bridge notebook, but have an Ivy Bridge desktop (and I verified based on the plenty of debug info Wine prints that it does skip over the nearly useless "partial" Vulkan support on it and is using OpenGL code paths.) It now has 23.2.1 on it. I don't usually game on this system but I ran The Stanley Parable on there to test. Looks good! I realized the Ivy Bridge supports up to OpenGL 4.2 rather than the 3.3 of the Sandy Bridge so I also ran with MESA_GL_VERSION_OVERRIDE=3.3 to hold it down to an older OpenGL version and make sure it works then too. It did. Also tested with MESA_GL_VERSION_OVERRIDE=2.1 to make sure the version override was working. Indeed wine said the requested D3D feature levels are unavailable and the game didn't load. Fixed! Thanks! --Henry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Sorry about that! I initially filed this bug, but I'm no long-time user of the bug system. If 1956422 is marked dup and pointed here, it's fine with me! Still, as for GCP kernel specifically, a bot auto-generated the request to test against GCP kernel. I wonder how many drivers GCP kernel is missing (that'll be why the touchpad and lid switch didn't work.) I think for GCP kernel specifically, it won't matter if this patch is applied or not, no integrated GPUs so they won't be running affected hardware. I suppose first start is to attach any relevant logs and info -- does kern.log or dmesg show anything interesting when you suspend & resume? If you can ssh into the machine, does the machine lock solid on resume, or does it have a black screen but still running? You probably provided this info in 1956422 already but if it's being dup'ed to here, feel free to put it here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
I don't think this patch is intended to fix suspend/resume bug, that's not the problem I was seeing at any rate. That said... Does this bug apply to GCP kernel? I'm assuming GCP is "Google Cloud Platform", so I'm not sure they are even using affected hardware. AMD CPUs are fairly power-efficient, so I could see Google using them, but probably not the ones with built-in GPU (in favor of getting ones with more CPU cores instead). I assume if they want to support CUDA-style workloads they'd thrown some monster GPUs into their "GPU compute" cloud systems. (That said, that all means for the use case of GCP kernel, it should be fine either way, apply or not apply this patch.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
I'm assuming the 5.14.15 or 5.14.16 amdgpu and amdkfd has been backported to the 5.13 Ubuntu kernel. Here's the patch in 5.14.17 that specifically addresses this. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.14.17&id=7883e13c249461877ea3be7b24a5935fc8946e46 The other amd-related patches for 5.14.17 largely appear to be fixes to DCN3.1 support (newest GPU models from last 6 months or so.) This is a fairly serious regression for those affected (I may have only gotten to a desktop because I"m using Gnome Flashback so no compositor trying to exercise the 3D hardware for desktop use. I've simply gone back to 5.13.0-22 for now.) If the plan is to ship a quick update, I could see just patching in that one patch; if it'll be fixed in 5.13.0-23 at a usual schedule I could see incorporating all of them to benefit DCN 3.1 users. Not to dissemble, but kudos to the open source GPU driver developers, the Intel support's amazing (it's amusing on my friends Sandybridge, that he can run DX11 games in steam through Proton that it would not be able to run in Windows since Intel never shipped DX11 drivers for it...), and amdgpu has run every game I've thrown at it so far, generally at very good frame rates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Additional note, I did notice one "un-regression" -- I have a build of rocm where I've tried enabling "GFX902" support for my card, this is an unsupported configuration so I don't know if I have it 100% functional but rocminfo (which as the name suggests dumps info about the rocm install and any video or compute cards it detects that can use. ) With the 5.4.0-91-generic kernel I can run rocminfo and it dumps some info about the card. On 5.13.0-22 it prints: hsa api call failure at: /home/hwertz/ROCm/rocminfo/rocminfo.cc:1143 Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events. On 5.13.0-23, although opengl is hosed the rocminfo didn't pause and printed the rocm-related information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
** Attachment added: "Some kernel log showing amdgpu errors and others resulting from it" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+attachment/5551255/+files/wow.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] [NEW] amdgpu hangs for 90 seconds at a time
Public bug reported: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
Suggested patch. For now, I've been running mesa 20.0.x on the affected system from (21.0.x is in ubuntu-updates, 20.0.x in base ubuntu repo, so I downgraded to that and thank goodness for apt-mark hold...) But I can update it straight away to test any update that comes out. Thanks! --Henry ** Patch added: "wine-fix-updated.diff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+attachment/5544778/+files/wine-fix-updated.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952970] [NEW] mesa GLX change leads to wine showing GLXBadFBConfig
Public bug reported: A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both wine and Proton (on an older system that does not have Vulkan.. SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to fire up OpenGL. Wine, for Direct3D support it tries to fire up (in order) Vulkan then progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even 1.4 (of course the older the OpenGL the lower supported Direct3D version). Wine does not like getting an error back with the same transaction serial number as it sent out. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 Mesa issue 3969, The patch there throws in an "XNoOp()" to increment the transaction serial number. But the patch there caused issues in other apps, per https://gitlab.freedesktop.org/mesa/mesa/-/issues/4763 Mes issue 4763, They found XNoOp() increments the serial number, but xcb keeps a "shadow copy" of the serial number which is not incremented, causing problems. XFlush() increments the serial number, keeps xcb in sync and happy, with no real side effects (running XFlush() frequently would slow things down, but this code only runs when a GLX context is being created anyway which just doesn't happen all that frequently.) Please find attached a patch implementing the updated patch suggested in issue 4763. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglx-mesa0 21.0.3-0ubuntu0.3~20.04.5 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Dec 1 18:59:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Dell Picasso [1028:0a12] InstallationDate: Installed on 2020-05-05 (575 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 3505 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=57669cb0-fd65-4eb0-9898-ed10f33d44d0 ro quiet splash nvme_core.io_timeout=300 nosmt vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.7 dmi.board.asset.tag: not specified dmi.board.name: 0RV9WY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.7 dmi.modalias: dmi:bvnDellInc.:bvr1.4.7:bd05/31/2021:br5.3:svnDellInc.:pnInspiron3505:pvr1.4.7:rvnDellInc.:rn0RV9WY:rvrA00:cvnDellInc.:ct10:cvr1.4.7:sku0A12: dmi.product.family: Inspiron dmi.product.name: Inspiron 3505 dmi.product.sku: 0A12 dmi.product.version: 1.4.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928030] [NEW] s3ql 3.7.0 crash, version bump requested
Public bug reported: I "backported" s3ql (built .debs for python3-pyfuse3_3.2.0-2build1, python3-trio_0.18.0-1, and s3ql_3.7.0+dfsg-2build1-local1 to use in Ubuntu 20.04), and encountered a fairly quick crash (like under a minute) when I started writing data to the s3ql filesystem. The log ends with several "During handling of the above exception, another exception occurred:" python tracebacks, ending with "s3ql.block_cache.NoWorkerThreads: no upload threads". Per the bug referenced, this won't result in data loss, a umount + fsck.s3ql cleans it up fine. But still. https://github.com/s3ql/s3ql/issues/234 Bug fixed in 3.7.1, I built 3.7.2 and it works a treat. No crashes under very heavy usage; it's a bit faster than 3.3.4 that 20.04 focal ships with in general usage and much faster to unmount. 3.7.0 is current version in hirsute and impish, so should be bumped to 3.7.2. ** Affects: s3ql (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928030 Title: s3ql 3.7.0 crash, version bump requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1928030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
"1) Do you actually have superflous key strokes, along with that which is logged in dmesg?" Nope, totally asymptomatic. "2) Could you please test the latest mainline kernel (now 5.9.1) and advise to the results?" Here ya go. I can attach entire dmesg if you want, but from 5.9.1 dmesg: [ 256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known. "3) Did you personally test this with your Inspiron 1545 in a prior version of Ubuntu" No. I don't think it started logging this (at least often enough to notice) until my battery went from holding like a minute or two of battery life to holding 0, which only happened in the last 2-4 weeks. Honestly, I'd be totally fine if it was closed "wontfix" (I guess launchpad doesn't have that) or "invalid", the kernel's logging a non- standard keystroke sent by the Dell, which seems legitimate and harmless (it'd be a nuisance if it was every second but it's not close to that); in addition the Dell is effectively sending it in response to a hardware failure, so I could see "if you don't want this in your kernel log, replace your battery" being a legitimate response. Let me know and I'll set it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
"1) Do you actually have superflous key strokes, along with that which is logged in dmesg?" Nope, totally asymptomatic. "2) Could you please test the latest mainline kernel (now 5.9.1) and advise to the results?" Here ya go. I can attach entire dmesg if you want, but from 5.9.1 dmesg: [ 256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known. "3) Did you personally test this with your Inspiron 1545 in a prior version of Ubuntu" No. I don't think it started logging this (at least often enough to notice) until my battery went from holding like a minute or two of battery life to holding 0, which only happened in the last 2-4 weeks. Honestly, I'd be totally fine if it was closed "wontfix" (I guess launchpad doesn't have that) or "invalid", the kernel's logging a non- standard keystroke sent by the Dell, which seems legitimate and harmless (it'd be a nuisance if it was every second but it's not close to that); in addition the Dell is effectively sending it in response to a hardware failure, so I could see "if you don't want this in your kernel log, replace your battery" being a legitimate response. Let me know and I'll set it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425626/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425632/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425630/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425634/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425636/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425627/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425629/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425628/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425635/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425631/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425633/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
(uname -a: Linux inspiron-1545.local 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ) I've been using 5.7.19 by default, but I'm on 5.4.0-52-generic for this since it's a supported kernel. (These atkbd messages are identical in both.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425625/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
apport information ** Tags added: apport-collected staging ** Description changed: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: hwertz 3637 F pulseaudio + CurrentDesktop: GNOME-Flashback:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-09-09 (774 days ago) + InstallationMedia: + + MachineType: Dell Inc. Inspiron 1545 + Package: linux (not installed) + ProcEnviron: + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off + ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-52-generic N/A + linux-backports-modules-5.4.0-52-generic N/A + linux-firmware1.173.19 + StagingDrivers: ashmem_linux + Tags: bionic staging + Uname: Linux 5.4.0-52-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra + _MarkForUpload: True + dmi.bios.date: 12/07/2009 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.name: 0G848F + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Inspiron 1545 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425623/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425624/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
** Description changed: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each - time the battery status changes. + time the battery status changes. Not sure what the point of the 0x8d + is, but it's harmless for Linux to ignore, it's well aware of the status + changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: - + ProcEnviron: - TERM=screen.xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: + I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 2
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
I assumed dmesg would be attached... It is now! ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1901083/+attachment/5425615/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] [NEW] Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
Public bug reported: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
I have an Inspiron 1545 that's doing this (Ubuntu 18.04.5); mine is nowhere near every second though. My battery is toast, a while ago it began (occasionally) having the "0% battery" occasionally drop off then reappear a few seconds later (both in gkrellm and the battery status on the top right near network-manager etc.). Based on the timing in the logs (0x8d then another a few seconds later), I think it sends a 0x8d keystroke both on battery disappearing and once on reappearing. I'd hesitate to consider it a bug; it's minorly spamming up the logs with a superfluous keystroke the Dell's sending, while causing no harm (if the point of the keystroke is to indicate change in battery status, Linux is already well aware of this via ACPI anyway.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792644] [NEW] If snapd is not working it can take down systemd
Public bug reported: I'll start out with saying, this bug is probably priority "invalid" due to my non-stock configuration (this 18.04.1 install is on an Acer Chromebook 13, so it has a held back kernel and Xorg for the lovely nvidia drivers it came with.) But I figure I'll file anyway since the problem is rather serious if it arises on your particular system, and the workaround/fix is easy once you figure out what the heck is happening. So, snapd has errored out since I updated to 18.04 due to my held back kernel (snap packages are using xz compression, and this kernel has no xz support...) I found within the last day or so that my machine would not boot to graphical environment, just to text login with no networking up and several missing services (ntp and a few others.) journalctl -xe showed failures due to "file not found" on files like tr, cut, modprobe, cat, that should definitely be found. PATH problems! Ultimately, I found /usr/lib/systemd/system-environment-generators/snapd-env-generator (which appears -- not sure since it's a binary instead of a shell script -- to be intended to just add "/snap/bin" to the PATH.)I moved this out of the folder, on reboot everything worked fine. Then I went ahead and uninstalled snapd. I suspect systemd is "too smart for it's own good", and instead of providing it's own environment variables then letting items in /usr/lib/systemd/system-environment-generators/ modify the environment (as docs say), instead systemd either decided "snapd-env-generator" is setting a PATH so systemd doesn't have to (resulting in PATH of ":/snap/bin") or systemd "rolled back" that PATH when snapd service failed, resetting PATH to empty instead of the default PATH value. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792644 Title: If snapd is not working it can take down systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1792644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643239] Re: Xorg crash on compiz login, with Intel 945
>I haven't verified this yet, but it looks from the XOrg log like these systems are booting into dual head (with the SVideo out on head 2), 2128x800 total. Suspicion confirmed, the "phantom" second head was causing causing compiz to fail due to the 2128 pixel width exceeding the 2048 pixel texture width limit of this chip. I booted up a D620, and verified Flashback (Compiz) failed. I logged in with Flashback (Metacity), went to Display control panel, hit Apply, and logged back out. I could then log into Flashback (Compiz) fine, it loaded quickly and everything worked fine. The display setting "stuck" fine so everything worked after a reboot as well. I guess you can close this bug! Maybe the info will remain useful for someone who runs into a similar issue. Thanks for the good work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643239 Title: Xorg crash on compiz login, with Intel 945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643239] Re: Xorg crash on compiz login, with Intel 945
I haven't verified this yet, but it looks from the XOrg log like these systems are booting into dual head (with the SVideo out on head 2), 2128x800 total. That width over 2048 is probably what's causing the problem. I did "lose the mouse" on one, and suspected a "phantom head." I went to System Settings -> Display, it didn't show a second head but the whole desktop flickered (I suspect it turned the superfluos head off then.) I suspect it stored this in .config/monitors.xml, I'll check tomorrow if it'll now log into compiz, and if it's got some hotkey that may toggle that on and off. I guess if that works out, then there's no real X bug; perhaps compiz should fall back to llvmpipe if it sees an an otherwise-working opengl implementation, but asks for a large texture and has it fail. Kudos to the compiz, Xorg, and llvmpipe developers btw... the CPU and RAM use were already decent in 14.04 but much lower now, and llvmpipe's actually reasonably fast too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643239 Title: Xorg crash on compiz login, with Intel 945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643239] [NEW] Xorg crash on compiz login, with Intel 945
Public bug reported: I went to install Ubuntu (via systemback) onto some Dell D620s, and found "Gnome Flashback (compiz)" crashes back to login prompt, while "Gnome Flashback (Metacity)" does not. The attached logs reflect booting up, (attempting to) log in with Flashback (compiz) then logging in with Flashback (Metacity) to file a bug report. This may be chipset-specific, as I have several other rather antiquated systems: Intel 865-based (Compaq DC5000): Works. (Using LLVMPipe -- this chip is missing a few OpenGL features compiz requires.) Intel 915-based (Dell Inspiron 2200): Works. Intel 945-based (Dell Latitude D620): Crashes to login prompt (this is the machine in this bug report.) Intel 965-based (Dell Latitude 755?): Works. Intel G35-based (slightly newer Dell Latitude 755): Works. I can rule out software differences; since I knew Compiz worked on a 915, I assumed I'd screwed up my systemback LiveUSB somehow, and test- ran it on the D620, 2200, and one of the 755s, and it worked on the 2200 and 755. Left up to me, I'd categorize this as severity "low", I'm just setting these to Flashback Metacity and then stability seems fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 BootLog: SB@: clean, 208182/2244608 files, 1302234/8973568 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Sat Nov 19 10:12:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1028:01c2] Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1028:01c2] InstallationDate: Installed on 2016-04-29 (203 days ago) InstallationMedia: MachineType: Dell Inc. Latitude D620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=702f73f8-ca72-4102-9c59-48f182329bfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Nov 19 10:12:01 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor LPL xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug crash i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643239 Title: Xorg crash on compiz login, with Intel 945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
I wonder if this is a compiler error? Can anyone tell if Chromium for Ubuntu 14.04 and Chromium for 16.04 have different build flags, or if their configure scripts detect something different? To me, it seems like if they have the same or very similar build flags, 16.04 build breaks but 14.04 build doesn't, it implies gcc-5.4 is misbuilding something that gcc-4.8 isn't (or, much less likely, gcc-5.4 is building something correctly but chromium relies on some misbehavior of older gcc.) I have an Acer Chromebook 13 (Tegra K1) which had 14.04 on it; Chromium 52 or 53 worked fine. Went to 16.04 (managing to hold back X so I could keep the nvidia driver...) and chromium blew up as others have reported. I also found the 14.04 build of (at this point, chromium 53) worked fine after I set "--disable-namespace-sandbox"... I had the "Aw, snap!" but found (per google) that "--disable-namespace-sandbox" fixed it without the ill effects of "--no-sandbox". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563184 Title: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539284] Re: Firefox 44.0 repeatedly crashes on ARMHF
Since the bug's still open, I did have it reoccur but found the cause and fixed it. I had switched to the mesa libGL.so.1 to build some software*, and firefox 44.0 runs with this, but did crash when I went back to tegra libGL. Long story short, the firefox profile's from my previous portable and had gfx.blacklist.*, webgl.force-neabled and layers.acceleration.force-enabled settings in there, clearing these fixed it. I cleared layers.acceleration.force-enabled last, this was causing it in particular. about:support indicates hardware accel is off (firefox disables on nvidia driver less than 257.21, and tegra driver shows as nvidia version 21.4). I looked to see if there was any bug report of recent layers- related crashes (new between 43 and 44), but I didn't find anything; presumably it works on supported drivers. * The tegra libGL.so.1 causes dpkg-buildpackage to fail to build any package that uses OpenGL, with an error that there is no dependency info for libGL.so.1, but with mesa libGL.so.1 it builds fine and runs with either libGL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539284 Title: Firefox 44.0 repeatedly crashes on ARMHF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1539284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539284] Re: Firefox 44.0 repeatedly crashes on ARMHF
Please go ahead and close this bug. When I ran the updates today it reinstalled 44.0+build3-0ubuntu0.14.04.1, and today it's working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539284 Title: Firefox 44.0 repeatedly crashes on ARMHF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1539284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539284] Re: Firefox 44.0 repeatedly crashes on ARMHF
I guess I just wasn't patient enough; the bug reports I said had hung for like an hour actually completed. But, now they want me to make a new bug report rather than be able to attach it to an existing one. Whoops. Here's the URLs: https://bugs.launchpad.net/ubuntu/+source/firefox/+filebug/437c2c30-c604-11e5-9da3-68b5996a96c8? https://bugs.launchpad.net/ubuntu/+source/firefox/+filebug/95b06742-c608-11e5-b400-0025b3df357a? https://bugs.launchpad.net/ubuntu/+source/firefox/+filebug/12a84d08-c60b-11e5-8930-68b5996a96c8? Maybe you won't need them; here's the "apport.bug" report from when I collected a report then used "ubuntu-bug -c (existing file)" to submit it. I never got a crash dump so these 3 reports probably had the same data anyway (other than time stamps). In summary, it looks like a lot of the file is the alsa config (which is huge since for some reason the audio chip on here has like 150 switches and volume controls), the other hardware info is almost empty (since there's no PCI bus). Enjoy! Thanks for the help! ** Attachment added: "apport.bug" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1539284/+attachment/4558675/+files/bug.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539284 Title: Firefox 44.0 repeatedly crashes on ARMHF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1539284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539284] [NEW] Firefox 44.0 repeatedly crashes on ARMHF
Public bug reported: (First off, I did try to use ubuntu-bug, as well as collecting info with apport-cli then submitting with ubuntu-bug. The several automated bug reports I filed just hung up, launchpad claimed it was processing the report and refreshed for over an hour.) Running firefox_43.0.4+build3-0ubuntu0.14.04.1_armhf is running fine. 44.0+build3-0ubuntu0.14.04.1 repeatedly crashes. I tried removing all my extensions (first in Firefox 44, but it crashed loading the about:addons), then manually (moving them out of extensions directory). No help. I restored my profile from a backup, went to Ubuntu 43.0.4 and uninstalled the extensions there.Upon upgrade to Ubuntu 44.0, it crashes repeatedly with no extensions. One crash did indicate a floating point exception, the rest just inidcated "signal 11". I'm running Ubuntu 14.04.4 for ARMHF on a Acer Chromebook 13. This has a Tegra K1, a quad-core ARM with an Nvidia video card with 192-core CUDA unit (the GK20A is closest in specs to a Geforce GT720 or so.) Let me know if you want more information. Thanks! ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539284 Title: Firefox 44.0 repeatedly crashes on ARMHF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1539284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968218] Re: ssh x11 forwarding precise to oneiric causes glibc malloc(): memory corruption
Note, I see this bug between my Natty too... between my Natty netbook and my Gentoo desktop (once the X server upgraded to 1.12.99, and still with 1.13.0. Not sure why, because this computer just has a mouse and keyboard, no touch screen or touchpad to provide exciting new XInput events.) Installing libxi6_1.4.3-3ubuntu1.1_i386.deb from Oneiric-updates works fine (no dependency problems and fixes the bug.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968218 Title: ssh x11 forwarding precise to oneiric causes glibc malloc(): memory corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/968218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930447] Re: Unable to Install Ubuntu 12.04 on Pentium M x86 Laptop due to PAE kernel
I know that this is a bug report and not a forum. But my 2 cents... First, it's a damn shame the Pentium M shipped without PAE, otherwise this would not really be as much of an issue. I don't use my Pentium M any more but it was a great machine, and I am planning to give it to someone to use shortly. Other than lack of PAE it's a significant upgrade for them... 1) Regarding the argument that people should just upgrade hardware... this isn't the Linux way. Linux (and UNIX before that in general...) let people keep using their system until it was either too slow, or they couldn't cram enough RAM into it, to run current software. Not forced obsolescence. I would say, if anything, those running 4GB+ of RAM should be encouraged to get a 64-bit system, rather than expecting people who have already shown they are not interested in the upgrade treadmill (by having old non-PAE systems) to replace a working system. 2) 2 constructive solutions. I would ship the CD with the non-PAE kernel, then have a little something similar to the "Additional Drivers" app that runs on first boot and presents the option of installing a PAE kernel on PAE-capable systems. (As opposed to the current situation where I'm sure some users miss out on PAE's benefits since they have to know to choose it in the package manager, this would allow a 1-click choice.) Barring that, I do urge Canonical et al. to at least have an alternate non-PAE build available (at least once it's out of alpha), perhaps just note that Pentium M users should select this build. I'd guess there are more Ubuntu users with Pentium Ms than users of the Ubuntu ARM builds (as much as I'd love to have an ARM notebook, I don't...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930447 Title: Unable to Install Ubuntu 12.04 on Pentium M x86 Laptop due to PAE kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726339] Re: [armel] libreoffice built with -marmv4t on armel
*** This bug is a duplicate of bug 725763 *** https://bugs.launchpad.net/bugs/725763 Title is a dup of 725763. Description is not; that build error occurs for me with gcc-4.6 on my gentoo boxes too, one with -march =athlon-xp and other -march=k8-sse3. So the "error: uninitialized const 'aVectorPair' [-fpermissive]" is not related to ARM arch. I assume gcc-4.6 is being stricter and (if the libreoffice code is not fixed) that adding "-fpermissive" to build flags would "fix" it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726339 Title: [armel] libreoffice built with -marmv4t on armel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692389] [NEW] window manager closes during dist-upgrade
Public bug reported: Upgrading from Ubuntu 10.04 to 10.10, I ran update-manager -d and let 'er rip for the 10.10 upgrade. The window manager crashed (that is, I still had the gnome menus at top and bottom of the screen, but no window borders or decorations.). Fair enough, no big deal. BUT, dist-upgrade appeared to hang updating a font package, and control-dragging the terminal out of the way (it can be dragged by it's menu bar) I found it "hung" because of a msttcorefonts EULA window. I could click "I accept" but the dist-upgrade window blocked the "next" button, there's no way without a window manager to drag the dist-upgrade window, and I couldn't force the EULA window to get keyboard focus either. Running gnome-wm in a text console (after doing export DISPLAY=:0.0) it gave an error regarding libgdk_pixbuf-2.0 and would not run. (This system was given an extensive upgrade recently, it was previously just a bit too sluggish with desktop effects, so they're turned off still. Therefore "gnome-wm" should run metacity and not compiz.) I ended up copying a twm binary from one of my gentoo systems and running that so I could regain window controls. I left the package as "I don't know" because, really, is this some dependency problem dist-upgrade should deal with, is it a problem with either libgdk_pixbuf installing but not configuring something, is it a problem with metacity binary being replaced but not restarted? I don't know. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692389 Title: window manager closes during dist-upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566324] Re: Xorg crash
"Me too", also with a GX260. dmesg shows streams of errors such as: [97544.908019] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [97544.908032] render error detected, EIR: 0x [97544.908056] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 6540 at 6213) when this happens. I think this is why the "Failed to submit batchbuffer: Input/output error" occurs within XOrg, the GPU indeed is hung. I have ssh on this box and can verify that other than XOrg going into a restart loop and burning a few CPU cycles (until I run sudo /etc/init.d/gdm stop) everything else is unaffected. If anyone has a patch to try, I have a head on this box but mostly treat it as headless, so I'm in a good position to try out patches. -- Xorg crash https://bugs.launchpad.net/bugs/566324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577693] Re: squid restart fails
Yep. With stock config, just telnetting to localhost 3128 and getting one item, restart is fine. But the browser, I think it keeps persistent connections open so squid doesn't immediately quit and the restart fails. -- squid restart fails https://bugs.launchpad.net/bugs/577693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1] Re: Microsoft has a majority market share
"I had two potential Windows-to-Linux converts. Typical home users with web, email, writing a few documents/letters + home office. The basic additional requirements for home office environment in these cases is multipage scanning and fax. Didn't either try the fax as already the multipage scanning was not possible in a bug-free way." I hadn't tried faxing either until a week or two ago. It turns out it works great. Right about when you're like "Oh man is this going to be ghetto or what?" It turns out you can just "Print to fax", the fax app pops up and has you dial the number (or pick of an address list, or I think send to multiple), you click "next" and it faxes. I'm sure incoming faxes were easy too. As for the scanner -- that's a shame. However, I've seen scanners goes just as poorly by going from XP to 7 (go from super-fancy to a plain 1-page-at-a-time scanner), and totally die from 98 to 2000, 2000 to XP, XP to Vista (no drivers). It's a fantasy that you can just take random hardware and expect it to 100% work with Windows either. To be clear, I think their decisions to go with Windows in this case was sensible (since the hardware works with it) but this is really not a strong argument against Linux adoption *in general*, as I've found Ubuntu has supported FAR more hardware for me than Windows ever has. -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577693] Re: squid restart fails
I am running 2.7.STABLE7-1ubuntu12. Yeah, hadn't realized I had that 3.0RC1 config file (I have another proxy running on a gentoo box, which probably has 3.0). I will try just dropping in the stock ubuntu squid.conf to make sure it's not some oddity of my config file preventing it from restarting. If it still doesn't restart, I suspect this is the root cause of bugs 561750 (squid starts and stops immediately (after upgrade from karmic to lucid)) and573839 (Local Squid quits working on interface change). -- squid restart fails https://bugs.launchpad.net/bugs/577693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577693] Re: squid restart fails
Here's squid.conf, in case there's some configuration option that does what I need ** Attachment added: "squid.conf" http://launchpadlibrarian.net/48101673/squid.conf -- squid restart fails https://bugs.launchpad.net/bugs/577693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577693] Re: squid restart fails
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/48100554/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/48100555/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/48100556/ProcStatus.txt -- squid restart fails https://bugs.launchpad.net/bugs/577693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577693] [NEW] squid restart fails
Public bug reported: Binary package hint: squid Any method of restarting squid fails to restart it. Such as: u...@scrap:~$ sudo /etc/init.d/squid restart [sudo] password for user: Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service squid restart Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the restart(8) utility, e.g. restart squid restart: Job failed to restart = u...@scrap:~$ sudo service squid restart [sudo] password for user: restart: Job failed to restart === u...@scrap:~$ sudo restart squid restart: Job failed to restart == After a while, a "start" using any of these methods works fine. I'm assuming the root problem is that squid takes considerable time to shut down; in the previous init system, "/etc/init.d/squid stop" would not return until squid had exited. The new behavior of returning immediately is quite desirable in the effort to speed suspend and shutdown times, but I think "restart" is still just implemented by "stop" immediately followed by a "start". If the current "stop" behavior is retained, I would guess "restart", instead of being "stop" then "start", will have to have a check for pid exit placed into it. squid shutdowns are on the order of 10s of seconds so if this involves polling I would check every second at the most. Find attached my squid.conf, in case there's some configuration workaround... ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: squid 2.7.STABLE7-1ubuntu12 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 8 23:54:16 2010 ExecutablePath: /usr/sbin/squid ProcEnviron: PATH=(custom, no user) SourcePackage: squid ** Affects: squid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- squid restart fails https://bugs.launchpad.net/bugs/577693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539908] Re: can't change own password with users-admin
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/41058982/Dependencies.txt -- can't change own password with users-admin https://bugs.launchpad.net/bugs/539908 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539908] [NEW] can't change own password with users-admin
Public bug reported: Binary package hint: gnome-system-tools Using "System->Admin->Users & Groups" (which runs users-admin), once I have elevated priveleges, I could change the root password; I could change the password of other users. However, changing my own user password *appears* to work (it says it works, and re-authenticating with the new password within the app works). But logout, and the user still has the old password. System->Preferences->About Me's "Change password" and the "Change password" option for your own user within users-admin look the same, but the "About me" one actually works. passwd at a terminal also works. I read a comment here http://ubuntuforums.org/showthread.php?t=1372144 that "Users & Groups" is more of a sysadmin tool, and it clearly is, but I assume if the user can change everyone else's passwords (with elevated priveleges) they should be able to change their own as well. I wouldn't say this is too high a priority bug, since the user has two other methods to change the password. But, for consistency's sake it'd be good to fix. ProblemType: Bug Architecture: i386 Date: Tue Mar 16 16:23:36 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: gnome-system-tools 2.28.1-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.57-generic SourcePackage: gnome-system-tools Uname: Linux 2.6.31-20-generic i686 XsessionErrors: (gnome-settings-daemon:5256): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:5256): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:5291): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:5323): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (firefox:5364): GLib-WARNING **: g_set_prgname() called multiple times ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- can't change own password with users-admin https://bugs.launchpad.net/bugs/539908 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441835] Re: [Karmic] floppy is not working
"Me too". Using Places->either floppy drive, the light blinks for about a second. Places->Computer then selecting a floppy, the light runs for a second then "Unable to mount location -- no media in the drive" Yes, "either floppy drive" -- my parents still have some 5.25s around and so they've got one of those dual drives. opening a terminal and running "sudo mount /dev/fd0" or "sudo mount /dev/fd1" works just fine, and unmounting via GUI then works too. -- [Karmic] floppy is not working https://bugs.launchpad.net/bugs/441835 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441835] Re: [Karmic] floppy is not working
"Me too". Using Places->either floppy drive, the light blinks for about a second. Places->Computer then selecting a floppy, the light runs for a second then "Unable to mount location -- no media in the drive" Yes, "either floppy drive" -- my parents still have some 5.25s around and so they've got one of those dual drives. opening a terminal and running "sudo mount /dev/fd0" or "sudo mount /dev/fd1" works just fine, and unmounting via GUI then works too. -- [Karmic] floppy is not working https://bugs.launchpad.net/bugs/441835 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311601] Re: start up
A "UNC" style error means a bad hard disk. But, in the mini 9 it'd actlually be SSD (solid state disk), rather than a rotating disk. Still though, either the disk didn't get plugged in properly or it's bad. Dell should cover that under warranty. -- start up https://bugs.launchpad.net/bugs/311601 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 257286] Re: No sound in Intrepid alpha 3 using ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01)
Well, see bug #272205, there's still *some* problems with this in some specific cases. Since there's good discussion there I wouldn't reopen this bug though... -- No sound in Intrepid alpha 3 using ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01) https://bugs.launchpad.net/bugs/257286 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272205] Re: No sound with kernel 2.6.27, Toshiba ATI IXP SB4x0
I have the same problem with a Toshiba Satellite (L35-S2316... thanks Toshiba, for wiring every single Satellite L35 differently heh..) What I ended up with was using model=hp instead of model=dallas. The internal speakers are almost uselessly quiet (I don't recall if they were louder before (i.e. with 8.04.1) or not, it's not my computer). But the headphones work fine. This machine might just have quiet speakers 8-) This machine has a RS480 primary chipset, which uses the SB400 for most of the goods (including IXP SB4X0 audio.) -- No sound with kernel 2.6.27, Toshiba ATI IXP SB4x0 https://bugs.launchpad.net/bugs/272205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75179] Re: AoE module doesn't work with vblade
I can confirm this is a probelm in 8.10. I updated just now (Nov 13th). Steps to reproduce: sudo modprobe aoe dmesg ... [85898.044715] aoe: AoE v47 initialised. [EMAIL PROTECTED]:~$ sudo aoe-discover aoe-discover: /dev/etherd/discover does not exist or is not writeable. [EMAIL PROTECTED]:~$ ls /dev/ether* ls: cannot access /dev/ether*: No such file or directory [EMAIL PROTECTED]:~$ It appears that udev has no rules for aoe whatsoever. Suggested possibilities for repair: 1) Put in udev rules. Probably best but I have no idea where to start. 2) Easy hack, change aoe-mkdevs so it doesn't sanity check (currently: [EMAIL PROTECTED]:~$ sudo aoe-mkdevs /dev/etherd aoe-mkdevs Error: udev detected. You shouldn't need to use aoe-mkdevs. aoe-mkdevs: Please see the aoe-mkdevs manpage. aoe-mkdevs: Exiting. ) Let them go under /dev/.static/dev/ or whatever, as long as the aoetools are self-consistant I don't see the harm, except from an aesthetic standpoint.) 3) Are there newer aoetools that just aren't in tree? the kernel aoe atuff is v47, aoetools is v26. For me severity is low. I thought I'd play with ata-over-ethernet a little. it doesn't work right now. I didn't have specific plans for it, I was just going to keep around with trying to share CD-ROMs, see if aoe over some ethernet gives xp the massive speedup I got when I put a bunch of XPs applications on a samba share instead of local. (I don't have an XP install any more, though so that might put a monkey in the wrench. 2 Gentoo and 4 Ubuntu systems 8-). ** Changed in: linux (Ubuntu) Status: Won't Fix => New -- AoE module doesn't work with vblade https://bugs.launchpad.net/bugs/75179 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281610] Re: [regression, intrepid] Xorg servers broken "No core keyboard" and "failed to initialize core devices"
"Me to." 1.25ghz G5, the 1.5.2-2ubuntu3 xserver-xorg-core and related xserver-xorg-ubuntu3 packages fixed things up. Nice work! -- [regression, intrepid] Xorg servers broken "No core keyboard" and "failed to initialize core devices" https://bugs.launchpad.net/bugs/281610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232051] Re: talkd does not work
Yeah. inetd.conf, "udp"s should be "udp4"s or an IPV6 connection is being used I think. Also, I found when running as "nobody" (since nobody.tty doesn't work), that ytalk would return "[EMAIL PROTECTED] refusing messages". Running as "root" I get a ytalk request properly. I suppose this is insecure, "nobody" should be placed into the tty group (it appears in /etc/group tty has no members whatsoever.) -- talkd does not work https://bugs.launchpad.net/bugs/232051 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232051] Re: talkd does not work
So, I pulled the source, commented out the sanity checks that force talkd to say "talkd[13554]: recvfrom: bogus address length". WIth this commented out it said "bogus address family". With *this* commented out, it logs lines such as "Oct 3 23:44:56 voltron talkd[15391]: ::a00:205:0:0 (0.0.0.0): unintelligible packet" There's the problem! That looks suspiciously like (part of) an IPV6 address -- I think it is not specifying the address type, is being given the IPv6 address, and is thoroughly not IPv6 compatible. I'm going to look into this, if not tonight then pretty soon. I'm assuming it'll be a 1-line patch to specify IPV4 only. (Well, 3 lines maybe if I patch the broken username in Bug 250971.) I think this will also fix 250975 (Ytalk hangs). Ytalk does hang, as a direct result of talkd not working. -- talkd does not work https://bugs.launchpad.net/bugs/232051 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247003] Re: gnome-session makes Xorg crash in xf86SetScrnInfoModes
Umm... never mind I guess? The local OpenBSD expert was netbooted the box into OpenBSD for a few days. When I rebooted into Ubuntu, without even running any updates since the last time it didn't work, it now works. Odd. I do have a different Trinitron hooked up..? -- gnome-session makes Xorg crash in xf86SetScrnInfoModes https://bugs.launchpad.net/bugs/247003 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247003] Re: gnome-session makes Xorg crash in xf86SetScrnInfoModes
"Me too". I upgraded from 8.04.1 for PowerPC to 8.10... on a well, it's a Frankenstein. 1250mhz G4 Windtunnel motherboard, but stuck into a Compaq SP750 case. Yeah.. kind of a prank. (When I was on vacation, my coworkers backed up my data, pulled the SP750 board, replaced the G4 with an identical 8.04 PPC setup, complete with proper USB adapter so I had the same IBM Model M keyboard hooked up and everything; they took bets on how long it'd take me to notice... about 4 hours. It was pretty obvious after I rebooted and heard the mac startup sound & Mac boot loader; otherwise, not obvious at all.) Excerpt from Xorg.0.log.old, which is attached. The failsafe terminal works; I put on xfce4, which was super-stripped but a friend showed me how to add some menus and launchers; it doesn't crash either. X.Org X Server 1.4.99.905 (1.5.0 RC 5) Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Ubuntu (xorg-server 2:1.4.99.905-0ubuntu5) Current Operating System: Linux user-desktop 2.6.24-19-powerpc #1 Fri Jul 11 21:37:37 UTC 2008 ppc Build Date: 01 August 2008 12:03:37AM Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0x94) [0x10088c44] 1: [0x100344] 2: [0x10211c98] 3: /usr/X11R6/bin/X(xf86SetScrnInfoModes+0x1e0) [0x100b80f0] 4: /usr/X11R6/bin/X [0x100c23e8] 5: /usr/X11R6/bin/X(RRGetInfo+0xf8) [0x1014caa8] 6: /usr/X11R6/bin/X(ProcRRGetScreenResources+0x13c) [0x10151c2c] 7: /usr/X11R6/bin/X [0x101494ac] 8: /usr/X11R6/bin/X(Dispatch+0x4b0) [0x10047bb0] 9: /usr/X11R6/bin/X(main+0x43c) [0x100289dc] 10: /lib/libc.so.6 [0xf975b24] 11: /lib/libc.so.6 [0xf975ce0] Fatal server error: Caught signal 11. Server aborting === And, relevant line from lspci -v: :00:10.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (rev 01) Subsystem: ATI Technologies Inc Radeon RV250 If [Radeon 9000] Flags: bus master, stepping, 66MHz, medium devsel, latency 255, IRQ 48 Memory at 9800 (32-bit, prefetchable) [size=128M] I/O ports at 0400 [size=256] Memory at 9000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at f100 [disabled] [size=128K] Capabilities: Kernel driver in use: radeonfb I just updated today, but I don't know how far behind the PPC builds are compared to regular. libgl1-mesa-dri is at 7.1~rc3.1ubuntu2 though. ** Attachment added: "Xorg.0.log.old" http://launchpadlibrarian.net/16484550/Xorg.0.log.old -- gnome-session makes Xorg crash in xf86SetScrnInfoModes https://bugs.launchpad.net/bugs/247003 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247266] Re: possible bug in Firefox when using dialup connection ?
*** This bug is a duplicate of bug 191889 *** https://bugs.launchpad.net/bugs/191889 >Will this just a normal update to Hardy 8.04.1 or will it be a new release >of Hardy ? Since the plan is to replace Firefox 3 with 3.0.1, it'll just come as a regular update via the update manager. Rock on! -- possible bug in Firefox when using dialup connection ? https://bugs.launchpad.net/bugs/247266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192888] Re: firefox crashes on flash contents when using libflashsupport
So I've generally just dealt with this, since firefox now at least has the option to reload it's tabs. My gentoo boxes do not crash with flash though -- now with flash10 or previously with flash9 (even when using libflashsupport, to get me audio over the network.) I never thought much of it, I mean, they're totally different distros.. I didn't think I'd track down the root difference. But, today I looked -- gentoo uses a different libflashsupport! It gets it from https://svn.revolutionlinux.com/MILLE/XTERM/trunk/libflashsupport/Tarballs/libflashsupport-1.2.tar.bz2 I built it, installed it on my ubuntu system. No sound. It checks for pulse then esd by looking in /tmp/.pulse-[USER], /var/lib/run/pulse, and /tmp/.esd. So I put "export FLASH_FORCE_PULSEAUDIO=1" into my .bashrc. Sound, and virtually no crashes! I've managed to crash once, but I have bwin.de AND lepoint.fr up, no crashes, even if I play the vid on bwin.de. (As they say way up there --^ bwin or lepoint alone crash almost 100% of the time). Someone ought to take a look at this copy of libflashsupport, and either adapt it to ubuntu, or find what bug(s) it fixes compared to the 0pointer code. I suppose per the code from 05-16-2008, it might not be a 100% fix but it seems quite a bit more stable to me. Or, alternately, get flash10 into hardy... then of course libflashsupport can be ditched. -- firefox crashes on flash contents when using libflashsupport https://bugs.launchpad.net/bugs/192888 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191889] Re: [MASTER] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager.
---^ I second Jonathan Blow's idea.. having apps behave differently if they think they are online or not is just not "UNIXey". IMHO, they should do what they are told, and just find out they have "no route to host" if there in fact isn't one. -- [MASTER] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager. https://bugs.launchpad.net/bugs/191889 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191889] Re: [MASTER] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager.
>Do you have more than one login session running when you see this >issue? Nope.. just one session. Without my kludge, It's just like what Daniel Newman etc. have described where the CDMA aircard is a PPP link, and NetworkManager0.6x apparently doesn't track PPP state. If I use wifi, or ethernet, firefox is online. If I don't have a wifi or ethernet connection, and use PPP only, firefox decides I'm offline. With the kludge, as I say, nm-applet doesn't show proper status for ethernet or static IP wifi (or PPP) (the machine DOES get online, nm- applet just doesn't show it.) For normal wifi, nm-applet doesn't show the DHCP swirl but otherwise does operate fully (shows access point list, joins access points, shows signal strength, etc.) And, at all points, firefox shows online status as the UNIX gods intended 8-). -- [MASTER] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager. https://bugs.launchpad.net/bugs/191889 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191889] Re: [MASTER] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager.
I've found a kludgy "fix" for this (that doesn't just involve removing nm, since it's wireless and wired handling are nice). In my case, I have a Inspiron 2200 with wifi set via ndiswrapper (which works fine) and an aircard (Verizon PC5740) which worked except for the "Offline mode" problem. So it's the case where if I don't have wifi, and dial via CDMA, I get the "Work Offline" stuff going on. So, if I go into /etc/dbus-1/system.d/NetworkManager.conf, I inserted in line 18 (all on one line): (That's in the 'policy at_console="true" ' section of the file in case yours is arranged a little differently for whatever reason.) This file seems to be checked on-the-fly, I could change this and see an immediate effect on firefox (although I rebooted to check for side effects). Consequences: This blocks firefox and any other app's attempt to get the online/offline state from NetworkManager, which makes it (and probably any other apps that try to check NetworkManager) decide Networkmanager is not there and assume online state. It ALSO blocks nm-applets access to this though... Since nm-applet can't get the online/offline state from NetworkManager either, it doesn't show online state properly (it'll show the exclamation mark while the network is up and running fine for static IP wifi and ethernet)... For regular ol' DHCP wifi, it does still show the signal bars (since blocking "status" doesn't block wifi signal strength info). Also, under "manual configuration" the "Roaming mode" text changes to "This network interface is not configured", and the checked "Roaming mode" checkboxes change to uncheckd "Enable this connection" checkboxes. But the interface seems consistent and to behave itself. Problem solved as far as I'm concerned, until I got to NetworkManager 0.7! -- [MASTER] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager. https://bugs.launchpad.net/bugs/191889 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224773] Re: console-setup/layoutcode=en_US causes wrong keyboard selection
Maybe this has already been fixed in docs? I probably had gotten the layoutcode=en_US from some old debian doc, or blog or something, last year. Now the only URL I can find anywhere that mentions this is: http://ubuntulinuxhelp.com/ubuntu-linux-plug-n-play-zone-revisited/ Umm.. yeah. I looked around the pxeboot, network install, etc. docs and don't see anywhere good to put a note regarding layoutcode (since the instructions seem to set keyboard using an entirely separate preseed). Unless Damian finds something maybe this bug just needs to be set invalid? -- console-setup/layoutcode=en_US causes wrong keyboard selection https://bugs.launchpad.net/bugs/224773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224773] [NEW] console-setup/layoutcode=en_US causes wrong keyboard selection
Public bug reported: Binary package hint: console-setup I'm running a preseed install with Ubuntu 8.04, and what I found is with console-setup/layoutcode=en_US in the isolinux.cfg (for CD) and pxelinux.cfg/default (for net install), the keyboard layout is set to "af" (Afghanistan), so I cannot even login. I did eventually realize in ubuntu.seed, I had "d-i console- setup/layoutcode string us" and changing the string in isolinux.cfg and pxelinux.cfg/default to match fixed it (changed en_US to us). There are quite a few examples online that use en_US though, so I would say there are two solutions: 1) Add a mention to the online preseed documentation that en_US and similar do not work for layoutcode even if they used to. (Preferred IMHO). 2) Work up console-setup so it accepts formats like en_US again. (Might save a few people grief, but I do see this as inelegant since US keyboard layout's not language dependent, this isn't the clean solution.) Great work everybody! We've installed 1000's of copies of Ubuntu at the computer surplus I work at, and use it at home, and it works great! Since they are surplus, we get so many different models and ages of machines (right down to P2s and P3s), it's great to be able to just plug it into the install LAN and go work on something else knowing the install will work out of the box. (Also makes a nice burn-in test -- install failure points pretty solidly to a flakey computer 8-) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- console-setup/layoutcode=en_US causes wrong keyboard selection https://bugs.launchpad.net/bugs/224773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181201] [hardy] dist-upgrade removes a lot of (non-)obsolete packages
Public bug reported: Binary package hint: update-manager I have a bare copy of Ubuntu 7.10 in a qemu disk image that I tried this on (bare as in I haven't installed extra packages or reconfigured it at all.) I fired up update-manager to make sure it was up to date (it was, as of 7 Jan 2008). I then ran "sudo update-manager -d". First time, I didn't pay attention to what it was removing, and the result is VERY bare. The games were gone, all but the word processor gone, firefox was gone, and the desktop was a solid orange/tan color rather than having any desktop image. After reverting to a 7.10 image again and looking at what it's doing, it currently wants to remove as obsolete: beforelight, bitmap, firefox, firefox-gnome-support, gnome-cards-data, gnome-games, gnome-games-data, hal-device-manager, ico, libbrlapi1, libcdio6, libchromexvmc1, libchromexvmcpro1, libgpod2, libmtp6, libntfs- 3g12, libopencdk8, libpt-plugins-alsa, libtotem-plparser7, libuniconf4.3, libwvstreams4.3-base, libwvstreams4.3-extras, linux- headers-2.6.22-14, linux-headers-2.6.22-14-generic, openoffice.org (and openoffice.org-calc, -draw, -evolution, -gnome, -gtk, -impress, -java- common, -math), ubufox, xf86dga, and xgc. Oddly this list doesn't match the list of packages to be removed when it asks "Do you want to start the upgrade?" (I assume that's odd at least -- but I don't know, maybe the obsolete packages are found in a seperate sweep.) Well, no comment on the libraries, but firefox, gnome-games, and openoffice.org-* shouldn't be removed for sure (oddly, the word processor is not removed, just all the rest.) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- [hardy] dist-upgrade removes a lot of (non-)obsolete packages https://bugs.launchpad.net/bugs/181201 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
