Obsolete.
No idea when this was fixed, but I'm using v1.2.3 which runs bog stable.
Closed.
** Changed in: pcmanfm (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hopefully, Marius.
This despotic attitude of Adobe people is simply disgusting, as it's showing
here.
BTW, why "Fix Released" in Debian? Trying to crack a good joke??
NO FIX WAS EVER RELEASED. Period. Bart was right that the Debian people
cannot do anything about it, as "upstream ain't giving
strike 'Back in 2012, '
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968759
Title:
adobe-flashplugin 11.2.202.228-0lucid1freezes firefox display -
crashes some webkit programs (depends on cpu)
** Summary changed:
- (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
+ Remove EISA support from main kernel image and make it M (modular)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543919
Title:
(Wishlist) Remove EISA support from main
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543919
Title:
(Wishlist) Remove EISA support from main kernel image and make it M
(modular)?
To manage notifications about
>Use 'apt-get autoremove' to remove them.
>while it should give the warning as
>Use 'sudo apt-get autoremove' to remove them
It NOT that simple.
There should be made a case decision:
- Are we really sudo'ing?
- Are we working directly under root, i. e. the shell with the hash prompt?
In the
Public bug reported:
(This is a sort of RfC. )
I have a PC that still has the good old PCI ports, but I am 100% sure that the
active use of EISA dates back yet more 10 years.
In other words, boards that _only_ support EISA date back 25 years now, while
those that provide *one* EISA slot date
** Summary changed:
- (Wishlist) Change EISA support to M (modular)?
+ (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Why "Incomplete"? There's nothing to supply. I simply need some
maintainer's/kernel team's/iuser's feedback on this.
Funny enough that even if I muzzled that bot, "New" still gets auto-changed to
"Incomplete", this time even without an explanation.
Brad, let your bots behave a little more
Nothing to do ??
I beg to differ!
kernel.org #111901 is a kind of RfC whether CRS usage with old hardware should
be levitated or whether users are---even in future---entitled to boot their <
4.4.0 kernels with pci=nocrs.
And as the forced enabling of CRS was causing the problems that Sergey
Besides, about your "fixed upstream": I think it was entirely accidental.
Something got modified in PCI handling, and abracadabra, it made old hardware
work again.
But as fas as I could read the code fix, it didn't look as if Sergey's and mine
hardware was actually targeted.
We were LUCKY that
>It's not useful on a normal system since it's for debugging
Depends on point of view. :)
*As long as* everything is still working fine, there is no need for that tool.
But once evince goes all wonky with a certain PDF, it's the best tool to use
and NOT (as most users do) put the entire blame
Guessed so. Oleg did a marvellous job in figuring that out. That was not
easy-peasy by any means.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't
** Bug watch added: Linux Kernel Bug Tracker #111901
http://bugzilla.kernel.org/show_bug.cgi?id=111901
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=111901
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Oleg, huge thanks for your hard work!!
Ты чудо!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
To manage notifications about this bug go to:
Lubuntu + Openbox + LXDE.
I think Unity would be a little too much for my hardware...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540713
Title:
Tools drop-down menu displays as all empty
Public bug reported:
I've just discovered this bug when I was (desperately) trying to
document an issue in gedit which showed here a certain drop-down menu as
blank, no menu items.
scrot ALWAYS goes on strike when you have hotkey set to PrtSc (for example) and
you want to document a bug in a
Just discovered yet another bug.
Wasn't able to make a screenshot of the problem because drop-down menu had to
be SHOWN to you.
However, for scrot, this will cause the hotkey to get blocked!!
ksnapshot came to mind. (I don't use KDE, but this ksnapshot tool is
simply excellent.)
** Summary
Public bug reported:
(Before I mention anything about the bug, just wanted to make sure to
leave some BIG PRAISE to the gedit dev team for 3.18.2. Main Menu was
absent throughout in pre-3.18 and it was the horror, now everything
feels pefect again. Thank you.)
This report is for gedit 3.18.2
Christopher, it's NOT that simple in this case.
I can confirm that 4.3.4 fails and that 4.4.0 works.
But there is definitely nothing in the mainline that might give a chance to
find the "offending" patch, that broke it.
All we _could_ probably do is test 4.4.rc1 ... 4.4rc8.
But that might
hah.
Maybe this is not a "bug" after all...
Got this as well, and ended up at this LP bug...BUT...there was
something peculiar.
$ head -1 /boot/grubenv
did NOT cleanly display "GRUB Environment Block" but had a few characters
garbled in that line.
I remember this from IDE times, with
No problem, can do.
user@mybuntubox~$:~$ sudo apt-get --no-install-recommends install
libgtk-3-common=3.18.6-1ubuntu1
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed.
The following
Heheh, Manfred, I like that. You're trying to prove in the end that it's
a PEBKAC case after all. But still we can agree it is none...that is,
STILL. :-)
andy@andy-lubuntubox:~$ apt-get --simulate --no-install-recommends install
libgtk-3-common=3.18.6-1ubuntu1 adwaita-icon-theme
NOTE: This is
** Summary changed:
- libgtk-3-common: Adwaita theme dependency not recognized
+ libgtk-3-common: Adwaita theme dependency misdetected because of missing
libgtk-3-bin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6.
I think the following content will speak for itself:
user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme
Reading package lists... Done
Building dependency tree
Reading state
Public bug reported:
I'm having an occasional issue with evince, and since the issue is
clearly related to the PDF engine underneath which it uses (*this), I
got a tip to run a PDF directly with 'poppler-glib-demo' in the
'poppler-demos' package.
However, this tip was NOT suitable for Ubuntu, as
@Sergey, to find the actual bugger we'd have to test somewhere _between_ 4.3.5
and 4.3.9[99].
However, there was nothing like that available for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>4.3.0-040300-generic = pata_amd, pata_acpi error
>4.3.4-040304-generic = pata_amd, pata_acpi error
Confirmed!
> I tried to load Xubuntu 15.10 installation LiveCD from USB Stick. It
was loaded normally. (4.2.0-16-generic)
Aha, _that_ worked?
Well, my 4.2.x was exactly ... let me see ...
Many, many thanks Sergey!!
This problem really fussed me as I thought it's my hardware (as usual).
They must really have fixed a huge bug in 4.4.0.
For the Ubuntu folks here, note that 4.3.4 from Kernel Mainline will
still NOT work. (neither does 4.3.0-7, which made it into main repo only
2 days
So here we go again.
http://git.lxde.org/gitweb/?p=lxde/lxpanel.git;a=commit;h=bd6533554418767438eee066c3d76efe54fc1c64
Note, it's not exactly the commit that turned 'flawed' to 'fixed'; the crucial
file in any case is launchtaskbar.c .
That's where the fix was done in; but Andriy has fixed
---
GIT version works! !
---
(compiled it, sick and tired of it as I was)
Now please tell me why the Ubuntu packagers have slept again with their
eyes open and not used THAT version, distributing the flawed version
instead?!
--
You
"Ubuntu is essentially Debian Unstable, so you'd want to complain to
their packagers."
HAHA, I love that phrase, especially the first half! :) YMMD
Seriously though, no problem.
1. "Upstream" would have been an idea, but I haven't found anything
lxde/lxpanel related on GNOME Bugzilla. Pretty
Public bug reported:
This is not easy to explain, but it can be reproduced.
Running Lubuntu Wily FINAL with lxpanel 0.8.1-1ubuntu2 .
Reproduction of the bug:
- Have Task Bar at bottom. If you haven't, set it to screen bottom at
first.
- Make sure you have a few task items, i. e. programs
** Summary changed:
- LXpanel might auto-restart when RMB is pressed and mouse cursor is below
task pane
+ LXpanel might auto-restart when RMB is pressed and mouse cursor is at or
below task pane
** Summary changed:
- LXpanel might auto-restart when RMB is pressed and mouse cursor is at or
This is interesting..
https://sourceforge.net/p/lxde/bugs/758/
Sounds very closely related to me...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510364
Title:
LXpanel might auto-restart when
Oh, it *IS* a crash!!
I installed lxpanel-DBG and now I could figure out where the crash
happened:
Starting program: /usr/bin/lxpanel --log 5 --profile Lubuntu
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread
FIXED! Definitely. Thanks to the dev team.
(using wily FINAL, no beta crud)
** Changed in: lxappearance (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: lubuntu-artwork (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
^^ I wrote this above in "Comment on this change" but it appeared here.
Tough luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460192
Title:
new themes in lxappareance does not apply until
Wasn't aware that I have the permission to do that, but it worked :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460192
Title:
new themes in lxappareance does not apply until after login and
Fix now available in Wily FINAL version (out on Oct 22, 2015)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460192
Title:
new themes in lxappareance does not apply until after login and
logout.
Ok, but why "Invalid" and not "Fix Released"?
(just curious :))
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504078
Title:
[4.2.0-15.18] broken sound: 'output devices' not detected
To manage
Reinhard, you did the right thing in assuming that python-gnucash is always
present.
However, this is only legitimate because Sebastien made it an *essential*
dependency (see comment 20). So it wouldn't have been a legit fix unless these
two things get _combined_.
Good work both of you.
--
...which has even been marked 'Invalid' as now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434986
Title:
Not working network connection after boot
To manage notifications about this bug go to:
TBH, I only enabled -proposed because openbox 3.6.0 runs so well and
because of major and severe bugs with old openbox and lxappearance. This
was so unbearable that I chose to upgrade to (allegedly "unstable")
v3.6.0 ... and lo' and behold, haven't run into problems for weeks.
--
You received
AND TO EVERYBODY:
Please do NOT confuse the line
sudo apt-key update
with
sudo apt-get update
Always make sure you're referring to the one or the other.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, nuked /etc/apt/trusted.gpg and rebuilt is using
sudo apt-key update
YAY!!
That finally caused the error message of the very key 40976EAF437D05B5 to
disappear. Good riddance. :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(comment 7)
I can't believe it! THAT'S MINE!!!
40976EAF437D05B5
As I thought that it could even be related to some local repo not
updating their stuff in time (yes this happens sometimes in minor form),
I chenged to fr. and ch. domains sequentially. To no avail at all.
Thanks for the idea to
>For reference, the way to upgrade NetworkManager is the following:
>
>sudo apt-get install -t wily-proposed network-manager libnm0 libnm-glib4
>libnm-util2 gir1.2-networkmanager-1.0
Mathieu,
though this ssounds all pretty structured and logical, I think I know where
these issues come from.
JFTR, mine is 2.45.3-1 . (libglibmm @ 2.44.0-1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489154
Title:
NetworkManager does not start / fails to start
To manage notifications about this bug
Importance=Critical --- YES!
No network, no internet - zilch. That is, if you choose to use this broken
version.
Any developer around?
Please, anyone don't you go annoying me with apport reports (I hate
apport), you will only get these few gdb lines from me, which ought to
be enough to find the
Confirming with 1.0.4.
But WFM with 0.19.10.0.
BTW, instead of funny guessing, just do
ps -ef | grep NetworkManager
/usr/sbin/NetworkManager *MUST* be running if you want to access the Internet.
1.0.4 did NOT run. When checking /var/log/*.crash files, I found a
network-manager-related crash
OK, so my bug must be in ./NetworkManager/libnm/nm-device-wifi.c
in the function as follows:
prepare_scan_options (GVariant *options)
{
..
if (!options)
284 variant = g_variant_new_array (G_VARIANT_TYPE ({sv}),
NULL, 0);
285 else {
286
Public bug reported:
This is, in fact, NOT a real bug report.
However, as Manfred asked me to report it here anyway
(https://answers.launchpad.net/ubuntu/+source/hdparm/+question/270310 ) I will
do so.
(Let alone because the genuine Debian OS is also still at 9.43...)
Yes, (*)Ubuntu is VERY
No, you didn't get the point. ToZ does not want that the install
procedure forces light-locker/screensaver on the users by default,
thinking they could need it. There should be a way to select either of
them, both of them, or none of them at all.
--
You received this bug notification because you
Here's mine:
https://bugs.launchpad.net/ubuntu/+source/lxappearance/+bug/1469276
If you can't resist, mark it duplicate, I don't care. However, this bug
contains two solutions:
hackish: downgrade lxappearance-obconf-plugin which is the actual
culprit
non-hackish: upgrade openbox to 3.6.0
--
Andreas (#4), thanks for speaking up.
However, I need to do my stuff even though I have no system at the moment.
So the kernel update can't fix things for me, as I am running off a live cd
(better than nothing).
Still, it's really a bad bug that you have to REBOOT the machine to get things
back
Reinald, this is VERY interesting what you've written!
and found the diskless system serveral times hanging after a day or so
with unrecoverable:
This is exactly what I could witness on my live cd. It will work perfectly for
one day, then these artifacts will come up.
Whatever you're trying to
Got it! Just uploaded about 10 hours ago.
However, after enabling wily-proposed for openbox in /etc/apt/sources.list, I
had to use
$ sudo apt-get dist-upgrade
since the ordinary upgrade option did not install the new openbox.
--
You received this bug notification because you are a member of
** Also affects: lxappearance (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I just don't understand it.
Towards 0.2.2-1, lxappearance-obconf plugin 0.2.2-2 only seems to have
undergone a cosmetical change (i. e. information update).
But lxappearance
SUCCESS!
Managed to fix it myself.
However, I had to install openbox 3.6.0 first (yet marked unstable) and the new
dependencies (since lxappearance-obconf 0.2.2.3) libobrender31 and libobt4.
Works now, but should not be closed, as openbox 3.6.0 is still a little
futuristic ;)
--
You received
3.6 in wily? That's a great news, thank you!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469276
Title:
lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
To manage
Public bug reported:
I just don't understand it.
Towards 0.2.2-1, lxappearance-obconf plugin 0.2.2-2 only seems to have
undergone a cosmetical change (i. e. information update).
But lxappearance 0.6.1-1 works perfectly with 0.2.2-1 here on Wily.
However lxappearance 0.6.1-1 with plugin version
** Summary changed:
- lxappearance-obconf plugin causes lxappearance 0.6.1.-1 to segfault
+ lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does not only happen with dark panels.
Darklooks *IS* my default, and just to see some action I changed it in some
ugly one, e. g. HighContrast.
No effect.
But wait...after logout and logging back in, theme showed up as expected.
--
You received this bug notification because you are a member
Same ugly nonsense when attempting to install kde-cli-tools and kde-cli-
tools-data.
This is THAI LANG SUPPORT problem.
I had to do a
$ sudo apt-get remove kde-l10n-th
to fix it on my side.
However, this definitely should not happen at all. And why only for Thai
support? There must be
to comment 18:
I am not so sure if the fix inside gparted will be enough.
I remember that even here on Vivid I had to manually update to
libglibmm-2.4-1c2a (version 2.44).
The reason for this is that the significant fix was not applied yet in 2.43.x,
but in 2.44 :
** Description changed:
My CPU does not support SSE2, this is a fact.
- And as far as I knew, there was nowhere a *requirement* listed that for the
use of Chromium, a SSE2-capable CPU would be mandatory.
+ And as far as I knew (unless I missed something) for the use of Chromium on
Linux,
Public bug reported:
My CPU does not support SSE2, this is a fact.
And as far as I knew, there was nowhere a *requirement* listed that for the use
of Chromium, a SSE2-capable CPU would be mandatory.
For instance, old(er) Athlon XP machines support SSE, but not SSE2.
I've run a DEBUG build of
** Attachment removed: ProcEnviron.txt
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+attachment/4343042/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
First of all, I do not really know whether ths is a PCManFM issue at
all...maybe it's distro-specific enough to blame the individual
packagers...
Minor issue, no big deal.
Reproduction:
- Preferably use LXDE/Openbox (which is the default on Lubuntu here)
- Launch PCManFM
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1431414/+attachment/4343043/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
screenshot here:
** Attachment added: createlink_menuentry_pcmanfm.png
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+attachment/4343086/+files/createlink_menuentry_pcmanfm.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I do not see the open with create launcher with panel in my version
of vivid.
OK. A screenshot might clear things up, to see WHERE exactly this is
active:
(this was tricky to do; just learned that open menus _cannot_ be handled
with scrot; had to use ksnapshot)
--
You received this bug
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1431414/+attachment/4343041/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431414
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1431414/+attachment/4343042/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431414
apport information
** Tags added: apport-collected gnome3-ppa third-party-packages vivid
** Description changed:
First of all, I do not really know whether ths is a PCManFM issue at
all...maybe it's distro-specific enough to blame the individual
packagers...
Minor issue, no big deal.
apport information
** Attachment added: Udisks_dump.txt
https://bugs.launchpad.net/bugs/1431414/+attachment/4343044/+files/Udisks_dump.txt
** Attachment removed: Udisks_dump.txt
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+attachment/4343044/+files/Udisks_dump.txt
--
As of March 03, 2015. there is nothing like Beta 2. Title changed
appropriately.
** Summary changed:
- no permissions to install packages in vivid daily lubuntu beta 2
+ no permissions to install packages in vivid daily lubuntu beta 1
--
You received this bug notification because you are a
I second that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369273
Title:
gnucash crashed with ImportError in /usr/share/gnucash/python/init.py:
No module named gnucash
To manage notifications
This is for 2.6.3.
Wish I knew why 2.6.4 has been released _without_ fixing this No
module bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369273
Title:
gnucash crashed with ImportError in
Added RH bug (from my duplicate, which is likely to be disregarded
unlike this one here)
** Bug watch added: Red Hat Bugzilla #1167132
https://bugzilla.redhat.com/show_bug.cgi?id=1167132
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=1167132
Importance: Unknown
** Package changed: fedora = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297624
Title:
pcmanfm crashed with SIGSEGV in fm_mime_type_ref()
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1297117 ***
https://bugs.launchpad.net/bugs/1297117
See also bug 1297624 (public)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415648
Title:
pcmanfm
thanks for the information type change!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297624
Title:
pcmanfm crashed with SIGSEGV in fm_mime_type_ref()
To manage notifications about this bug go
*** This bug is a duplicate of bug 1297117 ***
https://bugs.launchpad.net/bugs/1297117
#1297717 *IS* private, yes.
Maybe we should finally convince the Apport folks to make bugs *public*
by default, as this is a mayor annoyance.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1297624 ***
https://bugs.launchpad.net/bugs/1297624
Yes, dammit, this bug MIGHT be a duplicate.
But as we cannot look into that damn bug because the silly person who sent it
in marked the bug as PRIVATE, it is at least better to have something to look
Public bug reported:
Assigned to libfm, as this is definitely an internal core problem,
nothing visual.
I don't know what I did to trigger the bug, I think I just clicked on the next
file in my folder and pcmanfm was no more.
BTW, please also note that the configuration file in Lubuntu is not
*** This bug is a duplicate of bug 1297624 ***
https://bugs.launchpad.net/bugs/1297624
** Bug watch added: Red Hat Bugzilla #1167132
https://bugzilla.redhat.com/show_bug.cgi?id=1167132
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=1167132
Importance:
Public bug reported:
While messing around with my partitions and the directory tree contained
within, I got this crash.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: pcmanfm 1.2.3-1.1
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic i686
This is a horrible bug, and no one wants to seem to fix it.
Here's my version:
(Precondition: installed libvdpau-va-gl1, as it was not there.)
Thanks for the VDPAU_DRIVER tip, very appreciated.
~$ export VDPAU_DRIVER=va_gl
~$ cd /usr/lib/i386-linux-gnu/dri
~$ ls -l
total 91924
-rw-r--r-- 1
I hope you will soon.
Current totem is horrid, feels like a software for total illiterates.
Everything feels so crippled: no more split screen w/playlist, only most
basic preferences and - worse - no menu bar at all.
And 3.15.x doesn't even start here on Vivid, but just segfaults. (See
other
Bingo, because I can confirm FOR SURE that 0.19.0-1-ubuntu1 does NOT include
the fix for this _critical_ bug here at all!
Left to say, I'm sick and tired of finding the 0.19.0somethingbuildsomething
crap everywhere.
*It* *is* *simply* *unuseable*. Full stop.
I had to move my butt to
OK...I take it back...
The actual reason was that IDIOTIC and illogical naming.
I will never understand why a _fully published_ version of gparted in
Utopic is called 0.19.0-1___build___1 and your still somewhat unofficial
PPA-only version is called 0.19.0-1-___ubuntu___1.
Normally, the
Added upstart to affected software. Reason: mentioned in dupe #1389044.
** Also affects: upstart
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/1364630
Wish I knew *WHERE* this error while reading message comes from!
init can mean quite a lot.
On Ubuntu flavors, /sbin/init is actually init from upstart package.
But just FWIW, I've grep'd recursively (-ir) for both broken pipe and
error while reading messages. None there.
So this init: Error
Wait...
Found a match on this error message in 'io.c' which is part of libnih, which on
its part is needed by /sbin/init.
So if anyone wants to debug the reason of this, he should start debugging
libnih (even adding a printf will do to see what's going on) and check what
(illegal?) parameter
Nice ... just wondering if this fix wouldn't have to be rolled back
again soon since roughly 100 tools have been recompiled after the recent
change(s)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Additional info: Even though 0.18.x dumps out a MYRIAD of debug, warning
AND error messages when started from console, it works fine. It was my
life-saver when I urgently had to change a partition size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Uhhh, that's the 1build1 I have that too. (or better: got it installed
by upgrading from Trusty to Utopic (final)
Unfortunately 0.19.1 is not available as a package for either Ubuntu nor
its flavors. I've looked everywhere, including PPAs.
--
You received this bug notification because you are a
1 - 100 of 151 matches
Mail list logo
