Re: [Bug 209041] Re: pyxpcom doesn't get loaded/doesn't work
I'm still running 8.04 (it's an LTS after all.) However, if you are running either of those, it's trivial for *you* to check, just try to open "about:python" in firefox, and see if you get anything... On Fri, Dec 5, 2008 at 10:44 PM, Daniel T Chen <[EMAIL PROTECTED]> wrote: > Is this symptom still reproducible in 8.10 or 9.04? > > ** Changed in: xulrunner-1.9 (Ubuntu) > Status: New => Incomplete > > -- > pyxpcom doesn't get loaded/doesn't work > https://bugs.launchpad.net/bugs/209041 > You received this bug notification because you are a direct subscriber > of the bug. > -- _Mark_ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- pyxpcom doesn't get loaded/doesn't work https://bugs.launchpad.net/bugs/209041 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 346577] Re: dpkg-source failed to rename file across filesystems
Looks like debian fixed this for lenny in debbugs#507217 (dpkg-dev 1.14.24) -- dpkg-source failed to rename file across filesystems https://bugs.launchpad.net/bugs/346577 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 346577] Re: dpkg-source failed to rename file across filesystems
** Bug watch added: Debian Bug tracker #507217 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507217 ** Also affects: dpkg (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507217 Importance: Unknown Status: Unknown -- dpkg-source failed to rename file across filesystems https://bugs.launchpad.net/bugs/346577 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 58240] kpilot doesn't handle [ in pdb-doc names
Public bug reported: Binary package hint: kpilot Invalid entry (missing ']') at /home/eichin/.kde/share/config/kpilot_docconduitrc:14 Invalid entry (missing ']') at /home/eichin/.kde/share/config/kpilot_docconduitrc:15 those lines are: /home/eichin/Edge/docs/Swords Against Death [Book 2 of.txt=25fa6427e2feac62956ae9c0c3eeb80c /home/eichin/Edge/docs/Swords and Deviltry [Book 1 of .txt=4f872c06a3ab766656b04586c105c96c The bug seems to be that kpilot_docconduitrc is a .ini-style file, with everything in a [General] stanza -- and a parser that doesn't use enough context to tell the difference; a workaround would be to somehow quote (maybe urlencode?) the pathnames to the left of the = above. (The docfiles are conventional downloads from fictionwise.com, from at least 5 years back - and raw pilot-xfer doesn't have any trouble with them, of course.) (Aside from the warning, I think this is interfering with syncing, I always get the dialog about duplicate files now...) ** Affects: kdepim (Ubuntu) Importance: Untriaged Status: Unconfirmed -- kpilot doesn't handle [ in pdb-doc names https://launchpad.net/bugs/58240 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 58241] m-x debian-bug doesn't point to ubuntu instead
Public bug reported: Binary package hint: debian-el m-x debian-bug generates the standard template, with all the useful information, but sends it to debian instead (I tried reporting a bug in kpilot, in particular.) Since debian doesn't want them (Bug#385263 as an example) it should send them somewhere ubuntu (ideally, it should file them in malone directly...) ** Affects: emacs-goodies-el (Ubuntu) Importance: Untriaged Status: Unconfirmed -- m-x debian-bug doesn't point to ubuntu instead https://launchpad.net/bugs/58241 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
FYI I'm running pre-hardy, updated as of 20080422, on a Lenovo Thinkpad T60p: 26d10014b09439dc5a8573c2a6f85b0a /lib/firmware/2.6.24-16-generic/iwlwifi-3945-1.ucode 26d10014b09439dc5a8573c2a6f85b0a /lib/firmware/2.6.24-16-generic/iwlwifi-3945.ucode which match iwlwifi-3945-ucode-2.14.1.5.tgz from http://www.intellinuxwireless.org/iwlwifi/downloads, and I'm still seeing [ 2218.395642] wlan0: No ProbeResp from current AP 00:xx:xx:xx:xx:xx - assume out of range [ 2219.196315] wlan0: No STA entry for own AP 00:xx:xx:xx:xx:xx [ .988446] wlan0: No STA entry for own AP 00:xx:xx:xx:xx:xx which persist until I unload and reload the module. (I also have the problem that occasionally the reload entirely hangs the laptop, leaving just a blinking caps-lock light as an indication...) I do run across suspend and restore cycles, and move among a number of wireless domains (I always just force-reload the module after restoring from suspend; it sometimes doesn't need it, but the force reload is always faster :-) Only seems to happen with WPA; when I'm using WPA I'm also using 802.11a; lspci output: 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) Subsystem: Intel Corporation Unknown device 1010 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/144621 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 58240] Re: kpilot doesn't handle [ in pdb-doc names
What does "expired" mean? bugs don't magically improve because time has passed :-) On 9/21/07, Launchpad Janitor <[EMAIL PROTECTED]> wrote: > [Expired for kdepim (Ubuntu) because there has been no activity for 60 > days.] > > -- > kpilot doesn't handle [ in pdb-doc names > https://bugs.launchpad.net/bugs/58240 > You received this bug notification because you are a direct subscriber > of the bug. > -- _Mark_ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- kpilot doesn't handle [ in pdb-doc names https://bugs.launchpad.net/bugs/58240 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 21993] Re: When Print-server not found on network, cups-manager crashes
I see the problem in a new install of 7.10 Gutsy Gibbon as well - ServerName points to a printserver at work, I'm at home, I try to print, and it hangs (completely, no X updates at all) for a long time (more than 5 minutes) but then comes up with a print dialog that only lists postscript/default [which is fine, it's the delay that's the problem...] lsof shows the IPP connection in SYN_SENT (ie. it's not getting connection refused, it's getting nothing at all, as in a down machine or firewall. A misconfigured client.conf could probably do that too...) After printing to file it appears that it is trying to contact the server again, leading to a similar hang. -- When Print-server not found on network, cups-manager crashes https://bugs.launchpad.net/bugs/21993 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 209041] [NEW] pyxpcom doesn't get loaded/doesn't work
Public bug reported: Binary package hint: xulrunner-1.9 xulrunner-1.9 Version: 3.0~b4+nobinonly-0ubuntu1 $ lsb_release -rd Description:Ubuntu hardy (development branch) Release:8.04 Simplest expression: opening "about:python" fails, even though "about:buildconfig" lists python, and /usr/lib/xulrunner-1.9b4/components/pyabout.py /usr/lib/xulrunner-1.9b4/components/libpyloader.so are both in the xulrunner-1.9 package. (An additional symptom is not seeing Registering '@mozilla.org/module-loader/python;1' (libpyloader.so) Registering '@mozilla.org/network/protocol/about;1?what=python' (pyabout.py) registration messages at startup...) ** Affects: xulrunner-1.9 (Ubuntu) Importance: Undecided Status: New -- pyxpcom doesn't get loaded/doesn't work https://bugs.launchpad.net/bugs/209041 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 58240] Re: kpilot doesn't handle [ in pdb-doc names
As I'm still using 6.06, and kdepim hasn't gotten an update, yes, I'm still experiencing it. No idea if a later release fixes it. On 6/8/07, Richard Johnson <[EMAIL PROTECTED]> wrote: > Are you still experiencing this issue? > > ** Changed in: kdepim (Ubuntu) >Status: Unconfirmed => Needs Info > > -- > kpilot doesn't handle [ in pdb-doc names > https://bugs.launchpad.net/bugs/58240 > You received this bug notification because you are a direct subscriber > of the bug. > -- _Mark_ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- kpilot doesn't handle [ in pdb-doc names https://bugs.launchpad.net/bugs/58240 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 68953] printconf in edgy misconfigures USB printers
Public bug reported: Binary package hint: printconf printconf probed and found my lexmark E210, no problems there. (This is on a fresh upgrade from 6.06 to 6.10, but none of foomatic/cups were installed under 6.06 - I used magicfilter and lpr there.) However, printing didn't work, and ps showed gs and a tree of processes hanging. Some investigation turned up this changelog: * The USB backend no longer supports the usb:/dev/foo format on systems that support device ID queries since 1.2.1-1. Because Linux supports device ID queries, you have to replace your printer configuration uses usb:/dev/foo style with device ID style. usb backend will show device IDs of active USB printers. Sure enough, DeviceURI (in /etc/cups/printers.conf) was set to usb:/dev/usblp0. Manually changing it to DeviceURI usb://Lexmark/E210 after running the back end explicitly: # /usr/lib/cups/backend/usb direct usb://Lexmark/E210 "Lexmark E210" "Lexmark E210 USB #1" "MFG:Lexmark;CMD:GDI;MDL:E210;CLS:PRINTE" and restarting cups cause it to work just fine. ** Affects: foomatic-gui (Ubuntu) Importance: Undecided Status: Unconfirmed -- printconf in edgy misconfigures USB printers https://launchpad.net/bugs/68953 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795079] [NEW] doesn't actually work on ubuntu due to kernel permissions
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725 means the kernel isn't readable so debos (and fakemachine) can't work. The problem manifests as 2018/09/28 18:07:24 open failed: /lib/modules/4.15.0-15-generic/kernel/drivers/virtio/virtio.ko - open /lib/modules/4.15.0-15-generic/kernel/drivers/virtio/virtio.ko: no such file or directory and https://github.com/go-debos/fakemachine/issues/12 makes it clear that upstream doesn't really have any way to work around this. ** Affects: debos (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/1795079 Title: doesn't actually work on ubuntu due to kernel permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1795079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795079] Re: doesn't actually work on ubuntu due to kernel permissions
Ok, I over-interpreted some of the tickets - it doesn't get far enough to run into the permissions problems, because it doesn't deal with `virtio` being builtin instead of a module (which is what the error is from, the `writerKernelModules` function in `fakemachine/machine.go`. Still in the "why is this in ubuntu if there's no way for it to actually work" category, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795079 Title: doesn't actually work on ubuntu due to kernel permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1795079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762816] [NEW] chaoskey interferes with suspend on thinkpad
Public bug reported: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been going on for the last month of bionic, and *possibly* longer but I only recently caught that the Chaoskey was related. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ uname -a Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --status linux-image-4.15.0-13-generic Package: linux-image-4.15.0-13-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 72167 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.15.0-13.14 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-13-generic Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP This package contains the Linux kernel image for version 4.15.0 on 64 bit x86 SMP. . Also includes the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-generic meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762816 Title: chaoskey interferes with suspend on thinkpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762816] Re: chaoskey interferes with suspend on thinkpad
On inspection of apport-collect output, it doesn't appear to filter out serial numbers or SSIDs, so I can't submit it. Also, it seems to have left out any of the logs where the tracebacks mentioned above were included; I'll add at least a useful chunk of kern.log surrounding the problem as an attachment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762816 Title: chaoskey interferes with suspend on thinkpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762816] Re: chaoskey interferes with suspend on thinkpad
Marked confirmed per auto-comment #1 but I'm happy to add other logs on request (not going to audit 11,000 lines of apport output if I can at all avoid it, though.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762816 Title: chaoskey interferes with suspend on thinkpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762816] Re: chaoskey interferes with suspend on thinkpad
big chunk of kern.log with addresses and serial numbers elided. ** Attachment added: "kern.log with some privacy filtering" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+attachment/5109724/+files/kern.log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762816 Title: chaoskey interferes with suspend on thinkpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756621] [NEW] missing dependencies on ruby-sinatra, ruby-rack for -S
Public bug reported: To reproduce: grab a beta-1 ubuntu bionic iso, select "minimal install", apt install ruby-ronn, run "ruby-ronn -S ." and get: eichin@vm-bionic-1:~$ ronn -S . Traceback (most recent call last): 5: from /usr/bin/ronn:140:in `' 4: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 3: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 2: from /usr/lib/ruby/vendor_ruby/ronn/server.rb:2:in `' 1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- rack (LoadError) apt install ruby-rack gives: /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- sinatra/base (LoadError) Finally, apt install ruby-sinatra yields a working server. (I suspect they were previously satisfied indirectly by something else; I don't know when the problem appeared beyond "it was fine in 16.04 and it's not fine in 18.04.") ** Affects: ruby-ronn (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/1756621 Title: missing dependencies on ruby-sinatra, ruby-rack for -S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-ronn/+bug/1756621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899404] Re: please upgrade
Also the one-line fix is at https://github.com/hunterji/flickrapi/commit/e6c8004e61952d5e36929ff4d985b28aa5d3bb38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899404 Title: please upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flickrapi/+bug/1899404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899404] [NEW] please upgrade
Public bug reported:
I'm running in to https://github.com/sybrenstuvel/flickrapi/issues/75
under fossa/20.04 (but groovy/20.10 is the exact same version, 2.1.2-5.1
based on 2.1.2 upstream) and it makes the package pretty much unusable
(since it means initial setup fails with a traceback.)
>>> flickr = flickrapi.FlickrAPI(_api_key, _shared_not_actually_secret)
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/flickrapi/core.py", line 201, in __init__
self.flickr_oauth = auth.OAuthFlickrInterface(api_key, secret,
self.token_cache)
File "/usr/lib/python3/dist-packages/flickrapi/auth.py", line 159, in __init__
if oauth_token.token:
File "/usr/lib/python3/dist-packages/flickrapi/tokencache.py", line 175, in
token
curs.execute('''SELECT oauth_token, oauth_token_secret, access_level,
fullname, username, user_nsid
sqlite3.OperationalError: no such table: oauth_tokens
Latest release on pypi https://pypi.org/project/flickrapi/ and github
https://github.com/sybrenstuvel/flickrapi/ is 2.4.0.
** Affects: python-flickrapi (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/1899404
Title:
please upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-flickrapi/+bug/1899404/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901372] Re: cram3 crashes with "invalid literal for int"
Turns out this is actually triggered by `set -v` itself (there was another problem as well, but I can't reproduce it will enough for a proper ticket after all.) Closing. ** Changed in: cram (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901372 Title: cram3 crashes with "invalid literal for int" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cram/+bug/1901372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901372] [NEW] cram3 crashes with "invalid literal for int"
Public bug reported: ``` Traceback (most recent call last): File "/usr/bin/cram3", line 7, in sys.exit(cram.main(sys.argv[1:])) File "/usr/lib/python3/dist-packages/cram/_main.py", line 197, in main refout, postout, diff = test() File "/usr/lib/python3/dist-packages/cram/_cli.py", line 83, in testwrapper refout, postout, diff = test() File "/usr/lib/python3/dist-packages/cram/_run.py", line 71, in test return testfile(abspath, shell, indent=indent, File "/usr/lib/python3/dist-packages/cram/_test.py", line 227, in testfile return test(f, shell, indent=indent, testname=testname, env=env, File "/usr/lib/python3/dist-packages/cram/_test.py", line 167, in test ret = int(cmd.split()[1]) ValueError: invalid literal for int() with base 10: b'$?' ``` https://github.com/brodie/cram/issues/28 suggests that it's "tests with stdin lines" but my not-yet-reduced example doesn't have any of those. Interestingly, though `--verbose` doesn't change anything, using `--debug` does make the error not occur (at the cost of vast amounts of output.) ** Affects: cram (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/1901372 Title: cram3 crashes with "invalid literal for int" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cram/+bug/1901372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836429] [NEW] friendly-recovery generates a bad grub.cfg in a narrow set of conditions
Public bug reported: friendly-recovery (on 16.04 at least) runs update-grub in its postinst. If friendly-recovery and a linux-image get updated within the same apt command (particularly, linux-image-4.4.0-154-generic and friendly- recovery 0.2.31ubuntu2.1 hit a few weeks apart) then the update-grub scans and finds the new kernel, but *no* new initrd (because that doesn't get handled until the /etc/kernel/postinst.d update gets run) and so generates a grub.cfg which is syntactically valid and passes grub-script-check, but will panic on boot because the first menuentry only has a "linux" line for the 154 kernel and no "initrd" line at all, so it boots into Kernel panic - not syncing: VFS: unable to mount root fs on unknown- block(0,0) instead of a more graceful/less frightening grub error. Under normal conditions this is hard to discover - as long as the rest of the "dist-upgrade" runs to completion and the initrd actually gets built, the kernel package tools make sure update-grub gets run again, and this time it finds the initrd and produces a valid config. This is the "narrow" window - any crash after the inaccurate grub.cfg gets written and before it gets fixed leads to a machine that panics on boot, though you can extend the window arbitrarily simply by rebooting at the right time. I caught it because I was also upgrading another package of my own which had a buggy /etc/grub.d plugin, so when the kernel postinst.d ran, it generated a *syntactically* invalid grub.cfg, which was discarded by update-grub but did *not* fail the dist-upgrade, just produced more text among a bunch of other text (fortunately for debugging, this was visible in /var/log/apt/term.log later on.) Normally this discard mechanism saves the day, because any previous grub.cfg can be assumed bootable, but in this case it just forces the window for this bug entirely open. Is this obscure and hard to trigger? Yes. Can the end user recover from it? As long as they're actually in front of the machine to select an alternate grub menu item, and have an older kernel (which is likely, since this needs a linux-image package upgrade to trigger - if the linux-image upgrade happened in an earlier apt command, friendly-recovery.postinst actually finds an initrd already in place) Yes. I don't actually have advice on fixing this (the kernel-postinst mechanism isn't really available for other packages to trigger, and the direct update-grub dpkg-trigger went away after grub-legacy was replaced with grub2, which would be the obvious choices) but I think "never write an invalid grub.cfg" is a reasonable rule... ** Affects: friendly-recovery (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/1836429 Title: friendly-recovery generates a bad grub.cfg in a narrow set of conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1836429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780841] Re: ubuntu-release-upgrader should transition debs to snaps
Not sure if this should get a new ticket, but if `snap debug connectivity` fails, the whole upgrade mysteriously aborts (user sees ```Reading state information... Done Restoring original system state Aborting ``` and `main.log` shows ```2018-12-12 21:24:20,067 DEBUG running Quirks.bionicPostInitialUpdate 2018-12-12 21:24:20,367 DEBUG abort called ``` with literally no other output anywhere. `strace` is what finds the `snap debug connectivity` call, and `service snapd status` shows `Active: failed (Result: start-limit-hit)` - `service snapd start` fixes that and `do-release-upgrade` goes through fine. (It's not just me, https://askubuntu.com/questions/1078692/cant-upgrade- ubuntu-16-04-to-18-04-lts/1100514 looks to be the same symptoms, but it wasn't until I'd figured out that `snap` was involved that I found this feature-ticket; I don't think it's widely known, I believe most users don't even know snap is *in* 16.04, and certainly won't notice `snapd` being broken without other hints...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780841 Title: ubuntu-release-upgrader should transition debs to snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782953] Re: Software Center doesn't detect changes in sources until update-apt-xapian-index is ran by cron
If the index is updated from cron.daily, is it *ever* going to usefully trigger on a LiveCD (USB stick)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782953 Title: Software Center doesn't detect changes in sources until update-apt- xapian-index is ran by cron To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/782953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062554] Re: LightDM Switch session icon don't work, I need to select another user to resolve it
Just saw this on a fresh trusty install. ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062554 Title: LightDM Switch session icon don't work, I need to select another user to resolve it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1062554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 587186] Re: libc6 upgrade fails: illegal instruction
Apparently this: ~$ cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 7 model name : VIA Samuel 2 stepping: 3 cpu MHz : 399.000 cache size : 64 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr cx8 mtrr pge mmx 3dnow up bogomips: 799.92 clflush size: 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management: also somehow fits the description "i586 and lower processors, as well as i686 processors without cmov support"? Because I just tried to do- release-upgrade -d and got the subprocess new post-removal script killed by signal (Illegal instruction) Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) failure. (The machine is a 2003-era "Martian Netdrive" which originally shipped as a Debian box, and makes a fine wireless printer+scanner server under Ubuntu, or did until just now... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/587186 Title: libc6 upgrade fails: illegal instruction -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341922] [NEW] do-release-upgrade -p fails because update-manager-kde
Public bug reported: update-manager-kde triggered a removal-blacklist check and failed. removing it by hand was fine; I have no idea why it was even present (headless server, upgrading from 12.04->14.04.) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.15 ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26 Uname: Linux 3.5.0-45-generic i686 NonfreeKernelModules: openafs ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Mon Jul 14 22:43:36 2014 GsettingsChanges: MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US.UTF-8 TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: Upgraded to precise on 2014-07-15 (0 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341922 Title: do-release-upgrade -p fails because update-manager-kde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1341922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341979] [NEW] 12.04->14.04 upgrade fails, apparently on texlive packages
Public bug reported: I tried to be clever and use ubuntu-bug to push the files, but *it* blows up on a partial failure... The collected information can be sent to the developers to improve the application. This might take a few minutes. ERROR: hook /usr/share/apport/package-hooks//source_ubuntu-release-upgrader.py crashed: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport/report.py", line 769, in add_hooks_info symb['add_info'](self, ui) File "/usr/share/apport/package-hooks//source_ubuntu-release-upgrader.py", line 28, in add_info root_command_output(["cat", clone_file], decode_utf8=False) TypeError: root_command_output() got an unexpected keyword argument 'decode_utf8' . What looks to be the proximate cause: Setting up texlive-base (2013.20140215-1) ... Installing new version of config file /etc/libpaper.d/texlive-base ... Installing new version of config file /etc/texmf/fmt.d/10texlive-base.cnf ... Installing new version of config file /etc/texmf/texdoctk/texdocrc.defaults ... mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... mktexlsr: Updating /var/lib/texmf/ls-R... mktexlsr: Done. /usr/bin/tl-paper: setting paper size for dvips to a4. /usr/bin/tl-paper: setting paper size for dvipdfmx to a4. /usr/bin/tl-paper: setting paper size for xdvi to a4. /usr/bin/tl-paper: setting paper size for pdftex to a4. /usr/bin/tl-paper: setting paper size for dvipdfmx to letter. /usr/bin/tl-paper: setting paper size for dvips to letter. /usr/bin/tl-paper: setting paper size for pdftex to letter. /usr/bin/tl-paper: setting paper size for xdvi to letter. Running mktexlsr. This may take some time... done. Building format(s) --refresh. This may take some time... done. Warning: Old configuration style found in /etc/texmf/updmap.d Warning: For now these files have been included, Warning: but expect inconsistencies. Warning: These packages should be rebuild with tex-common. Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz Warning: found file: /etc/texmf/updmap.d/00updmap.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-base.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-fonts-extra.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-fonts-recommended.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-lang-cyrillic.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-lang-czechslovak.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-lang-french.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-lang-greek.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-lang-mongolian.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-lang-polish.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-lang-vietnamese.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-latex-base.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-latex-extra.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-math-extra.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-pictures.cfg Warning: found file: /etc/texmf/updmap.d/20tetex-extra.cfg Running mktexlsr. This may take some time... done. Building format(s) --all. This may take some time... done. Removing obsolete conffile /etc/texmf/dvipdfm/config/config ... Removing obsolete conffile /etc/texmf/xdvi/xdvi.cfg ... Processing triggers for tex-common (4.04) ... Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.jFFFTRH9 Please include this file if you report a bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26 Uname: Linux 3.5.0-45-generic i686 NonfreeKernelModules: openafs ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 CrashDB: ubuntu Date: Tue Jul 15 01:46:45 2014 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US.UTF-8 TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader-core UpgradeStatus: Upgraded to trusty on 2014-07-15 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341979 Title: 12.04->14.04 upgrade fails, apparently on texlive packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1341979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341979] Re: 12.04->14.04 upgrade fails, apparently on texlive packages
also says: Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory (That directory has a bunch of *.cfg files, plus 10tetex- base.cfg.obsolete dated Jun 1 2006, but that doesn't look like what the complaint is talking about...) The /tmp/updmap.jFFFTRH9 mentioned in the failure: updmap: resetting $HOME value (was /home/eichin) to root's actual home (/root). updmap is using the following updmap.cfg files (in precedence order): /var/lib/texmf/web2c/updmap.cfg /usr/share/texmf/web2c/updmap.cfg /usr/share/texlive/texmf-dist/web2c/updmap.cfg updmap is using the following updmap.cfg file for writing changes: /etc/texmf/web2c/updmap.cfg dvips output dir: "/var/lib/texmf/fonts/map/dvips/updmap" pdftex output dir: "/var/lib/texmf/fonts/map/pdftex/updmap" dvipdfmx output dir: "/var/lib/texmf/fonts/map/dvipdfmx/updmap" ERROR: The following map file(s) couldn't be found: antp.map (in /var/lib/texmf/web2c/updmap.cfg) comicvn.map (in /var/lib/texmf/web2c/updmap.cfg) csother.map (in /var/lib/texmf/web2c/updmap.cfg) cstext.map (in /var/lib/texmf/web2c/updmap.cfg) fi4.map (in /var/lib/texmf/web2c/updmap.cfg) grverb.map (in /var/lib/texmf/web2c/updmap.cfg) mscorevn.map (in /var/lib/texmf/web2c/updmap.cfg) slantcm.map (in /var/lib/texmf/web2c/updmap.cfg) troff-updmap.map (in /var/lib/texmf/web2c/updmap.cfg) zpeu.map (in /var/lib/texmf/web2c/updmap.cfg) Did you run mktexlsr? You can disable non-existent map entries using the option --syncwithtrees. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341979 Title: 12.04->14.04 upgrade fails, apparently on texlive packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1341979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341979] Re: 12.04->14.04 upgrade fails, apparently on texlive packages
Running "updmap --syncwithtrees" gives instead On Debian systems it is not recommendable to use --syncwithtrees. (and some followup text that presumably makes no sense on ubuntu either.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341979 Title: 12.04->14.04 upgrade fails, apparently on texlive packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1341979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341979] Re: 12.04->14.04 upgrade fails, apparently on texlive packages
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1304972 looks like it might be the root cause (or possibly the duplicate at https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1304972 ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341979 Title: 12.04->14.04 upgrade fails, apparently on texlive packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1341979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341979] Re: 12.04->14.04 upgrade fails, apparently on texlive packages
Certainly taking the xxx.map references from comment #2 above out of the updmap.cfg was enough to get updmap-sys to work (when run implicitly) as suggested in https://bugs.launchpad.net/ubuntu/+source/tex- common/+bug/1236951/comments/11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341979 Title: 12.04->14.04 upgrade fails, apparently on texlive packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1341979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245303] [NEW] gphoto2 fails to recognize current Canon S100 with An error occurred in the io-library ('Bad parameters')
Public bug reported:
x220t$ gphoto2 -l --debug
finds the camera, and then:
0.090692 gphoto2-camera(2): Listing folders in '/'...
0.090698 gphoto2-camera(2): Initializing camera...
0.090721 context(0): An error occurred in the io-library ('Bad parameters'): No
error description available
Turns out this is fixed for 2.5.3 back in July (vs. the 2.5.2 that Saucy
includes) though it appears that hasn't shipped yet.
http://sourceforge.net/p/gphoto/bugs/958/
This is, oddly, a regression from raring (which I guess didn't have the
listing? and worked fine with this camera by default...)
I don't yet know of a workaround.
** Affects: gphoto2 (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/1245303
Title:
gphoto2 fails to recognize current Canon S100 with An error occurred
in the io-library ('Bad parameters')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1245303/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245303] Re: gphoto2 fails to recognize current Canon S100 with An error occurred in the io-library ('Bad parameters')
(actually, sf/gphoto/958 only fixes the S110, based on looking at
svn://svn.code.sf.net/p/gphoto/code/trunk/libgphoto2/camlibs/canon/canon.c
r14452, but the same fix is needed for the S100 on line 128 as well
(should say 2000 instead of 2001.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245303
Title:
gphoto2 fails to recognize current Canon S100 with An error occurred
in the io-library ('Bad parameters')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1245303/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245303] Re: gphoto2 fails to recognize current Canon S100 with An error occurred in the io-library ('Bad parameters')
https://sourceforge.net/p/gphoto/bugs/965/ includes a patch for the S100
case. The attached patch built and worked under Saucy with my own S100
(and includes the S110 case from upstream as well, though I didn't test
that.)
** Attachment added: "upstream-r14452-plus-S100-change"
https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1245303/+attachment/3893310/+files/upstream-r14452-plus-S100-change
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245303
Title:
gphoto2 fails to recognize current Canon S100 with An error occurred
in the io-library ('Bad parameters')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1245303/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245303] Re: gphoto2 fails to recognize current Canon S100 with An error occurred in the io-library ('Bad parameters')
https://sourceforge.net/p/gphoto/bugs/965/
is the upstream recognition of the fix if anyone is motivated to cherry
pick upstream revisions instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245303
Title:
gphoto2 fails to recognize current Canon S100 with An error occurred
in the io-library ('Bad parameters')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1245303/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997056] Re: WiFi disconnects shortly after connection established
I just fought through literally and hour and a half of "Activation (wlan0/wireless): association took too long.", made worse by keyring problems that cause each failure to produce a prompt for the key (not the subject of this bug, that's unrelated.) Adding [ipv6] method=ignore as suggested above to /etc/NetworkManager/system-connections/Auto (ssid elided as I'm a guest here) and bouncing NetworkManager to make sure it reread the file (for about the 10th time) immediately stopped the spinloop... so this probably deserves more attention. (The local wifi is WEP with a hex key, on a WRT-54G running factory firmware, which worked fine when this laptop was running Oneiric.) (local system is an x220t) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997056 Title: WiFi disconnects shortly after connection established To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/997056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554984] Re: [lucid] enable trackpoint scroll emulation by default
Argh, I finally found and identified this. "The control-middle-button menu in xterm doesn't work anymore" should find this bug; I wasted a bit of time assuming it was xterm-specific (xterm has had active development, much to my surprise.) Is there a proper way to turn this override off other than editing/deleting /usr/share/X11/xorg.conf.d/11 -evdev-trackpoint.conf itself? (Alternatively, a matching "how to get the xterm menu back" bug would probably be useful...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/554984 Title: [lucid] enable trackpoint scroll emulation by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/554984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509425] Re: svn-load can't connect to my repository
With svn-load 1.2-1 in maverick, I'm still seeing this: Warning: Unimplemented callback: get_login TypeError: PyCXX: Error creating object of type N2Py5TupleE from None Error connecting or no such repository: https://*** It looks like my normal svn use is using gnome-keyring to get the password, based on looking at $HOME/.subversion/auth/svn.simple... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509425 Title: svn-load can't connect to my repository -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509425] Re: svn-load can't connect to my repository
A quick look at the source shows that this is due to
client.callback_get_login = get_login
def get_login(realm, username, may_save):
nocallback()
## pysvn supports a number of callbacks for scenarios I've yet to
## encounter. For now, just emit a warning to hopefully clue the user
## in about what went wrong - maybe they'll send a patch! :)
def nocallback():
sys.stderr.write("Warning: Unimplemented callback: %s\n" %
(sys._getframe(1).f_code.co_name))
callback_get_login itself is documented here:
http://pysvn.tigris.org/docs/pysvn_prog_ref.html#pysvn_client_callback_get_login
so, a somewhat crude approach is to just install
def get_login(realm, username, may_save):
print "Called get_login with", repr(username), repr(may_save)
return (True, username, raw_input("Password for %s (svn): " %
username), True)
(The second "True" tells svn to "save" the password and not reprompt -
which causes the svn.simple entry to switch from gnome-keyring to
"passtype=simple" and keeps the password in plaintext in that file...
just so you know...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/509425
Title:
svn-load can't connect to my repository
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
FTR I'm seeing this on maverick, with radeon.modeset=1 (and options radeon modeset=1) on a Thinkpad T60p, lspci says "ATI Technologies Inc M56GL [Mobility FireGL V5200]", with the fglrx drivers --purged (because they dropped support for this chipset a while back - with the useless proprietary drivers installed, X starts fine but all GL code (glxinfo, glxgears) dies with a near-immediate coredump.) With the "start gdm, kill gdm, start xdm" workaround, I get working glxinfo and glxgears. (I haven't tried turning off modeset with fglrx purged, yet.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/585853 Title: Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 641259] Re: grub does not appear to load after maverick post-beta install
@migrax what you suggest isn't actually what we're doing - we're installing Lucid itself on a partition. Simpler things like booting a lucid live CD and just telling it to grub-install onto the maverick partition *don't* work (probably because some part of what that does actually comes from the target disk.) When I tried this, none of the boot-from-memory-stick Maverick installs worked at all on the Vaio P (the Lucid ones worked fine, but the Maverick ones all failed to find the stick they were booted from) so I don't have a fast way of cycling through versions... otherwise, divide- and-conquer on the grub package history might be worth doing (and not actually need grub experience.) Hmm, maybe booting a Lucid stick and grub-install'ing the extra *lucid* partition might work, I'll give that a poke if this doesn't get anywhere... -- grub does not appear to load after maverick post-beta install https://bugs.launchpad.net/bugs/641259 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 641259] Re: grub does not appear to load after maverick post-beta install
I can confirm that grub2 1.98+20100804-5ubuntu3 fixes the original problem on the Sony Vaio P as well (and I got it directly via "aptitude safe-upgrade", if you needed evidence that it's percolated through to the release repos.) Terrific, thanks! -- grub does not appear to load after maverick post-beta install https://bugs.launchpad.net/bugs/641259 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 641259] Re: grub does not appear to load after maverick post-beta install
@cjwatson the "workaround" was the one @fader suggested at #8 -- install 10.04.1 on another partition, let *it* install grub (the Lucid grub, in this case) and autodetect the other partitions (including the Maverick one) - that grub boots just fine, and you can manually select the 10.10 install instead of the 10.04.1 one, and it comes up just fine. That's probably why people are calling it a clear regression - because the Lucid one still works fine with everything else Maverick (the bug *could* be more subtle than that, of course.) -- grub does not appear to load after maverick post-beta install https://bugs.launchpad.net/bugs/641259 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 641259] Re: grub does not appear to load after maverick post-beta install
It breaks on the Vaio P (1st gen) if that helps... if someone in the Boston area is working on it, I can make some arrangement. (The workaround works for me, and if there are useful grub diags or alternative versions, I can try...) On Sep 20, 2010 11:56 AM, "Robbie Williamson" < robbie.william...@canonical.com> wrote: > I don't believe we can fix this in time for the release, especially > given that Colin would need to be in physical contact with the hardware > to make any significant progress in the short time between now and the > RC. Does IBM have anyone within the LTC who can do some debugging on > this. If they can find the problem and propose a possible solution, > then we *might* have a chance of making 10.10. > > ** Changed in: grub2 (Ubuntu Maverick) >Milestone: None => maverick-updates > > -- > grub does not appear to load after maverick post-beta install > https://bugs.launchpad.net/bugs/641259 > You received this bug notification because you are a direct subscriber > of the bug. > -- grub does not appear to load after maverick post-beta install https://bugs.launchpad.net/bugs/641259 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 2061924] [NEW] grip missing from (pre)noble (2024-04-16)
Public bug reported: $ apt-cache show grip N: Unable to locate package grip E: No packages found Jammy/22.04 had grip_4.2.0-3_all.deb "Preview GitHub Markdown files like Readme locally". (Not the ancient gnome cd player/ripper app.) Didn't see any bugs here about the package being dropped. No sources.list.d changes (machine was installed from a pre-noble iso about half an hour ago, full-upgrade changed nothing.) (Looking at https://tracker.debian.org/pkg/grip it's been untouched in a while and fell out of debian main releases; perhaps that's the cause, though it is still in sid. I'm just not sure why I don't see some matching reference ubuntu-side.) ** Affects: grip (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/2061924 Title: grip missing from (pre)noble (2024-04-16) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grip/+bug/2061924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061924] Re: grip missing from (pre)noble (2024-04-16)
Thanks! That's the detail I was hoping for. (In the meantime I found that "pandoc --from gfm --to html" did just as good a job and swapped over to it, so I am no longer personally concerned about the package itself.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061924 Title: grip missing from (pre)noble (2024-04-16) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grip/+bug/2061924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
still seeing Apr 9 15:30:54 drafting-table /usr/libexec/gdm-x-session[355145]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found in an install which is "jammy daily iso from a week or two back with daily dist upgrades", under i3; $ dpkg -l gdm3 x11-common i3-wm Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii gdm3 42.0-1ubuntu2 amd64GNOME Display Manager ii i3-wm 4.20.1-1amd64improved dynamic tiling window manager ii x11-common 1:7.7+23ubuntu2 all X Window System (X.Org) infrastructure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2088102] Re: streamdeck crashed with AttributeError in _render_key_image(): 'ImageDraw' object has no attribute 'textsize'
Upstream ticket: https://github.com/timothycrosley/streamdeck- ui/issues/353 with workaround and PR. That ticket also links to a more active fork https://github.com/streamdeck-linux-gui/streamdeck-linux-gui (backstory: https://github.com/streamdeck-linux-gui/streamdeck-linux- gui/discussions/203 ) if that's more helpful going forward. ** Bug watch added: github.com/timothycrosley/streamdeck-ui/issues #353 https://github.com/timothycrosley/streamdeck-ui/issues/353 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2088102 Title: streamdeck crashed with AttributeError in _render_key_image(): 'ImageDraw' object has no attribute 'textsize' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/streamdeck-ui/+bug/2088102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
