[Bug 2023630] Re: cups-browsed - AppArmor profile missing rights for "/run/systemd/resolve/io.systemd.Resolve"
I was able to get around this by running the following
$ sudo mkdir /etc/apparmor.d/abstractions/nss-systemd.d
$ echo -e '# vim:syntax=apparmor\n\n abi ,\n
@{run}/systemd/resolve/io.systemd.Resolve rw,' | sudo tee
/etc/apparmor.d/abstractions/nss-systemd.d/resolver
$ sudo systemctl reload apparmor
There may very well be better ways to do this, but this seems to work.
NB: FWIW, I believe this gives many applications the ability to use
systemd-resolved to resolve hostnames, but I can't imagine that being a
security issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2023630
Title:
cups-browsed - AppArmor profile missing rights for
"/run/systemd/resolve/io.systemd.Resolve"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2023630/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786125] Re: Incorrect UpgradeStatus field value in saved crash file
Ahh.. That's what it checks. No need. My problem then is I haven't been using do-release-upgrade to do updates for a long time. I have a ton of complicated dependencies that always seem to fail on upgrade, so I've been manually replacing the codename in /etc/apt/sources.list for each upgrade. So this isn't strictly a duplicate, but it might be for all intents and purposes though if a decision is made to use a different means of obtaining this information. I can understand if this is a wontfix though. If this is to be corrected, the obvious way that occurs to me though is to pull the files specifying the OS version information (i.e. /etc/debian_version /etc/lsb-release /usr/lib/os-release) into their own package and change it once per release and use the install date of that package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786125 Title: Incorrect UpgradeStatus field value in saved crash file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1786125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786125] [NEW] Incorrect UpgradeStatus field value in saved crash file
Public bug reported: For whatever reason, when I run apport-bug or apport-cli, the crash file that is generated/submitted contains the line: UpgradeStatus: Upgraded to bionic on 2014-12-03 (1344 days ago) Obviously this is wildly incorrect, and I'm not even sure how this value was obtained. (I imagine the last modified date on some file?) Happy to help debug if there's any other info I can provide. Expected value is the correct one (about a month ago). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashReports: 640:0:176:18730739:2018-08-03 16:06:47.263502851 -0400:2018-08-03 16:06:24.015502521 -0400:/var/crash/_usr_lib_virtualbox_VirtualBox.0.crash CurrentDesktop: KDE Date: Wed Aug 8 17:27:42 2018 InstallationDate: Installed on 2012-01-06 (2406 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2014-12-03 (1344 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786125 Title: Incorrect UpgradeStatus field value in saved crash file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1786125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756997] Re: plasmashell leaks memory uncontrollably
FYI, this is fixed in Bionic running the latest NVidia drivers and KDE version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756997 Title: plasmashell leaks memory uncontrollably To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1756997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756997] Re: plasmashell leaks memory uncontrollably
Console output from apport-valgrind attached, NB: I invoked it with: /usr/bin/apport-valgrind -l valgrind.$$.log -C ./cache -v /usr/bin/plasmashell < /dev/null &> apport-valgrind.$$.log & ** Attachment added: "Console output from apport-valgrind" https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1756997/+attachment/5084461/+files/apport-valgrind.24972.log ** Also affects: nvidia-graphics-drivers-384 (Ubuntu) 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/1756997 Title: plasmashell leaks memory uncontrollably To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1756997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756997] [NEW] plasmashell leaks memory uncontrollably
Public bug reported: I'm not sure if this is a problem with the plasmashell executable itself, or the the nvidia libraries, or perhaps plasmashell not interacting with the nvidia libraries correctly, but for the past several months I've noticed that the memory usage of plasmashell creeps slowly and consistently upward the longer it is running. This is at the level for me that within a day or two after (re)starting it, it is taking up all of my 12 gigs of ram and my my swap space engages and my system starts thrashing to the point that it takes minutes to get to a console to killall plasmashell. If I'm not sure if I'll even get to that point, I do SysRq+F (Sometimes it locks up completely -- presumably due to a kernel panic -- if I don't catch the extensive thrashing before too long, but that's a secondary issue.) This problem began several months ago (I was sort of expecting someone would quickly patch it, so I lived with it for a bit) so unfortunately I can't point to a specific version number. I did run apport-valgrind on plasmashell (output to be attached), which is what implicates the nvidia drivers. Happy to provide any additional information requested or to try other versions of these applications. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: plasma-workspace 4:5.10.5-0ubuntu1 [modified: usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml] ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Mon Mar 19 15:48:15 2018 InstallationDate: Installed on 2012-01-06 (2264 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to artful on 2014-12-03 (1202 days ago) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "apport-valgrind Log" https://bugs.launchpad.net/bugs/1756997/+attachment/5084456/+files/valgrind.24972.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756997 Title: plasmashell leaks memory uncontrollably To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1756997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Out of curiosity, can you link me to the upstream git repo for http://kernsec.org/pipermail/linux-security-module- archive/2017-December/004638.html? I want to be sure I'm looking at the right place. Interestingly, it looks like someone replied to your patch saying they would incorporate it in early December, so it seems this bug fell through the cracks more than once. Joseph Salisbury is subscribed to this bug and has commented on it above, so hopefully he will update regarding this when he gets a chance. This seems like a really simple fix, so I'm actually going to see if I can recompile 4.13.0-25-generic with this patch added to make it work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Thanks! Should I mark this bug as a duplicate then? Also, what is the process/timeline for that patch you linked being applied downstream into Artful? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Okay, the bug still exists in 4.13.0-21-generic, but went away in 4.13.0-25-generic once I removed 'apparmor=0'. So I think Tetsuo may be on to something. Could this be a duplicate of this[0] bug? This would make sense considering the message of one the problematic commits is "add stacking support to apparmor network hooks". I'm not well versed enough in the kernel internals to say for sure, so I'm deferring to someone who knows better. Also, I'm not sure if I'm missing something, but while that bug is marked as "Fix Committed" in Launchpad[0], and a request was made to revert the pair of commits[1], I neither see a reply to that email saying the commits were indeed reverted nor subsequent commits to the Artful repo reverting the files affected by these commits. Is it possible that email got lost? [0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734327 [1] https://lists.ubuntu.com/archives/kernel-team/2017-December/088715.html [2] http://kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/log/security/apparmor/lsm.c and http://kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/log/security/selinux/netlabel.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Okay, I tested it with 4.15.0-041500rc7-generic and the issue disappeared. Thanks! Does that provide any insight into what exactly the error is and/or a possible workaround? Unfortunately I'm unable to use this kernel in the interim as I rely on the Nvidia kernel modules, which aren't compiling in DKMS. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742572] [NEW] System Hangs and General Protection Fault Occurs following NFS Access
Public bug reported: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1742572/+attachment/5034766/+files/dmesg.log ** Description changed: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. - Attached is the console log (obtained via netconsole), lspci (with - -vnvn), and the output from lsb_release -a. + Attached is the console log (obtained via netconsole) which includes the + kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: mvastola 4661 F pulseaudio - /dev/snd/controlC1: mvastola 4661 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: mvastola 4661 F pulseaudio + /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
[Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Please note that I ran 'ubuntu-bug' from my most recent working kernel (from Zesty): 4.10.0-42-generic, so some of this log output may be inaccurate as a result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587574] [NEW] VLC Crashes on Media Menu Selections
Public bug reported: Crash also occurs (every time) when selecting any of the following: - Media -> Open Multiple Files - Media -> Open Disc - Media -> Open Network Stream - Media -> Open Media Device - Media -> Convert / Save - Media -> Stream Each time, the console output is: ASSERT failure in QList::operator[]: "index out of range", file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, line 518 Aborted (core dumped) OS is Ubuntu 16.04 LTS. Expected result was (obviously) for a crash not to occur and for the relevant window to open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 31 12:45:32 2016 InstallationDate: Installed on 2012-01-06 (1607 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2014-12-03 (544 days ago) ** Affects: vlc (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587574 Title: VLC Crashes on Media Menu Selections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1587574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587573] Re: VLC Crashes on Media -> Open Media Device
Disregard this bug report. It is missing my core dump. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587573 Title: VLC Crashes on Media -> Open Media Device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1587573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587574] Re: VLC Crashes on Media Menu Selections
Disregard this bug. It is missing the core dump. ** Changed in: vlc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587574 Title: VLC Crashes on Media Menu Selections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1587574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587573] Re: VLC Crashes on Media -> Open Media Device
** Changed in: vlc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587573 Title: VLC Crashes on Media -> Open Media Device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1587573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587573] [NEW] VLC Crashes on Media -> Open Media Device
Public bug reported: Crash also occurs (every time) when selecting any of the following: - Media -> Open Multiple Files - Media -> Open Disc - Media -> Open Network Stream - Media -> Convert / Save - Media -> Stream Each time, the console output is: ASSERT failure in QList::operator[]: "index out of range", file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, line 518 Aborted (core dumped) OS is Ubuntu 16.04 LTS. Expected result was (obviously) for a crash not to occur and for the relevant window to open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc-nox 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 31 12:29:09 2016 InstallationDate: Installed on 2012-01-06 (1607 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2014-12-03 (544 days ago) ** Affects: vlc (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587573 Title: VLC Crashes on Media -> Open Media Device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1587573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876829] Re: Oneiric's ifupdown breaks ip aliases
I'm experiencing the same behavior as LStranger. My IP aliases are coming up, but they're just not reflected anywhere as online (in either ifconfig or ip). I can do the following and see the actual commands being run to bring up the interfaces, which as far as I can tell are working correctly except for the whole showing the interfaces as up thing. root@server_name:~# ifdown -av ifup -av [ . . . ] ip route del default via xxx.yyy.100.1 metric 100 dev eth0 21 1/dev/null || true ip -4 addr flush dev eth0 ip link set dev eth0 down run-parts --verbose /etc/network/if-post-down.d Configuring interface eth0:1=eth0:1 (inet) run-parts --verbose /etc/network/if-down.d run-parts: executing /etc/network/if-down.d/postfix run-parts: executing /etc/network/if-down.d/upstart ip -4 addr flush dev eth0:1 ip link set dev eth0:1 down run-parts --verbose /etc/network/if-post-down.d [ . . . ] Configuring interface eth0=eth0 (inet) iptables-restore /etc/iptables.rules run-parts --verbose /etc/network/if-pre-up.d ip addr add xxx.yyy.100.11/255.255.255.0 broadcast xxx.yyy.100.255 dev eth0 ip link set dev eth0 up ip route add default via xxx.yyy.100.1 metric 100 dev eth0 [ . . . ] Configuring interface eth0:1=eth0:1 (inet) run-parts --verbose /etc/network/if-pre-up.d ip addr add xxx.yyy.100.23/255.255.255.0 dev eth0:1 ip link set dev eth0:1 up [ . . . ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876829 Title: Oneiric's ifupdown breaks ip aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/876829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 675054] Re: liborc causes segfault in pidgin when playing sound
** Attachment added: pidgin-backtrace5.log https://bugs.launchpad.net/ubuntu/+source/orc/+bug/675054/+attachment/1732668/+files/pidgin-backtrace5.log -- liborc causes segfault in pidgin when playing sound https://bugs.launchpad.net/bugs/675054 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 675054] [NEW] liborc causes segfault in pidgin when playing sound
Public bug reported: This will happen when I get an IM that triggers a sound alert, or even when I go into preferences and preview a sound. Expected Result: Sound plays and segfault does not occur. Actual Result: Sound does not play, segfault occurs. Backtrace attached. Please let me know if I can supply any more info to help fix this bug. Thanks, Mike ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: liborc-0.4-0 0.4.6-1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Nov 13 18:53:03 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: orc ** Affects: orc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- liborc causes segfault in pidgin when playing sound https://bugs.launchpad.net/bugs/675054 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 675054] Re: liborc causes segfault in pidgin when playing sound
-- liborc causes segfault in pidgin when playing sound https://bugs.launchpad.net/bugs/675054 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 675054] Re: liborc causes segfault in pidgin when playing sound
** Bug watch added: Pidgin Trac #12880 http://developer.pidgin.im/ticket/12880 ** Also affects: pidgin via http://developer.pidgin.im/ticket/12880 Importance: Unknown Status: Unknown -- liborc causes segfault in pidgin when playing sound https://bugs.launchpad.net/bugs/675054 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
