[Bug 2081150] [NEW] Python3 TQDM package is missing version specification
Public bug reported: The python3-tqdm (version 4.66.2-2) package is created with version 0.0.0 as the internal version specifier, meaning any attempt at using Python to check it against a version will fail. I have a python script using pkg_resources.require() / packaging.requirements which requires tqdm>=4.62.3 (something the Ubuntu package satisifies). HOWEVER: /usr/lib/python3/dist-packages/ contains the folder tqdm-0.0.0.dist-info which contains the files entry_points.txt INSTALLER METADATA top_level.txt WHEEL The METADATA file contains at the top: Metadata-Version: 2.1 Name: tqdm Version: 0.0.0 Note the version 0.0.0 in both METADATA and folder name python3-numpy is an example of being correct with both the folder and METADATA file containing the correct version. The result is that version checks work against python3-numpy but not python3-tqdm. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3-tqdm 4.66.2-2 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 19 10:00:08 2024 Dependencies: InstallationDate: Installed on 2024-09-18 (1 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: tqdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tqdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081150 Title: Python3 TQDM package is missing version specification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tqdm/+bug/2081150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
I have a similar problem on 18.04 on a Lenovo V330. Suspend works fine without external monitor, but no matter what I do it's inhibited when its connected. I want it to suspend always. $ grep -i lid /etc/systemd/logind.conf #HandleLidSwitch=suspend HandleLidSwitchDocked=suspend #LidSwitchIgnoreInhibited=yes $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true $ systemd-inhibit --list --mode=block Who: gdm (UID 121/gdm, PID 5935/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: gaute (UID 1000/gaute, PID 1713/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Only the second of these goes away when monitor is unplugged, but lid close still works. This is possibly due to a bug in gsd-power which is mentioned in the following guthub issues. https://github.com/systemd/systemd/issues/7137 https://github.com/linuxmint/cinnamon-settings-daemon/issues/224 https://github.com/linuxmint/Cinnamon/issues/7347 ** Bug watch added: github.com/linuxmint/cinnamon-settings-daemon/issues #224 https://github.com/linuxmint/cinnamon-settings-daemon/issues/224 ** Bug watch added: github.com/linuxmint/Cinnamon/issues #7347 https://github.com/linuxmint/Cinnamon/issues/7347 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956071] Re: Xorg crashed with SIGSEGV in XIGetDeviceProperty()
Just to chime in about 1.5.99.902-0ubuntu5. No crashes for 3 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956071] Re: Xorg crashed with SIGSEGV in XIGetDeviceProperty()
I've got this bug on every laptop in the household :-( an Eee PC 1005HA, an older dell inspiron and my own dell Vostro V131. I _think_ they all have Intel graphics -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872244] Re: grub2 recordfail logic prevents headless system from rebooting after power outage
Agree: A more stripped-down grub2-package is appropriate for servers. Also, for either servers or desktops: There should be a setting in /etc/default/grub, called GRUB_RECORDFAIL_TIMEOUT or GRUB_TIMEOUT_AFTER_BOOTFAIL or something. This is today effectively hard coded to -1 (forever). And it is this hardcoding many users fiddle with. Conclusion: go from hardcoded setting to configurable option. I propose that the bootfail-timeout is set to 30 sec by default for servers, perhaps also for clients. This is not unlike how it is on a different OS we all know: after a failed boot, you're halted for 30sec at the boot menu, but then the default entry boots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872244 Title: grub2 recordfail logic prevents headless system from rebooting after power outage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/872244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 430809] Re: [Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch
Just what I was doing, and it seems to have solved the problem. Found it mentioned in Bug# 441768 V1520A04-32_64.exe did the trick. Thanks for the quick response anyway :) -- [Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch https://bugs.launchpad.net/bugs/430809 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 430809] Re: [Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch
Sorry guys, but I seem to be having this exact problem in the released Karmic. Dell vostro 1520. Starting with hw switch off works fine. Exactly same crash of smbios-wireless-ctl as in comment #56 ( posted as Bug #464449 ) Perhaps just need to blacklist vostro 1520 ? Haven't looked into how that works yet. -- [Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch https://bugs.launchpad.net/bugs/430809 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 464449] Re: smbios-wireless-ctl crashed with IndexError in __getitem__()
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/34667799/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/34667800/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/34667801/ProcStatus.txt ** Attachment added: "Traceback.txt" http://launchpadlibrarian.net/34667802/Traceback.txt ** Visibility changed to: Public -- smbios-wireless-ctl crashed with IndexError in __getitem__() https://bugs.launchpad.net/bugs/464449 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 326117] Re: syndaemon gone after resume on intrepid and jaunty
Problem seem to persist on Jaunty.
I _may_ have seen it survive a few times, but I am uncertain of the
circumstances, and can't reliably reproduce.
Anyway I have found a workaround.
In /usr/lib/pm-utils/sleep.d/ I have created "50syndaemon" as follows:
#!/bin/sh
resume_syndaemon()
{
if [ ! "$( pidof syndaemon )" ]; then
export DISPLAY=:0.0
sudo -u gaute syndaemon -d -t -i 2
fi
}
case "$1" in
thaw|resume)
resume_syndaemon
;;
*) exit $NA
;;
esac
exit 0
--
I cannot quite see how this could be generalized however.
There is the hardcoded username, and I guess DISPLAY=:0.0 cannot always be
guaranteed,
and a user may have wanted other arguments to syndaemon anyway.
I guess the right thing to do is make the daemon survive in the first place.
I would still like to contribute to this, but it would be good to know if I am
the only one that have this problem,
and if not, then some guidance on what to try or how to instrument would be
good.
--
syndaemon gone after resume on intrepid and jaunty
https://bugs.launchpad.net/bugs/326117
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 326117] Re: syndaemon gone after resume on intrepid and jaunty
** Summary changed: - syndaemon gone after resume on intrepid + syndaemon gone after resume on intrepid and jaunty ** Tags removed: needs-xorglog -- syndaemon gone after resume on intrepid and jaunty https://bugs.launchpad.net/bugs/326117 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 367815] Re: Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
That was the hint I needed. Mea culpa :( /var/log/pm-suspend.log contained the lines: /usr/lib/pm-utils/sleep.d/45vmware-stop suspend suspend: /usr/lib/pm-utils/sleep.d/45vmware-stop: 34: Syntax error: "}" unexpected Returned exit code 2. Mon Apr 27 23:03:21 CEST 2009: Inhibit found, will not perform suspend Which was an empty proc in a script I made to work around a problem where bonjour and vmware would cause a hang on resume. Finally the script got called :-/ I went over to https://wiki.ubuntu.com/DebuggingKernelSuspend with a view to putting in a mention of /var/log/pm-suspend.log, but on second thought that does not seem the right place. ** Changed in: pm-utils (Ubuntu) Status: New => Invalid -- Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000 https://bugs.launchpad.net/bugs/367815 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 367815] Re: Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
** Attachment added: "lsmod.output.txt" http://launchpadlibrarian.net/26021428/lsmod.output.txt -- Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000 https://bugs.launchpad.net/bugs/367815 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 367815] Re: Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/26021418/dmesg.txt -- Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000 https://bugs.launchpad.net/bugs/367815 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 367815] Re: Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
** Attachment added: "syslog" http://launchpadlibrarian.net/26021388/syslog -- Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000 https://bugs.launchpad.net/bugs/367815 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 367815] [NEW] Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
Public bug reported: Linux sniff 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux Suspend and Hibernate simply fails to work. ( focusing on Suspend ) I chose Suspend from the menu, screen fades to black, disk chirps slightly, and I am presented with the "unlock" screen. Neither /var/log/messages, /var/log/dmesg or /var/log/Xorg.0.log has anything new, but in /var/log/syslog i find about this: Apr 27 10:12:35 sniff kernel: [ 1302.696203] [drm:i915_getparam] *ERROR* Unknown parameter 6 Apr 27 10:12:36 sniff kernel: [ 1303.661656] [drm:i915_getparam] *ERROR* Unknown parameter 6 Apr 27 10:12:37 sniff anacron[6064]: Anacron 2.3 started on 2009-04-27 Apr 27 10:12:37 sniff anacron[6064]: Normal exit (0 jobs run) Apr 27 10:12:37 sniff kernel: [ 1304.253637] CPU0 attaching NULL sched-domain. Apr 27 10:12:37 sniff kernel: [ 1304.268087] CPU0 attaching NULL sched-domain. Tried to switch to VT1 by pressing Ctrl-Alt-F1, but that fails too. sudo pm-suspend at a regular prompt just does nothing. tried booting Linux sniff 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux and now the message is: Apr 27 10:47:24 sniff kernel: [ 214.572000] [drm:i915_getparam] *ERROR* Unknown parameter 5 Apr 27 10:47:25 sniff kernel: [ 215.556000] [drm:i915_getparam] *ERROR* Unknown parameter 5 Otherwise, exactly the same. The instructions at: https://wiki.ubuntu.com/DebuggingKernelSuspend focuses on resume, so now I am at loss for what to try. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: suspend -- Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000 https://bugs.launchpad.net/bugs/367815 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 367815] Re: Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/26021399/Xorg.0.log -- Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000 https://bugs.launchpad.net/bugs/367815 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 326117] Re: syndaemon gone after resume on intrepid
Status is still "Incomplete".. Did I miss something? ** Attachment removed: "Xorg.0.log.old.txt" http://launchpadlibrarian.net/23625015/Xorg.0.log.old.txt -- syndaemon gone after resume on intrepid https://bugs.launchpad.net/bugs/326117 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 326117] Re: syndaemon gone after resume on intrepid
** Attachment added: "Xorg.0.log.old" http://launchpadlibrarian.net/23624991/Xorg.0.log.old -- syndaemon gone after resume on intrepid https://bugs.launchpad.net/bugs/326117 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 326117] Re: syndaemon gone after resume on intrepid
Here are both after a fresh restart, and one suspend/resume. ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/23624988/Xorg.0.log -- syndaemon gone after resume on intrepid https://bugs.launchpad.net/bugs/326117 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 326117] Re: syndaemon gone after resume on intrepid
Better mimetype :) ** Attachment added: "Xorg.0.log.old.txt" http://launchpadlibrarian.net/23625015/Xorg.0.log.old.txt -- syndaemon gone after resume on intrepid https://bugs.launchpad.net/bugs/326117 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 326117] Re: syndaemon gone after resume on intrepid
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/22039291/Dependencies.txt -- syndaemon gone after resume on intrepid https://bugs.launchpad.net/bugs/326117 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 326117] [NEW] syndaemon gone after resume on intrepid
Public bug reported: Binary package hint: xfree86-driver-synaptics I have been digging into this for a while now, and I'm pretty certain it has not been mentioned anywhere. The situation: Ubuntu 8.10, 2.6.27-9-generic, dell inspiron 6000, xserver-xorg-input- synaptics 0.15.2-0ubuntu7 # cat /etc/hal/fdi/policy/shmconfig.fdi True No active SHM in xorg.conf syndaemon starts nicely by hand, and from system->prefs->session # ps aux | grep sy[n] root 19030 0.4 0.0 2988 508 ? Ss 09:42 0:09 syndaemon -d -t However, after a resume it is just gone. With the -S option as mentioned in bug 295236 it survives, but stops working after resume. I have tried a workaround by way of a small script: /usr/lib/pm-utils/sleep.d/55syndaemon-resume my log-lines verifies that it does get called, and the right function executed, but apparently it fires too early in the resume sequence since I am then greeted with an error on the root terminal. Almost identical to bug 295236. # X Error of failed request: BadDevice, invalid or uninitialized input device Major opcode of failed request: 146 (XInputExtension) Minor opcode of failed request: 4 (X_CloseDevice) Serial number of failed request: 22691 Current serial number in output stream: 22692 I tried "99Zsyndaemon-resume" as well, and with a "sleep 10" just to be sure, so perhaps the sequence is not the problem after all.. I tried the scripts in Bug:253079 "should include script for launching syndaemon" but unless I'm mistaken, /etc/X11/Xsession.d/ does not get sourced on resume? What now? I'm out of ideas.. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: xserver-xorg-input-synaptics 0.15.2-0ubuntu7 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfree86-driver-synaptics Uname: Linux 2.6.27-11-generic i686 ** Affects: xfree86-driver-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- syndaemon gone after resume on intrepid https://bugs.launchpad.net/bugs/326117 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
RE: [Bug 133552] Re: Config option to enable debug logging inunattended-upgrade
I was only using debugging to find out why specific packages weren't installed. The answer was config-file-prompt so I agree that if that is included in the regular output, it is OK - and one should rather consider my approach of letting the user (when in need) include the --debug output by configuration directive in /etc/apt/apt.conf.d/... Med vennleg helsing / Best regards Gaute Lund > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Vogt > Sent: Tuesday, March 11, 2008 10:01 AM > To: [EMAIL PROTECTED] > Subject: [Bug 133552] Re: Config option to enable debug > logging inunattended-upgrade > > Thanks for your bugreport. > > what information in the debug output do you find most > important? I wonder if those shouldn't be included in the > regular output then. > > Thanks, > Michael > > ** Changed in: apt (Ubuntu) >Importance: Undecided => Wishlist >Status: New => Incomplete > > -- > Config option to enable debug logging in unattended-upgrade > https://bugs.launchpad.net/bugs/133552 > You received this bug notification because you are a direct > subscriber of the bug. > -- Config option to enable debug logging in unattended-upgrade https://bugs.launchpad.net/bugs/133552 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 133551] Re: Config option to enable debug logging
If packages held back by conffile prompt are shown in the logs w/o debug, I'm personally OK. I can only note that there is still no way to run with --debug enabled without modifying the /etc/cron.daily/apt script - but personally, I don't need this. Case closed. -- Config option to enable debug logging https://bugs.launchpad.net/bugs/133551 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 133551] Re: Config option to enable debug logging
See aditional info at the parallel bug report https://bugs.launchpad.net/ubuntu/+source/apt/+bug/133552 I might be best if it was unattended-upgrade honouring a new config option to produce debug logging, but not debug output to console. -- Config option to enable debug logging https://bugs.launchpad.net/bugs/133551 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
[Bug 133552] Re: Config option to enable debug logging in unattended-upgrade
The line + unattended-upgrade --debug could be + unattended-upgrade --debug > /dev/null 2>&1 because unattended-upgrade in debug mode gives extra output "Done downloading", generating cron mail. Based on this it might be a better option if unattended-upgrade itself honoured a new config option to produce debug logging, but not debug output to console. -- Config option to enable debug logging in unattended-upgrade https://bugs.launchpad.net/bugs/133552 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
[Bug 133551] Config option to enable debug logging
Public bug reported: Binary package hint: unattended-upgrades DISCLAIMER: I don't code python, and don't usually post patches. So please bear with me if I stick my foot in my mouth. BACKGROUND: I have unattended-upgrades running on edgy with a well- working setup. apache2-common didn't get upgraded automatically. Only when I turned on debug logging I discovered this was because it had "conffile prompt". To run unattended-upgrade with debug logging, I had to edit the appropriate line in /etc/cron.daily/apt. PATCH: I propose a new config option "Unattended-Upgrade::Debug" which I set to "1" in my /etc/apt/apt.conf.d/50unattended-upgrades. Now, I modified the /etc/cron.daily/apt script to respect this option and launch unattended-upgrade with the --debug option. I have files a parallell "bug" report including simple patch to the apt package, as the cron script belongs to that package. I am posting here also in case you think it should rather be fixed in /usr/bin/unattended-upgrade. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- Config option to enable debug logging https://bugs.launchpad.net/bugs/133551 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
[Bug 133552] Config option to enable debug logging in unattended-upgrade
Public bug reported: Binary package hint: apt DISCLAIMER: I don't code python, and don't usually post patches. So please bear with me if I stick my foot in my mouth. BACKGROUND: I have unattended-upgrades running on edgy with a well- working setup. apache2-common didn't get upgraded automatically. Only when I turned on debug logging I discovered this was because it had "conffile prompt". To run unattended-upgrade with debug logging, I had to edit the appropriate line in /etc/cron.daily/apt. PATCH: I propose a new config option "Unattended-Upgrade::Debug" which I set to "1" in my /etc/apt/apt.conf.d/50unattended-upgrades. Now, I modified the /etc/cron.daily/apt script to respect this option and launch unattended-upgrade with the --debug option: --- /tmp/apt.org2007-08-19 23:39:06.0 +0200 +++ /etc/cron.daily/apt 2007-08-19 23:30:29.0 +0200 @@ -158,4 +158,7 @@ eval $(apt-config shell UnattendedUpgradeInterval APT::Periodic::Unattended-Upgrade) +DebugLogging=0 +eval $(apt-config shell DebugLogging Unattended-Upgrade::Debug) + # laptop check, on_ac_power returns: @@ -195,5 +198,9 @@ UPGRADE_STAMP=/var/lib/apt/periodic/upgrade-stamp if check_stamp $UPGRADE_STAMP $UnattendedUpgradeInterval; then -unattended-upgrade +if [ ! $DebugLogging -eq 0 ]; then +unattended-upgrade --debug +else +unattended-upgrade +fi update_stamp $UPGRADE_STAMP fi I have filed a parallell "bug" report to the unattended-upgrades- package, in case you think it should rather be fixed in /usr/bin /unattended-upgrade. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- Config option to enable debug logging in unattended-upgrade https://bugs.launchpad.net/bugs/133552 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
[Bug 95795] Re: wireless does not connect through network-manager
" Wedel said on 2007-03-25: (permalink) I can confirm this bug. I have a rt2500 pcmcia card and i can not connect to the network." There is a big chance that your bug is not the same as this bug. Since you have an RT2500 card, you could be suffering from https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/37120";>this bug instead (37120). -- wireless does not connect through network-manager https://bugs.launchpad.net/bugs/95795 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
[Bug 37120] Re: rt2500 driver does not implement wireless extensions correctly
"Try out the new rt2x00 module instead. This is the module that will eventually be merged into the Linux kernel." Unfortunately, the rt2x00 module seems pretty much unmaintained and is not reported to support the Linux Wireless Extensions yet. I found some discussion about this back in July: http://mail.gnome.org/archives/networkmanager-list/2006-July/msg00054.html Sadly, nothing seems to have happened with it since. If at least Network Manager worked with WEP and without any security that would at least be something. -- rt2500 driver does not implement wireless extensions correctly https://bugs.launchpad.net/bugs/37120 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
