[Bug 288797] Re: [Intrepid] Synaptic unusable - Can not find packages
On an upgrade from Hardy to Jaunty (via Intrepid) I found out that package apt-xapian-index was not installed. Installing it solved this problem for me. After installing it, an indexing task started automatically, which progress is shown by issuing: sudo update-apt-xapian-index. Upon completion of the indexing, the quick search in Synaptic became usable -- [Intrepid] Synaptic unusable - Can not find packages https://bugs.launchpad.net/bugs/288797 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372340] [NEW] distro upgrade doesn't utilise CD source
Public bug reported: Binary package hint: update-manager Attempting to upgrade from 8.10 to 9.04 using the Alternate ISO image which is loop-mounted fails. Mounting the ISO image at /media/cdrom0 as described in the [[http://www.ubuntu.com/getubuntu/upgrading|upgrade guide]] or even at /media/cdrom directly doesn't cause the software sources manager to recognise the volume as containing packages, After manually launching sudo sh /media/cdrom/cdromupgrade the upgrading is initiated; the mount point is added to the sources in the "third party" tab as cdrom: and other sources are modified respectively. However the mounted ISO source is not recognised properly in the software sources manager section titled "Installable from CD-ROM/DVD, and attempting to add it manually using "Add CD-ROM" fails. When prompted to specify whether I want to include updates from the Internet, choosing "No" doesn't seem to have any effect; the upgrader still does fetch packages from the Internet, and unplugging the network causes the fetching to fail. It seems that the cdrom:/ source, although present, isn't used at all. I faced this problem yesterday when updating from 8.04 to 8.10, I've seen reports for this bug, but the posters end up burning the iso to a CD-ROM or upgrading through the network. [e.g: http://ubuntuforums.org/archive/index.php/t-640626.html] I've also seen related bug reports, but not the same: #294057, #222319, and #155833 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- distro upgrade doesn't utilise CD source https://bugs.launchpad.net/bugs/372340 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372340] Re: distro upgrade doesn't utilise CD source
** Description changed: Binary package hint: update-manager Attempting to upgrade from 8.10 to 9.04 using the Alternate ISO image which is loop-mounted fails. - Mounting the ISO image at /media/cdrom0 as described in the - [[http://www.ubuntu.com/getubuntu/upgrading|upgrade guide]] or even at - /media/cdrom directly doesn't cause the software sources manager to - recognise the volume as containing packages, + Mounting the ISO image at /media/cdrom0 as described in the http://www.ubuntu.com/getubuntu/upgrading";>upgrade guide or + even at /media/cdrom directly doesn't cause the software sources manager + to recognise the volume as containing packages, After manually launching sudo sh /media/cdrom/cdromupgrade the upgrading is initiated; the mount point is added to the sources in the "third party" tab as cdrom: and other sources are modified respectively. However the mounted ISO source is not recognised properly in the software sources manager section titled "Installable from CD-ROM/DVD, and attempting to add it manually using "Add CD-ROM" fails. When prompted to specify whether I want to include updates from the Internet, choosing "No" doesn't seem to have any effect; the upgrader still does fetch packages from the Internet, and unplugging the network causes the fetching to fail. It seems that the cdrom:/ source, although present, isn't used at all. - I faced this problem yesterday when updating from 8.04 to 8.10, + I faced this problem earlier when updating the same system from 8.04 to + 8.10, I've seen reports for this bug, but the posters end up burning the iso to a CD-ROM or upgrading through the network. [e.g: http://ubuntuforums.org/archive/index.php/t-640626.html] I've also seen related bug reports, but not the same: #294057, #222319, and #155833 -- distro upgrade doesn't utilise CD source https://bugs.launchpad.net/bugs/372340 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373016] [NEW] Network Manager, device not managed
Public bug reported: Binary package hint: network-manager I'm using a wired network. After upgrading to Intrepid from Hardy, I noticed that the Network Manager had a little red x mark on it indicating that it was not detecting a network, and the "Wired" tab didn't list any connections. However the network was working normally, so I ignored it temporarily concentrating on continuing the upgrade to Jaunty and hoping that it will be solved then. After upgrading to Jaunty the issue persisted; similar to what's described at http://ubuntuforums.org/showthread.php?t=1109585 Likewise, changing "false" [ifupdown] managed=false in /etc/NetworkManager/nm-system-settings.conf to "true" solved the problem and the connection is detected in NM. However output of lspci | grep Ethernet is: 00:0c.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) and output of sudo lshw -C network is: *-network description: Ethernet interface product: VT6105/VT6106S [Rhine-III] vendor: VIA Technologies, Inc. physical id: c bus info: p...@:00:0c.0 logical name: eth0 version: 86 serial: 00:0f:3d:ca:d8:a1 size: 100MB/s capacity: 100MB/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full ip=192.168.42.43 latency=64 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s when in fact my NIC is D-Link DFE-530TX PCI Fast Ethernet Adapter and was being detected as such in Hardy This maybe related: https://bugs.launchpad.net/ubuntu/intrepid/+source /network-manager/+bug/327053 may be related ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373016 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373015] [NEW] Network Manager, device not managed
Public bug reported: Binary package hint: network-manager I'm using a wired network. After upgrading to Intrepid from Hardy, I noticed that the Network Manager had a little red x mark on it indicating that it was not detecting a network, and the "Wired" tab didn't list any connections. However the network was working normally, so I ignored it temporarily concentrating on continuing the upgrade to Jaunty and hoping that it will be solved then. After upgrading to Jaunty the issue persisted; similar to what's described at http://ubuntuforums.org/showthread.php?t=1109585 Likewise, changing "false" [ifupdown] managed=false in /etc/NetworkManager/nm-system-settings.conf to "true" solved the problem and the connection is detected in NM. However output of lspci | grep Ethernet is: 00:0c.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) and output of sudo lshw -C network is: *-network description: Ethernet interface product: VT6105/VT6106S [Rhine-III] vendor: VIA Technologies, Inc. physical id: c bus info: p...@:00:0c.0 logical name: eth0 version: 86 serial: 00:0f:3d:ca:d8:a1 size: 100MB/s capacity: 100MB/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full ip=192.168.42.43 latency=64 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s when in fact my NIC is D-Link DFE-530TX PCI Fast Ethernet Adapter and was being detected as such in Hardy This maybe related: https://bugs.launchpad.net/ubuntu/intrepid/+source /network-manager/+bug/327053 may be related ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373015 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373014] [NEW] Network Manager, device not managed
Public bug reported: Binary package hint: network-manager I'm using a wired network. After upgrading to Intrepid from Hardy, I noticed that the Network Manager had a little red x mark on it indicating that it was not detecting a network, and the "Wired" tab didn't list any connections. However the network was working normally, so I ignored it temporarily concentrating on continuing the upgrade to Jaunty and hoping that it will be solved then. After upgrading to Jaunty the issue persisted; similar to what's described at http://ubuntuforums.org/showthread.php?t=1109585 Like what is described in the above thread, changing "false" in [ifupdown] managed=false in /etc/NetworkManager/nm-system-settings.conf to "true" solved it and the connection is detected in NM. However output of lspci | grep Ethernet is: 00:0c.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) and output of sudo lshw -C network is: *-network description: Ethernet interface product: VT6105/VT6106S [Rhine-III] vendor: VIA Technologies, Inc. physical id: c bus info: p...@:00:0c.0 logical name: eth0 version: 86 serial: 00:0f:3d:ca:d8:a1 size: 100MB/s capacity: 100MB/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full ip=192.168.42.43 latency=64 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s when in fact my NIC is D-Link DFE-530TX PCI Fast Ethernet Adapter and was being detected as such in Hardy; i.e. before the upgrade to Intrepid. This maybe related: https://bugs.launchpad.net/ubuntu/intrepid/+source /network-manager/+bug/327053 may be related ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373013] [NEW] Network Manager, device not managed
Public bug reported: Binary package hint: network-manager I'm using a wired network. After upgrading to Intrepid from Hardy, I noticed that the Network Manager had a little red x mark on it indicating that it was not detecting a network, and the "Wired" tab didn't list any connections. However the network was working normally, so I ignored it temporarily concentrating on continuing the upgrade to Jaunty and hoping that it will be solved then. After upgrading to Jaunty the issue persisted; similar to what's described at http://ubuntuforums.org/showthread.php?t=1109585 Like what is described in the above thread, changing "false" in [ifupdown] managed=false in /etc/NetworkManager/nm-system-settings.conf to "true" solved it and the connection is detected in NM. However output of lspci | grep Ethernet is: 00:0c.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) and output of sudo lshw -C network is: *-network description: Ethernet interface product: VT6105/VT6106S [Rhine-III] vendor: VIA Technologies, Inc. physical id: c bus info: p...@:00:0c.0 logical name: eth0 version: 86 serial: 00:0f:3d:ca:d8:a1 size: 100MB/s capacity: 100MB/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full ip=192.168.42.43 latency=64 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s when in fact my NIC is D-Link DFE-530TX PCI Fast Ethernet Adapter and was being detected as such in Hardy; i.e. before the upgrade to Intrepid. This maybe related: https://bugs.launchpad.net/ubuntu/intrepid/+source /network-manager/+bug/327053 may be related ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373013 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373041] [NEW] Network Manager, device not managed
Public bug reported: Binary package hint: network-manager Binary package hint: network-manager I'm using a wired network. After upgrading to Intrepid from Hardy, I noticed that the Network Manager had a little red x mark on it indicating that it was not detecting a network, and the "Wired" tab didn't list any connections. However the network was working normally, so I ignored it temporarily concentrating on continuing the upgrade to Jaunty and hoping that it will be solved then. After upgrading to Jaunty the issue persisted; similar to what's described at http://ubuntuforums.org/showthread.php?t=1109585 Like what is described in the above thread, changing "false" in [ifupdown] managed=false in /etc/NetworkManager/nm-system-settings.conf to "true" solved it and the connection is detected in NM. However output of lspci | grep Ethernet is: 00:0c.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) and output of sudo lshw -C network is: *-network description: Ethernet interface product: VT6105/VT6106S [Rhine-III] vendor: VIA Technologies, Inc. physical id: c bus info: p...@:00:0c.0 logical name: eth0 version: 86 serial: 00:0f:3d:ca:d8:a1 size: 100MB/s capacity: 100MB/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full ip=192.168.42.43 latency=64 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s when in fact my NIC is D-Link DFE-530TX PCI Fast Ethernet Adapter and was being detected as such in Hardy; i.e. before the upgrade to Intrepid. This maybe related: https://bugs.launchpad.net/ubuntu/intrepid/+source /network-manager/+bug/327053 may be related ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Gconf: NonfreeKernelModules: nvidia Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager Uname: Linux 2.6.28-11-generic i686 WpaSupplicantLog: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373041 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373041] Re: Network Manager, device not managed
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/26416072/Dependencies.txt ** Attachment added: "IfupdownConfig.txt" http://launchpadlibrarian.net/26416073/IfupdownConfig.txt ** Attachment added: "NetDevice.eth0.txt" http://launchpadlibrarian.net/26416074/NetDevice.eth0.txt ** Attachment added: "NetDevice.lo.txt" http://launchpadlibrarian.net/26416075/NetDevice.lo.txt ** Attachment added: "Syslog.txt" http://launchpadlibrarian.net/26416076/Syslog.txt -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373041 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373016] Re: Network Manager, device not managed
*** This bug is a duplicate of bug 373041 *** https://bugs.launchpad.net/bugs/373041 ** This bug is no longer a duplicate of bug 373013 Network Manager, device not managed ** This bug has been marked a duplicate of bug 373041 Network Manager, device not managed -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373016 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373015] Re: Network Manager, device not managed
*** This bug is a duplicate of bug 373041 *** https://bugs.launchpad.net/bugs/373041 ** This bug is no longer a duplicate of bug 373013 Network Manager, device not managed ** This bug has been marked a duplicate of bug 373041 Network Manager, device not managed -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373015 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373013] Re: Network Manager, device not managed
*** This bug is a duplicate of bug 373041 *** https://bugs.launchpad.net/bugs/373041 ** This bug has been marked a duplicate of bug 373041 Network Manager, device not managed -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373013 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373014] Re: Network Manager, device not managed
*** This bug is a duplicate of bug 373041 *** https://bugs.launchpad.net/bugs/373041 ** This bug is no longer a duplicate of bug 373013 Network Manager, device not managed ** This bug has been marked a duplicate of bug 373041 Network Manager, device not managed -- Network Manager, device not managed https://bugs.launchpad.net/bugs/373014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 269379] Re: arabic translations cause a crash
gettext benefited from tightening the code, but there's still a string messed up somewhere in the Arabic translation. On Mon, Sep 15, 2008 at 2:18 PM, Jad Madi <[EMAIL PROTECTED]> wrote: > So it was a gettext related issue not a translation string issue? -- arabic translations cause a crash https://bugs.launchpad.net/bugs/269379 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352046] Re: Notebook remix unusable on EEE PC 900 because the menu is too slow
*** This bug is a duplicate of bug 349314 *** https://bugs.launchpad.net/bugs/349314 I'm confirming on 701 as well -- Notebook remix unusable on EEE PC 900 because the menu is too slow https://bugs.launchpad.net/bugs/352046 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408417] Re: No option to log in remotely via XDMCP
I require this functionality as well. -- No option to log in remotely via XDMCP https://bugs.launchpad.net/bugs/408417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589934] [NEW] dependency review
Public bug reported: Binary package hint: virtualbox-ose-fuse Why does this package have to depend on virtualbox-ose ? Removing this dependency, should enable using vdfuse with VirtualBox 3.2 (the non-free version of VirtualBox), if the suer chooses to. ** Affects: virtualbox-ose (Ubuntu) Importance: Undecided Status: New -- dependency review https://bugs.launchpad.net/bugs/589934 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589934] Re: dependency review
I meant to file this for package virtualbox-ose-fuse but I must have made a mistake! -- dependency review https://bugs.launchpad.net/bugs/589934 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589934] Re: dependency review
A user who's installed virtualbox-3.2 (or virtualbox-3.1) would also have the required libraries; i.e VBoxDD.so and VBoxDDU.so -- dependency review https://bugs.launchpad.net/bugs/589934 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246928] Re: [upstream] [3.1] Random Kashida in fully-justifed Arabic paragraph
There still seems to be an issue of inserting kashidas between disconnected letters within the one word. I've filed a bug report upstream http://qa.openoffice.org/issues/show_bug.cgi?id=104928 ** Bug watch added: OpenOffice.org Issue Tracker #104928 http://qa.openoffice.org/issues/show_bug.cgi?id=104928 ** Changed in: openoffice Status: Fix Released => In Progress -- [upstream] [3.1] Random Kashida in fully-justifed Arabic paragraph https://bugs.launchpad.net/bugs/246928 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246928] Re: [upstream] [3.1] Random Kashida in fully-justifed Arabic paragraph
No. I just tried the version you mentioned (3.1.1, OOO310m19, build 9420) and the issue is indeed solved. -- [upstream] [3.1] Random Kashida in fully-justifed Arabic paragraph https://bugs.launchpad.net/bugs/246928 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329538] Re: Brasero shows loading bar perpetually when opening saved project file
Using Brasero 2.26.1 on Jaunty and I have the same problem -- Brasero shows loading bar perpetually when opening saved project file https://bugs.launchpad.net/bugs/329538 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
I faced this issue while upgrading a cloud-based system from 18.04 to 20.04. Naturally I had created a snapshot of the system before attempting the upgrade it, so when the upgraded system failed to boot, and after having read much of what may have caused it here and elsewhere, I restored the snapshot, re-performed the upgrade, and before rebooting, I re-installed grub and issued an update-grub command. I'm blind guessing that in my case it had to do with the mapping of the virtual system volume between the guest system and its host/hypervisor. Somewhere in the upgrade grub misses where it should install/update itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132219] Re: xsane crashes on startup with segmentation fault.
xsane crashes with several instances of the following messages on the console: `(xsane:1031048): Gtk-CRITICAL **: 21:09:50.699: IA__gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed` This is now happening again on Ubuntu 20.04 xsane-0.999 libgtk2.0-0 2.24.32-4ubuntu4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/132219 Title: xsane crashes on startup with segmentation fault. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/132219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902897] Re: AusweisApp2 launches without UI, logs errors about missing QT Modules
I found out that installing qml-module-qtgraphicaleffects and qml- module-qtquick-layouts solves the issue and now AusweisApp2 shows its interface when launched in Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902897 Title: AusweisApp2 launches without UI, logs errors about missing QT Modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ausweisapp2/+bug/1902897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373041] Re: Network Manager, device not managed
I have not met this issue in 12.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/373041 Title: Network Manager, device not managed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/373041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344878] Re: file name to long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)
Hello Tyler and every body, I guess those who suggested compressing the filename meant for it to take place before encrypting the filename, when there's still reasonable redundancy in it, not after encryption and before encoding. I like both ideas of the storage in file header and in xattr. I guess the hit on performance should be the determinant of which is more feasible, and I'm slightly favourable of xattr. If such choice is made, then I think making the process uniformal is sounder on the long term, even though it will be a hassle for current users of eCryptfs - like me - who will have to recreate their encrypted storage. By uniformal I mean there shouldn't be a check of whether the name is short enough and as such is to be found in the underlying filesystem, or longer than the threshold and thus is stored elsewhere. This will make the next version of eCryptfs incompatible with the previous. Yeah, radical but better now than bloat, in my opinion. Lastly, regarding the name to leave in the underlying filesystem, I guess the encoded cryptographic hash of the encrypted filename should be far within the length limit, while almost globally unique. I've hit this the first day I upgraded to 10.04 using eCryptfs over ext4, almost 6 months ago. Thank you for your efforts, Tyler. I'm interested to know the direction the solution is heading. Regards, -- file name to long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) https://bugs.launchpad.net/bugs/344878 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756840] Re: Buggy, under-maintained, not fit for main anymore; alternatives exist
I've been using FScrypt on my Ubuntu 20.04 for a couple of months so far, and it's working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756840 Title: Buggy, under-maintained, not fit for main anymore; alternatives exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
