[Bug 1882846] [NEW] IndexError: list index out of range
Public bug reported:
I had been running s-tui in a terminal for several hours without issue.
I returned to the open terminal and saw the process had exited:
```
hugh@goat:~$ s-tui
Traceback (most recent call last):
File "/usr/bin/s-tui", line 11, in
load_entry_point('s-tui==1.0.0b3', 'console_scripts', 's-tui')()
File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 882, in main
graph_controller.main()
File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 738, in main
loop.run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 286, in run
self._run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 384, in _run
self.event_loop.run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 788, in run
self._loop()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 821, in _loop
alarm_callback()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 172, in cb
callback(self, user_data)
File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 829, in
animate_graph
self.view.update_displayed_information()
File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 252, in
update_displayed_information
graph.update()
File "/usr/lib/python3/dist-packages/s_tui/sturwid/bar_graph_vector.py", line
173, in update
self.graph_data[graph_idx], current_reading[graph_idx])
IndexError: list index out of range
```
At some point I had open and closed my laptop lid, causing it the
suspend (maybe, that's also unreliable on my UX433FA which is a separate
issue), and also perhaps connected and disconnected some external
peripherals. I only mention that because there is an [upstream
issue](https://github.com/amanusk/s-tui/issues/144) related to changing
hardware (NB that bug report has a different stack trace).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: s-tui 1.0.0-1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 9 22:01:58 2020
InstallationDate: Installed on 2019-11-07 (215 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: s-tui
UpgradeStatus: Upgraded to focal on 2020-06-08 (1 days ago)
** Affects: s-tui (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882846
Title:
IndexError: list index out of range
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s-tui/+bug/1882846/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690718] Re: Firefox en-GB locale uses google.com for search
Of course please close it, I'm sure things have changed and improved beyond recognition in the last 8 years :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690718 Title: Firefox en-GB locale uses google.com for search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/690718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740306] Re: Dragging Nautilus window painfully slow/sticky
Is this waiting for some input from me? I'm not able to attempt the repro suggested in #2. ** Changed in: nautilus (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740306 Title: Dragging Nautilus window painfully slow/sticky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/740306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740313] Re: gedit declines to take focus when opening second document
Here's a screencast. In it I follow the steps of the original repro. 1. Double-click fake.txt in Nautilus. gedit opens. 2. Type 'asdf' into gedit. 3. alt-tab back to Nautilus. 4. Double click foobar.txt. 5. gedit opens the file and comes to the front, but doesn't have focus. 5. Type ctrl-I to goto line in gedit and end up renaming a file (NB pressing 'F2' is even worse, since Nautilus doesn't come to the front). ** Attachment added: launchpad-740313.ogv https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/740313/+attachment/2593159/+files/launchpad-740313.ogv ** Changed in: gedit (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740313 Title: gedit declines to take focus when opening second document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/740313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740313] Re: gedit declines to take focus when opening second document
Ok so the steps I follow in the screencast are slightly different, but you get the idea. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740313 Title: gedit declines to take focus when opening second document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/740313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740313] Re: gedit declines to take focus when opening second document
Funnily enough, I've started seeing this again just in the last few days. The fact I'd forgotten about the problem suggests it must be intermittent. Right now, I double-click a file in Nautilus which opens it in gedit, hit Ctrl+I to scroll to a given line in gedit, type the line and hit enter. Since Nautilus retains focus the whole time (even though gedit is above it in the z-order), this has the effect of renaming the selected file... I'm running gedit 2.30.3-0ubuntu0.1 on lucid. I'm not at my work machine right now so I can't confirm the repro steps, but I'm 95% sure they still apply. I'll have another look tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740313 Title: gedit declines to take focus when opening second document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/740313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740306] Re: Dragging Nautilus window painfully slow/sticky
I'm afraid I don't have time to do that. If I upgrade to Oneiric (reasonably likely to happen in the next 18 months) I'll let you know if I can reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740306 Title: Dragging Nautilus window painfully slow/sticky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/740306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35876] Re: 'Downloading package information' and 'building dependency tree' progress dialogs request focus too often
Still an issue in Maverick, using xfwm4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/35876 Title: 'Downloading package information' and 'building dependency tree' progress dialogs request focus too often -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740306] Re: Dragging Nautilus window painfully slow/sticky
Ok, turns out this is misfiled. I /do/ see the same painful behaviour in other programs too. I just hadn't noticed before, because the window slowdown seems to be proportional to the fraction of monitor area filled by the window. Yes indeed. I can only think it's a misfeature in the window manager. I'd appreciate it if someone with more knowledge of Ubuntu could move this bug over to the relevant package, if such a thing is possible. Failing that, go ahead and close as invalid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740306 Title: Dragging Nautilus window painfully slow/sticky -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740313] Re: gedit declines to take focus when opening second document
** Description changed: Binary package hint: gedit 1. Open Nautilus 2. Double-click a text file 3. gedit opens and takes focus 4. Return to Nautilus 5. Double-click a second text file - 6. The file opens in gedit, but Nautilus retains focus + 6. The file opens in gedit and gedit comes to the front, but Nautilus retains focus (even if gedit is maximised!) 7. Use the mousewheel to scroll the document while reading 8. Time passes 9. Fail to observe that gedit didn't take focus the second time 10. Press Ctrl-W to close the document you were reading 11. Nautilus closes AFAICT, this behaviour was recently introduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740313 Title: gedit declines to take focus when opening second document -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740306] [NEW] Dragging Nautilus window painfully slow/sticky
Public bug reported: Binary package hint: nautilus When moving the Nautilus window around, if any of the edges of the window is close to the edge of the screen, dragging becomes painfully slow; the amount the window moves relative to the mouse becomes drastically reduced. It's like there's some logic for 'snap to edge' that is malfunctioning. I usually run a single Nautilus instance, large enough to almost fill the screen (but not maximised). Frequently I need to move the window between my two monitors, and instead of a simple drag, the procedure is: 1. Move Nautilus window down such that none of its edges is close to the edge of the screen (i.e. so that the bottom edge of the window is safely off the bottom of the visible area) 2. Perform horizontal movement to other monitor 3. Raise window back up to desired position At first I assumed this was something to do with the window manager, but I only see this behaviour with Nautilus and not other programs. ** Affects: nautilus (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/740306 Title: Dragging Nautilus window painfully slow/sticky -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740313] [NEW] gedit declines to take focus when opening second document
Public bug reported: Binary package hint: gedit 1. Open Nautilus 2. Double-click a text file 3. gedit opens and takes focus 4. Return to Nautilus 5. Double-click a second text file 6. The file opens in gedit, but Nautilus retains focus 7. Use the mousewheel to scroll the document while reading 8. Time passes 9. Fail to observe that gedit didn't take focus the second time 10. Press Ctrl-W to close the document you were reading 11. Nautilus closes AFAICT, this behaviour was recently introduced. ** Affects: gedit (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/740313 Title: gedit declines to take focus when opening second document -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660754] Re: Turning off show smileys as images does not persist after closing the dialog.
I have the same problem in 10.10 with all latest updates applied (Empathy says it is version 2.32.1 in the About box). It's quite an annoying niggle where I'm using it to post code snippets all day. ** Changed in: empathy (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/660754 Title: Turning off show smileys as images does not persist after closing the dialog. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 593603] Re: automount segfault if get_query_dn fails
+1 to comment #7. If 'dmesg fills with segfaults and my machine becomes practically unusable' is low priority, I shudder to think what is high. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in ubuntu. https://bugs.launchpad.net/bugs/593603 Title: automount segfault if get_query_dn fails -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 593603] Re: automount segfault if get_query_dn fails
+1 to comment #7. If 'dmesg fills with segfaults and my machine becomes practically unusable' is low priority, I shudder to think what is high. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/593603 Title: automount segfault if get_query_dn fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579290] Re: Adjusting volume gives uneven response
Hey got an update here. I regularly update the packages on my system, and I'm not sure what package is responsible (new kernel?), but the behaviour seems to have changed for the better. The first indication was after restarting, my music was much quieter than usual, and too quiet even at max volume. Now if I look in alsamixer, adjusting 'Master Front' actually does make a difference to perceived loudness. I reverted the edit I had made to analog-output.conf, and hey presto the volume keys do the right thing, with volume output now ranging from very quiet to max volume, and Master Front/PCM/Front all being adjusted sensibly. Incidentally the 'Headphone' column in alsamixer is now greyed out and disabled. Daniel, I guess the underlying issue with VIA hardware was fixed or worked around? Yay! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579290 Title: Adjusting volume gives uneven response -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691611] Re: Help-Report a Problem... gives no feedback
AFAICT, apport was not running; enabled was set to 0 in the config file. If I follow the steps you describe and then repeat Help-Report a Problem..., the 'Collecting problem information' dialog appears almost immediately, giving the necessary feedback. Perhaps apport should be enabled by default? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691611 Title: Help-Report a Problem... gives no feedback -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691611] [NEW] Help-Report a Problem... gives no feedback
Public bug reported: Binary package hint: nautilus If you click Help-Report a Problem in Nautilus, nothing happens. At least, there is no visible indication that you successfully clicked the menu entry for over a minute, at which point a 'collecting information' dialog appears. By this time the user might reasonably have tried clicking the entry a few times, leading to several bug report windows all appearing on top of each other. ** Affects: nautilus (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/691611 Title: Help-Report a Problem... gives no feedback -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691611] Re: Help-Report a Problem... gives no feedback
** Changed in: apport (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691611 Title: Help-Report a Problem... gives no feedback -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691611] Re: Help-Report a Problem... gives no feedback
** Changed in: apport (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691611 Title: Help-Report a Problem... gives no feedback -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690718] [NEW] Firefox en-GB locale uses google.com for search
Public bug reported: Binary package hint: firefox Current behaviour: 1) Start Firefox 2) Press ctrl-k, type e.g. 'laptop' and hit enter 3) You are taken to a page of google.com search results, including links to US-only stores, shopping results with prices in dollars etc. Correct behaviour: You are taken to google.co.uk, and correctly localised results are displayed. Extra info: See http://ubuntuforums.org/showthread.php?t=1354830#4 for a workaround. ** 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/690718 Title: Firefox en-GB locale uses google.com for search -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579290] Re: Adjusting volume gives uneven response
Hi Fabio, can you be more specific? What exactly do you want me to do to determine if the problem is still present? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579290 Title: Adjusting volume gives uneven response -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579290] Re: Adjusting volume gives uneven response
Hi Fabio. To me the issue seems to be that the default config file is incorrect. If I revert my edit to /usr/share/pulseaudio/alsa-mixer/paths /analog-output.conf, and restore it to how it was left after my last dist upgrade, then restart pulseaudio, I still have the same problem. So I think the answer to your question in #5 is 'yes'. I have to leave the config edit in place to get the desired behaviour, even after 'apt-get upgrade'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579290 Title: Adjusting volume gives uneven response -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579290] Re: Adjusting volume gives uneven response
For anyone who may be interested, I just upgraded to Ubuntu 10.10 'Maverick Meerkat', which helpfully undid the edits I had made to the conf file (without asking). The fix as described in #3 still does the trick. To see the effects after editing the config, you may need to 'killall pulseaudio' or maybe log out and back in again. -- Adjusting volume gives uneven response https://bugs.launchpad.net/bugs/579290 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 593603] Re: automount segfault if get_query_dn fails
Here's my nsswitch.conf ** Attachment added: nsswitch.conf https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/593603/+attachment/1539622/+files/nsswitch.conf -- automount segfault if get_query_dn fails https://bugs.launchpad.net/bugs/593603 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 593603] Re: automount segfault if get_query_dn fails
Here's the gdb transcript, potentially sensitive info eliminated. I followed the instructions to get debug symbols, but gdb still says Reading symbols from /usr/lib/debug/usr/sbin/automount...(no debugging symbols found) (the file does exist). ** Attachment added: gdb transcript http://launchpadlibrarian.net/51233464/gdb-automount.txt -- automount segfault if get_query_dn fails https://bugs.launchpad.net/bugs/593603 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 593603] [NEW] automount segfault on start (ldap, nfs4)
Public bug reported:
Binary package hint: autofs5
# lsb_release -rd
Description:Ubuntu 10.04 LTS
Release:10.04
# apt-cache policy autofs5
autofs5:
Installed: 5.0.4-3.1ubuntu5
Candidate: 5.0.4-3.1ubuntu5
Version table:
*** 5.0.4-3.1ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
Possibly related to
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/512595.
After upgrading 9.04 - 10.04, my automounts from LDAP no longer appear.
Instead, I get the following in dmesg at the rate of one per second:
[ 62.189700] automount[5011]: segfault at 0 ip 7f956cb1c022 sp
7fff3cd1a978 error 4 in libc-2.11.1.so[7f956ca99000+178000]
[ 63.301490] automount[5023]: segfault at 0 ip 7f2de5007022 sp
7fff33695618 error 4 in libc-2.11.1.so[7f2de4f84000+178000]
[ 64.328963] automount[5038]: segfault at 0 ip 7fdc5f4b4022 sp
7fffb09a47a8 error 4 in libc-2.11.1.so[7fdc5f431000+178000]
...
I guess something is trying to repeatedly respawn automount. Here's a
couple of pointers for anyone trying to debug (sensitive info turned to
*):
# automount -dvf
Starting automounter version 5.0.4, master map /etc/auto.master
using kernel protocol version 5.01
lookup_nss_read_master: reading master file /etc/auto.master
parse_init: parse(sun): init gathered global options: (null)
lookup_read_master: lookup(file): read entry +auto.master
lookup_nss_read_master: reading master ldap auto.master
parse_server_string: lookup(ldap): Attempting to parse LDAP information from
string auto.master.
parse_server_string: lookup(ldap): mapname auto.master
parse_ldap_config: lookup(ldap): ldap authentication configured with the
following options:
parse_ldap_config: lookup(ldap): use_tls: 0, tls_required: 0, auth_required: 1,
sasl_mech: (null)
parse_ldap_config: lookup(ldap): user: (null), secret: unspecified, client
principal: (null) credential cache: (null)
find_server: trying server uri ldap://*
do_bind: lookup(ldap): auth_required: 1, sasl_mech (null)
do_bind: lookup(ldap): ldap anonymous bind returned 0
get_query_dn: lookup(ldap): check search base list
get_query_dn: lookup(ldap): query failed for search dn
ou=aufo.master,ou=autofs,dc=*,dc=*,dc=com: No such object
Segmentation fault (core dumped)
# strace automount -f 21 | tail -n20
poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP}], 1, -1) = 1 ([{fd=7,
revents=POLLIN}])
read(7, 0\f\2\1\1a\7\n, 8)= 8
read(7, \1\0\4\0\4\0, 6) = 6
open(/etc/default/autofs, O_RDONLY) = 8
fcntl(8, F_SETFD, FD_CLOEXEC) = 0
fstat(8, {st_mode=S_IFREG|0644, st_size=3708, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fb316bc6000
read(8, #\n# Define default options for a..., 4096) = 3708
read(8, , 4096) = 0
close(8)= 0
munmap(0x7fb316bc6000, 4096)= 0
write(7, 0\201\203\2\1\2c~\0045ou=aufo.master,ou=auto..., 134) = 134
poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP}], 1, -1) = 1 ([{fd=7,
revents=POLLIN}])
read(7, 02\2\1\2e-\n, 8) = 8
read(7, \1 \4ou=autofs,dc=*,dc=ac..., 44) = 44
write(2, get_query_dn: lookup(ldap): quer..., 124get_query_dn: lookup(ldap):
query failed for search dn ou=aufo.master,ou=autofs,dc=*,dc=*,dc=com:
No such object) = 124
write(2, \n, 1
) = 1
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++
** Affects: autofs5 (Ubuntu)
Importance: Undecided
Status: New
--
automount segfault on start (ldap, nfs4)
https://bugs.launchpad.net/bugs/593603
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 593603] Re: automount segfault on start (ldap, nfs4)
Ok, fixed the problem thanks to an eagle-eyed colleague. If you look at the end of the 'automount -dvf' trace above, I made a typo: get_query_dn: lookup(ldap): query failed for search dn ou=aufo.master,ou=autofs,dc=*,dc=*,dc=com: No such object is looking for ou=aufo.master rather than ou=auto.master (f - t). The query correctly returns 'No such object', but then the response of automount shouldn't be a segfault. ** Summary changed: - automount segfault on start (ldap, nfs4) + automount segfault if get_query_dn fails -- automount segfault if get_query_dn fails https://bugs.launchpad.net/bugs/593603 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 579290] Re: Adjusting volume gives uneven response
fk, thanks a lot for that link. I've discovered something useful on a page linked to from the Ubuntu wiki (see http://pulseaudio.org/wiki/PulseAudioStoleMyVolumes). Briefly, PulseAudio uses the product of several settings (in my case and perhaps yours, 'Master Front', 'PCM' and 'Front') to achieve the desired volume level. However, the first of those three doesn't actually influence the volume coming out of my headphones, perhaps because they're plugged in at the back of my PC and not the front. The fix seems to be to remove the Master Front horse from the big volume carousel, achieved by: Alt+F2, run 'gksudo gedit /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf' look for [Element Master Front] around line 37 change 'volume = merge' to 'volume = ignore' This gives a much better result for me. Now the range of settings on the volume widget from 50-100% are useful. 100% corresponds to full volume, and below 50% there is still a continuous range of levels, but they are all too quiet to be useful. Still, 10 volume levels is much better than 1. -- Adjusting volume gives uneven response https://bugs.launchpad.net/bugs/579290 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 579290] [NEW] Adjusting volume gives uneven response
Public bug reported: I am listening to music using Rhythmbox. To adjust the volume I use the vol -/+ keys built in to my Microsoft Natural 4000 keyboard. This arrangement worked fine in 9.10. A pop-up OSD in the top-right of the screen appeared whenever I changed the volume. The full range of this indicator (from empty to full) correctly corresponded to the full range of silence to maximum volume output over my headphones. Since upgrading to 10.04, the control behaves as follows. At the lowest setting, I get no sound output, as expected. With one press of the vol+ key, the bar becomes one notch full (I note there appear to be 18 discrete values that the OSD can indicate). However, the sound output is fairly loud: around half of the maximum output. After two presses of the vol+ key, the bar is only about 10% full, but the sound output is at or near the maximum (uncomfortably loud through my headphones). Successive presses of vol+ continue to raise the indicated volume, but have no discernible effect on the output volume. I can watch what's going on in alsamixer while I press the vol -/+ keys. (side note: alsamixer says 'Card: HDA ATI SB' and 'Chip: VIA VT1708S'). At volume zero, the bars marked Master Front, PCM and Front are all on zero, and are marked as muted. On volume notch one (after one press of vol+), those channels are marked as unmuted, and have respective values 0, 98, 60. After two presses 0, 98, 88. After three presses 6, 98, 100. Successive presses just increase the Master Front value. If I manually scale the PCM and Front columns using the arrow keys, I get the expected response. i.e. perceived volume output is proportional to the product of PCM and Front. I'm using a Dell Inspiron 546. uname -a gives: Linux alma 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux The bits of lspci that I think are relevant: 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller Expected behaviour: output volume scales linearly with the scale displayed on screen. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: I am listening to music using Rhythmbox. To adjust the volume I use the vol -/+ keys built in to my Microsoft Natural 4000 keyboard. This arrangement worked fine in 9.10. A pop-up OSD in the top-right of the screen appeared whenever I changed the volume. The full range of this indicator (from empty to full) correctly corresponded to the full range of silence to maximum volume output over my headphones. Since upgrading to 10.04, the control behaves as follows. At the lowest setting, I get no sound output, as expected. With one press of the vol+ key, the bar becomes one notch full (I note there appear to be 18 discrete values that the OSD can indicate). However, the sound output is fairly loud: around half of the maximum output. After two presses of the vol+ key, the bar is only about 10% full, but the sound output is at or near the maximum (uncomfortably loud through my headphones). Successive presses of vol+ continue to raise the indicated volume, but have no discernible effect on the output volume. I can watch what's going on in alsamixer while I press the vol -/+ keys. + (side note: alsamixer says 'Card: HDA ATI SB' and 'Chip: VIA VT1708S'). At volume zero, the bars marked Master Front, PCM and Front are all on zero, and are marked as muted. On volume notch one (after one press of vol+), those channels are marked as unmuted, and have respective values 0, 98, 60. After two presses 0, 98, 88. After three presses 6, 98, 100. Successive presses just increase the Master Front value. If I manually scale the PCM and Front columns using the arrow keys, I get the expected response. i.e. perceived volume output is proportional to the product of PCM and Front. I'm using a Dell Inspiron 546. uname -a gives: Linux alma 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux The bits of lspci that I think are relevant: 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller - - Expected behaviour: output volume scales linearly with the scale displayed on screen. + Expected behaviour: output volume scales linearly with the scale + displayed on screen. -- Adjusting volume gives uneven response https://bugs.launchpad.net/bugs/579290 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 270206] Re: RB should never start minimised to tray
This is really dire if you happen not to have Notification Area on your panel. You start rhythmbox (e.g. from Main Menu or Alt+F2) and apparently nothing happens at all -- there's no indication that the app has started. I've been living with this annoying behaviour for a few months. I think it's the cause of this guy's problems too: http://bugs.debian.org/504936. A workaround is to open gconf-editor and edit the gumph in /apps/rhythmbox/plugins/status-icon/ (hint found in this thread: http://www.uluga.ubuntuforums.org/showthread.php?p=8571328). Try unticking 'active'. Perhaps there's a bug in the 'remember if minimised to tray' code: in my case it seems to remember it was minimised to tray on exit even though I don't have a tray to minimise to. ** Bug watch added: Debian Bug tracker #504936 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504936 -- RB should never start minimised to tray https://bugs.launchpad.net/bugs/270206 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 413360] Re: Pango text select with double click stops at underscore.
I second that! Your plugin is fantastic Derek, many thanks. -- Pango text select with double click stops at underscore. https://bugs.launchpad.net/bugs/413360 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 111339] Re: Middle-Click does not scroll web site in feisty
Re: comments #3 and #8 What exactly do you mean by 'novice users might get confused'? The select-to-copy, middle-click-to-paste functionality in Ubuntu is one of its best-hidden secrets that you're only likely to discover by mistake if at all. And if by 'novice users' you mean 'users with some experience of Windows but little experience of Ubuntu' (which I suspect applies to many newcomers to Ubuntu) then the more confusing outcome for those familiar with Firefox on Windows would be for the middle-click scroll to be seemingly broken or absent, and then one day to middle-click (accidentally or otherwise) in a text input field, only to have some semi-random text unexpectedly appear. The middle-click scroll functionality is a great bit of user interface design. For reading long web pages it's much less taxing on the hand than dragging the vertical scrollbar, and hugely preferable to endlessly scrolling the mouse wheel. It seems a shame not to make it available in Ubuntu. Or why not with a little extra effort implement the best of both worlds: middle click a text input box to paste the X primary selection, middle click anywhere else on the page to activate the scroll behaviour? -- Middle-Click does not scroll web site in feisty https://bugs.launchpad.net/bugs/111339 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
