[Bug 1419338] Re: pcmanfm crashed with SIGSEGV in pango_attr_list_unref()
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. https://bugs.launchpad.net/bugs/1419338 Title: pcmanfm crashed with SIGSEGV in pango_attr_list_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1419338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968759] Re: adobe-flashplugin 11.2.202.228-0lucid1freezes firefox display - crashes some webkit programs (depends on cpu)
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 a damn" as pointed out so verbosely (and correctly) above by Rafal. As Flash is closed source, it would have to be done by Adobe themselves...OR...by some genius who knows about reverse engineering (disassemble everything and kickout all SSE2 shit). But knowing how big these files are, this may become a 1-year job... *** WARNING *** UNOFFICIAL *** Back in 2012, I decided to put up a Debian package back in 2013, and I stll get an insanely lot of download requests each week for it (even though I have never pestered any distro teams directly that they should include it) http://www65.zippyshare.com/v/78802631/file.html Install it, and it will work OOTB on any non-SSE2 machine. Created from an older maverick package, I simply replaced the Flash bloatware by yet another Chrome build (11.2.202.236) and fired this up to ZippyShare. -- 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/968759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968759] Re: adobe-flashplugin 11.2.202.228-0lucid1freezes firefox display - crashes some webkit programs (depends on cpu)
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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/968759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543919] Re: Remove EISA support from main kernel image and make it M (modular)
** 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. https://bugs.launchpad.net/bugs/1543919 Title: Remove EISA support from main kernel image and make it M (modular) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543919] Re: (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
** 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 kernel image and make it M (modular)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543919] Re: (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
** 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658960] Re: add "sudo" before apt-get autoremove in warning
>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 latter case, a 'sudo' would be total nonsense. In a nutshell, we have to check for internal user ID (zero, non-zero). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658960 Title: add "sudo" before apt-get autoremove in warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/658960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543919] [NEW] (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
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 back roughly 15 years (one of the Elitegroup K7 series comes to mind, from about 2001/02). So the EISA support *should* be provided, as we should even support ancient hardware (Linux principle :)) However, why the EISA support is *compiled in* is beyond me. For instance, it creates lots of totally unnecessary noise in dmesg: [0.08] EISA bus registered [1.598316] platform eisa.0: Probing EISA bus 0 [1.598345] platform eisa.0: Cannot allocate resource for EISA slot 1 (repeated 10 times, i=i+1) [1.598368] platform eisa.0: EISA: Detected 0 cards For a 1997 mainboard, this would make perfect sense. But it is very probable that said mainboard would require linux-image-extra nonetheless to support some days-of-yore chipset. So why not leave it as a *module*, while removing its support from main kernel image once and for all? Your turn. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543919] Re: (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
** 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. https://bugs.launchpad.net/bugs/1543919 Title: (Wishlist) Remove EISA support from main kernel image and make it M (modular)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543919] Re: (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
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 nicely. Yes, _still_. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
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 reported, I would not say "it has nothing to do". At least I would not believe it unless a more verbose explanation is given _why_ _not_. -- 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: https://bugs.launchpad.net/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
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 worked from some certain 4.4.0 RC. That's about it. -- 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: https://bugs.launchpad.net/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537895] Re: Please include poppler-glib-demo tool in standard package
>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 on evince itself. But evince is merely the "executive power", while highly dependent on the API it accesses under the hood. >Do you know if what binary fedora includes the binary? Sure, but you will get the information only because you've explicitly asked for it. :) So here goes... Originally, it was in poppler-utils, cf. https://bugzilla.redhat.com/show_bug.cgi?id=872338 Later, Marek moved it to its own subpackage 'poppler-demos'. Version 0.40 is now in the wild out there: http://arm.koji.fedoraproject.org/koji/rpminfo?rpmID=1912994 ** Bug watch added: Red Hat Bugzilla #872338 https://bugzilla.redhat.com/show_bug.cgi?id=872338 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537895 Title: Please include poppler-glib-demo tool in standard package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1537895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
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 load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
** 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 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: https://bugs.launchpad.net/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540713] Re: Tools drop-down menu displays as all empty (3.18.2)
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 (3.18.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1540713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540715] [NEW] scrot not working via hotkey if drop-down menu of source window is activated
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 window. So in that source window, you would show the dropped-down menu, and THEN hit the hotkey for scrot. Result: Nothing. You can almost bet your life on it that once you retract the drop-down menu (i. e. so that it doesn't show), scrot via hotkey will work fine again. Proved easily by polling my $HOME for new files. Whenever I hardcopied a window w/its menu dropped down = no new files. Would be great if this could be fixed. Unless...it's not a scrot issue but has to be reported upstream (DE? WM?) No idea where, really. ** Affects: scrot (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 window. So in that source window, you would show the dropped-down menu, and THEN hit the hotkey for scrot. Result: Nothing. - - You can almost bet your life on it that once you retract the drop-down - menu (i. e. so that it doesn't show), scrot via hotkey will work fine - again. + You can almost bet your life on it that once you retract the drop-down menu (i. e. so that it doesn't show), scrot via hotkey will work fine again. Proved easily by polling my $HOME for new files. Whenever I hardcopied a window w/its menu dropped down = no new files. + + Would be great if this could be fixed. Unless...it's not a scrot issue + but has to be reported upstream (DE? WM?) No idea where, really. ** Summary changed: - scrot not working via hotkey if drop-down menu of window is activated + scrot not working via hotkey if drop-down menu of source window is activated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540715 Title: scrot not working via hotkey if drop-down menu of source window is activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scrot/+bug/1540715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540713] Re: Tools drop-down menu displays as all empty (3.18.2)
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 changed: - Tools drop-down menu all empty (3.18.2) + Tools drop-down menu displays as all empty (3.18.2) ** Attachment added: "snapshot1.png" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1540713/+attachment/4561761/+files/snapshot1.png ** Description changed: (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.) + feels perfect again. Thank you.) This report is for gedit 3.18.2 running on Xenial. Things are working real fine, except for the TOOLS drop-down menu which contains absolutely no menu items. No idea why, but it looks somewhat wrong... -- 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 (3.18.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1540713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540713] [NEW] Tools drop-down menu all empty (3.18.2)
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 running on Xenial. Things are working real fine, except for the TOOLS drop-down menu which contains absolutely no menu items. No idea why, but it looks somewhat wrong... ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2016-02-02-040945_1029x739_scrot.png" https://bugs.launchpad.net/bugs/1540713/+attachment/4561760/+files/2016-02-02-040945_1029x739_scrot.png ** Description changed: (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. Menu was absent - in pre-3.18 and it was the horror, now everything feels pefect again. - Thank you.) + 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 running on Xenial. Things are working real fine, except for the TOOLS drop-down menu which contains absolutely no menu items. No idea why, but it looks somewhat wrong... -- 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 all empty (3.18.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1540713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
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 become a 2-weekend job :) -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439784] Re: Error: Invalid environment block
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 badly-seated cables that don't display MAXTOR but MBYUIPR or whatever on HDD detection. That's because one single bit is off due to one bent pin. It hasn't happened too rarely that I only saw a skew cable connection when using a magnifiier, or, at least a good lighting source (which is not always given) So thanks everybody for the "fix", but I can't blame grub2 for it yet. See above output ($ head) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/439784 Title: Error: Invalid environment block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/439784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537915] Re: libgtk-3-common: Adwaita theme dependency not recognized
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 information may help to resolve the situation: The following packages have unmet dependencies. libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Same thing, no? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537915 Title: libgtk-3-common: Adwaita theme dependency not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537915] Re: libgtk-3-common: Adwaita theme dependency not recognized
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 only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done adwaita-icon-theme is already the newest version (3.18.0-2ubuntu1). Some packages could not be installed. The following information may help to resolve the situation: The following packages have unmet dependencies. adwaita-icon-theme : Depends: libgtk-3-bin but it is not going to be installed E: Unable to correct problems, you have held broken packages. HEH! Now it wants libgtk-3-bin first... Dude, YOU DO KNOW YOUR STUFF! I take my hat off. $ sudo apt-get install libgtk-3-bin=3.18.6-1ubuntu1 THAT fixed it. Still, I think behavior is wrong, because it clearly told about > libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going > to be installed And adwaita...3.18 was working and installed. It didn't mention _anything_ about libgtk-3-bin, until you did that sneaky simulation line. Anyways, it was worth posting here, because I might need that "trick" somewhere else in the future! :) Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537915 Title: libgtk-3-common: Adwaita theme dependency not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537915] Re: libgtk-3-common: Adwaita theme dependency misdetected because of missing libgtk-3-bin
** 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. https://bugs.launchpad.net/bugs/1537915 Title: libgtk-3-common: Adwaita theme dependency misdetected because of missing libgtk-3-bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537915] [NEW] libgtk-3-common: Adwaita theme dependency not recognized
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 information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to upgrade. Need to get 0 B/897 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 307199 files and directories currently installed.) Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ... Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ... Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ... +++ OKAY. Adwaita Icon Theme is now installed and expected to be working. Version = __3.18.0-2__ user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to be installed Recommends: libgtk-3-0 but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. There is clearly something wrong. Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to be sure it is really expected to be there. But it seems to be a bug that libgtk-3-common does not recognize it as there. Plus, --force-depends appears to be unavailable when using the '=' sign for a version-specific downgrade. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to upgrade. Need to get 0 B/897 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 307199 files and directories currently installed.) Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ... Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ... Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ... +++ OKAY. Adwaita Icon Theme is now installed and expected to be - working. Version = 3.18.0-2. + working. Version = __3.18.0-2__ user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. - libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to be installed -Recommends: libgtk-3-0 but it is not going to be installed + libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to be installed + Recommends: libgtk-3-0 but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. There is clearly something wrong. Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to be sure it is really expected to be there. But it seems to be a bug that libgtk-3-common does not recognize it as there. Plus, --force-depends appears to be unavailable when using the '=' sign for a version-specific downgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537915 Title: libgtk-3-common: Adwaita theme dependency not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537895] [NEW] Please include poppler-glib-demo tool in standard package
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 there is nothing like a 'poppler-demos' package, but the whole package structure is different. So this is one more for the wishlist. poppler-glib-demo is not just a demo for developers, but will also show errors that evince may be blamed for (for no reason at all). evince simply uses lots of things under the hood, and one of them is poppler for PDF rendering. ISTR that our Fedora colleagues do have this tool compiled in binary form and included in the package. As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no longer do without it when building the Ubuntu poppler package. Thanks for considering. ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Description changed: 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. This is one more for the wishlist. poppler-glib-demo is not just a demo for developers, but will also show errors that evince may be blamed for (for no reason at all). evince simply uses lots of things under the hood, and one of them is poppler for PDF rendering. ISTR that our Fedora colleagues do have this tool compiled in binary form and included in the package. - As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no longer omit it when building the package. + As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no longer omit it when building the Ubuntu poppler package. Thanks for considering. ** Description changed: 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. This is one more for the wishlist. poppler-glib-demo is not just a demo for developers, but will also show errors that evince may be blamed for (for no reason at all). evince simply uses lots of things under the hood, and one of them is poppler for PDF rendering. ISTR that our Fedora colleagues do have this tool compiled in binary form and included in the package. - As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no longer omit it when building the Ubuntu poppler package. + As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no longer do without it when building the Ubuntu poppler package. Thanks for considering. ** Description changed: 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. - This is one more for the wishlist. + However, this tip was NOT suitable for Ubuntu, as there is nothing like a 'poppler-demos' package, but the whole package structure is different. + So this is one more for the wishlist. poppler-glib-demo is not just a demo for developers, but will also show errors that evince may be blamed for (for no reason at all). evince simply uses lots of things under the hood, and one of them is poppler for PDF rendering. ISTR that our Fedora colleagues do have this tool compiled in binary form and included in the package. As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no longer do without it when building the Ubuntu poppler package. Thanks for considering. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537895 Title: Please include poppler-glib-demo tool in standard package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1537895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
@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. https://bugs.launchpad.net/bugs/1536397 Title: [nForce2] pata_amd pata_acpi can't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
>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 ... 4.2.0-10-generic and it FAILED. Yours is a mere 6 patch levels newer and ... works. This _is_ peculiar. -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
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 ago, Jan 21) -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510364] Re: LXpanel might auto-restart when RMB is pressed and mouse cursor is below or at task pane
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 YET another crash (this tmie in _NET_WM_ICON), so why not kill two birds with one stone? I mean, *if* we point to such version upstream, AND it only involves one main source file, we should take the one with the last successful fix. And this is bd65335... -- 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 RMB is pressed and mouse cursor is below or at task pane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1510364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510364] Re: LXpanel might auto-restart when RMB is pressed and mouse cursor is below or at task pane
--- 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 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 RMB is pressed and mouse cursor is below or at task pane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1510364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510364] Re: LXpanel might auto-restart when RMB is pressed and mouse cursor is below or at task pane
"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 sure I was at the wrong place... 2. The version I compiled is this here: http://git.lxde.org/gitweb/?p=lxde/lxpanel.git;a=summary And again, I can't but agree with you that you MAY have to ask for it because of being unable to find it on your own. Everything is so abysmally documented... I had to google quite a bit until I found that repo I *actually* wanted. The Github repo (https://github.com/lxde) will lead you totally up the garden path, because there will be no lxpanel for you, just lots of lxQt stuff. -- 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 RMB is pressed and mouse cursor is below or at task pane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1510364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510364] [NEW] LXpanel might auto-restart when RMB is pressed and mouse cursor is below task pane
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 running. Task bar must not be empty! - Place mouse pointer over one of the task tabs and press RIGHT mouse button. (expected) * You ought to get the small Raise, Restore, Maximise, Minimise ... popup menu (actual, sometimes) * Instead of displaying the menu, LXpanel might... ** do nothing at all ** or, auto-reset. That is, lxpanel is SILENTLY restarted. It will disapear from desktop, and then reappear, re-initializing itself. In 'top', I can see that task is gracefully (!) ended and restarted. No crash reporter is triggered. /var/crash is empty. If you cannot reproduce the bug, try to click BELOW the task pane, on the very bottom margin of the task tabs. It's strange: sometimes you can reproduce the bug by right-clicking directly on the tab; another time it will only trigger if you click around on the very bottom on the task pane. (Either I am wanting some perception, or this has really never happened in v0.7.2. But I'm not absolutely sure.) ** Affects: lxpanel (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 running. Task bar + - Make sure you have a few task items, i. e. programs running. Task bar must not be empty! - Place mouse pointer over one of the task tabs and press RIGHT mouse button. (expected) * You ought to get the small Raise, Restore, Maximise, Minimise ... popup menu (actual, sometimes) * Instead of displaying the menu, LXpanel might... - ** do nothing at all + ** do nothing at all - ** or, auto-reset. That is, lxpanel is SILENTLY restarted. In 'top', I - can see that task is gracefully (!) ended and restarted. No crash - reporter is triggered. /var/crash is empty. + ** or, auto-reset. That is, lxpanel is SILENTLY restarted. It will + disapear from desktop, and then reappear, re-initializing itself. In + 'top', I can see that task is gracefully (!) ended and restarted. No + crash reporter is triggered. /var/crash is empty. If you cannot reproduce the bug, try to click BELOW the task pane, on the very bottom margin of the task tabs. It's strange;: sometimes you can reproduce the bug by clicking directly on the tab; another time it will only trigger if you click around on the very bottom on the task pane. ** Description changed: 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 running. Task bar must not be empty! - Place mouse pointer over one of the task tabs and press RIGHT mouse button. (expected) * You ought to get the small Raise, Restore, Maximise, Minimise ... popup menu (actual, sometimes) * Instead of displaying the menu, LXpanel might... ** do nothing at all ** or, auto-reset. That is, lxpanel is SILENTLY restarted. It will disapear from desktop, and then reappear, re-initializing itself. In 'top', I can see that task is gracefully (!) ended and restarted. No crash reporter is triggered. /var/crash is empty. If you cannot reproduce the bug, try to click BELOW the task pane, on the very bottom margin of the task tabs. - It's strange;: sometimes you can reproduce the bug by clicking directly on the tab; another time it will only trigger if you click around on the very bottom on the task pane. + It's strange: sometimes you can reproduce the bug by clicking directly on the tab; another time it will only trigger if you click around on the very bottom on the task pane. + + (Either I am wanting some perception, or this has really never happened + in v0.7.2. But I'm not absolutely sure.) ** Description changed: 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 running. Task bar must not be empty! - Place mouse pointer over one of the task tabs and press RIGHT mouse button. (expected) * You ought to get the small Raise, Restore, Maximise, Minimise ... popup menu (actual, sometimes) * Instead of displaying the menu, LXpanel might...
[Bug 1510364] Re: 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 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 below task pane + LXpanel might auto-restart when RMB is pressed and mouse cursor is below or at task pane -- 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 RMB is pressed and mouse cursor is below or at task pane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1510364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510364] Re: LXpanel might auto-restart when RMB is pressed and mouse cursor is below or at task pane
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 RMB is pressed and mouse cursor is below or at task pane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1510364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510364] Re: LXpanel might auto-restart when RMB is pressed and mouse cursor is below task pane
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 0xb66a5b40 (LWP 16643)] [New Thread 0xb5ea4b40 (LWP 16644)] ** Message: x-terminal-emulator has very limited support, consider choose another terminal ** (lxpanel:16639): WARNING **: XDG_TEMPLATES_DIR is set to invalid path, ignoring it [New Thread 0xb3457b40 (LWP 16645)] [New Thread 0xb2c43b40 (LWP 16646)] [Thread 0xb3457b40 (LWP 16645) exited] [New Thread 0xadeb6b40 (LWP 16669)] [New Thread 0xad2ebb40 (LWP 16674)] (lxpanel:16639): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE Program received signal SIGSEGV, Segmentation fault. 0x80010433 in taskbar_task_control_event (widget=0x8015c928, tk=0x8018b8e8, popup_menu=, event=, event=) at launchtaskbar.c:2574 2574launchtaskbar.c: No such file or directory. (gdb) bt full #0 0x80010433 in taskbar_task_control_event (widget=0x8015c928, tk=0x8018b8e8, popup_menu=, event=, event=) at launchtaskbar.c:2574 items = 0x8013a6a0 item = 0x0 i = 1 ltbp = visible_task = 0x8018b8e8 tb = 0x8016c7e8 tc = #1 0xb7a8f22b in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #2 0xb752eb8b in g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #3 0xb7540ffc in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #4 0xb754988c in g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #5 0xb7549fc5 in g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #6 0xb7baf1f4 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #7 0xb7a8d5c9 in gtk_propagate_event () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #8 0xb7a8da1d in gtk_main_do_event () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #9 0xb78fffb9 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 No symbol table info available. #10 0xb7435ce9 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 No symbol table info available. #11 0xb7435f89 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 No symbol table info available. ---Type to continue, or q to quit--- #12 0xb7436339 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 No symbol table info available. #13 0xb7a8c7a5 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #14 0x800098e5 in main (argc=5, argv=0xb024, env=0xb03c) at main.c:485 i = desktop_name = This is MUCH more like it now. -- 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 RMB is pressed and mouse cursor is below or at task pane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1510364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
^^ 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 after login and logout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
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 logout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504078] Re: [4.2.0-15.18] broken sound: 'output devices' not detected
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369273] Re: gnucash crashed with ImportError in /usr/share/gnucash/python/init.py: No module named gnucash
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. -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1369273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434986] Re: Not working network connection after boot
...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: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489154] Re: NetworkManager does not start / fails to start
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 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 go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1489154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.
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. https://bugs.launchpad.net/bugs/1263540 Title: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1263540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.
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. https://bugs.launchpad.net/bugs/1263540 Title: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1263540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.
(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 use the 'del' option in apt-key. I can't believe that so many people have problems with this, and all that developers are (usually) raving about is whether Ubuntu should be verbose to the user about global hotkey assignments or not. Securtity paranoiacs, most of them, but if it comes to such basic-security issue as here, they just go 'shrug, works for me, you're just too daft'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263540 Title: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1263540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489154] Re: NetworkManager does not start / fails to start
>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. Most users will just go the all-in-one upgrade way by 'apt-get upgrade' and hence would not be able to fine-tune settings as in the APT line I've quoted from you above. What you've suggested must be executed BEFORE even THINKING about using apt-get upgrade. Because then, the network-manager including its dependencies will already have been crossed out from the list. -- 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 go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1489154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489154] Re: NetworkManager does not start / fails to start
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 go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1489154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489154] Re: NetworkManager does not start / fails to start
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 problem: Reading symbols from /usr/sbin/NetworkManager...(no debugging symbols found)...done. [New LWP 1745] [New LWP 1746] [New LWP 1747] [New LWP 1748] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Core was generated by `NetworkManager'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb6f4961a in g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 -- g_variant_iter_loop() It's an iterator mechanism: https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-iter-loop Possibly one pointer is NULL or the new NM build will only work with a bleeding-edge, devel version of glib (I assume it's the latter). -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1489154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434986] Re: Not working network connection after boot
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 file which indicated that NM had crashed way before it got to the graphical login screen. Downgraded NM and everything worked as expected. -- 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: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489154] Re: NetworkManager does not start / fails to start
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 g_variant_builder_init (builder,
G_VARIANT_TYPE_VARDICT);
287 g_variant_iter_init (iter, options);
288 while (g_variant_iter_loop (iter, {sv}, key,
value))
289 {
290 // FIXME: verify options here?
291 g_variant_builder_add (builder, {sv}, key,
value);
292 }
293 variant = g_variant_builder_end (builder);
294 }
...
}
Heh...
// FIXME: verify options here?
Yes, that would be a good idea. Otherwise things like these here may
happen. :-]
--
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 go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1489154/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484289] [NEW] hdparm 9.43 - 9.45+ update request
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 much behind with hdparm, quasi-stuck at 9.43 for more than 2 years. This is a bit much. If you'd like to know why it may be sensible to update, here's an example: https://sourceforge.net/p/hdparm/bugs/51/ --read-sector is byte-swapped in every version = 9.43. Mark fixed this in 9.45+. unfortunately you guys were asleep with both eyes open and still haven't considered a tool update for 2 + years :) ** Affects: hdparm (Ubuntu) Importance: Undecided Status: New ** Affects: hdparm (Debian) Importance: Undecided Status: New ** Also affects: hdparm (Debian) 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/1484289 Title: hdparm 9.43 - 9.45+ update request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1484289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304128] Re: Both light-locker and xscreensaver enabled after upgrade
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304128 Title: Both light-locker and xscreensaver enabled after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1304128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1468529] Re: lxappearance segmentation fault
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1468529 Title: lxappearance segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxappearance/+bug/1468529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363430] Re: [mesa] firefox: intel_do_flush_locked failed: Invalid argument
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 to work again. Every time. Not even when purging the whole mozilla cache, firefox will ever recover from that issue again until the machine is rebooted. That's simply unbelievable. :-@ @Chris Unfortunately you've shot a little too quick! I am on an older Athlon XP machine here, and there is nothing with intel inside! (thank goodness). Nvidia VGA inserted. However, I must add that everything posted in the OP about error messages in MessageChannel.cpp is true BUT the intel_do_flush_locked failed line which I'm (obviously) lacking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363430 Title: [mesa] firefox: intel_do_flush_locked failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1363430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172937] Re: SQUASHFS error while booting from live cd
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 start, xterm or so, it will always give the error message that Bump has reported as well: [ xxx.yy] SQUASHFS error: zlib_inflate error, data probably corrupt My CD *is* perfectly clean and well-burned. Because it works for 24 hours. Hence, I don't believe the bad hardware fairy-tale at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/172937 Title: SQUASHFS error while booting from live cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469276] Re: lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxappearance/+bug/1469276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469276] Re: lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
** 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 0.6.1-1 works perfectly with 0.2.2-1 here on Wily. + + (Using Openbox 3.5.2-8.) However lxappearance 0.6.1-1 with plugin version 0.2.2-2 makes it crash! So if you can reproduce the crash, LEAVE lxappearance at its latest version and only do a minimal downgrade of lxappearance-obconf! It's the plugin that literally forces lxappearance main program into the segfault abyss. gdb ... Reading symbols from lxappearance...(no debugging symbols found)...done. (gdb) handle SIG33 pass nostop noprint SignalStop Print Pass to program Description SIG33 NoNo Yes Real-time event 33 (gdb) run - Starting program: /usr/bin/lxappearance + Starting program: /usr/bin/lxappearance [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0xb6927f65 in preview_theme () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so (gdb) bt full #0 0xb6927f65 in preview_theme () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #1 0xb692878e in preview_update_all () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #2 0xb6928f71 in theme_load_all () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #3 0xb6926b78 in plugin_load () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #4 0x0804f270 in plugins_init () No symbol table info available. #5 0x0804ba78 in main () No symbol table info available. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxappearance/+bug/1469276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469276] Re: lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxappearance-obconf/+bug/1469276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469276] Re: lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxappearance/+bug/1469276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469276] [NEW] lxappearance-obconf plugin causes lxappearance 0.6.1.-1 to segfault
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 0.2.2-2 makes it crash! So if you can reproduce the crash, LEAVE lxappearance at its latest version and only do a minimal downgrade of lxappearance-obconf! It's the plugin that literally forces lxappearance main program into the segfault abyss. gdb ... Reading symbols from lxappearance...(no debugging symbols found)...done. (gdb) handle SIG33 pass nostop noprint SignalStop Print Pass to program Description SIG33 NoNo Yes Real-time event 33 (gdb) run Starting program: /usr/bin/lxappearance [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0xb6927f65 in preview_theme () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so (gdb) bt full #0 0xb6927f65 in preview_theme () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #1 0xb692878e in preview_update_all () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #2 0xb6928f71 in theme_load_all () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #3 0xb6926b78 in plugin_load () from /usr/lib/i386-linux-gnu/lxappearance/plugins/obconf.so No symbol table info available. #4 0x0804f270 in plugins_init () No symbol table info available. #5 0x0804ba78 in main () No symbol table info available. ** Affects: lxappearance-obconf (Ubuntu) Importance: Undecided Status: New ** Tags: crash lxappearance obconf plugin -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxappearance-obconf/+bug/1469276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469276] Re: lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
** 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. https://bugs.launchpad.net/bugs/1469276 Title: lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxappearance-obconf/+bug/1469276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: lubuntu dark panel does not apply a dark panel without logout
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460192 Title: lubuntu dark panel does not apply a dark panel without logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430593] Re: package khelpcenter (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/th/LC_MESSAGES/kcmhtmlsearch.mo', which is also in package kde-l10n-th 4:4.10.97
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 something seriously broken here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430593 Title: package khelpcenter (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/th/LC_MESSAGES/kcmhtmlsearch.mo', which is also in package kde-l10n-th 4:4.10.97-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/khelpcenter/+bug/1430593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376051] Re: gpartedbin crashed with SIGABRT in g_assertion_message()
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 : https://git.gnome.org/browse/glibmm/commit/?id=10e24926a149c8dbfbc5853b2d4ff5a4cd50bc4b Unfortunately, nobody has ever thought about pushing 2.44 to the standard 'Buntu repos so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376051 Title: gpartedbin crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1376051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437070] Re: chromium-browser crashes with SIGILL if CPU does not support SSE2
** 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, there was nowhere a *requirement* listed that 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 chromium v41 to demonstrate this fact. These are the most evident 2 lines: # # Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82 # CHECK(cpu.has_sse2()) failed # - Looks to me that the _asm routines _blindly_ assume that the CPU is capable of SSE2 instruction set. - At least the browser should exit more gracefully if this is the case, but not crash with a SIGILL. + Looks to me that the more recent _asm routines now _blindly_ assume that the CPU is capable of SSE2 instruction set. + If you really DO want to lock us out (I think we still are millions of users worldwide with Athlon XP machines), we can't stop you. + But at least the browser should exit more gracefully if this is the case, but not crash with a SIGILL. ** Description changed: My CPU does not support SSE2, this is a fact. And as far as I knew (unless I missed something) for the use of Chromium on Linux, there was nowhere a *requirement* listed that 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 chromium v41 to demonstrate this fact. These are the most evident 2 lines: # # Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82 # CHECK(cpu.has_sse2()) failed # Looks to me that the more recent _asm routines now _blindly_ assume that the CPU is capable of SSE2 instruction set. - If you really DO want to lock us out (I think we still are millions of users worldwide with Athlon XP machines), we can't stop you. + If you really CAN'T help the cool feeling of locking us out (I think we still are millions of users worldwide with Athlon XP machines), we can't stop you. But at least the browser should exit more gracefully if this is the case, but not crash with a SIGILL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437070 Title: chromium-browser crashes with SIGILL if CPU does not support SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1437070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437070] [NEW] chromium-browser crashes with SIGILL if CPU does not support SSE2
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 chromium v41 to demonstrate this fact. These are the most evident 2 lines: # # Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82 # CHECK(cpu.has_sse2()) failed # Looks to me that the _asm routines _blindly_ assume that the CPU is capable of SSE2 instruction set. At least the browser should exit more gracefully if this is the case, but not crash with a SIGILL. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: assembler chromium cpu crash sse2 ** Attachment added: gdb_chromium.txt https://bugs.launchpad.net/bugs/1437070/+attachment/4357436/+files/gdb_chromium.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437070 Title: chromium-browser crashes with SIGILL if CPU does not support SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1437070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] Re: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel
** 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. https://bugs.launchpad.net/bugs/1431414 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] [NEW] For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel
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 - Type menu:// into the address bar in PCManFm (You will end up in menu://applications/ .) - Visit a folder, e. g. Internet. - Click RIGHT mouse button, and say Open With - Create Launcher on the panel. Result: It does not work. It complains about no running instance of xfce4-panel found. Well, what we use is lxpanel, not xfce4-panel. These are two entirely different pairs of socks, or more exactly: they're even mutually exclusive. AFAIK you cannot (nor should) run them simultaneously. ** Affects: pcmanfm (Ubuntu) Importance: Undecided Status: New ** Tags: desktop link lxde lxpanel xfce4-panel ** 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. Reproduction: - Preferably use LXDE/Openbox (which is the default on Lubuntu here) - Launch PCManFM - Type menu:// into the address bar in PCManFm (You will end up in menu://applications/ .) - Visit a folder, e. g. Internet. - Click RIGHT mouse button, and say Open With - Create Launcher on the panel. Result: It does not work. It complains about no running instance of xfce4-panel found. Well, what we use is lxpanel, not xfce4-panel. These are two entirely - different pairs of socks. + different pairs of socks, or more exactly: they're even mutually + exclusive. AFAIK you cannot (nor should) run them simultaneously. ** Summary changed: - PcManFM should not rely on xfce4-panel for creating launchers + For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel ** Tags added: lxde -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431414 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] RelatedPackageVersions.txt
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. https://bugs.launchpad.net/bugs/1431414 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] Re: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431414 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] Re: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431414 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] Dependencies.txt
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 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] ProcEnviron.txt
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 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] Re: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel
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. Reproduction: - Preferably use LXDE/Openbox (which is the default on Lubuntu here) - Launch PCManFM - Type menu:// into the address bar in PCManFm (You will end up in menu://applications/ .) - Visit a folder, e. g. Internet. - Click RIGHT mouse button, and say Open With - Create Launcher on the panel. Result: It does not work. It complains about no running instance of xfce4-panel found. - Well, what we use is lxpanel, not xfce4-panel. These are two entirely - different pairs of socks, or more exactly: they're even mutually - exclusive. AFAIK you cannot (nor should) run them simultaneously. + Well, what we use is lxpanel, not xfce4-panel. These are two entirely different pairs of socks, or more exactly: they're even mutually exclusive. AFAIK you cannot (nor should) run them simultaneously. + --- + ApportVersion: 2.16.2-0ubuntu2 + Architecture: i386 + Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf' + CurrentDesktop: LXDE + DistroRelease: Ubuntu 15.04 + Package: pcmanfm 1.2.3-1.1 + PackageArchitecture: i386 + ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 + Tags: vivid gnome3-ppa third-party-packages + Uname: Linux 3.18.0-9-generic i686 + UpgradeStatus: Upgraded to vivid on 2014-12-30 (71 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: Config_libfm_Home_Lubuntu.txt https://bugs.launchpad.net/bugs/1431414/+attachment/4343040/+files/Config_libfm_Home_Lubuntu.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 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431414] Udisks_dump.txt
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431414 Title: For creating launchers, PcManFM relies on xfce4-panel, while LXDE uses lxpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1431414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424362] Re: no permissions to install packages in vivid daily lubuntu beta 1
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424362 Title: no permissions to install packages in vivid daily lubuntu beta 1 To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-software-center/+bug/1424362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369273] Re: gnucash crashed with ImportError in /usr/share/gnucash/python/init.py: No module named gnucash
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1369273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369273] Re: gnucash crashed with ImportError in /usr/share/gnucash/python/init.py: No module named gnucash
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 /usr/share/gnucash/python/init.py: No module named gnucash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1369273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297624] Re: pcmanfm crashed with SIGSEGV in fm_mime_type_ref()
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 Status: Unknown -- 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: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1297624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297624] Re: pcmanfm crashed with SIGSEGV in fm_mime_type_ref()
** 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: https://bugs.launchpad.net/ubuntu/+bug/1297624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415648] Re: pcmanfm crashed with SIGSEGV in fm_mime_type_ref()
*** 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 crashed with SIGSEGV in fm_mime_type_ref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1415648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297624] Re: pcmanfm crashed with SIGSEGV in fm_mime_type_ref()
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 to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1297624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358486] Re: pcmanfm crashed with SIGSEGV in fm_mime_type_ref()
*** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358486 Title: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1358486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420998] Re: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() (bug in libfm core)
*** 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 into! Plus, had I known before that all my internal info (incl. disassembly) would be GONE when the bug is set as duplicate, I would have linked it externally in the first place!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420998 Title: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() (bug in libfm core) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfm/+bug/1420998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420998] [NEW] pcmanfm crashed with SIGSEGV in fm_mime_type_ref() (bug in libfm core)
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 found. (/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf) Current only two VALID paths are: /etc/xdg/pcmanfm/lubuntu/pcmanfm.conf /etc/xdg/pcmanfm/default/pcmanfm.conf Hopefully this report will give some deeper insight what was responsible for 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 ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf' CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Feb 11 23:15:18 2015 ExecutablePath: /usr/bin/pcmanfm ProcCmdline: pcmanfm --desktop --profile lubuntu SegvAnalysis: Segfault happened at: 0xb6d74de4 fm_mime_type_ref+4: lock addl $0x1,0x10(%eax) PC (0xb6d74de4) ok source $0x1 ok destination 0x10(%eax) (0x0010) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: pcmanfm StacktraceTop: fm_mime_type_ref () from /usr/lib/i386-linux-gnu/libfm.so.4 ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 Title: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() UpgradeStatus: Upgraded to vivid on 2014-12-30 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: libfm (Ubuntu) Importance: Undecided Status: New ** Affects: fedora Importance: Unknown Status: Unknown ** Tags: apport-crash gnome3-ppa i386 need-i386-retrace third-party-packages vivid ** Attachment removed: Udisks_dump.txt https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1420998/+attachment/4317526/+files/Udisks_dump.txt ** Package changed: pcmanfm (Ubuntu) = libfm (Ubuntu) ** Information type changed from Private to Public ** Description changed: 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 found. (xdg... path) + BTW, please also note that the configuration file in Lubuntu is not found. (/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf) + + Current only two VALID paths are: + + /etc/xdg/pcmanfm/lubuntu/pcmanfm.conf + + /etc/xdg/pcmanfm/default/pcmanfm.conf Hopefully this report will give some deeper insight what was responsible for 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 ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf' CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Feb 11 23:15:18 2015 ExecutablePath: /usr/bin/pcmanfm ProcCmdline: pcmanfm --desktop --profile lubuntu SegvAnalysis: - Segfault happened at: 0xb6d74de4 fm_mime_type_ref+4: lock addl $0x1,0x10(%eax) - PC (0xb6d74de4) ok - source $0x1 ok - destination 0x10(%eax) (0x0010) not located in a known VMA region (needed writable region)! + Segfault happened at: 0xb6d74de4 fm_mime_type_ref+4: lock addl $0x1,0x10(%eax) + PC (0xb6d74de4) ok + source $0x1 ok + destination 0x10(%eax) (0x0010) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: pcmanfm StacktraceTop: - fm_mime_type_ref () from /usr/lib/i386-linux-gnu/libfm.so.4 - ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 - ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 - ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 - ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 + fm_mime_type_ref () from /usr/lib/i386-linux-gnu/libfm.so.4 + ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 + ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 + ?? () from /usr/lib/i386-linux-gnu/libfm.so.4 + ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 Title: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() UpgradeStatus: Upgraded to vivid on 2014-12-30 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420998 Title: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() (bug in libfm core) To manage notifications about
[Bug 1420998] Re: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() (bug in libfm core)
*** 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: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420998 Title: pcmanfm crashed with SIGSEGV in fm_mime_type_ref() (bug in libfm core) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfm/+bug/1420998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419338] [NEW] pcmanfm crashed with SIGSEGV in pango_attr_list_unref()
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 ApportVersion: 2.16-0ubuntu1 Architecture: i386 Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf' CrashCounter: 1 CurrentDesktop: LXDE Date: Sat Feb 7 21:00:00 2015 Disassembly: = 0xd948c0b6: Cannot access memory at address 0xd948c0b6 ExecutablePath: /usr/bin/pcmanfm ProcCmdline: pcmanfm --desktop --profile lubuntu SegvAnalysis: Segfault happened at: 0xd948c0b6: Cannot access memory at address 0xd948c0b6 PC (0xd948c0b6) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: pcmanfm StacktraceTop: ?? () pango_attr_list_unref () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: pcmanfm crashed with SIGSEGV in pango_attr_list_unref() UpgradeStatus: Upgraded to vivid on 2014-12-30 (39 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: pcmanfm (Ubuntu) Importance: Medium Status: New ** Tags: apport-crash gnome3-ppa i386 third-party-packages vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419338 Title: pcmanfm crashed with SIGSEGV in pango_attr_list_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1419338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
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 root root 17780 Jan 18 09:03 dummy_drv_video.so -rw-r--r-- 5 root root 6214508 Jan 29 18:22 i915_dri.so -rw-r--r-- 5 root root 6214508 Jan 29 18:22 i965_dri.so -rw-r--r-- 1 root root 1779560 Jan 27 21:57 i965_drv_video.so -rw-r--r-- 7 root root 8729848 Jan 29 18:22 kms_swrast_dri.so -rw-r--r-- 7 root root 8729848 Jan 29 18:22 nouveau_dri.so lrwxrwxrwx 1 root root 18 Aug 8 01:22 nouveau_drv_video.so - vdpau_drv_video.so -rw-r--r-- 5 root root 6214508 Jan 29 18:22 nouveau_vieux_dri.so lrwxrwxrwx 1 root root 18 Aug 8 01:22 nvidia_drv_video.so - vdpau_drv_video.so ~$ vdpauinfo display: :0.0 screen: 0 [VS] Software VDPAU backend library initialized libva info: VA-API version 0.37.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nouveau_vieux_drv_video.so libva info: va_openDriver() returns -1 [VS] error (compile_shaders): compilation of shader #0 failed with '' [VS] error (vdpDeviceCreateX11): gl error 1280 Error creating VDPAU device: 25 OK, shared object file simply ISN'T THERE. So why not do this? ~$ sudo ln -s vdpau_drv_video.so nouveau_vieux_drv_video.so vdpauinfo display: :0.0 screen: 0 [VS] Software VDPAU backend library initialized libva info: VA-API version 0.37.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nouveau_vieux_drv_video.so libva info: Found init function __vaDriverInit_0_35 STALLED vdpauinfo is stuck after it found the init function Something is seriously broken here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300215 Title: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393067] Re: totem 3.14
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 bug.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393067 Title: totem 3.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1393067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376051] Re: gpartedbin crashed with SIGABRT in g_assertion_message()
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 ubuntuupdates.org to get the 0.19.1 release, which works great, but is virtually unavailable elsewhere. The same I can also recommend to you desperate users, for the waiting is really a little bit too long now. How long are we still supposed to wait? Spring 2015 ?? This has nothing to do with impatience; the bug described in #1376051 is *SO* critical that I have to revert to 0.18.x otherwise. PPA sometimes feels like a home for the elderly recently, needing dozens of nudges to get things going there... Plus, a lot of those PPAs you'd find there are already available in the *standard* distros. However, people would usually move over to PPA to find packages *NOT YET* in distros. When one finds greatly the very same stuff in there again, there is no point of having a PPA to your disposal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376051 Title: gpartedbin crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1376051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376051] Re: gpartedbin crashed with SIGABRT in g_assertion_message()
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 x.yy.z-p-ubuntuQ naming ought to be used for releases that are in the *standard* distribution, and not the PPA. It is always way better to indicate certain builds of packages coming from a PPA by using an appropriate filename (at least not the above one, that's for sure). So JFTR, at the moment, 0.19.0-1build1 is the (non-working, crap) version shipped with Utopic, whilst 0.19.0-1ubuntu1 is the (working) PPA version. Just to get this clear for further readers running into this extremely time-consuming problem. BTW sorry for the rude tone, but I've really wasted way too much pointless time with this stuff now, and that---may I quote the description---so-called minor regression. I'd burst out laughing, if it wasn't so pathetic...? That oh-so minor regression will be enough for me for months again... Mind you all of you, essential tools with little bugs and essential tools that do not run at all is not quite the same thing... Lastly: YES 0.19.0-1ubuntu1 is the first version that works again since 0.18.x. Good Lord...don't get me started about the QA here therefore... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376051 Title: gpartedbin crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1376051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
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 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
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 while... must come from the kernel itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1364630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
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 is fed into it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1364630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384416] Re: coreutils 'info command' broken
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. https://bugs.launchpad.net/bugs/1384416 Title: coreutils 'info command' broken To manage notifications about this bug go to: https://bugs.launchpad.net/coreutils/+bug/1384416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376051] Re: gpartedbin crashed with SIGABRT in g_assertion_message()
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376051 Title: gpartedbin crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1376051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376051] Re: gpartedbin crashed with SIGABRT in g_assertion_message()
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376051 Title: gpartedbin crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1376051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
