[Bug 1852985] Re: X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Unfortunately, gitk is crashing again when it tries to display the symbol "". I don't know why it worked after installing the unifont only to stop working shortly afterwards again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852985 Title: X Error of failed request: BadLength (poly request too large or internal Xlib length error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1852985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852985] Re: X Error of failed request: BadLength (poly request too large or internal Xlib length error)
I got gitk to not crash by installing unifont package. E.g. sudo apt install unifont the font isn't displayed in gitk properly (shows up as an empty square) but at least gitk no longer crashes - Details of System VERSION="20.04.1 LTS (Focal Fossa)" $ dpkg --list gitk Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii gitk 1:2.25.1-1ubuntu3 all fast, scalable, distributed revision control system (revision tree visualizer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852985 Title: X Error of failed request: BadLength (poly request too large or internal Xlib length error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1852985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852985] Re: X Error of failed request: BadLength (poly request too large or internal Xlib length error)
I get this in gitk if a commit has "unprintable" characters like this symbol (\xd83d , \xdd25) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852985 Title: X Error of failed request: BadLength (poly request too large or internal Xlib length error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1852985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901235] [NEW] ERROR: Rosdep experienced an error: a bytes-like object is required, not 'str'
Public bug reported:
On Ubuntu 20.04 with stock installed packages, the command "rosdep
--all-versions" generates the following error:
$rosdep --all-versions
0.18.0
ERROR: Rosdep experienced an error: a bytes-like object is required, not 'str'
Please go to the rosdep page [1] and file a bug report with the stack trace
below.
[1] : http://www.ros.org/wiki/rosdep
rosdep version: 0.18.0
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/rosdep2/main.py", line 144, in
rosdep_main
exit_code = _rosdep_main(args)
File "/usr/lib/python3/dist-packages/rosdep2/main.py", line 387, in
_rosdep_main
installer_version_strings = installer.get_version_strings()
File "/usr/lib/python3/dist-packages/rosdep2/platforms/debian.py", line 235,
in get_version_strings
version = output.splitlines()[0].split(' ')[1]
TypeError: a bytes-like object is required, not 'str'
---
Details on installed packages:
$ dpkg --list | grep "ii ros"
ii ros-actionlib-msgs 1.12.7-2
all Messages relating to Robot OS actionlib,
definitions
ii ros-base 1.15
all Python Robot OS base metapackage
ii ros-base-dev 1.15
all Robot OS base development metapackage
ii ros-base-lisp-dev 1.15
all Lisp Robot OS base development metapackage
ii ros-base-python-dev1.15
all Python Robot OS base development metapackage
ii ros-cmake-modules 0.5.0-1
all Robot OS CMake Modules
ii ros-core 1.15
all Robot OS core metapackage
ii ros-core-dev 1.15
all Robot OS core development metapackage
ii ros-core-lisp-dev 1.15
all Lisp Robot OS core development metapackage
ii ros-core-python-dev1.15
all Python Robot OS core development metapackage
ii ros-core-rosbuild-dev 1.15
all Robot OS rosbuild core development metapackage
ii ros-desktop1.15
all Robot OS desktop metapackage
ii ros-desktop-full 1.15
all Robot OS desktop-full metapackage
ii ros-desktop-full-python-dev1.15
all Python Robot OS desktop-full development
metapackage
ii ros-desktop-python-dev 1.15
all Python Robot OS desktop development metapackage
ii ros-diagnostic-msgs1.12.7-2
all Messages relating to Robot OS diagnostic,
definitions
ii ros-environment1.2.2-2
all Robot OS environment hooks
ii ros-geometry-msgs 1.12.7-2
all Messages relating to Robot OS geometry,
definitions
ii ros-map-msgs 1.13.1-1
all Definitions of map-related ROS Messages
ii ros-message-generation 0.4.0-4
all Generates build-time messaging dependencies for
Robot OS packages
ii ros-message-runtime:amd64 0.4.12-6
amd64Generates runtime messaging dependencies for
Robot OS package
ii ros-mk 1.14.7-3build2
all Robot OS make file helpers
ii ros-move-base-msgs 1.13.1-1
all Definitions of move-base-related ROS Messages
ii ros-nav-msgs 1.12.7-2
all Messages relating to Robot OS nav, definitions
ii ros-perception 1.15
all Python Robot OS perception metapackage
ii ros-perception-python-dev 1.15
[Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Reading the initial bug report I see kolAflash said > nomodeset seems to be essential, but not sufficient. When I added nomodeset to /etc/default/grub ( GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" ) then I can boot without issues, but suspend does not work. To reiterate: * the TTY1 screen is not blank on boot * sleep works * suspend does not work - you get this bug Given this error in syslog: > kernel: [0.047848] You have booted with nomodeset. This means your GPU > drivers are DISABLED > kernel: [0.047849] Unless you actually understand what nomodeset does, > you should reboot without enabling it > [0.047849] Any video related functionality will be severely degraded, and > you may not even be able to suspend the system properly > [0.047849] Unless you actually understand what nomodeset does, you should > reboot without enabling it I tried a few things without nomodeset in grub options. In this case: * the default screen, TTY1, (CTRL-ALT-F1) is blank on boot (or has the HP logo only) * sleep works * suspend doesn't seem to work. If you leave the laptop in suspend mode for a long time it does not resume. The screen is black with just a white underscore on it. The last log lines in /var/log/syslog is systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[8263]: Suspending system... kernel: [ 9425.088936] PM: suspend entry (s2idle) As a workaround for the default screen being blank on boot, you can go to TTY2 (CTRL-ALT-F2), log in and run startx from the command prompt. Some tests: * This does not seem to be the same issue as https://bugzilla.kernel.org/show_bug.cgi?id=204241 because the following command works just fine. for i in $(seq 30); do sudo rtcwake -m mem -s 5; sleep 15; done * I've tried adding GRUB_GFXMODE=1920x1080 to /etc/default/grub but that doesn't seem to solve the issue with the screen on TTY1 being blank on boot. The commands pm-hibernate and pm-suspend give the errors in /var/log/syslog > [ 2566.154192] Lockdown: grep: hibernation is restricted; see man > kernel_lockdown.7 and nothing happens The command pm-powersave gives the same "hibernation is restricted" error in /var/log/syslog but the system goes blank and the is unresponsive. ** Bug watch added: Linux Kernel Bug Tracker #204241 https://bugzilla.kernel.org/show_bug.cgi?id=204241 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Update 2: This isn't actually fully solved. What's working is short-term "Sleep" but if you leave the laptop lid closed for a while it goes to suspend (s2idle) and that crashes the system. Aug 23 14:22:56 REDACTED systemd[1]: NetworkManager-dispatcher.service: Succeeded. Aug 23 14:23:08 REDACTED kernel: [ 124.757545] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 23 14:23:08 REDACTED NetworkManager[734]: [1598210588.2565] manager: sleep: sleep requested (sleeping: no enabled: yes) Aug 23 14:23:08 REDACTED NetworkManager[734]: [1598210588.2567] manager: NetworkManager state is now ASLEEP Aug 23 14:23:08 REDACTED whoopsie[1113]: [14:23:08] offline Aug 23 14:23:08 REDACTED kernel: [ 124.760864] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 23 14:23:08 REDACTED kernel: [ 124.761905] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 23 14:23:08 REDACTED systemd[1]: Reached target Sleep. Aug 23 14:23:08 REDACTED systemd[1]: Starting Suspend... Aug 23 14:23:08 REDACTED kernel: [ 124.775535] PM: suspend entry (s2idle) Aug 23 14:23:08 REDACTED systemd-sleep[1370]: Suspending system... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
update: installed pm-utils ( sudo apt install pm-utils ) and the machine no longer gives a black screen when raising the laptop lid and resumes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Have the same issue with HP envy x360 running KDE and Ubuntu 20.04.1 LTS uname -a Linux rix360 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux First entry in /proc/cpuinfo shows processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 96 model name : AMD Ryzen 7 4700U with Radeon Graphics stepping: 1 microcode : 0x8600103 cpu MHz : 1395.962 cache size : 512 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 8 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 16 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_ apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topo ext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp v mmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv 1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vml oad vgif umip rdpid overflow_recov succor smca bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass bogomips: 3992.69 TLB size: 3072 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769890] Re: Icingaweb2 does not work with PHP 7.2
Can confirm in Jan 2020, still an issue with Ubuntu 18.04.3 Fixed by following changes in https://github.com/Icinga/icingaweb2/pull/3315/commits/dadd2c80f6819111f25e3799c072ec39c991897e and John Gerde's note above. What's the best way to help move this into a release for 18.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769890 Title: Icingaweb2 does not work with PHP 7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icingaweb2/+bug/1769890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20 - 5.3
Also happening with HP Zbook x360, but only recently started (today). As a workaround to stop your HD from filling up with this, create the file /etc/rsyslog.d/10-hidsensor.conf With the two lines: # Disable runaway messages: :msg, contains, "hid-sensor-hub 001F:8087:0AC2.0003" ~ Then run sudo service rsyslog restart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 - 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610075] Re: kubuntu-driver-manager application opens to show nothing
I now have this exact same issue with KUbuntu 19.10. Device Manager worked fine in KUbuntu 19.04 but then I upgraded to 19.10 (do-release-upgrade) and now get exactly the same hang of the kubuntu- driver-manager The commands "ubuntu-drivers list" , "ubuntu-drivers debug" and "ubuntu-drivers devices" are ok but "ubuntu-drivers install" reports an issue $ sudo ubuntu-drivers install 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: nvidia-driver-435 : Depends: libnvidia-gl-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: nvidia-compute-utils-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-decode-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-encode-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: xserver-xorg-video-nvidia-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-cfg1-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-ifr1-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-fbc1-435 (= 435.21-0ubuntu2) but it is not going to be installed Recommends: libnvidia-compute-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-decode-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-encode-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-ifr1-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-fbc1-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-gl-435:i386 (= 435.21-0ubuntu2) E: Unable to correct problems, you have held broken packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610075 Title: kubuntu-driver-manager application opens to show nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1610075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610075] Re: kubuntu-driver-manager application opens to show nothing
I now have this exact same issue with KUbuntu 19.10. Device Manager worked fine in KUbuntu 19.04 but then I upgraded to 19.10 (do-release-upgrade) and now get exactly the same hang of the kubuntu- driver-manager The command "ubuntu-drivers" seems to report info ok but installing reports an issue $ sudo ubuntu-drivers install 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: nvidia-driver-435 : Depends: libnvidia-gl-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: nvidia-compute-utils-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-decode-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-encode-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: xserver-xorg-video-nvidia-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-cfg1-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-ifr1-435 (= 435.21-0ubuntu2) but it is not going to be installed Depends: libnvidia-fbc1-435 (= 435.21-0ubuntu2) but it is not going to be installed Recommends: libnvidia-compute-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-decode-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-encode-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-ifr1-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-fbc1-435:i386 (= 435.21-0ubuntu2) Recommends: libnvidia-gl-435:i386 (= 435.21-0ubuntu2) E: Unable to correct problems, you have held broken packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610075 Title: kubuntu-driver-manager application opens to show nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1610075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842683] Re: Default Install of mpd not able to open /var/log/mpd/mpd.log on Disco Dingo so mpd.service fails.
More information:
$ls -ld /var/log/mpd
drwxr-xr-x 2 mpd audio 4096 Sep 1 00:00 /var/log/mpd/
$ ls -l /var/log/mpd/
total 8
-rw-r--r-- 1 root root 600 Sep 4 09:36 mpd.log
-rw-r--r-- 1 root root 164 Aug 31 21:58 mpd.log.1.gz
$cat /etc/logrotate.d/mpd
/var/log/mpd/*.log {
weekly
missingok
rotate 7
compress
notifempty
copytruncate
create 600
}
So I'd guess that the create statement in /etc/logrotate.d/mpd should read
"create 600 mpd audio"
and not just "create 600"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842683
Title:
Default Install of mpd not able to open /var/log/mpd/mpd.log on Disco
Dingo so mpd.service fails.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1842683/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842683] [NEW] Default Install of mpd not able to open /var/log/mpd/mpd.log on Disco Dingo so mpd.service fails.
Public bug reported: Brand new installation of Ubuntu 19.04 (Disco Dingo) on laptop. Reviewing syslog messages returned the following Sep 4 09:36:31 REDACTED mpd[1606]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 39): Permission denied Sep 4 09:36:31 REDACTED systemd[1590]: mpd.service: Main process exited, code=exited, status=1/FAILURE Sep 4 09:36:31 REDACTED systemd[1590]: mpd.service: Failed with result 'exit-code'. Sep 4 09:36:31 REDACTED systemd[1590]: Failed to start Music Player Daemon. I can easily fix by modifying permissions or modifying the config file, but reporting as this probably impacts others. ** Affects: mpd (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/1842683 Title: Default Install of mpd not able to open /var/log/mpd/mpd.log on Disco Dingo so mpd.service fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1842683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099201] Re: Transcode can't rip DVD's (in K3b with file type MPEG4)
Got this same error with Ubuntu 17.10 and k3b. The k3b debug window shows -- /usr/bin/transcode --log_no_color --progress_meter 2 --progress_rate 551 -i /dev/sr0 -x dvd -T 1,-1,1 -a 0 -j 0,0,0,0 -R 0,/tmp/k3b_0.log -y ffmpeg -N 0x2000 -A -o /tmp/foobar.avi -F mpeg4 -Z 848x480 ... *** Error in `/usr/bin/transcode': munmap_chunk(): invalid pointer: 0x7efd97e43f3a *** Aborted (core dumped) -- However: If I run that same command in bash it creates an ok file. It appears that this error message from transcode causes k3b to delete the file even though it appears the file was created ok by transcode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099201 Title: Transcode can't rip DVD's (in K3b with file type MPEG4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transcode/+bug/1099201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561278] Re: internal sound card not detected HP X2
alsa-info output: http://www.alsa- project.org/db/?f=12cbba27e12cc27ede2a9934df4f3a1ce12ff545 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561278] Re: internal sound card not detected HP X2
Have the same issue with Ubuntu 17.10 $ uname -a Linux raiaHPx2 4.13.0-39-generic #44-Ubuntu SMP Thu Apr 5 14:25:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux "aplay -l" gives the following $aplay -l List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 0: Baytrail Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 Attempted to solve with following the directions here with dkms https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but did not fix the no sound issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
After upgrading from 17.04 to 17.10 I also had this issue with error: > pulseaudio[6267]: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Fixed like in #4 by commenting load-module module-switch-on-connect out of /etc/pulse/default.pa Have not tried any plug-in-devices to see if this fix affects their usage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589028] Re: Improper blocksize set by usb-creator, leads to problems during formatting
+1 here. On Ubuntu 17.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589028 Title: Improper blocksize set by usb-creator, leads to problems during formatting To manage notifications about this bug go to: https://bugs.launchpad.net/parted/+bug/1589028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662860] Re: /sbin/ldconfig.real: /usr/lib/nvidia-375/libEGL.so.1 is not a symbolic link
Confirmed with Ubuntu 17.04 with upgrading to libcuda1-384 nvidia-384 nvidia-opencl-icd-384 Get the following errors: /sbin/ldconfig.real: /usr/lib/nvidia-384/libEGL.so.1 is not a symbolic link /sbin/ldconfig.real: /usr/lib32/nvidia-384/libEGL.so.1 is not a symbolic link -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662860 Title: /sbin/ldconfig.real: /usr/lib/nvidia-375/libEGL.so.1 is not a symbolic link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1662860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599745] Re: libvirt block commit stuck at 100%
I had something similar happen. I think it is related to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1197592 " blockcopy always failed when with option "--pivot" " This was on Ubuntu Server 16.04.1 $ uname -a Linux oslo 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ virsh --version 1.3.1 $ dpkg --list | grep libvirt ii libvirt-bin 1.3.1-1ubuntu10.1 amd64programs for the libvirt library ii libvirt0:amd64 1.3.1-1ubuntu10.1 amd64library for interfacing with different virtualization systems To fix requires an upgrade to libvirt-1.3.2-1.el7 ** Bug watch added: hacking a member #1197592 https://bugzilla.redhat.com/cgi-bin/bugreport.cgi?bug=1197592 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599745 Title: libvirt block commit stuck at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1599745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591249] Re: Bonding NICs results in errors in ncftool and virsh
$ uname -a Linux 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ more /etc/issue Ubuntu 16.04 LTS \n \l -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591249 Title: Bonding NICs results in errors in ncftool and virsh To manage notifications about this bug go to: https://bugs.launchpad.net/netcfg/+bug/1591249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591249] Re: Bonding NICs results in errors in ncftool and virsh
Tried moving the IP to the bridge instead of the bond. - source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eno1 allow-bond eno1 iface eno1 inet manual bond-master bond0 auto eno2 allow-bond eno2 iface eno2 inet manual bond-master bond0 auto bond0 iface bond0 inet manual bond-miimon 100 bond-mode 4 bond-slaves eno1 eno2 auto br0 iface br0 inet static address 192.168.1.16 gateway 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255 bridge_ports bond0 bridge_hello 2 bridge_stp off bridge_fd 9 bridge_maxwait 12 -- Makes it worse. $ ncftool list error: unspecified error error: errors in loading some config files - $ virsh iface-list error: Failed to list interfaces error: internal error: failed to get number of host interfaces: unspecified error - errors in loading some config files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591249 Title: Bonding NICs results in errors in ncftool and virsh To manage notifications about this bug go to: https://bugs.launchpad.net/netcfg/+bug/1591249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591249] Re: Bonding NICs results in errors in ncftool and virsh
I read in some comments that the format of /etc/network/interfaces can confuse Ubuntu's back-end processing for ncftool. I tried removing all comments and simplifying that file as source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eno1 allow-bond eno1 iface eno1 inet manual bond-master bond0 auto eno2 allow-bond eno2 iface eno2 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 192.168.1.16 gateway 192.168.1.1 netmask 255.255.255.0 bond-mode 4 bond-slaves eno1 eno2 --- and rebooted. It did not solve the issue. ** Also affects: 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/1591249 Title: Bonding NICs results in errors in ncftool and virsh To manage notifications about this bug go to: https://bugs.launchpad.net/netcfg/+bug/1591249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579988] Re: Image will not delete
Exact same thing happened to me. Tried LXD for the first time ever. Created then deleted an image. Still shows up with "lxc image list" lxc version: 2.0.1 lxd version: 2.0.2 Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial Noticed that /var/lib/lxd has uid/gid = lxd/nogroup Halverneus' delete-it-all method worked to reset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579988 Title: Image will not delete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1579988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532460] Re: Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above)
It works well in Ubuntu 15 and checking the package list for xenial shows ( http://packages.ubuntu.com/xenial/ )it has versions of qemu=2.5 and libvirt= 1.3.1 so it is a feature that is in 16.04 as well. Not tested, but looks good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532460 Title: Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1532460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532460] [NEW] Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above)
Public bug reported: This is a feature request ticket. Blockcommit makes snapshot/commit steps take fractions of a second instead of minutes. Perform efficient live disk backups using virsh blockcommit. This is possible with versions: QEMU 2.1 (and above), libvirt-1.2.9 (and above), but not any LTS version of Ubuntu. Perhaps Trusty-Proposed? ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1532460 Title: Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1532460/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1532460] [NEW] Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above)
Public bug reported: This is a feature request ticket. Blockcommit makes snapshot/commit steps take fractions of a second instead of minutes. Perform efficient live disk backups using virsh blockcommit. This is possible with versions: QEMU 2.1 (and above), libvirt-1.2.9 (and above), but not any LTS version of Ubuntu. Perhaps Trusty-Proposed? ** Affects: libvirt (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/1532460 Title: Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1532460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525310] Re: virsh with apparmor misconfigures libvirt-UUID files during snapshot
This bug also appears in Ubuntu 15.10 $ apt-cache policy apparmor apparmor: Installed: 2.10-0ubuntu6 Candidate: 2.10-0ubuntu6 Version table: *** 2.10-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libvirt-bin libvirt-bin: Installed: 1.2.16-2ubuntu11.15.10.1 Candidate: 1.2.16-2ubuntu11.15.10.1 Version table: *** 1.2.16-2ubuntu11.15.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.16-2ubuntu11 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525310 Title: virsh with apparmor misconfigures libvirt-UUID files during snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1525310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525310] [NEW] virsh with apparmor misconfigures libvirt-UUID files during snapshot
Public bug reported:
Reproducible: Yes, every time.
Background:
When you create a virtual machine (VM) under KVM/Qemu in Ubuntu,
apparmor files are created as:
/etc/apparmor.d/libvirt/libvirt-
and
/etc/apparmor.d/libvirt/libvirt-.files
And in the file /etc/apparmor.d/libvirt/libvirt-.files there is
the line
"PATH_to_BLOCK_DEVICE" rw,
where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g. something
like /var/lib/libvirtd/images/asdf.qcow2)
and is the UUID of the VM container.
The problem:
When creating a shapshot of a running VM under KVM/Qemu you run the
command
$ sudo virsh snapshot-create-as DOMAIN_NAME DESCRIPTION --no-
metadata --disk-only --atomic
which creates a new file and stops writing to the old VM block device.
However: the old PATH_to_BLOCK_DEVICE in /etc/apparmor.d/libvirt
/libvirt-UUID.files is deleted and replaced with the new block device
info BEFORE virsh is done creating the snapshot. So you get the error
error: internal error: unable to execute QEMU command 'transaction':
Could not open 'PATH_to_BLOCK_DEVICE': Could not open
'PATH_to_BLOCK_DEVICE': Permission denied: Permission denied
and in /var/log/syslog you get the error:
type=1400 audit(1449752104.054:539): apparmor="DENIED" operation="open"
profile="libvirt-" name="PATH_to_BLOCK_DEVICE" pid=8710 comm
="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=106 ouid=106
When you look now at /etc/apparmor.d/libvirt/libvirt-.files you
find that the line that was there
"PATH_to_BLOCK_DEVICE" rw,
has been replaced with
"PATH_to_BLOCK_DEVICE.DESCRIPTION" rw,
but you need BOTH LINES. in order for the command "virsh snapshot-
create-as" to work. (or at least have the old file have read
permissions)
-
Workarounds:
1. Disable apparmor for libvirtd
or
2. Change /etc/apparmor.d/libvirt/libvirt- to look like this
--
#
# This profile is for the domain whose UUID matches this file.
#
#include
profile libvirt-UUID {
#include
#include
"PATH_to_BLOCK_DEVICE*" rw,
}
---
(
So if the old line was
"/var/lib/libvirtd/images/asdf.qcow2" rw,
, the line you can add would read something like this
"/var/lib/libvirtd/images/asdf*" rw,
)
Details on server:
# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
# apt-cache policy apparmor
apparmor:
Installed: 2.8.95~2430-0ubuntu5.3
Candidate: 2.8.95~2430-0ubuntu5.3
Version table:
*** 2.8.95~2430-0ubuntu5.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.8.95~2430-0ubuntu5.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
2.8.95~2430-0ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy libvirt-bin
libvirt-bin:
Installed: 1.2.2-0ubuntu13.1.14
Candidate: 1.2.2-0ubuntu13.1.14
Version table:
*** 1.2.2-0ubuntu13.1.14 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
1.2.2-0ubuntu13.1.7 0
500 http://security.u buntu.com/ubuntu/ trusty-security/main amd64
Packages
1.2.2-0ubuntu13 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
-
Apologies if this is the wrong place to submit this bug.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- virsh with apparmor misconfigures libvirtd-UUID files during snapshot
+ virsh with apparmor misconfigures libvirt-UUID files during snapshot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525310
Title:
virsh with apparmor misconfigures libvirt-UUID files during snapshot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1525310/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525310] Re: virsh with apparmor misconfigures libvirt-UUID files during snapshot
** Description changed:
Reproducible: Yes, every time.
Background:
When you create a virtual machine (VM) under KVM/Qemu in Ubuntu,
apparmor files are created as:
/etc/apparmor.d/libvirt/libvirt-
- and
+ and
/etc/apparmor.d/libvirt/libvirt-.files
And in the file /etc/apparmor.d/libvirt/libvirt-.files there is
the line
- "PATH_to_BLOCK_DEVICE" rw,
+ "PATH_to_BLOCK_DEVICE" rw,
- where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g.
something like /var/lib/libvirtd/images/asdf.qcow2)
- and is the UUID of the VM container.
+ where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g.
something like /var/lib/libvirtd/images/asdf.qcow2)
+ and is the UUID of the VM container.
The problem:
When creating a shapshot of a running VM under KVM/Qemu you run the
command
$ sudo virsh snapshot-create-as DOMAIN_NAME DESCRIPTION --no-
metadata --disk-only --atomic
which creates a new file and stops writing to the old VM block device.
However: the old PATH_to_BLOCK_DEVICE in /etc/apparmor.d/libvirt
/libvirt-UUID.files is deleted and replaced with the new block device
info BEFORE virsh is done creating the snapshot. So you get the error
error: internal error: unable to execute QEMU command 'transaction':
Could not open 'PATH_to_BLOCK_DEVICE': Could not open
'PATH_to_BLOCK_DEVICE': Permission denied: Permission denied
and in /var/log/syslog you get the error:
type=1400 audit(1449752104.054:539): apparmor="DENIED" operation="open"
profile="libvirt-" name="PATH_to_BLOCK_DEVICE" pid=8710 comm
="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=106 ouid=106
+ When you look now at /etc/apparmor.d/libvirt/libvirt-.files you
+ find that the line that was there
- When you look now at /etc/apparmor.d/libvirt/libvirt-.files you find
that the line that was there
+ "PATH_to_BLOCK_DEVICE" rw,
- "PATH_to_BLOCK_DEVICE" rw,
+ has been replaced with
+ "PATH_to_BLOCK_DEVICE.DESCRIPTION" rw,
- has been replaced with
-
- "PATH_to_BLOCK_DEVICE.DESCRIPTION" rw,
-
-
- but you need BOTH LINES. in order for the command "virsh snapshot-create-as"
to work. (or at least have the old file have read permissions)
+ but you need BOTH LINES. in order for the command "virsh snapshot-
+ create-as" to work. (or at least have the old file have read
+ permissions)
-
Workarounds:
1. Disable apparmor for libvirtd
- or
+ or
2. Change /etc/apparmor.d/libvirt/libvirt- to look like this
+
--
#
# This profile is for the domain whose UUID matches this file.
- #
-
+ #
+
#include
-
+
profile libvirt-UUID {
- #include
- #include
-
- "PATH_to_BLOCK_DEVICE*" rw,
- }
+ #include
+ #include
+
+ "PATH_to_BLOCK_DEVICE*" rw,
+ }
---
+ (
+ So if the old line was
+ "/var/lib/libvirtd/images/asdf.qcow2" rw,
+ , the line you can add would read something like this
+
+ "/var/lib/libvirtd/images/asdf*" rw,
+
+ )
+
Details on server:
# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
-
# apt-cache policy apparmor
apparmor:
- Installed: 2.8.95~2430-0ubuntu5.3
- Candidate: 2.8.95~2430-0ubuntu5.3
- Version table:
- *** 2.8.95~2430-0ubuntu5.3 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
- 100 /var/lib/dpkg/status
- 2.8.95~2430-0ubuntu5.1 0
- 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
- 2.8.95~2430-0ubuntu5 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ Installed: 2.8.95~2430-0ubuntu5.3
+ Candidate: 2.8.95~2430-0ubuntu5.3
+ Version table:
+ *** 2.8.95~2430-0ubuntu5.3 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
+ 100 /var/lib/dpkg/status
+ 2.8.95~2430-0ubuntu5.1 0
+ 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
+ 2.8.95~2430-0ubuntu5 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy libvirt-bin
libvirt-bin:
- Installed: 1.2.2-0ubuntu13.1.14
- Candidate: 1.2.2-0ubuntu13.1.14
- Version table:
- *** 1.2.2-0ubuntu13.1.14 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
- 100 /var/lib/dpkg/status
- 1.2.2-0ubuntu13.1.7 0
- 500 http://security.u buntu.com/ubuntu/ trusty-security/main amd64
Packages
- 1.2.2-0ubuntu13 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
-
+ Installed: 1.2.2-0ubuntu13.1.14
+ Candidate: 1.2.2-0ubuntu13.1.14
+ Version table:
+ *** 1.2.2-0ubuntu13.1.14 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
+ 100 /var/lib/dpkg/status
+ 1.2.2-0ubuntu13.1.7 0
+ 500
[Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
Upgraded to Kubuntu 15.04 and with that came nvidia 346.59 ( 346.59-0ubuntu1 ) $ uname -a Linux redacted 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --list | grep 346.59 ii libcuda1-346 346.59-0ubuntu1 amd64NVIDIA CUDA runtime library ii libxnvctrl0 346.59-0ubuntu1 amd64NV-CONTROL X extension (runtime library) ii nvidia-346346.59-0ubuntu1 amd64NVIDIA binary driver - version 346.59 ii nvidia-opencl-icd-346 346.59-0ubuntu1 amd64NVIDIA OpenCL ICD ii nvidia-settings 346.59-0ubuntu1 amd64Tool for configuring the NVIDIA graphics driver You can specify which GPU to use with the program nvidia-settings. Using: the GPU PRIME Profiles set for Intel (Power Saving Mode) which sets: $cat /proc/acpi/bbswitch :01:00.0 OFF After a few days of this setting I can report that the issue of the dimming screen and random lock-ups seems to have disappeared. I've just now run nvidia-settings to change back to use the GPU that's labeled NVIDIA (Performance Mode) and will update in later if this also no-longer has the issue. Tentatively reporting as fixed pending further testing . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1405489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
Christopher, I tried. Running the program from http://www.nvidia.com/Download/driverResults.aspx/82252/en-us as sudo ./NVIDIA-Linux-x86_64-346.47.run results in the following: nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Wed Mar 4 14:44:37 2015 installer version: 346.47 PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin nvidia-installer command line: ./nvidia-installer Using: nvidia-installer ncurses user interface - Detected 8 CPUs online; setting concurrency level to 8. WARNING: You do not appear to have an NVIDIA GPU supported by the 346.47 NVIDIA Linux graphics driver installed in this system. For further details, please see the appendix SUPPORTED NVIDIA GRAPHICS CHIPS in the README available on the Linux driver download page at www.nvidia.com. - I find the statement odd as my card is listed by lspci as $ lspci | grep -i nvid 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev ff) 01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev ff) which is on the list. It then asks me if I want to continue with the installation. Continue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1405489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645818] Re: Unknown keyword in configuration file: gfxboot
Just confirming that I created a USB boot device using Startup Disk Creator a few days ago using Ubuntu 14.04 for a 14.10 installation iso and got the same problem on booting a Lenovo Thinkpad X230 (i5 CPU) laptop. $ usb-creator-kde -v Qt: 4.8.6 KDE Development Platform: 4.13.3 Startup Disk Creator: 0.2.23 $ dpkg --list | grep usb-creator ii usb-creator-common 0.2.56.2 amd64create a startup disk using a CD or disc image (common files) ii usb-creator-kde 0.2.56.2amd64 create a startup disk using a CD or disc image (for KDE) Using the workaround of typing live at the boot: prompt got me to a graphical interface, but I didn't test more as the installation failed, for what I think was an unrelated issue. WORKAROUND: I created a 14.10 installation usb using a 14.10 computer and that worked on the laptop with no errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645818 Title: Unknown keyword in configuration file: gfxboot To manage notifications about this bug go to: https://bugs.launchpad.net/usb-creator/+bug/645818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
+ Did this not occur with a prior version of the NVIDIA proprietary drivers? Unknown. This is a fresh install. + Does this happen with nouveau? It did not. + Did this happen in a prior release? Unknown. This is a fresh install on a new machine but there is a bug opened for Ubuntu 14.04 on the same laptop model by someone else at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762?comments=all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
I have updated the BIOS. ( Asside: For any other ZBook users note that the directions at https://help.ubuntu.com/community/BIOSUpdate are incorrect as there is no README in the download from HP. Instead, on Boot press ESC to get into the BIOS setup and follow the instructions in the BIOS Upgrade section. ) After having upgraded the BIOS I changed NVIDIA back to the NVIDIA - Power mode $ cat /proc/acpi/bbswitch :01:00.0 ON And now can confirm that this issue still occurs. Changing to confirmed as per instructions and posting updated BIOS data. $ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date L70 Ver. 01.30 12/08/2014 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
As per comment #4 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405489] [NEW] [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
Public bug reported: As per Comment #31 on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762/comments/31 creating bug via ubuntu-bug linux. This issue is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762?comments=all but with Ubuntu 14.10 instead of 14.04 $ cat /proc/version_signature Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug nvidia utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310762] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up
Done: See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310762 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310762] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up
Also getting this with a zBook 15 and Ubuntu 14.10 Linux 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:37:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev ff) $ dpkg --list | grep nvidia ii nvidia-331 331.113-0ubuntu0.1 amd64NVIDIA binary driver - version 331.113 ii nvidia-331-uvm 331.113-0ubuntu0.1 amd64NVIDIA Unified Memory kernel module ii nvidia-opencl-icd-331 331.113-0ubuntu0.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.6.7 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64Tool for configuring the NVIDIA graphics driver Ctrl-alt-F1 , ctrl-alt-f7 workaround unlocks things. Tried changing /etc/default/grub to have GRUB_CMDLINE_LINUX_DEFAULT=quiet splash rcutree.rcu_idle_gp_delay=1 but it did not change the lockup. In kern.log get kernel: [ 6891.094246] ACPI Warning: \_SB_.PCI0.PEGP.DGFX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) If I run nvidia-settings and change PRIME profiles from NVIDIA (Performance Mode) to Intel (Power Saving Mode) then it stops the lock up May be related to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=763272 as I noticed that With PRIME profile as NVIDIA you get (the below number is from memory - but the ON I know was set ) $ cat /proc/acpi/bbswitch :01:00.0 ON and it can't be changed as per bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763272 Also with PRIME profile as Intel you get $ cat /proc/acpi/bbswitch :01:00.0 OFF ** Bug watch added: Debian Bug tracker #763272 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763272 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310762 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259423] Re: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Christopher M. Penalver, Thank you for your response. I believe I have already done what you asked when I ran the command ubuntu-bug xorg and uploaded the file here https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/+attachment/3926455/+files/apport.xorg.u992bm.apport as seen in comment #1 ( https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/comments/1 ) Let me know if I have mis-understood your comment. When running this command I can only do so in text mode ans so saved the file and attached it to this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259423 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069199] Re: 1002:682f Unity does not start after installing fglrx-updates Radeon HD 7700M Series
*** This bug is a duplicate of bug 1068404 *** https://bugs.launchpad.net/bugs/1068404 As Christopher M. Penalver requested, I filed a new bug report as bug #1259423 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069199 Title: 1002:682f Unity does not start after installing fglrx-updates Radeon HD 7700M Series To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1069199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259709] [NEW] Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Public bug reported: This is a duplicate of bug #1259423. It was created automatically as part of the would you like to report this problem question hopefully answering request https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/comments/2 ProblemType: Package DistroRelease: Ubuntu 13.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSBuildLog: DKMS make.log for fglrx-8.970 for kernel 3.11.0-14-generic (x86_64) Mon Dec 9 23:28:30 CST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.11.0-14-generic/build/include not found or incomplete file: /lib/modules/3.11.0-14-generic/build/include/linux/version.h DKMSKernelVersion: 3.11.0-14-generic Date: Mon Dec 9 23:28:34 2013 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3604] InstallationDate: Installed on 2013-02-18 (295 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8530w MarkForUpload: True PackageVersion: (not installed) PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UpgradeStatus: Upgraded to saucy on 2013-10-18 (53 days ago) dmi.bios.date: 12/08/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDV Ver. F.20 dmi.board.name: 30E7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.27 dmi.chassis.asset.tag: USH91201DK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.20:bd12/08/2011:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.20:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8530w dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Dec 10 15:34:26 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: radeon ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259709 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1259709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259423] Re: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Hi, I restored back to opensource drivers and on login it asked me to report a bug with fglrx. I did so and it created this bug #1259709 https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1259709 My apologies in advance, if this was done in error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259423 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259423] [NEW] Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Public bug reported: As requested by Christopher M. Penalver, opening a separate bug for this hardware configuration as a possible duplicate of Bug #1069199 Description: After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. Xserver logs indicate that the driver fglrx does not load. Reverting to the opensource version gets things working again E.g. To get back to things working I have to run $sudo dpkg --purge fglrx fglrx-amdcccle fglrx-dev sudo apt-get install xserver-xorg-video-ati xserver-xorg-video-radeon ProblemType: Bug ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: fglrx, 8.970: added XorgLog: [63.002] X.Org X Server 1.14.3 Release Date: 2013-09-12 [63.002] X Protocol Version 11, Revision 0 [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 [63.002] Build Date: 15 October 2013 09:23:37AM [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) ... [63.010] (II) LoadModule: fglrx [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.025] (II) UnloadModule: fglrx [63.025] (II) Unloading fglrx [63.025] (EE) Failed to load module fglrx (loader failed, 7) ... [63.025] (II) LoadModule: fglrx [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.040] (II) UnloadModule: fglrx [63.040] (II) Unloading fglrx [63.040] (EE) Failed to load module fglrx (loader failed, 7) ... xserver.errors: Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. GLX error: Can not get required symbols. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: display edid version 1.3 display manufacturer AUO display model 197b display serial no. 0 product id6523 size horizontal 331 mm size max horizontal33 cm size max vertical21 cm size vertical 207 mm vendor AUO xserver.version: 2:1.14.3-3ubuntu2 ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Attachment added: Apport Report https://bugs.launchpad.net/bugs/1259423/+attachment/3926455/+files/apport.xorg.u992bm.apport ** Summary changed: - Unity does not start after installing fglrx x64 drivers Mobility Radeon Mobile HD 3650 + Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259423 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1259423/+subscriptions -- ubuntu-bugs mailing list
[Bug 1259423] Re: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
** Description changed: As requested by Christopher M. Penalver, opening a separate bug for this hardware configuration as a possible duplicate of Bug #1069199 Description: - After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. + After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. Xserver logs indicate that the driver fglrx does not load. + + To duplicate: + 1) Download http://www2.ati.com/drivers/legacy/amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.zip + + Note: Catalyst 13.1 is the version AMD recommends for Mobility Radeon HD + 3650 + + 2) sudo sh ./amd-driver-installer-catalyst-13.1-legacy- + linux-x86.x86_64.run --buildpkg Ubuntu/saucy + + 3) sudo dpkg -i *.deb + + 4) reboot and then try to login + Reverting to the opensource version gets things working again E.g. To get back to things working I have to run $sudo dpkg --purge fglrx fglrx-amdcccle fglrx-dev sudo apt-get install xserver-xorg-video-ati xserver-xorg-video-radeon ProblemType: Bug ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: fglrx, 8.970: added XorgLog: - [63.002] - X.Org X Server 1.14.3 - Release Date: 2013-09-12 - [63.002] X Protocol Version 11, Revision 0 - [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu - [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 - [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 - [63.002] Build Date: 15 October 2013 09:23:37AM - [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) + [63.002] + X.Org X Server 1.14.3 + Release Date: 2013-09-12 + [63.002] X Protocol Version 11, Revision 0 + [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu + [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 + [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 + [63.002] Build Date: 15 October 2013 09:23:37AM + [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) ... - [63.010] (II) LoadModule: fglrx - [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so - [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn + [63.010] (II) LoadModule: fglrx + [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so + [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension - [63.025] (II) UnloadModule: fglrx - [63.025] (II) Unloading fglrx - [63.025] (EE) Failed to load module fglrx (loader failed, 7) + [63.025] (II) UnloadModule: fglrx + [63.025] (II) Unloading fglrx + [63.025] (EE) Failed to load module fglrx (loader failed, 7) ... - [63.025] (II) LoadModule: fglrx - [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so - [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn + [63.025] (II) LoadModule: fglrx + [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so + [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension - [63.040] (II) UnloadModule: fglrx - [63.040] (II) Unloading fglrx - [63.040] (EE) Failed to load module fglrx (loader failed, 7) +
[Bug 1069199] Re: 1002:682f Unity does not start after installing fglrx-updates Radeon HD 7700M Series
*** This bug is a duplicate of bug 1068404 *** https://bugs.launchpad.net/bugs/1068404 I think the duplicate status is wrong. I think this is NOT a duplicate of bug #1068404 because **this** bug has the error: [ 593.127] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra- modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg- tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension or in other words it can't load the fglrx driver while bug #1068404 does NOT have that issue. So to be clear - this bug relates to the module fglrx driver is NOT loading which results in X crashing. The other bug looks like it loads the module fglrx but X crashes for other reasons. Seems like a completely different root cause therefore should be a different bug. I am also affected by this bug #1069199 and am running DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 I downloaded and built sudo sh ./amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --buildpkg Ubuntu/saucy After doing the install and rebooting I get EXACTLY the same results and have the same error messages as the original bug reporter for this bug when I install the fglrx proprietary drivers. I was hoping to load the AMD drivers because I wanted to get sound out of the HDMI port. I'm running with the following hardware on an HP 8530w. The opensource versions run perfectly for video with both the VGA and HDMI ports, but I can't get sound out of the HDMI port too and read that the only solution is to upgrade to the proprietary fglrx drivers. $ lspci | grep -i Radeon 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV635 HDMI Audio [Radeon HD 3600 Series] Symptons: 1) lightdm prompt appears 2) Login succeeds 3) screen goes blank and then login screen appears again. The following (I think relevant) error messages appear in Xorg.0.log and mark this as different than the other bug. [ 699.570] (II) LoadModule: fglrx [ 699.570] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so [ 699.585] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [ 699.585] (II) UnloadModule: fglrx [ 699.585] (II) Unloading fglrx [ 699.585] (EE) Failed to load module fglrx (loader failed, 7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069199 Title: 1002:682f Unity does not start after installing fglrx-updates Radeon HD 7700M Series To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1069199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974374] Re: Error on unmounting a NFSv4 share
Just got hit by the same thing and completely unrelated to comment #4. We had this with fully formed paths (with slashes) and an NFS server that went away suddenly. Trying unmount with -f , -l and those two flags in combination did not solve the issue. When I tried the suggestion in #7 I found it only has the effect of removing the line describeing the mount in /etc/mtab but not in /proc/mounts or actually doing an umount. This is why, I think, the poster gets the hang in his next comment (#8) as the mount is not actually unmounted, just no longer tracked in /etc/mtab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974374 Title: Error on unmounting a NFSv4 share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/974374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974374] Re: Error on unmounting a NFSv4 share
Forgot to inlcude uname -a: 3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:18:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux This is also tracked here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711183 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711184 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711187 ** Bug watch added: Debian Bug tracker #711183 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711183 ** Bug watch added: Debian Bug tracker #711184 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711184 ** Bug watch added: Debian Bug tracker #711187 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711187 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974374 Title: Error on unmounting a NFSv4 share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/974374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097096] Re: can't scan more after scan all from document feeder
I can confirm that this fixed the issue for me. Seems like the application is faster too. Nice work. Now running: simple-scan 3.4.3-0ubuntu1. Still running Ubuntu 12.04 LTS. I do not see where I can change the tag from from verification-needed to verification-done. Perhaps I do not have rights to add/change tags on launchpad.net? But I can confirm that it fixed the issue on my system. ** Tags added: verification-done ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1097096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097096] Re: can't scan more after scan all from document feeder
I think I found how to change the tag from from verification-needed to verification-done and did so. If I did it in error - my apologies in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1097096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097096] Re: can't scan more after scan all from document feeder
Just to note: the version I'm now running is simple-scan 3.4.1-0ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1097096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097096] Re: can't scan more after scan all from document feeder
After some apt-get upgrade to Ubuntu 12.04-LTS I now get this exact same problem with a Brother MFC-8660DN. I don't know which upgrade caused the problem or when it started, but with the original Ubuntu 12.04-LTS I was able to make multiple runs. It never had this problem before. I have to quit from simple scan and restart in order to scan more pages. The last lines of simple-scan.log are: [+53.78s] DEBUG: scanner.vala:818: sane_get_option_descriptor (12) [+53.78s] DEBUG: scanner.vala:480: sane_control_option (4, SANE_ACTION_SET_VALUE, Automatic Document Feeder) - (SANE_STATUS_GOOD, Automatic Document Feeder) [+53.78s] DEBUG: scanner.vala:480: sane_control_option (2, SANE_ACTION_SET_VALUE, True Gray) - (SANE_STATUS_GOOD, True Gray) [+53.78s] DEBUG: scanner.vala:422: sane_control_option (3, SANE_ACTION_SET_VALUE, 150) - (SANE_STATUS_GOOD, 150) [+53.78s] DEBUG: scanner.vala:462: sane_control_option (10, SANE_ACTION_SET_VALUE, 215.84) - (SANE_STATUS_GOOD, 215.880234) [+53.78s] DEBUG: scanner.vala:462: sane_control_option (11, SANE_ACTION_SET_VALUE, 355.51) - (SANE_STATUS_GOOD, 355.567444) [+53.78s] DEBUG: scanner.vala:1124: sane_start (page=0, pass=0) - SANE_STATUS_NO_DOCS As you can see the last line says SANE_STATUS_NO_DOCS so it's saying that there are no documents even though there are. Quitting and restarting simple-scan allows you to use the scanner again, but this defeats the goal of being able to scan several times (e.g. front and back of pages) and combining them into one saved document. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1097096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
