[Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_uni
I have created a more specific bug report, for a crash triggered from the file browser in the Discord app, here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736664 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860052] [NEW] gnome-shell crash when typing into file browser dialog in Discord app
Public bug reported: This is a specific instance of https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1736664 I cannot see the journal that will be attached to the bug in advance, so I can't copy the error message to the summary. While using the Discord app I clicked the (+) button in order to select a file to upload into a chat, which led to the normal file browser dialog. I then typed either "/hom" or "~/.l" or ".loc" and before the interface could update to show that I had typed anything it froze, then a few seconds later almost all programs had closed and gnome-shell was restarting after having crashed. I am running Ubuntu 19.10, gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_1065_75_oem_61 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 15:18:26 2020 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-28 (19 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-12-30 (17 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860052 Title: gnome-shell crash when typing into file browser dialog in Discord app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_uni
https://errors.ubuntu.com/oops/89b39b4a-38b3-11ea-b8ae-fa163e102db1 https://errors.ubuntu.com/oops/9d568826-30e1-11ea-a775-fa163ee63de6 these two crashes seem to be this bug. this is a recurring (but not easily reproducible) problem for me, most often triggered by typing into the File > Open dialog in various applications (typing in order to navigate to a file path, often starting with / or .) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736664 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832086] [NEW] bug report
Public bug reported: Cant send bug report from Ubuntu Studio 19.10 ** Affects: xfce4-panel (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/1832086 Title: bug report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1832086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274613] Re: module-bluetooth-discover does not load on login
This problem seems to persist in Xubuntu 15.04. The PPA mentioned in comment #20 does not have packages for vivid, only trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274613 Title: module-bluetooth-discover does not load on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189653] [NEW] User Accounts password change form incorrectly says Wrong password when password chage restrictions in effect
Public bug reported: If a user has password expiry restrictions in place that prevent password changes (such as a minimum password age set with chage) and they try to change their password through the User Accounts tool, they will see a red warning icon to the right of the Current password field, and the hover text for that icon is Wrong password. This text is misleading in this circumstance. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189653 Title: User Accounts password change form incorrectly says Wrong password when password chage restrictions in effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1189653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189653] Re: User Accounts password change form incorrectly says Wrong password when password chage restrictions in effect
`xprop WM_CLASS` says the user account and password change windows both have the class gnome-control-center ** Package changed: ubuntu = gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189653 Title: User Accounts password change form incorrectly says Wrong password when password chage restrictions in effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1189653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224477] Re: /usr/sbin/invoke-rc.d calls /sbin/runlevel without DEPENDSing upstart
Thank you Mark. This should, perhaps, be moved to a bug on one of the sysv packages. My original assignment to the upstart package was likely mistaken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/224477 Title: /usr/sbin/invoke-rc.d calls /sbin/runlevel without DEPENDSing upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/224477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583056] Re: Assertion error (r == n_visible_rows) in gtk_file_system_model_sort causes applications to crash
I am still seeing this bug in multiple applications while using GTK+ 2.24 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583056 Title: Assertion error (r == n_visible_rows) in gtk_file_system_model_sort causes applications to crash To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/583056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588441] Re: Prompted for root password for Administration features as non-sudoer
1. the specific steps or actions you took that caused you to encounter the problem, - Log in as a user who is not an Admin or a sudoer - From the menu bar click System Adminstration Printing Add 2. the behavior you expected - prompt for root password or sudoer credentials with better explanation 3. the behavior you actually encountered (in as much detail as possible). - prompt for root password All of this information was in my original bug report. Making me retype it is silly. ** Changed in: ubuntu Status: Invalid = New -- Prompted for root password for Administration features as non-sudoer https://bugs.launchpad.net/bugs/588441 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 61463]
http://z1owlxoyjtw.ezacutjupl.com -- Script that are using bash could be broken with the new symlink https://bugs.launchpad.net/bugs/61463 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 588441] [NEW] Prompted for root password for Administration features as non-sudoer
Public bug reported: While logged in as a user who is neither an Admin nor a sudoer, attempting to do System Administration Printing Add (or any of a hundred other administration tasks) results in a prompt for the root password. I have no root password, nor do I use the root user. This prompt is very confusing. I do have the username and password for the user who installed the system, and can enter both of those pieces of information at the prompt to proceed, but the prompt does not make it evident that this is a viable option. At best this is a verbiage issue. ** Affects: ubuntu Importance: Undecided Status: New -- Prompted for root password for Administration features as non-sudoer https://bugs.launchpad.net/bugs/588441 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 455073] Re: A mouse pointer keeps reappearing during video playback in smplayer
The fault here lies with mplayer, specifically 22disable- xscreensaver.patch https://code.launchpad.net/~ubuntu-branches/ubuntu/karmic/mplayer/karmic revision 54 the patch was turned off revision 56 it was turned back on ** Package changed: smplayer (Ubuntu) = mplayer (Ubuntu) ** Changed in: mplayer (Ubuntu) Status: New = Confirmed -- A mouse pointer keeps reappearing during video playback in smplayer https://bugs.launchpad.net/bugs/455073 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 423446] Re: Shell autocomplete will not proceed past path with escaped characters
*** This bug is a duplicate of bug 419509 *** https://bugs.launchpad.net/bugs/419509 This problem persists after uninstalling bash-completion. I may have failed to test that situation adequately, but so far I believe this to be a bash bug, not a bash-completion bug. -- Shell autocomplete will not proceed past path with escaped characters https://bugs.launchpad.net/bugs/423446 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 423446] [NEW] Shell autocomplete will not proceed past path with escaped characters
Public bug reported: Binary package hint: bash When using bash to autocomplete a path that contains escaped characters (such as a space), it will not complete anything once the path contains the escaped character. mkdir foo\ bar[ENTER] mkdir foo\ bar/baz[ENTER] cd foo[TAB] result: cd foo\ bar/ [TAB] expected: cd foo\ bar/baz/ actual: cd foo\ bar/ This problem did not occur in 9.04, but does in Karmic (development branch) as of two weeks ago through today. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- Shell autocomplete will not proceed past path with escaped characters https://bugs.launchpad.net/bugs/423446 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 413950] Re: Incorrect cursor positioning in Firefox.
I am seeing a possibly related issue with dragging tabs, occasionally what I intend to be a horizontal drag (or even a click) will be interpreted as enough of a vertical drag to tear the tab off into a new window. -- Incorrect cursor positioning in Firefox. https://bugs.launchpad.net/bugs/413950 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 348818] [NEW] forcedeth random MAC for nvidia chipset on boot
Public bug reported: My onboard nVidia NIC is assigned a random MAC address every time I boot. The detected MAC is invalid because it is being read backwards. This may be related to Bug #175333 (and many other similar suspend/resume bug reports with the same symptom), but is not a duplicate because that bug is supposed fixed in recent kernels and only applies to suspend/resume behavior. I am currently running Jaunty. The problem has been apparent since around Gutsy. Relevant excerpts from dmesg [0.00] Linux version 2.6.28-9-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu2) ) #31-Ubuntu SMP Wed Mar 11 15:43:58 UTC 2009 (Ubuntu 2.6.28-9.31-generic) [3.644504] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61. [3.644844] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 20 [3.644852] forcedeth :00:07.0: PCI INT A - Link[APCH] - GSI 20 (level, low) - IRQ 20 [3.644856] forcedeth :00:07.0: setting latency timer to 64 [3.644899] forcedeth :00:07.0: Invalid Mac address detected: 2f:d3:61:ea:0f:00 [3.644985] forcedeth :00:07.0: Please complain to your hardware vendor. Switching to a random MAC. [4.165131] forcedeth :00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:00:6c:35:bc:d0 [4.165136] forcedeth :00:07.0: highdma pwrctl mgmt timirq gbit lnktim msi desc-v3 [ 63.674057] forcedeth :00:07.0: irq 2300 for MSI/MSI-X [ 63.674286] eth0: no link during initialization. [ 63.674968] ADDRCONF(NETDEV_UP): eth0: link is not ready and from lspci - 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2) Subsystem: Giga-byte Technology Device e000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (250ns min, 5000ns max) Interrupt: pin A routed to IRQ 2300 Region 0: Memory at f7004000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at c800 [size=8] Capabilities: access denied Kernel driver in use: forcedeth Kernel modules: forcedeth ** Affects: ubuntu Importance: Undecided Status: New -- forcedeth random MAC for nvidia chipset on boot https://bugs.launchpad.net/bugs/348818 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 339100] Re: jaunty upgrade fails when libboost-python-dev is installed
More detailed output, also including another python upgrade problem. I
had to remove libboost-dbg and libboost-python-dev and pitivi, then
python upgraded successfully. Should this one bug encompass all 3
problems, or should separate bugs be opened?
Setting up python (2.6.1-0ubuntu3) ...
running python rtupdate hooks for python2.6...
/usr/share/python/runtime.d/libboost-dbg.rtupdate unknown python version
python2.6
error running python rtupdate hook libboost-dbg
/usr/share/python/runtime.d/libboost-python-dev.rtupdate unknown python version
python2.6
error running python rtupdate hook libboost-python-dev
Compiling /usr/lib/pitivi/python/pitivi/objectfactory.py ...
SyntaxError: ('invalid syntax',
('/usr/lib/pitivi/python/pitivi/objectfactory.py', 399, 14, 'as =
self.audio_info_stream\n'))
pycentral: pycentral updatedefault: error byte-compiling files (55)
pycentral updatedefault: error byte-compiling files (55)
error running python rtupdate hook pycentral
Updating *.pc symlinks for python-gst0.10...
Updating *.pc symlinks for python-gtk2-dev...
dpkg: error processing python (--configure):
subprocess post-installation script returned error exit status 4
Errors were encountered while processing:
python
--
jaunty upgrade fails when libboost-python-dev is installed
https://bugs.launchpad.net/bugs/339100
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 82108] Re: forcedeth changes MAC address after suspend/resume
I encounter this same problem, but every boot instead of on resume. Problem originated in gutsy (I think), persists through hardy and intrepid. It also caused the eth0,eth1,...,eth99 bug, but a fix for the network device name rules found elsewhere resolved that. If that is a sufficiently different issue then I will file a new bug. lspci, trimmed 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2) Subsystem: Giga-byte Technology Device e000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (250ns min, 5000ns max) Interrupt: pin A routed to IRQ 220 Region 0: Memory at f7004000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at c800 [size=8] Capabilities: access denied Kernel driver in use: forcedeth Kernel modules: forcedeth dmesg, trimmed [3.160371] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61. [3.160763] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 21 [3.160771] forcedeth :00:07.0: PCI INT A - Link[APCH] - GSI 21 (level, low) - IRQ 21 [3.160776] forcedeth :00:07.0: setting latency timer to 64 [3.160807] forcedeth :00:07.0: Invalid Mac address detected: 2f:d3:61:ea:0f:00 [3.160863] forcedeth :00:07.0: Please complain to your hardware vendor. Switching to a random MAC. [3.681020] forcedeth :00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:00:6c:73:c9:cb [3.681025] forcedeth :00:07.0: highdma pwrctl mgmt timirq gbit lnktim msi desc-v3 -- forcedeth changes MAC address after suspend/resume https://bugs.launchpad.net/bugs/82108 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 297373] Re: depends on nonexistent binutils-avr (= 2.18-4)
This seems to be fixed, with the dependency changed to = 2.16.1-1 ** Changed in: gcc-avr (Ubuntu) Status: New = Fix Committed -- depends on nonexistent binutils-avr (= 2.18-4) https://bugs.launchpad.net/bugs/297373 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 297373] [NEW] depends on nonexistent binutils-avr (= 2.18-4)
Public bug reported: Binary package hint: gcc-avr I am using Intrepid. As far as I can see, binutils-avr 2.18-3 is the latest version available. I am unable to apt-get build-dep gcc-avr because of this. ** Affects: gcc-avr (Ubuntu) Importance: Undecided Status: New -- depends on nonexistent binutils-avr (= 2.18-4) https://bugs.launchpad.net/bugs/297373 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 225297] [NEW] update-menus fvwm-crystal calls sh with bash parameter -r
Public bug reported: Binary package hint: fvwm-crystal /etc/menu-methods/fvwm-crystal (package fvwm-crystal) contains a call on line 20 to sh -r ..., although -r is not a valid POSIX sh parameter. Specifically, it is a valid bash parameter but not a valid dash parameter. This causes many errors during `update-menus`. A quick fix is to call bash directly, but that adds an unwanted dependency. A solution should use sh without -r, or some other alternative. Upstream (debian) bug report and possible solutions: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375205 ** Affects: fvwm-crystal (Ubuntu) Importance: Undecided Status: New -- update-menus fvwm-crystal calls sh with bash parameter -r https://bugs.launchpad.net/bugs/225297 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 224477] [NEW] upstart /usr/sbin/invoke-rc.d calls /sbin/runlevel without DEPENDSing sysvinit or upstart-compat-sysv
Public bug reported: upstart's /usr/sbin/invoke-rc.d script makes a call to /sbin/runlevel (on line 274). if neither sysvinit nor upstart-compat-sysv are installed then /sbin/runlevel won't exist, and it complains. one of those packages, or one of their PROVIDES, should be a DEPENDS of upstart. ** Affects: ubuntu Importance: Undecided Status: New -- upstart /usr/sbin/invoke-rc.d calls /sbin/runlevel without DEPENDSing sysvinit or upstart-compat-sysv https://bugs.launchpad.net/bugs/224477 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 134725] xrandr rotates screen, does not change resolution
Public bug reported: Binary package hint: xserver-xorg-video-i810 After upgrading to gutsy (on 2007 08 22) xrandr now rotates the screen but does not change the apparent resolution. When it should change from 1024x768 to 768x1024 (a not-native resolution) it does not, leaving me with a 1024x768 desktop on a 768x1024 display. This makes the right 1/4 of the desktop cut off, and the bottom 1/4 of the display blank. This could be related to bug #116514 or bug #111859 ** Affects: xserver-xorg-video-i810 (Ubuntu) Importance: Undecided Status: New -- xrandr rotates screen, does not change resolution https://bugs.launchpad.net/bugs/134725 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134729] kde panel buttons jump when moved
Public bug reported: Using gutsy, when I have a non-kde-application on my panel (as a button) and I drag it around, the outline box showing where it will land jumps around and is sometimes not visible. When I drop the button that I am dragging often it will drop in the wrong place, or other buttons will move incorrectly. ** Affects: ubuntu Importance: Undecided Status: New -- kde panel buttons jump when moved https://bugs.launchpad.net/bugs/134729 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105962] Re: Feisty: KDE System Settings crashed when trying to open it (Backtrace attached)
I have the same problem, system settings crashes when i try to load it. This started after edgy-feisty dist-upgrade, and possibly some other package installations. This same issue may also be causing kcontrol to display only a few rare options (empty Network folder and Perhiperals-OBEX Devices). backtrace below: (no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1232766768 (LWP 9618)] 0xe410 in ?? () #0 0xe410 in ?? () #1 0xbfd7fa48 in ?? () #2 0xb7b31ff4 in ?? () from /lib/tls/i686/cmov/libc.so.6 #3 0xbfd7fa34 in ?? () #4 0xb7a7ee90 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #5 0xb7a7ecc7 in sleep () from /lib/tls/i686/cmov/libc.so.6 #6 0xb7878ad9 in KCrash::startDrKonqi (argv=0xbfd81c4c, argc=17) at /build/buildd/kdelibs-3.5.7/./kdecore/kcrash.cpp:312 #7 0xb788f4de in KCrash::defaultCrashHandler (sig=11) at /build/buildd/kdelibs-3.5.7/./kdecore/kcrash.cpp:229 #8 0xe420 in ?? () #9 0x000b in ?? () #10 0x0033 in ?? () #11 0xc010 in ?? () #12 0x007b in ?? () #13 0x007b in ?? () #14 0x080ab800 in ?? () #15 0x08108d50 in ?? () #16 0xbfd81ff8 in ?? () #17 0xbfd81fd0 in ?? () #18 0x in ?? () -- Feisty: KDE System Settings crashed when trying to open it (Backtrace attached) https://bugs.launchpad.net/bugs/105962 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-systemsettings in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
Once again I feel the need to point out that this change is no worse than upgrading from XFree to X.org, or from GCC2/3 to GCC3/4. Those changes also broke* many existing programs, build processes, and scripts, but we made them for the greater good. * broke in this context meaning exposed existing previously-hidden brokenness in. The changes did not actually break anything (with few exceptions like posix echo), they simply brought to light problems that have always existed in those packages. -- Script that are using bash could be broken with the new symlink https://bugs.launchpad.net/bugs/61463 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
I believe that FAR less dashisms will creep in than bashisms have over time. Just like switching web browsers... A developer who switches from IE to Firefox has to give up all his IE-isms. He might pick up a couple of Firefox-isms, but I am almost certain that there will be less of them and they will be less problematic. The solution to dashisms is to report them as bugs. Just like you did for bashisms in the past (you did, right?). dash *IS* Unix-2003-compliant (on this issue at least). If you read a couple lines farther down, -n is not an option, it is an operand: A string to be written to standard output. If the first operand is -n, or if any of the operands contain a backslash ( '\' ) character, the results are implementation-defined. If every person who has posted to this bug report so far instead took the time to submit a patch to one bashism-laden project, this would be a non-problem. On 2/17/07, Martin Buchholz [EMAIL PROTECTED] wrote: dash cannot claim to be taking the moral high ground here, since dash's builtin echo is also not Unix-2003-compliant. According to http://www.opengroup.org/onlinepubs/009695399/utilities/echo.html Implementations shall not support any options. but dash's echo supports the (historic BSD) -n option. If Ubuntu persists in its present course of using dash as /bin/sh, there will be no way to have future reliable Ubuntu LTS versions, since dashisms will creep in. Users will merely have the choice of different sets of bugs, depending on whether they choose /bin/sh to point to /bin/bash or /bin/dash. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
I could maybe see patching dash to die with an error This script contains invalid syntax, try running it with /bin/bash instead of /bin/sh when it encounters one of various known bashisms like echo -e. On 2/17/07, nemti [EMAIL PROTECTED] wrote: No matter how many script devs you complain to, there is _always_ going to be a script that contains bashisms. If /bin/sh _absolutely_ has to point to dash, instead of refusing to run scripts with bashisms, why not do something constructive like scanning the script for bashisms, and then running it in bash? Or perhaps even patching dash to do something useful with bashisms when it comes across them, like issuing a warning, instead of just dying for reasons unknown to the user? -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
On 2/16/07, Martin Buchholz [EMAIL PROTECTED] wrote: I will probably continue to use Ubuntu on my home machine, since I am a bit of a reckless hobbyist there myself, but will recommend NOT using Ubuntu at work, and will look around for a distribution that values reliability more for my next at-home experimental install. Something like, say, Ubuntu LTS? -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
Because there shouldn't be one. There was no warning when the default X switched from XFree to X.org, because non-broken programs don't know the difference. There is no warning when upgrading gcc from 2.x to 3.x to 4.x, despite it being well known that that breaks MANY build processes. On 2/4/07, Ulrich Lukas [EMAIL PROTECTED] wrote: I just lost half a day figuring out why several configure scripts who ran perfectly under Dapper are broken in Edgy. Why isn't there at least a warning or note indicating the changed defaults? -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
On 1/24/07, Mark Constable [EMAIL PROTECTED] wrote: I have a choice, do I edit all these scripts (1000s!!!), do I self maintain a hacked /bin/sh link to /bin/bash, or, do I assign my future to another distro that I can trust not to put me in this position again? Or do you take the simple solution and just sudo dpkg-reconfigure dash and answer the single question No. Viola, you're back to bash as /bin/sh, and dont have to self maintain a hacked anything. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
I cannot disagree more. The Ubuntu devs have done a far greater good here than with any other distro I have used in the past. Being willing to take steps like this, instead of waiting for optional compliance that will never happen, is exactly what we need more of. On 1/23/07, Mark Constable [EMAIL PROTECTED] wrote: What worries me about this issue is the attitude of the ubuntu developers. I no longer trust the ubuntu devs to do the right thing to help me keep the systems I make a living from up and running and am now looking at migrating everything to etch+ instead of edgy+. The overwhelming right thing to do would have been to advertise the need to change from bash to dash and put a deadline on it no less than 1/2 a year on notice, THEN make the change. Suddenly unleashing KNOWN breakage like this is unacceptable to me. Such a pity I have to forgo such a good distro in all other respects because of this stupid move by a few devs. Like I say, I no longer trust ubuntu devs not to do something like this again in the future. And yes, breaking trust is a serious bug. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
The overwhelming majority of Ubuntu users would almost never notice application installs running faster? I am serious. There are packages that take over a minute for post-install dpkg configuration, and dash speeds them up a LOT. It's the difference in spending 10 minutes or 30 minutes on dist-upgrade (or I guess adept probably just does upgrade). Bash being optionally POSIX compliant, with or without exceptions, really has no bearing here. Bashisms are bad. They need to be fixed. I understand the idea of keeping Ubuntu easy for everyone to use, but you also need to understand that sometimes you have to do things the hard way to make the world a better place. Ubuntu is the first major distro to move to dash. I think we have begun down a slippery slope towards eradication of bashisms. They never would have gone away if it was just 'the right thing to do', but now if you write broken scripts you give up support for a major distro. I don't think any new bashisms will be entering the world as soon as a year from now, and I expect we can resolve any existing problems by then as well. Bite the bullet. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
$10 says neither of you reported the problem to those at fault, GPH and VMWare, instead of just discussing it in forums. If people put half as much time into getting the problem fixed as they do whining about it, the vast majority of packages would already be fixed. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
Nothing in an Ubuntu package is unsupported. If the upstream has abandoned it then the maintenance falls on the package maintainer. If the package maintainer is lax then replace him yourself. On 1/3/07, LionsPhil [EMAIL PROTECTED] wrote: Because getting large groups of people to fix software/data, much of which is [now] unsupported, is /so/ much more practical than leaving alone something which Just Works. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
The fact is in the majority of cases [dash] fails miserably This is what polite people call a falsehood, and what I call a lie. By my gross overestimate, dash fails while compiling less than 5% of available packages, and while installing less than 1%. The failure rate for third party software, such as cedega and commercial installers, is around 5%. This is not a majority by quite a bit. While I somewhat sympathize with the make it work, even if it's wrong sentiment, I would be willing to bet that less than half of the people who have posted here have bothered to report the real bugs to their package maintainers and/or upstream. Start making efforts in the right direction. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 61463] Re: Script that are using bash could be broken with the new symlink
The 'bug' is not with dash, it is with every package that dash breaks. They should all be fixed. *maybe* dash should not be the default until they are fixed, but I think they would never get fixed if it wasn't. On 10/30/06, Stephen Thorne [EMAIL PROTECTED] wrote: Suggested resolution: Use /bin/dash instead of /bin/sh for scripts that are desired to run fast, and revert the change. If you like ./configure running faster, then patch the code so that ./configure has #!/bin/dash. This change has obviously caused regressions, and should be considered a high priority bug that should be fixed, not justified. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Wrong target.
Complain to the script authors who are making the mistake. Dash has been a viable provider of /bin/sh (by way of debconf on the dash package) for a long time. There are other shells that provide 'sh' functionality too. If a script really requires /bin/bash then it needs to start with #!/bin/bash. Analogy: If I needed a square, I would not ask you for a rectangle. Although you might give me the square that I need, since that would fulfill my stated rectangle requirements, it is not guaranteed. People who need /bin/bash should not ask for /bin/sh and hope that the result they get just happens to be /bin/bash. I have used dash as my /bin/sh for over a year now. It is insanely faster, especially for huge shell scripts such as 'configure' in large projects. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
