I have the same problem with a Presario 2199US, which also has the
Radeon Mobility U1. As with Thomas, I get bios, boot messages, and
usplash on the external monitor. Just before GDM comes up, the laptop
LCD goes completely blank (no backlight) for a few seconds; at that
time, the external monito
[Trying this again. Apologies if this is a duplicate.]
Wow! Thanks for the fast reply.
> What resolution are the monitors you are using (both the internal LCD
> and external monitor)?
The internal LCD is 1024x768. The external monitor is a CRT capable of
a variety of resolutions; I was aimi
> Are you trying to clone the internal monitor or have an extended
> desktop?
Cloning would be fine - I really just want to be able to use a projector
for presentations. But using
xrandr --ouput VGA-0 --same-as LDVS
doesn't work any better than the --left-of commands.
> Another thing you probab
I found that bug 231081 describes the same problem in the ATI IGP 340M
video card. Apparently, the IGP 340M is nearly identical to the
Mobility U1 (also known as the IGP 320M). The solution to bug 231081
was to update xserver-xorg-video-ati to 6.8.192. I couldn't find that
specific release, but
I've found how to activate the external monitor using xrandr from the
command line:
$ xrandr --output LDVS --mode "800x600"
$ xrandr --output LDVS --mode "1024x768"
The first will get a signal to the external monitor, and the second
restores the screen to the usual resolution. Running the seco
This was probably unspeakably gauche of me, but I removed the -needswork
tag until someone can explain to me why we would want metacity mucking
about with the audible system bell events. This bug (and system bell
events in general) obviously does still need work, but I just don't see
what more is
I don't know if this helps or not, but I've found a work-around for my
test case. The trick is to hold off on importing gtk and vte until
after the child process forks off. I'm guessing that the error is due
to two separate processes holding the same objects. (This affects both
gtk and vte, but
OK, I'm not having any problems with "ico -threads 10" with the PPA.
BUT: Is there any reason to believe that the problems with ico are the
same as this bug? As far as I can tell, the problem here is that Python
programs using X which execute a fork reliably throw a specific
assertion error. (I
Chris Halse Rogers wrote:
> There has recently been work done upstream to fix these sort of bugs.
> I've pushed some testing packages incorporating these fixes to
> https://edge.launchpad.net/~raof/+archive/aubergine/+packages.
I've tried installing packages from this PPA, and the test case still
> "Both would be bugs in the application."
I would like to point out my test case again (comment 31), a simple
pyGTK app that displays the same problem. While it may have a bug
(please point it out if you see it!), I find that unlikely given how
short and simple it is, and because it works perfec
Sorry - I did not intend to nominate for Lucid. It appears that Lucid
recently pulled in changes from Python's 2.6 maintenance branch, so I
assume this is fixed there (though I haven't checked). I can't figure
out how to undo the nomination, though.
Nonetheless, what are the chances of getting t
Since there's been no action from the Ubuntu maintainers on this, I
finally got around to reporting this upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=607906 Please take a look
and add anything that I forgot.
** Bug watch added: GNOME Bug Tracker #607906
https://bugzilla.gnome.org/show_
Public bug reported:
Both the gtk-apply and gtk-ok icons end up being sym-linked to the same
file. Some applications (Reinteract is where I noticed it) use both of
these icons to indicate similar but distinct states. Upon upgrading to
Karmic, and thereby being switched to the Humanity theme, I l
I've created a branch of metacity with the changes from the attached
patch, and requested a merge with master, as that seems to be what I was
supposed to do (https://wiki.ubuntu.com/SponsorshipProcess). For
purposes of cross-referencing, here's the merge request:
https://edge.launchpad.net/~rschro
** Branch linked: lp:~rschroll/metacity/system-bell
--
System beep broken in Karmic despite heroic efforts to fix it
https://bugs.launchpad.net/bugs/486154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I can confirm that Adam Collard's PPA version solves this issue. I have
not seen any side effects.
Adam, thanks for putting this PPA together. If there's anything I can
do to help, please let me know.
--
spurious trailing space after tab completion
https://bugs.launchpad.net/bugs/470824
You re
> so is this a metacity issue?
This is most definitely a metacity issue. The rate limiting does not
occur in compiz, nor does it occur in a simple xterm session.
> does applying the upstream patch fixes the issue for you?
Dunno. Is there an easy way to do this? I tried apt-getting the
source,
> You seem to not have cdbs, a build dependency for metacity, installed.
Thanks - that did it!
I can confirm that this change does fix issue (3) in Karmic.
As an editorial aside, I'd like to note that this was an insanely
complicated way to adjust a setting that would be better set in a
configur
> This was fixed in 2.6.4-4
Does this mean that I should not expect this fix to make it into Karmic?
--
spurious trailing space after tab completion
https://bugs.launchpad.net/bugs/470824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> The beep could be re-enabled by the user if he specifically requires
it,
How does the user re-enable the PC speaker beep? This user can't figure
it out.
--
Overuse of system beep without volume control
https://bugs.launchpad.net/bugs/77010
You received this bug notification because you are a
In reply to Grondr's post from yesterday:
> But if you hit rubout at the start of a line in that shell, you'll
> hear the bell out your line-out, not from the motherboard speaker. If
> you rmmod/modprobe, -then- a rubout there will -not- come out of
> line-out and -will- come out of the motherboard
Since we have some new people following this now, and our history of
trying to track this down has been long and convoluted, I though it
might help for me to summarize my understanding of the current
situation. As you read this, please keep in mind that I have no idea
what I'm talking about. The
Quoth Grondr:
> Re the rmmod/modprobe fandango: I'm not the only person who needs to
> do this. In fact, it would never have occurred to me that it would
> even change the behavior if I hadn't seen it mentioned in bug #398161
> (see comments #1 and #2 in this thread, where Philip asked if I'd
> tri
> 4. In my case the sound coming from the sound card was missing (point 1)
> and it works only if you disable compiz so I have to understand why
> compiz stops that sound.
If I understand correctly, this has nothing to do with the motherboard
speaker. In Metacity, you're getting a sound file (bel
We seem to be having slightly different problems - I am getting a sound
out of my speakers when I would expect a system beep. What I'm trying
to do is go back to the ugly PC speaker beep that I know and love. I
was guessing that the sound was being produced by pulse audio, and it
seems that modul
I've found two work-arounds. Let me know if either works for you.
Workaround #1
Whatever is trapping system bell events tries to play the file
/usr/share/sounds/ubuntu/stereo/bell.ogg. If I rename this file, it falls back
to the using the system bell. So long as the PC speaker is enabled (`su
Grondr wrote:
> Robert: I think actually we had exactly the same problem, and your
> workaround works for me. I'll explain, 'cause it'll help in debugging
> this for real.
That seems like a reasonable assessment. I'll point out a few places where our
systems differ. These should be signs of
One of the reasons I wanted to disable the PA bell was that it only
fires about once a second (as discussed in bug #430203) when, e.g., you
hold down the backspace key at a terminal prompt. I prefer the old
behavior of the PC speaker of nearly-continuous beeping. When I first
implemented workarou
> Now, let's consider whether your window manager uses libcanberra
> fully. I know metacity does. Compiz doesn't.
Everything I've reported has been using metacity. If I turn on desktop
effects (which switches to compiz, if I'm not mistaken), I don't get any
system bells at first. If I enable th
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: GNOME Bug Tracker #593355
https://bugzilla.gnome.org/show_bug.cgi?id=593355
** Also affects: metacity via
https://bugzilla.gnome.org/show_bug.cgi?id=593355
Importance: Unknown
Status
The original report raised three issues:
1) There was silence before and after the sound in bell.ogg.
2) There may be a delay in loading bell.ogg for playback.
3) The bell was only repeated at a rate of 1/s.
The fix to ubuntu-sounds only addressed (1). The linked bug addresses (3).
(This fix has
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libcanberra (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Invalid
--
System beep broken in Karmic despite heroic efforts to fix i
I've marked the Pulse Audio bug as invalid.
The bug I feel is in metacity or libcanberra is that there is no (easy)
way to disable the system bell played back through the sound card in
favor of the PC speaker. (This is point (d) from above.) I don't know
whether the problem is in metacity, libca
I'm having the same problem on a Presario 2100 running 32-bit Karmic.
Running `modprobe pcspkr` enables beeping from the ttys, but Pulse Audio
continues to handle the system bell for X. Please let me know if you
need more hardware info from me, but this really looks like a software
issue to me.
O
Public bug reported:
Binary package hint: gnome-themes-ubuntu
In Lucid, a number of themes (Ambiance, Radiance, and Dust, e.g.) make
the menu bar of GTK apps the same color as the title bar. Additionally,
the window can be grabbed by the non-menu part of the menu bar, just as
with the title bar.
Public bug reported:
Binary package hint: gnome-themes-ubuntu
The grays of the Gnome panel are slightly different than the grays used
elsewhere in the New Wave theme. Maybe this is by design, but the
effect is subtle enough that it just looks wrong to my eyes. I would
advocate either making the
Sorry I'm not more clear.
In Lucid, GTK apps may have a grab target for the window in the area to
the right of the menu bar. That is, if you click and drag in this
region, you will drag the entire window. This behavior seems to be
theme-dependent: It exists in Ambiance, Radiance, and Dust, but n
Well, speaking solely as a user, my thought when seeing this was not,
"Ooh, usable!" but, "Looks like they forgot to change the defaults on
the panel color." Only when I looked more carefully did I find that the
colors changed slightly from Radiance (Lucid's default) but didn't match
the window co
> has anyone tried to reproduce this on lucid?
I just tried the test case and got the same error as before. (Although
now, it's caught by apport, so I have to wait for that think before I
can see the problem. Progress!) This is on a VM image of lucid that is
about 2 weeks old. libxcb isn't lis
Just to confirm my previous assertion, I installed the Lucid beta on a virtual
machine. I applied my patch [1], restarted metacity, and unloaded and reloaded
Pulse Audio's module-x11-bell [2]. System bells rang the same bell.ogg sound
file, but through Pulse Audio. Additionally, I could now s
Dmitrijs Ledkovs wrote:
> I'm part of Ubuntu Reviewers team. Your patch is good to brute-force
> revert the change but what about people who want both options and switch
> between the two behavior? As discussed in this long bug report it's not
> possible yet due to many issues raised and the patch
I've edited the description to try to give a better overview of our
current understanding of the various problems in this bug. Please add
anything I left out.
Also, I nominated this for Lucid because, hey, why not?
** Description changed:
- In a fully up-to-date AMD64 Karmic on an MSI MS-7511 a
Public bug reported:
I am writing a PyGTK application which involves a vte Terminal. I use a
forkpty() call to launch a child process in the terminal. When the
child process runs a raw_input(), it dies with the message:
python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long)
(dpy
** Attachment added: "Test case"
http://launchpadlibrarian.net/38847560/echotest.py
--
xcb_io.c assertion error following forkpty and raw_input in PyGTK
https://bugs.launchpad.net/bugs/518269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I just submitted bug #518269, in which this same error is seen in a
PyGTK application. I don't know if it is the same bug as this one. But
I did manage to put together a rather simple test case. If these turn
out to be the same bug, please mark mine as a duplicate.
--
apport-kde assert failure:
Here is the test case that I originally posted in #518269. It is a
PyGTK app with a vte Terminal. It uses forkpty() to create a child
process inside the terminal. That child process dies with this
assertion error when it reaches the raw_input() statement. (Actually,
it seems to need some action
I am beginning to wonder if this is a problem with the playback of the
beep, not with xset itself. After all, `xset q` reports the same values
that are set with xset. Additionally, pulse audio's module-x11-bell
properly respect the volume set by xset. Could the code that plays the
beep be gettin
Public bug reported:
Poppler (and therefore Evince) place the anchors of hyperlinks
incorrectly with some PDFs. I've attached a sample PDF which displays
the problem. The link is the work "link" in the second sentence, but
Evince misplaces the anchor to around the word "[This]". The same
proble
** Attachment added: "The testcase PDF"
http://launchpadlibrarian.net/41674730/testcase.pdf
--
Incorrect placement of hyperlink anchors in certain PDFs
https://bugs.launchpad.net/bugs/544743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Attachment added: "The LaTeX source for the test case."
http://launchpadlibrarian.net/41674769/testcase.tex
--
Incorrect placement of hyperlink anchors in certain PDFs
https://bugs.launchpad.net/bugs/544743
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Evince properly places the anchor in the case. It was made from the
same source file, but using pdflatex instead of latex > dvips > ps2pdf.
** Attachment added: "The test case compiled by pdflatex"
http://launchpadlibrarian.net/41674835/testcase.pdflatex.pdf
--
Incorrect placement of hyperli
The testcase still fails on the daily ISO.
** Changed in: libxcb (Ubuntu Lucid)
Status: Incomplete => Confirmed
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)'
failed.
https://b
This seems to have been fixed with revisions 75531 and 75725 in the
Python trunk, but these didn't make it into 2.6.4. Might these be
imported to Ubuntu's version?
Alternatively: This problem seems to have been caused by changes between
readline5 and readline6. If I link /lib/readline.so.6 to po
Donald, I fear you've mis-understood what this bug is about. We are
trying to get the system beep to come out of the PC speaker, which is
that speaker on your motherboard that can only play square waves. You
probably don't want to use this for your video conferencing, unless
you'll be talking to
Grondr, thanks for your exhaustive efforts to describe the many
permutations of this bug. I have only one thing to add: On my 9.04
system, the system bell seems to work exactly as it did in previous
versions. So I think what changed, changed between 9.04 and 9.10.
Perhaps we need to start diff-in
> > The beep could be re-enabled by the user if he specifically requires it,
>
> How does the user re-enable the PC speaker beep? This user can't figure it
> out.
Several of us have been spending a fair amount of time over in bug
#486154 trying to figure this out, and we still haven't accomplish
I think I've solved the issue of metacity grabbing audible system bell
events. The attached patch contains my changes to metacity
(specifically src/core/bell.c). Please give it a try and let me know if
it works for you. If not, please let me know. I am a complete novice
at dealing with .deb fil
As best I can read the code, this rate limiting in metacity affects
audible and visual bells identically. Thus, this change should allow
metacity to flash a visible bell at 10 Hz. (I can't figure out how to
enable the visual bell in 9.10, so I can't actually test this.) This
seems like a bad ide
> Confirmed---your patch fixes the issue.
Good to hear!
> Strictly speaking, I don't think you need part 3 of your patch
I this is correct. Part 3 only re-enables the gconf
/apps/metacity/general/audible_bell key to turn the bell on and off.
Whether metacity *should* have a key to do this, I do
** Summary changed:
- spurious trailing space after tab completion in cd
+ spurious trailing space after tab completion
--
spurious trailing space after tab completion
https://bugs.launchpad.net/bugs/470824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
A demonstration of this bug in the standard python interpreter:
>>> import rlcompleter
>>> import readline
>>> readline.parse_and_bind('tab: complete')
>>> read
In previous versions (with readline5), this expands to "readline". In
Karmic (with readline6), this expands to "readline". Although
th
** Description changed:
+ When linked against readline6, Python's readline module inserts a space
+ after tab completions. This differs from previous versions and in most
+ cases is unwanted.
+
+ Original description:
Using IPython 0.10, when I use tab completion after cd, IPython inserts an
*** This bug is a duplicate of bug 470824 ***
https://bugs.launchpad.net/bugs/470824
** This bug has been marked a duplicate of bug 470824
spurious trailing space after tab completion
--
Ipython adds extra space after successful completion
https://bugs.launchpad.net/bugs/463807
You receiv
*** This bug is a duplicate of bug 470824 ***
https://bugs.launchpad.net/bugs/470824
** This bug is no longer a duplicate of bug 463807
Ipython adds extra space after successful completion
** This bug has been marked a duplicate of bug 470824
spurious trailing space after tab completion
This issue has been fixed in Python's 2.6 maintenance branch with
revision 75747. (Here's the patch itself:
http://svn.python.org/view/python/branches/release26-maint/Modules/readline.c?r1=75747&r2=75746&pathrev=75747&view=patch)
What do I need to do to get this into Ubuntu's versions?
--
spurio
I have experienced this issue on several different computers running
8.04, 9.04, and 9.10. If it would help, I can provide hardware details
for these machines.
--
Cannot adjust system beep volume, only frequency and duration
https://bugs.launchpad.net/bugs/280767
You received this bug notificati
> Can you be precise about what you're doing to enable/disable compiz so
I can try the same tests?
I had been switching between "None" (metacity) and "Normal" (compiz) in
the Visual Effects panel of Appearance Preferences. I just figured out
that I can also switch by running "compiz --replace" an
Public bug reported:
On an upgrade from 12.04 to 14.04, there were many errors reported about
tex-common. Then this browser window opened trying to report a bug. So
here you go.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tex-common 4.04
ProcVersionSignature: Ubuntu 3.13.0-24.46-g
The linked patch fixes all of the problems I've noticed so far. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263317
Title:
Not working on GTK 3 windows
To manage notifications about this
I also had this problem after upgrading from 12.04 to 14.04. My TeX
install was broken afterwards. I eventually got it working by
uninstalling all tex-related packages, deleting /etc/texmf/texmf.d/, and
reinstalling the tex packages.
--
You received this bug notification because you are a membe
(Un)Fortunately, it appears the no bass bug (2) is a hardware problem.
I also got no bass when testing in Windows.
As for the only top speaker bug (1), I tested two more options in
/etc/modprobe.d/alsa-base.conf:
- "model=auto" had the same behavior as the majority.
- "single_cmd=1" didn't fix th
On 04/27/2012 12:52 PM, Joe H. wrote:
> Are there things I can run to give you extra info that maybe resolves
> the minor differences in hardware?
You could run `ubuntu-bug audio --save=bug.txt`. This should produce
the same information that I attached at the top of the bug report.You
can eithe
Public bug reported:
I have a HP Pavilion dv6-6186nr with "Beats Audio" (whatever that
means). As best I can tell, the notebook has four speakers: two under
the grill at the base of the screen ("top") and two along the front,
under the wrist rest ("front"). When playing audio through the
headpho
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971224
Title:
[HP Pavilion dv6 Notebook PC, IDT 92HD81B1X5, Speaker, Internal] No
bass, only 2/4 speakers working
To manage notifications about this b
Joe H.: Here's the Python script that hda_analyzer spit out for me. I
don't understand what it's doing, but it works for me. Maybe you'll be
lucky and have it work on your machine too. It doesn't look like it
needs any special packages, so it should run for you. Note that it
needs to be run as
On 04/26/2012 05:19 PM, Joe H. wrote:
> I do not get any out put with this script.
That's a good sign -- like all well-designed UNIX scripts, it is silent
on success. The question is, did it enable all four speakers?
--
You received this bug notification because you are a member of Ubuntu
Bugs
FWIW, the same problems occur when using JACK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971224
Title:
[HP Pavilion dv6 Notebook PC, IDT 92HD81B1X5, Speaker, Internal] No
bass, only 2/4 speake
Flailing around blindly in hda_analyzer, I've found that I can get sound
out of both the top and front speakers. If I change the connection of
Node 0x0f from 0x13 to 0x14, I get sound out of all four speakers.
Moreover, I can control the volumes independently. Node 0x13 controls
the volume of the
So, against what should this bug be filed? GTK/Qt? Vte? Python? All
of them? Something else?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to python-qt4 in Ubuntu.
https://bugs.launchpad.net/bugs/419501
Title:
apport-kde assert failure
In case it helps anyone else, here's a .deb I made by updating
2009-7ubuntu3 (current version in Lucid) to include REVTeX 4.1r. I can
confirm that this fixes the affiliation bug. Some obsure debuild bug
kept me from including the updated PDF files in this. But the .tex
files have been updated, s
And here's a .debdiff with those changes. Again, it's missing the
updated PDFs.
** Patch added: ".debdiff with REVTeX 4.1r"
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/575812/+attachment/1735959/+files/texlive-extra_2009-7ubuntu4.debdiff
** Tags added: patch
--
revtex4-1
Michael and Chris, thanks for taking a look at this. But I still don't
understand why the system bell should be tied to the window manager. It
seems to me a strange connection that leads to silly bugs like #430203.
IMHO, the obvious solution is to let Pulse Audio handle the beep and
leave the win
I also have this problem running under Gnome Shell. I'm currently on
14.04, and this happened both before and after I installed with SDK team
tools-development PPA. Previously on 12.04, I did not see this problem
under Gnome Shell.
--
You received this bug notification because you are a member
> It should be working on Nexus 4, 7 and 10
It's not working on my Nexus 7, but presumably that's because the flo
devel channel hasn't seen an update since April. Has it been abandoned
again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
See https://github.com/rschroll/beru/tree/section-crash for a test case.
This creates a page with a GridView and populates the gridview with
images loaded in from a javascript file. (This is to stand in for
loading from a database in the original.) This crashes most of the t
> Isn't that a bit old? For which device?
It was, until yesterday, the newest devel image available for flo. But
r2 just came out, so I upgraded to test, and aa-clickhook is broken.
I'll let you know when I've figured out how to work around that one.
FWIW, I am unable to reproduce the crash on a
This appears to be the problem I encountered after upgrading from devel
r1 to devel r2. The full traceback follows:
Fatal error: /tmp/com.ubuntu.developer.rschroll.beru_1.0.0_armhf.click failed
to install.
WARNING:root:Signature check failed, but installing anyway as requested
Traceback (most re
objdump doesn't exist on the device, so I copied the python3.4 binary
over to my desktop. Running that command doesn't produce any output.
(Just objdump -T alone does, so I assume it's working but producing
nothing that grep matches.)
FWIW, it looks like the only use for ctypes in click.py is to
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 2
device name: flo
channel: devel
alias: ubuntu-touch/vivid
last update: 2015-04-15 03:04:31
version version: 2
version ubuntu: 20150413
version device: 20150210
version custom: 20150413
phablet@ubuntu-phablet:~$ md5sum /usr/bin/py
Just to check my understanding, this change will cause an error when
trying to import a file with the same name as one that already exists.
Thus, there will be no way to import such a file while using a
ContentScope. Correct?
--
You received this bug notification because you are a member of Ubun
Public bug reported:
I could be nice to allow click packages to register as a handler for
some mimetypes. This would (presumably) allow the user to open a file
with the program from the file browser or from the command line with
xdg-open. (Issues about apparmor access would probably also need to
Well, when I asked about this on IRC, they referred me here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223891
Title:
Allow click packages to register as mimetype handlers
To manage notificatio
In #ubuntu-app-devel, David Planella pointed me over here. Of course,
"I was just following orders" is no defense :).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223891
Title:
Allow click packag
This is more than just an inconvenience. The toolkit has diverged
enough since this problem hit that code that runs on precise, quantal,
and raring will no longer run on saucy or trusty, and vice versa. In
particular, the internal API used by OptionSelectorDelegates has
changed; see #1257529.
--
Is this going to make it into the ubuntu-sdk-team ppa? If so, on what
sort of time scale?
Also, I notice that the ubuntu-ui-toolkit is no longer building for
saucy, due to missing 'qtbase5-dev (>= 5.2~)'. Since precise, quantal,
and raring are still on 5.0.2 in this ppa, I fear they will still f
Public bug reported:
When a ListItem is dragged, it emits "Started" and "Moving" events. But
if each "Moving" event is accepted, as happens in a live drag case, no
"Dropped" event will be emitted when the item is finally dropped. One
should be added. The "to" and "from" parameters could both be
Public bug reported:
ListItems in a ListView start off with a z of 1. When you start
dragging them, they get a z of 2. This causes two bits of weirdness:
1) Section headers in the ListView also have a z of 2. (See
http://doc.qt.io/qt-5/qml-qtquick-listview.html#section-prop) This
causes incon
Public bug reported:
By default, there is a separator at the bottom of all but the last
ListItem in a ListView. If drag-and-drop reordering is allowed, that
last item can be moved into the middle of the list. It does not gain a
separator in this case, resulting in two items without a separator
b
I just flashed my device with devel r2, and now I can no longer
reproduce the crash. Don't know if you want to close this as fixed or
not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444178
Title:
Public bug reported:
Triggering a in the HTML5 launcher does not open a
file picker and results in the error, "Content requested a file picker,
but the application hasn't provided one".
In contrast, the browser launches a Content Hub peer picker, accepts a
content import, and turns it into a HTM
1 - 100 of 142 matches
Mail list logo
