Hmm, a June 5 release date for this fix seems to be wait too late for
the severity of this system freeze bug. A large number of people who run
Ubuntu now (either long-time users or newcomers testing the desktop
platform) has his/her computer crash every hour or so. On that basis,
shouldn't
I've also been suffering from this issue. The kernel here
(http://people.canonical.com/~sforshee/lp1674838/) appears to have dealt
with the system hang, happily viewing videos on Firefox now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Timo, yes sorry, you've got the proper link :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620173
Title:
Qt5 5.6 regression: conversion from QVariant to QString is broken
To manage
Ok, while trying to create a debdiff (with the help of Simon Q on IRC,
thanks :) ), I realized the above is effectively part 2, and part 1 is
this commit:
Part 1: https://codereview.qt-project.org/#/c/127924/12//ALL,unified
Part 2: https://codereview.qt-project.org/#/c/127924/12//ALL,unified
** Description changed:
A regression was introduced in Qt5 5.5 - fixed in 5.7 - whereas
conversion from QVariant to QString is broken for double and float
values (you can see more details on this here:
https://bugreports.qt.io/browse/QTBUG-47192).
The patch fixing this issue is the
Public bug reported:
A regression was introduced in Qt5 5.5 - fixed in 5.7 - whereas
conversion from QVariant to QString is broken for double and float
values (you can see more details on this here:
https://bugreports.qt.io/browse/QTBUG-47192).
The patch fixing this issue is the following:
Dmitry, ok, I understand what's happening now. Prior to PyQt5 version
5.7, importing pyuic would run the code, whereas as of version 5.7, the
code is put under a main() function, which is called here:
if __name__ == '__main__':
main()
The PyQt5 author must have had his reason(s) to do so.
Dmitry,
I'm not familiar with the rational as to why QGIS (and I have to assume
other projects) have settled on going through this method to invoke
pyuic5. That said, this method used to work just fine when building QGIS
under Ubuntu 16.04, with pyqt5 5.5.1. The regression highlighted here
Execute this python script by typing:
python pyqt4.py dialogAbout.ui
This will successfully output the python generated code for the .ui
file.
** Attachment added: "pyqt4.py"
https://bugs.launchpad.net/ubuntu/+source/pyqt5/+bug/1619840/+attachment/4733899/+files/pyqt4.py
--
You received
Test .ui file, instructions coming in a separate post.
** Attachment added: "dialogAbout.ui"
https://bugs.launchpad.net/ubuntu/+source/pyqt5/+bug/1619840/+attachment/4733898/+files/dialogAbout.ui
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Execute this python script by typing:
python3 pyqt5.py dialogAbout.ui
This will fail to output any python generated code for the .ui file.
** Attachment added: "pyqt5.py"
https://bugs.launchpad.net/ubuntu/+source/pyqt5/+bug/1619840/+attachment/4733900/+files/pyqt5.py
--
You received this
(actually, you can run python pyqt5.py dialogAbout.ui to see the module
fail too, that eliminates the problem being python3-related)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619840
Title:
Dmitry, normally, having a python script that simply has:
from PyQt5.uic import pyuic
would trigger the error message when run without an argument (which the
imported pyuic module needs to trigger a .ui to .py output).
ATM, under 16.10:
- a python 2 script with this simple line: from PyQt4.uic
Public bug reported:
The python3-pyqt5's pyuic module doesn't appear to work under upcoming
Ubuntu Yakkety.
Normally, executing a script (with no additional argument) which simply
calls "from PyQt5.uic import pyuic" would return an error in the console
saying Error: one input ui-file must be
Sebastien, I'm running the nightly version of Firefox, and it is built
against gtk3, and well, it does crash :)
When you say the issue has been resolved, do you mean resolved in the
gfvs version that'll be shipped with ubuntu 15.10?
--
You received this bug notification because you are a member
Public bug reported:
The gfvs package in the repository of the forthcoming ubuntu 15.10 has a
bug that causes firefox to crash when opening up the file picker dialog
(see https://bugzilla.mozilla.org/show_bug.cgi?id=1212139).
The bug has been patched (see
I get similar keyboard issues on Nautilus, Gedit, and Filezilla.
Wondering whether its a 64-bit specific issue as my secondary computer
is on 14.10 32-bit and there I am not affected by this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Steven, thanks for the workaround, working here.
That said, at the risk of stating the obvious, this bug should really be
considered a top priority to fix. After installing 14.04 on a couple of
co-workers' laptops, this huge black borders upon resuming is the number
one complaint.
--
You
Public bug reported:
An automated build of QuantumGIS (http://www.qgis.org/) for Ubuntu's
forthcoming 'raring' 13.04 revealed a compilation issue with latest
python-sip 4.14.4. For background information, see QGIS' issue on this:
http://hub.qgis.org/issues/7352.
Python-sip's maintainer, Phil
Hmm, I got the problematic nm package on my system, and therefore can't
download the updated nm package as apt get fails to resolve domain.
Work around please? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same here. It has been happening for quite some time on Oneiric. As we
are getting closer to release date, I'm getting worried bug doesn't
appear to be on dev radar.
Anything we can do to make sure next version of ubuntu doesn't ship with
this bug in?
--
You received this bug notification
Andrea, indeed, I don't have issue dragging text. I also don't see the
freeze if I drag mixed content (i.e. text + image).
Can't remember whether I had the issue under Natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Glad we're moving forward and finding duplicates.
That being said, I suggest for the bug's importance to be elevated to
critical. When this bug was initially filed, only the top bar and/or
launcher was suffering from screen corruption but the main desktop area
was left unscrambled. In the
+1 over here; freezing can last 5 to 10 seconds, really bad user
experience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772445
Title:
Dragging image from firefox/chrome to dock causes
Omer Andrea,
Yes, I'm running a fully up-to-date oneiric system. Info:
Firefox: Nightly/9.0a1 (2011-09-06) (mozilla.org build)
Unity --version: unity 4.12.0
Regarding the steps, it's pretty straight forward. Load firefox, select
some texts and/or images, then start dragging. You'll notice
Additional info: freezing appears to be triggered more often when
dragging images. For e.g., I'm getting freezes 100% of the time when
dragging the unity logo image at the very top of this page.
It might have to do with the type of data firefox attaches to the
dragged object.
--
You received
Thinking out-loud: issue must be in the function analysing the dragged
object data. It could be that the data from a dragged image in firefox
is base64 encoded ascii character, making it quite a big chunk of data
for unity to analyze.
--
You received this bug notification because you are a
bug gone for me; opening of .zip archives now working using file-roller
(3.1.90-0ubuntu1)/oneiric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721284
Title:
[Upstream] file-roller unable to
I'm also victim of this issue. Hope this can be put on the radar of
ubuntu devs; it'd be a real show-stopper to end up releasing a final
product without proper .zip support : )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wondering whether
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/830299 is somehow a
duplicate of this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/676166
Title:
Screen corruption when
Also affecting me; it's pretty bad. It feels like a corrupt layer sized
to the screen is placed in between the unity launcher and the rest
(windows, desktop, pop up menus, etc.)
The only two interfaces displaying over the corrupt layer are the dash
and the switch-to window.
--
You received
Hope the screenshot can fully express the severity of this issue : )
** Attachment added: screenshot-video-corruption-resume.jpg
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/830299/+attachment/2297045/+files/screenshot-video-corruption-resume.jpg
--
You received this bug
The link mentioned in comment 4 also worked out for me. Thanks Piotr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764195
Title:
laptop screen blacklight brightness always at 100% (even on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764195
Title:
laptop screen blacklight brightness always at 100% (even on battery),
can't be lowered
--
ubuntu-bugs mailing list
Public bug reported:
Since I upgraded to Ubuntu natty, I can't change the screen's backlight
brightness. This is a huge regression from maverick (under which I could
change the brightness). It appears to have something to do with the new
nvidia drivers under natty.
The problem persists even when
Public bug reported:
Would be nice to have this update for all the GIS folks using ubuntu.
http://trac.osgeo.org/gdal/wiki/Release/1.8.0-News
** Affects: gdal (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Can we get a Ayatana design team member to join in the discussion over
here? Every day using unity increases my belief the mouse wheel is
currently being misused.
One way to go forward with this is to add a setting in the compiz unity
plugin. The default can remain scrolling launcher (big waste
Martin, apologies for the long delay.
I unfortunately was in a hurry to get my computer to a working stag. I
apparently did something that fixed the issue and therefore can't
provide debugging output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'll do as soon as I go home.
Just to clarify the situation, the only step I need to do for it to
crash is to start Jockey (either from terminal or from the menu). It
crashes before showing the window that displays the list of proprietary
drivers to activate/deactivate.
--
You received this bug
Jeremy, this bug affects my brand new dell vostro 3700 with an nvidia
gm330. It appears to be linked to the nouveau driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/636672
Title:
Brightness
I think these links are relevant:
https://bugzilla.redhat.com/show_bug.cgi?id=625171
https://bugzilla.redhat.com/show_bug.cgi?id=666462
** Bug watch added: Red Hat Bugzilla #625171
https://bugzilla.redhat.com/show_bug.cgi?id=625171
** Bug watch added: Red Hat Bugzilla #666462
I'm facing this issue on a brand new installation of latest Natty on my
Dell Vostro 3700. It turns out to be a big problem as it prevents me
from activating both the NVIDIA and the wireless broadcom drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bernhard, what he probably meant to say is that while scrolling does
work now, the poor visual feedback (I have to aggressively scroll 4
times before the icon loses a line next to the speaker) makes it harder
to use. It's very much possible that people will conclude scrolling
isn't working anymore
Part of the problem here (to devs: correct me if I'm wrong) is that this
bug is not about turning the tooltip switch back on but rather add code
into indicator-application to recreate the tooltip function that was
present in RIP system tray icons.
That requires more effort/time, but is well worth
- A tooltip displaying the name of currently playing song is needed for
Rhythmbox application indicator (I'm glad to see disabled menu displaying
current artist + song was added in the latest version but that requires a user
click and displays the rest of the menu which takes some visual space)
Mark, making things worse as a result of making changes for the sake of
changing is also a well established consequence of the less is more
principle ;o)
The whole system tray was a mess for many years and I raise my hat to
the Ubuntu team for making drastic changes to try and bring order to
Can we get an indicator-application to step in and comment on this bug
and/or flawed design choice? 10.04 final is approaching fast and IMO
fixing this bug (or having a serious discussion if it's a design choice)
needs to happen before then.
--
indicator-application menu item icon placement is
** Changed in: indicator-application (Ubuntu)
Status: Invalid = New
--
indicator-application menu item icon placement is wrong
https://bugs.launchpad.net/bugs/528243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Omer, well then this becomes a bug about a flawed indicator-application
design. Why would they create menus inconsistent with the rest of the
platform the indicator-application is running on?!
--
indicator-application menu item icon placement is wrong
https://bugs.launchpad.net/bugs/528243
You
Public bug reported:
I finally found out what made me feel uncomfortable with the indicator
application menus in current Lucid builds: the placement of menu item
icons are visually _inconsistent_ with menus found everywhere else in
gnome. See screen captures attached to this bug report.
**
Public bug reported:
I finally found out what made me feel uncomfortable with the indicator
application menus in current Lucid builds: the placement of menu item
icons are visually _inconsistent_ with menus found everywhere else in
gnome. See screen captures attached to this bug report.
**
*** This bug is a duplicate of bug 528240 ***
https://bugs.launchpad.net/bugs/528240
Public bug reported:
I finally found out what made me feel uncomfortable with the indicator
application menus in current Lucid builds: the placement of menu item
icons are visually _inconsistent_ with menus
On the left side, the current rhythmbox indicator menu, on the right
side, a rendering of the menu consistent with the rest of the gnome
world.
** Attachment added:
indicatormenu-rhythmbox-current(left)feeling-good(right).jpg
Same inconsistency present in the transmission indicator menu.
** Attachment added:
indicatormenu-transmission-current(left)feeling-good(right).jpg
http://launchpadlibrarian.net/39807894/indicatormenu-transmission-current%28left%29feeling-good%28right%29.jpg
--
indicator-application menu
... and the indicator messaging menu.
** Attachment added: menu-connect.jpg
http://launchpadlibrarian.net/39807899/menu-connect.jpg
--
indicator-application menu item icon placement is wrong
https://bugs.launchpad.net/bugs/528243
You received this bug notification because you are a member of
One example of a consistent menu in firefox.
** Attachment added: menu-other-firefox.jpg
http://launchpadlibrarian.net/39807970/menu-other-firefox.jpg
--
indicator-application menu item icon placement is wrong
https://bugs.launchpad.net/bugs/528243
You received this bug notification because
Consistent system menu of the Places menu.
** Attachment added: menu-other-system.jpg
http://launchpadlibrarian.net/39807980/menu-other-system.jpg
** Package changed: ubuntu = indicator-application (Ubuntu)
--
indicator-application menu item icon placement is wrong
*** This bug is a duplicate of bug 528243 ***
https://bugs.launchpad.net/bugs/528243
** This bug is no longer a duplicate of bug 528240
indicator-application menu item icon placement is wrong
** This bug has been marked a duplicate of bug 528243
indicator-application menu item icon
*** This bug is a duplicate of bug 528243 ***
https://bugs.launchpad.net/bugs/528243
Monkey, arg, my crappy Cambodian internet connection submitted the bug
twice. Can you make this bug (and #528241) a duplicate of #528243, in
which I've uploaded the screenshot.
** This bug has been marked a
*** This bug is a duplicate of bug 525295 ***
https://bugs.launchpad.net/bugs/525295
Why was this bug relating to a background color inconsistency flagged as
a duplicate of a bug relating to icons not showing up properly when
missing from icon theme?!
Please un duplicate the bug.
** Changed
Public bug reported:
Binary package hint: indicator-sound
The summary attached screen capture are pretty self explanatory.
With Gtk themes that define different color values for the window
background and the menu background, the indicator-sound volume slider
background will use the defined
** Attachment added: sliderbackground.png
http://launchpadlibrarian.net/39255261/sliderbackground.png
--
indicator-sound volume slider background is wrong under certain gtk themes
https://bugs.launchpad.net/bugs/522471
You received this bug notification because you are a member of Ubuntu
Few possible solutions:
1/ Apply the menu background color to the slider's background.
2/ Add a frame surrounding the slider so it has a more attractive look when
inserted in a menu.
Solution 1 can be a problem in itself if the slider is dark and the
theme assumes it will be displayed on a light
Same problem on my Dell Latitude D830, Intel video
--
Can't unblank my Inspiron 640m after a lid close
https://bugs.launchpad.net/bugs/496842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
https://bugzilla.gnome.org/show_bug.cgi?id=594760 seems to be the right
upstream bug.
** Bug watch added: GNOME Bug Tracker #594760
http://bugzilla.gnome.org/show_bug.cgi?id=594760
--
Karmic upgrade not shutting off backlight after time
https://bugs.launchpad.net/bugs/413168
You received
I wonder if the resurgence of this bug has anything to do with Bug
397892 (Screensaver does not turn on [Ubuntu/Xubuntu Karmic])
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs,
Confirmed on Ubuntu Karmic with latest updates up to August 13. (The
gnome-screensaver-command -a command does bring screensaver on too)
** Summary changed:
- Screensaver does not turn on [Xubuntu Karmic]
+ Screensaver does not turn on [Ubuntu/Xubuntu Karmic]
--
Screensaver does not turn on
*** This bug is a duplicate of bug 401386 ***
https://bugs.launchpad.net/bugs/401386
** This bug has been marked a duplicate of bug 401386
Missing plugins in avidemux - regression
--
avidemux. no audio decoder found
https://bugs.launchpad.net/bugs/404585
You received this bug
Problem persisting on kernel 2.6.31-3.
--
no sounds through alsa, errors in syslog
https://bugs.launchpad.net/bugs/398080
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
Same problem here, on a Dell Latitude D830. It seems to have appeared
after I've applied latest kernel 2.5.31-2 update.
Bug 397890 looks like a duplicate and mentions a work-around to re
enable sound pending resolution of this problem.
--
no sounds through alsa, errors in syslog
My Dell Latitude D830 is showing the exact same symptoms on Ubuntu
Karmic (updated to June 2007). The same laptop was however fine with
Ubuntu Jaunty.
Devs, is there anything we can do to help narrow down issue?
--
System freezes after putting display to sleep when inactive
Public bug reported:
summary says it all; resuming from latest kernel in Jaunty on a latitude
d830 fails. the screen goes from black to bright white in 10 seconds.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
Architecture:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/25372704/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/25372705/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25372706/Dependencies.txt
**
Still flickering using intel driver 2.4.1 with an intel mobile gm965
graphic card on a dell latitude d830.
--
Flickering with version 2.4.0
https://bugs.launchpad.net/bugs/256142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The black corrupted screen has been identified by the mesa team; you can
follow status of bug at
https://bugs.freedesktop.org/show_bug.cgi?id=14441 .
--
Intrepid, on latest updates (mesa updates - 7.1~rc1-0ubuntu1), compiz no longer
works and gives white screen on login
confirming also being victim of this resume after suspend bug on a dell
latitude d830 laptop on hardy beta release (kernel 2.6.24.12)
--
i8042 unbind required for keyboard/mouse to be useable following suspend/resume
hibernate/resume cycle
https://bugs.launchpad.net/bugs/23497
You received
Also seeing this on my laptop with NetworkManager 0.6.5ubuntu15
--
NetworkManager hangs with 100% cpu
https://bugs.launchpad.net/bugs/83623
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
updated to 0.6.2-2ubuntu2 and problem still persists, searches return 0
result (both from the tracker-search-gtk and the command line tracker-
search)
also get a bunch of GLib-CRITICAL message mentioned above if I run
trackerd -v 3 -R
--
tracker-search-tool reports no result
No sound on welcome screen, no sound on login on Gutsy Gibson i386 Tribe
5.
--
No Sound on Login Screen or during Login in Gutsy Tribe 3
https://bugs.launchpad.net/bugs/129029
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I confirm it's also happening to me, but I suspect it might not be, or
not entirely, gnome-power-manager's mistake. I updated hal to 0.5.9 on a
Feisty laptop and noticed the same bug: closing the lid would not
suspend unless you re-open and re-close lid. Downgrading to hal 0.5.8
did the trick.
see also hal bug #114595 and #114507 ...
--
gnome-power-manager does not suspend on laptop lid close
https://bugs.launchpad.net/bugs/120521
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: hal
Highlights of this release
- Solaris backend
- FreeBSD backend
- Lots of CPU/memory optimizations
- Support for ConsoleKit
- Support for ACL management
- Updated docs and man pages
- fdi info files in separate tarball
- Lots of bug fixes
- RF
I confirm applying the same procedures works for newer version of
CMapTools 4.07 released in October.
--
I think glib c - ihmc cmap tools broken
https://launchpad.net/bugs/63563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
83 matches
Mail list logo
